pUPnGO 2012

A home for all kinds of Puppy related projects
Message
Author
goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#196 Post by goingnuts »

greengeek:The h.pcf.gz origins from xwoaf and although a run of "mkfontdir" reveals only "h.pcf.gz -*-helvetica-*-r-*--13-130-*-*-*-*-*-*" the original xwoaf fonts.dir says:
h.pcf.gz -adobe-courier-medium-o-normal--12-*-*-*-*-*-*-*
h.pcf.gz -adobe-courier-medium-r-normal--12-120-75-75-m-70-iso8859-1
h.pcf.gz -*-times-medium-i-normal-*-14-*-*-*-*-*-*-*
h.pcf.gz -*-courier-medium-r-normal-*-14-*-*-*-*-*-*-*
h.pcf.gz -*-courier-bold-r-normal-*-14-*-*-*-*-*-*-*
h.pcf.gz -*-courier-medium-o-normal-*-14-*-*-*-*-*-*-*
h.pcf.gz -*-courier-medium-r-normal-*-12-*-*-*-*-*-*-*
h.pcf.gz -*-helvetica-bold-*-*--12-*-*-*-*-*-*-*
h.pcf.gz -*-helvetica-*-12*
I do not know how it was made so just used it. From time to time I try to get hold of the fonts in pupngo but I never really got a understanding of it...
Try to copy all original P412 fonts in there, remove the h.pcf.gz and see whats happening. You might also need to change the content of /etc/fonts...
The pupngo2012 has the gtkfonsel program but when choosing some of the present fonts it crashes.
Thats more or less what I can come up with...

Ibidem
Posts: 549
Joined: Wed 26 May 2010, 03:31
Location: State of Jefferson

#197 Post by Ibidem »

goingnuts wrote:I have been revisiting the build of busybox as the question arise if the umount of loop devises could auto delete the used /dev/loop. This remains unsorted but another thing popped up that I will report for future reference. I have used the same busybox source for pupngo through all the versions and the last rebuild was in June 2012. Since then I have changed my uclibc toolchain but the new builds of busybox uses the same source and the same .config file...

But now I have a problem with the xterm-wrapper script which wont launch rxvt. The original part that fail is

Code: Select all

exec rxvt "${@}"
This make rxvt error out with rxvt: unknown "" or something like that...
By replacing the line with

Code: Select all

#exec rxvt ${@}
rxvt is happy again...but thats not how the shell should pass variables.
So upgraded/rebuild gcc/uclib/kernel headers but no change.
To make this a bit short the reason was sed (GNU version 4.1.2 - it is too old to build BB-20100217 correctly). Replacing sed with BB-sed from the version I was building solved this misbehavior...
Hmm...don't get why that makes a difference.
Also, using "" for an argument is valid, so I don't see why "$EMPTYVAR" should be different, though I might be misunderstanding the issue.
"$MULTIWORD_VAR" is treated as a single argument, also.

FYI: Busybox 1.20.2 has a much more capable sed.

goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#198 Post by goingnuts »

Ibidem wrote:..
Hmm...don't get why that makes a difference.
Also, using "" for an argument is valid, so I don't see why "$EMPTYVAR" should be different, though I might be misunderstanding the issue.
"$MULTIWORD_VAR" is treated as a single argument, also.

FYI: Busybox 1.20.2 has a much more capable sed.
Hmm...tried to reproduce...seems not to be sed...seems to be the parsing of CFLAGS to already configured BB...strange...
I configure BB with

Code: Select all

CONFIG_EXTRA_CFLAGS="-static -Os -mtune=i386"
If I run just "make" the BB-binary seems ok...
If I run

Code: Select all

make CC="$CC_GLOBAL" CFLAGS="$CFLAGS_GLOBAL" LDFLAGS="$LDFLAGS_GLOBAL"
the binary is not ok and gives the errors described above with

Code: Select all

exec rxvt "${@}"
even if CFLAGS=""...I do not get it!

If compiling busybox-1.20.2 the error does not occour...so considering upgrade to busybox-1.20.2 in future pupngo´s but who knows what will break then...initial test shows different behavior of wc...pmfree reports wrong free space etc.

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#199 Post by greengeek »

Does puppy HAVE to have busybox? What would happen to Puppy if it used a full command set?

Ibidem
Posts: 549
Joined: Wed 26 May 2010, 03:31
Location: State of Jefferson

