(old)Puppy Linux Discussion Forum

Wow, the parser is really nice. It builds a Fluxbox menu in 20 milli-seconds

It stuffs everything in one menu category and no icons except those which have a full path (known Fluxbox limitation, arghhhh). Now I'm going to write a wrapper which takes all menu entries and puts the full path to their icon. Should work well.

Iguleder. Include symlink from /usr/sbin/gtkdialog3 to /usr/sbin/gtkdialog. For example 8-bit great new system-info pet depends on that. And Barry also symlinks it when he compiles Thunors new versions.
Also symlink from yad to zenity could be reasonable or checking mechanism if it is already included. See Barrys latest posts.

pemasu wrote: Thunors
from yad to zenity

This begins to sound like a sci-fi story ...

Iguleder. Regarding non working radeon driver. Stu90 has compared the Xorg packages and found that libdrm_radeon is missing. Including it should fix the radeon driver problem.

The package is: libdrm-radeon1_2.4.21-1~squeeze3_i386.deb

Fixed specs row here:

pemasu wrote:Iguleder. Regarding non working radeon driver. Stu90 has compared the Xorg packages and found that libdrm_radeon is missing. Including it should fix the radeon driver problem.

The package is: libdrm-radeon1_2.4.21-1~squeeze3_i386.deb

Hi Pemasu,
Yes this is the missing lib for radeon - put it in the .deb folder and rebuild the xorg_base package - there is also missing libdrm_nouveau (libdrm_nouveau 1_2.4.21-1~squeeze3_i386.deb) but i wasn''t sure if i read some where this that this should be included or not? so i never included it.

another thing if you look in /xorg_base/usr/lib/dri it seems not all of libglu1-mesa_7.7.1-4_i386.deb is has been copied - as it is a 14mb .deb i also did not include this.

Stu90. Great finding. The problem is Barrys woof/packages-templates xorg_base folder. Inside it in /usr/lib/dri is flag NOEXCEPTIONFILES and swrast_dri.so. That folder probably needs other dri templates also.

So...Xorg_High has been crippled and xorg_base needs another template to be processed properly.
Really great finding. I wonder what other packages are processed only partly.

Yep. Changing the flag to PLUSEXTRAFILES enables libgl1-mesa-dri processing properly when you execute xorg_base processing.

Stu90. Could you go through all the packages and check if they are processed properly. There is only 400 - 700 packages to compare depending of how lite you create, lol.

Cups and ghostscript templates were the other which needed some extra fixing if I remember right. Xserver_xorg need checking also.

Just joking, but you have done really good work with your research.

xcb is certainly one pemasu. I made my own template for spup.

pemasu wrote:Stu90. Great finding. The problem is Barrys woof/packages-templates xorg_base folder. Inside it in /usr/lib/dri is flag NOEXCEPTIONFILES and swrast_dri.so. That folder probably needs other dri templates also.

So...Xorg_High has been crippled and xorg_base needs another template to be processed properly.
Really great finding. I wonder what other packages are processed only partly.

Yep. Changing the flag to PLUSEXTRAFILES enables libgl1-mesa-dri processing properly when you execute xorg_base processing.

Good discovery Pemasu - i wonder if this has been done because libgl1-mesa is a fairly large package - things seem to work ok in the current state but of course you don't get the accelerated graphics - libgl1-mesa and mesa-utils could always be downloaded separately as a .pet to keep .iso download size down?

It took me 5 build to figure out one missing lib - i think it may take me years if i was to try and go through 700 packages

cheers.

Libdrm_radeon is needed for usually working radeon driver. But libdrm_nouveau is AFAIK for nouveau kernel module usage only. And nouveau kernel module by just existing prevents proprietary nvidia driver to be loaded. It reservers stuff for itselt just by existing. Really nasty module.
I have removed nouveau module from my kernel.
So....leaving that libdrm_nouveau out does not harm many.
There are some people who can use nouveau, but for them the nvidia proprietary driver works also.

Ummm ... still having trouble uploading my kernel package. This is very bad.

I started working on a truly barebones flavor, it has about 270 packages instead of the ~410 alpha 2 had. Gonna start from scratch and add only the truly basic stuff - I aim at the most lightweight desktop possible this time

Spent the weekend trying out Squeeze. It
took some time to get used to the interface.
I finally discovered that one can press the
'menu' key and use the arrow keys to
launch an application. That would be good
method for a netbook user.

I made a right click package that is great for
this version.

Just one click and it installs easily!

I added a few apps. In particular xdelta3
and dir2sfs
psnapshot for screenshots
pcd for cd playing

Also I included Lame 3.9.8 and wav2mp3
to convert wav files

