(old)Puppy Linux Discussion Forum

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.

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.

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...

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.

technosaurus wrote: Speaking of udev, it has grown into a behemoth, and the things it does _can_ be simple.

technosaurus wrote: I'll probably try to patch toybox's mdev instead.

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?

PANZERKOPF wrote: Attached tarball contains this script and
busybox configuration file.

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.

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

greengeek wrote: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 wrote:

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)

find /sys/devices -name uevent | xargs grep -h MODALIAS 2>/dev/null |cut -d = -f 2 

#!/bin/sh

#is there really a reason to try twice?
for ONEBUS in /sys/bus/* /sys/bus/*; do
    for ONEDEVICE in ${ONEBUS}/devices/*; do
	[ -r ${ONEDEVICE}/uevent ] || continue
	while read ONEUEVENTSTR; do
	    case $ONEUEVENTSTR in
		MODALIAS=*)
		    echo ${ONEUEVENTSTR#MODALIAS=} 2>/dev/null
		;;
		*)
		    continue
		;;
	    esac
	done < ${ONEDEVICE}/uevent
    done
done

grep -h MODALIAS /sys/bus/*/devices/*/uevent 2>/dev/null |cut -d = -f 2

find /sys -name uevent -exec echo add > {} \;

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?

Btw. diethotplug is an other close to udevd replacement.

Ibidem wrote: But udev/eudev provide one thing the other solutions don't: they can enumerate devices, which is what Xorg wants them for.