#200 Post by Ibidem »

greengeek wrote:Does puppy HAVE to have busybox? What would happen to Puppy if it used a full command set?
Can you spell B-L-O-A-T?

To elaborate, I can build a ~700k static busybox that provides everything needed to boot (I have run this as an OS). This equates to:
coreutils:12 MB
bash: 800k
dhcpcd (127 k) or dhclient 643 k
net-tools: 927k
module-init-tools: 340k
netcat: 192 k
sysklogd: 200 k
iputils-ping: 131 k
netbase: 98 k
sed: 52 k
awk: 322 k
util-linux: 2 MB
e2fs-progs: 2 MB
wget: 2 MB
bzip2: 156 k
...
ie, at least 20 MB.
Also you get slower startup, more RAM used, etc.

goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#201 Post by goingnuts »

No doubt busybox is needed. We could get through without it using ams-utils or the "multical call binary-technique" (mcb) of original apps...but BB delivers most of what is needed out of the box. Would be nice if they delivered some overview of which version is the most stable and content of apps between versions.
Also a "long term maintenance" version of BB could be nice. Upgrading BB (like upgrading other software) has the potential of breaking your existing scripts - so every script needs to be verified that it does what it is meant to do. On the other hand the new versions might offer apps that eliminate use of org apps and by then potentially reduce complexity and size.

User avatar
technosaurus
Posts: 4853
Joined: Mon 19 May 2008, 01:24
Location: Blue Springs, MO
Contact:

#202 Post by technosaurus »

Ibidem wrote:
greengeek wrote:Does puppy HAVE to have busybox? What would happen to Puppy if it used a full command set?
Can you spell B-L-O-A-T?

To elaborate, I can build a ~700k static busybox that provides everything needed to boot (I have run this as an OS). This equates to:
coreutils:12 MB
bash: 800k
dhcpcd (127 k) or dhclient 643 k
net-tools: 927k
module-init-tools: 340k
netcat: 192 k
sysklogd: 200 k
iputils-ping: 131 k
netbase: 98 k
sed: 52 k
awk: 322 k
util-linux: 2 MB
e2fs-progs: 2 MB
wget: 2 MB
bzip2: 156 k
...
ie, at least 20 MB.
Also you get slower startup, more RAM used, etc.
I wrote a small c init that will boot into X with jwm that compiles to a few kb. It wouldn't be that much more to add more of the boot process in parallel if anyone is interested. Tinycore has a patch to allow the initrd to be swappable (the initramfs I was using isn't) as well as a couple of other kernel patches that will speed up booting. Basically all you need for the desktop is xvesa/xfbdev, jwm, rxvt and a shell, but I never made them into a threadsafe mcb, so they can just as well be separate static builds.

over 90% of the boot process that happens before x can be in parallel.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].

amigo
Posts: 2629
Joined: Mon 02 Apr 2007, 06:52

#203 Post by amigo »

"Does puppy HAVE to have busybox?" Yes, Puppy probably does. No one else should have to suffer a complete system loaded with cut-down versions of everything. Yeah, there's a big size difference, but I like using the same toys that the BIG boys use... LOL

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#204 Post by greengeek »

technosaurus wrote:I wrote a small c init that will boot into X with jwm that compiles to a few kb. It wouldn't be that much more to add more of the boot process in parallel if anyone is interested. Tinycore has a patch to allow the initrd to be swappable (the initramfs I was using isn't) as well as a couple of other kernel patches that will speed up booting. Basically all you need for the desktop is xvesa/xfbdev, jwm, rxvt and a shell, but I never made them into a threadsafe mcb, so they can just as well be separate static builds.
This sounds rather interesting. I fear it will take me a long time to get to grips with all the things I don't understand about the boot process and componentry, but the more I look at the simpler stuff, the more I am learning.

User avatar
technosaurus
Posts: 4853
Joined: Mon 19 May 2008, 01:24
Location: Blue Springs, MO
Contact:

#205 Post by technosaurus »

to start X all that needs to happen is to mount /dev
to get a terminal emulator working, you also need to mount /dev/pts
and some (non-crucial) apps will need /sys and /proc mounted
this is one line of C each