Got back home, finally.

The Fluxbox build is underway. I'm downloading the latest Woof at the moment and I hope I'll be able to build a PupFlux-like Puppy based on dpup.

I also want to improve my Fluxbox menu generator tomorrow, I have a plan and I'm gonna get things working.

Good news, since pemasu and stu90 work on such good puplets I can focus on the base.

I decided to revive the famous "lts" kernel series I worked on until it failed hard at 2.6.32.43 due to incompatible patches. This time the kernel is much more vanilla and has just BFS.

It should boot much faster, especially from USB.

EDIT: same problem with 44, so this plan is canceled. However, today I was able to fix two critical bugs in Woof to make it work; now I'm building a truly barebones dpup with Window Maker, 4 extremely useful dock apps and no desktop icons. It has no browser and no applications at all, except a terminal emulator.

This thingy also has kernel 2.6.39.4 and some minor fixes. The main problem is (of course, as always!) the menu - Puppy's non-standard menu makes things problematic. Window Maker's built-in menu generator generates a very partial menu and that's something I don't like.

The reason I gave up on Fluxbox is the fact it offers less features than comparable window managers (e.g Window Manager, FVWM2, E16, ...) and has a very limited support for dock apps. In contrary, Window Manager is the #1 window manager for dock apps IMHO and doesn't require any third-party panel or configuration utilities; it's very complete and provides a full desktop.

Iguleder wrote:I'm building a truly barebones dpup with Window Maker, 4 extremely useful dock apps and no desktop icons. It has no browser and no applications at all, except a terminal emulator.

This thingy also has kernel 2.6.39.4 and some minor fixes. The main problem is (of course, as always!) the menu - Puppy's non-standard menu makes things problematic. Window Maker's built-in menu generator generates a very partial menu and that's something I don't like.

In contrary, Window Manager is the #1 window manager for dock apps IMHO and doesn't require any third-party panel or configuration utilities; it's very complete and provides a full desktop.

As long as you don't call it !puppywind

A link when your ready please, as you will be aware by now, I do like minimal systems.

scsijon wrote: A link when your ready please, as you will be aware by now, I do like minimal systems.

Chomping at the bit here as well.

So long as it plays nicely with our netbooks and notebooks (esp. the netbook keyboards, the assorted video cards, and the wifi nics), CUPS is stable and works with HP printers (in our case a LaserJet P1006 and a Deskjet 1000 J110, and a real bonus would be also a officejet 4215), and the browser and E-mail alternatives are diverse (is Dillo dead or too dependency-bound?).

Waiting ... patiently ... OK, maybe not real patiently ... even for something to break ...

I did a very nice trick last night, I opened two consoles, one with a silent Woof I hacked so it doesn't always ask questions (i.e my choice is hardcoded) and the other with "sleep $((60*60*3)); wmpoweroff" (which means it sleeps for 3 hours and shuts down).

The former processed all the packages and the latter is used to power off my computer in case something goes wrong and Woof shows some prompt that I forgot to automate

It worked great, all the packages are processed now. At the moment I'm building a small set of packages that will be used for my next build; I also want to give it another name, I was thinking of "NextPuppy". You still don't know why, but once you'll see what runs on top of it ... you'll get it

I also want to give it a new repository, because its packages are also compatible with 5.x. I think the name that makes most sense is "Packages-puppy-next-official"

Oh, and regarding artwork - at the moment everything is original. The window manager is pretty spartan and I also found a matching GTK theme and a matching terminal emulator, which pretty much provide a uniform desktop experience.

It's very lightweight, I also replaced ROX-Filer with emelFM2, for two reasons: although ROX is lighter, the use of multiple ROX windows for simple tasks wastes screen real estate and RAM, while the latter allows you to do many tasks using one file manager window. Also, I want to disable the pinboard; I can do this by modifying scripts, but if you only disable the code that starts it (~/.xinitrc), the desktop icon switcher will start it once you change the icon theme and that's bad. I can't fix all applications that start the pinboard, because that's not future-proof.

There are many rough edges, but this is the first build ... so I'm still allowed to do those wild experiments

Two missing libraries and broken Xorg_High, but RAM usage was 39 MB.

Doing another build with today's Woof, this time these issues will be fixed and Dash will be the default shell, if it works well enough. Should be another RAM saver.

I might upload this one if it's any good

EDIT: uploaded the packages, the sources and the Woof files to here.

specs.tar.xz, what is the way to unpack these tar.xz files. Normal xarchiver does not uncrompress, I would like to have right click for it also but I am at loss how to handle them. There isnt mime type for these tar.xz files. I wonder if they are in the /usr/share/mime/globs file for mime handling.