Re: [leaf-devel] cdrom module support loading from leaf.cfg
Etienne Charlier wrote: panic after linuxrc It seems that the /dev/cdrom computation done in /var/lib/lrpkg/root.blk.mk is done too early ( before leaf.cfg parsing) the packages cannot be loaded from /dev/cdrom After discussion with Eric Spakman, it seems that the /dev/cdrom computation could be moved to root.dev.mk that's executed after leaf.cfg parsing Charles ?? any clever idea ??? I don't think there would be any serious side effects of moving the /dev/cdrom symlink creation from before to after the leaf.cfg file is processed, although it would need to be tested. In general, the /dev/cddrom link is used to load packages, not configuration data, so it's absence when leaf.cfg runs shouldn't be too much of a hardship (ie: the likelyhood of setting LEAFCFG=/dev/cdrom is pretty low, although not completely unthinkable). Another option (that would work without any other modifications) would be to create the symlink in your leaf.cfg file, or change to the actual CD device (ie: /dev/hda or whatever) in your PKGPATH setting. I suppose another option would be to leave the current cdrom symlink generation in root.blk.mk alone, *AND* add symlink generation after processing leaf.cfg if /dev/cdrom doesn't already exist. I don't much care one way or another...if the Bering folks think the symlink generation code should move (or be duplicated), it's easy to do. If not, you have a work-around by adding a line or two of code to your leaf.cfg file...since you're manually bringing up devices in leaf.cfg, it doesn't seem too out of place to require you to build any symlinks, device entries, etc. that are required to access the newly functional device(s) in the same leaf.cfg script you used to insmod the modules. -- Charles Steinkuehler [EMAIL PROTECTED] --- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] cdrom module support loading from leaf.cfg
Hi, I'm testing bering-uclibc 2.2 beta 4 The new leaf.cfg is really great ! But I tried to load the modules for ide-cdrom support ( cdrom.o , ide-*.o, isofs...) from the config floppy ( to be able to use the standard initrd.lrp) ( I was testing a kernel that crashed with the modules in initrd-ide.lrp ) So Here is my leaf.cfg - # This file is parsed as a shell script # Kernel command line parameters are available as KCMD_ # ie: KCMD_LRP contains the LRP= portion of the kernel command line # NOTE: For kernel command line settings that do not include an equals # sign (ie: rw or similar), the variable is set to itself, allowing # for easy testing (ie: KCMD_rw=rw). # LRP and PKGPATH variables now support whitespace (space, tab, newline) # as well as commas for seperators. # Uncomment for more verbose execution. VERBOSE=1 # Other variables you might want to set in this file include: # LRP Packages to load # PKGPATH Device(s) to load packages from # syst_size Size of root ramdisk # tmp_size Size of /tmp ramdisk # log_size Size of /var/log ramdisk # Example: #LRP="$KCMD_LRP rsync" #LRP="root hdsupp libm iptables keyboard p9100 upnp config etc local modules dnsmasq ppp pppoe dropbear weblet shorwall ulogd ezipupd squid-2" LRP="root wireless wireutil libm ulogd iptables keyboard config etc local modules uhotplug dnsmasq ppp pppoe weblet shorwall" PKGPATH="/dev/fd0u1440:msdos,/dev/cdrom:iso9660" syst_size=32M log_size=4M tmp_size=4M insmod $MNT/cdrom.o insmod $MNT/ide-cor.o insmod $MNT/ide-cd.o insmod $MNT/ide-dsk.o insmod $MNT/ide-det.o insmod $MNT/isofs.o insmod $MNT/vfat.o -- but it didn't worked ;-( panic after linuxrc It seems that the /dev/cdrom computation done in /var/lib/lrpkg/root.blk.mk is done too early ( before leaf.cfg parsing) the packages cannot be loaded from /dev/cdrom After discussion with Eric Spakman, it seems that the /dev/cdrom computation could be moved to root.dev.mk that's executed after leaf.cfg parsing Charles ?? any clever idea ??? Kind regards, Etienne Charlier --- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