While X is starting up you can load additional kernel modules, mount file systems, do checks, set settings etc... from kernel boot parameters (boot parameters should be the way most settings are stored so that you don't have to mount a file system to get them, but no-one else does it that way)

Once X and the wm are up, a terminal or gui setup wizard can be used for the rest (and jwm has a convenient startup tag... also restart and shutdown, but that is another topic)
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#206 Post by greengeek »

technosaurus wrote:to start X all that needs to happen is to mount /dev
to get a terminal emulator working, you also need to mount /dev/pts
and some (non-crucial) apps will need /sys and /proc mounted
... you can load additional kernel modules, mount file systems, do checks, set settings etc... from kernel boot parameters
Once X and the wm are up, a terminal or gui setup wizard can be used for the rest (and jwm has a convenient startup tag...
I used the phrase "simpler stuff" but what I really meant was "more minimalistic stuff". Each time I read your posts I realise that the minimalistic stuff is way harder than the bigger stuff (like booting a fullblown puppy from CD...that I can do!) :-)

Understanding all this grassroots stuff about booting with the minimum required code is like getting to the moon on a bicycle. Enticing yet very difficult for the untrained :-)

Thank God for google!

User avatar
technosaurus
Posts: 4853
Joined: Mon 19 May 2008, 01:24
Location: Blue Springs, MO
Contact:

#207 Post by technosaurus »

The only reason it is complex is because we made it that way over time. For example puppy's init has tons of bloat dealing with finding the correct partitions, sfs and save file when it could just be added as a parameter to the kernel command line (same goes for kb, resolution, drivers to load, language and many others). Perhaps early bootloaders lacked this functionality and this is a holdover that exists because things still work? I don't know, but I literally spent days turning on and off kernel options to boil it down to the salts and then did the same with init. Once I realized how little was actually needed, it just made sense to write it in c since it was basically:

Mount /dev and /dev/pts
Fork and exec X
Set some basic env variables normally found in /etc/profile and DISPLAY
Fork and exec the wm
(Logic to reboot/shutdown/restartx)
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].

Ibidem
Posts: 549
Joined: Wed 26 May 2010, 03:31
Location: State of Jefferson

#208 Post by Ibidem »

If you use Xorg or xfbdev, you'll need to load modules first.
And an autoconfigured X requires udev or hal. But then, most people use udev for /dev and loading modules.

User avatar
technosaurus
Posts: 4853
Joined: Mon 19 May 2008, 01:24
Location: Blue Springs, MO
Contact:

#209 Post by technosaurus »

Ibidem wrote:If you use Xorg or xfbdev, you'll need to load modules first.
And an autoconfigured X requires udev or hal. But then, most people use udev for /dev and loading modules.
there _is_ a builltin option, IMHO everything needed by init _should_ be built-in unless there is some conflict (but in that case I would just have a separate version for the broken device)

Speaking of loading modules, there is a recent kernel patch to load modules by filename (previously they had to be memmapped) that would make my flat module method much easier in c (by flat I mean all modules in 1 dir). Even with standard tools it was faster this way because it didn't need to recurse into subdirs. I know this doesn't sound like much, but loading a single module previously required several lines of code, much of which was unnecessarily complex.

Speaking of udev, it has grown into a behemoth, and the things it does _can_ be simple. I'll probably try to patch toybox's mdev instead.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].

PANZERKOPF
Posts: 282
Joined: Wed 16 Dec 2009, 21:38
Location: Earth

#210 Post by PANZERKOPF »

technosaurus wrote: Speaking of udev, it has grown into a behemoth, and the things it does _can_ be simple.
Agree.
technosaurus wrote: I'll probably try to patch toybox's mdev instead.
Busybox already has mdev, it can be used as simple udev replacement.
I made some scripts and mdev.conf file (Idea was borrowed from Alpine linux).
One problem was discovered there: It does not create device node for parallel port (LPT), althought all needed drivers was successfully loaded (parport, parport_pc).
Attachments
mdev.tar.gz
(1.59 KiB) Downloaded 307 times
SUUM CUIQUE.

goingnuts
Posts: 932
Joined: Sun 07 Dec 2008, 13:33
Contact:

#211 Post by goingnuts »

PANZERKOPF: Never got mdev working...tried you scripts (deactivated udevd in init), run rc.mdev afterlogin. Had to add groups disk, uucp, cdrom and video. Then only minor warnings running mdev -s or rc.mdev.
But no drivers loaded afterwards...
When to launch rc.mdev? Do you need additional scripts/setup?

Btw. diethotplug is an other close to udevd replacement.

PANZERKOPF
Posts: 282
Joined: Wed 16 Dec 2009, 21:38
Location: Earth

#212 Post by PANZERKOPF »

goingnuts wrote:PANZERKOPF: Never got mdev working...tried you scripts (deactivated udevd in init), run rc.mdev afterlogin. Had to add groups disk, uucp, cdrom and video. Then only minor warnings running mdev -s or rc.mdev.
But no drivers loaded afterwards...
When to launch rc.mdev? Do you need additional scripts/setup?
Weird....
Usually mdev must be launched after mounting sysfs and proc.
Maybe Your busybox has different configuration?
Above code is a part of my system initscript. Attached tarball contains this script and
busybox configuration file.
Attachments
sysinit.tar.gz
(3.6 KiB) Downloaded 380 times
SUUM CUIQUE.

Ibidem
Posts: 549
Joined: Wed 26 May 2010, 03:31
Location: State of Jefferson

#213 Post by Ibidem »

Looking at the mdev scripts, I see a couple things...
1. mdev.conf is missing this section (from examples/mdev_fat.conf in the busybox source):

Code: Select all

# Syntax:
# [-]devicename_regex user:group mode [>|=path] [@|$|*cmd args...]
#
# =: move, >: move and create a symlink
# @|$|*: run $cmd on delete, @cmd on create, *cmd on both

# support module loading on hotplug
$MODALIAS=.*	root:root 660 @modprobe "$MODALIAS"
This is what handles hotplug module loading, which is important.

2. Most of the mknod stuff is unneeded with a proper mdev.conf.
I know /dev/{console,full,null,zero,urandom,random} are automatically created, even with mdev.conf absent.

3. sysctl -w kernel.hotplug=/sbin/mdev allows use wthout mounting /proc

4. Alpine uses/used something like:

Code: Select all

find /sys -name modalias |xargs sort -u |xargs modprobe -a -b
to load modules for devices that aren't hotplugged. This should really speed things up.
And to coldplug USB devices, you may need this:

Code: Select all

	# mdev -s will not create /dev/usb[1-9] devices with recent kernels
	# so we trigger hotplug events for usb for now
	for i in $(find /sys/devices -name 'usb[0-9]*'); do
		[ -e $i/uevent ] && echo add > $i/uevent
	done

Alpine's stuff is at:
http://git.alpinelinux.org/cgit/aports/ ... nitscripts

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#214 Post by greengeek »

PANZERKOPF wrote: Attached tarball contains this script and
busybox configuration file.
The rc.shutdown is very much simpler than some of the puppy shutdown scripts I have been looking at recently. Where would you use this? Is it taken from another distro or would it work in a cutdown puppy?

PANZERKOPF
Posts: 282
Joined: Wed 16 Dec 2009, 21:38
Location: Earth

#215 Post by PANZERKOPF »

Ibidem wrote:Looking at the mdev scripts, I see a couple things...
1. mdev.conf is missing this section (from examples/mdev_fat.conf in the busybox source):

Code: Select all

# Syntax:
# [-]devicename_regex user:group mode [>|=path] [@|$|*cmd args...]
#
# =: move, >: move and create a symlink
# @|$|*: run $cmd on delete, @cmd on create, *cmd on both

# support module loading on hotplug
$MODALIAS=.*	root:root 660 @modprobe "$MODALIAS"
This is what handles hotplug module loading, which is important.
We can use above trick as well as making script for particular event (see /lib/mdev/usbdev for example).
Ibidem wrote: 4. Alpine uses/used something like:

Code: Select all

find /sys -name modalias |xargs sort -u |xargs modprobe -a -b
to load modules for devices that aren't hotplugged. This should really speed things up.
And to coldplug USB devices, you may need this:

Code: Select all

	# mdev -s will not create /dev/usb[1-9] devices with recent kernels
	# so we trigger hotplug events for usb for now
	for i in $(find /sys/devices -name 'usb[0-9]*'); do
		[ -e $i/uevent ] && echo add > $i/uevent
	done

I learned Alpine scripts before making my one. That script unfortunately cannot detect
all devices plugged in my test boxes (like Broadcom wireless card).
Some devices hasnt modalias file in /sys directory but has uevent with modalias string inside.
Also, my version based on "pure shell", no grep, find, xargs etc. That is not important but
should be faster (IMHO) :)
SUUM CUIQUE.

Post Reply