Re: [leaf-devel] Leaf.cfg
Erich Titl wrote: Hi Charles another little problem showed up using the bash package, apparently bash is included in initdr.lrp (or at least in initrd.list) this prevents bash being backed up using lrcfg. Problem summary: - initrd.lrp includes /bin/bash (symlink to ash) - installing 'real' bash.lrp means multiple packages list /bin/bash in their package.list files, so bash never gets backed up. There's not a perfect solution to this problem, as it is impossible in the current packaging system to include the same file in more than one package. Options for work-arounds include: 1) Remove /bin/bash from initrd.lrp, creating the symlink 'on the fly' as part of the init scripts. This moves the problem to root.lrp (which will try to backup the /bin/bash symlink...if /bin/bash is added to root.exclude.list, we're back to where we started, and bash will never get backed up). 2) Move the 'real' bash to someplace like /usr/bin/bash. This keeps files from steping on each other when backing up, but /bin/bash will still be a symlink to /bin/ash, unless modified (at which point you can no longer make a 'clean' backup of initrd.lrp). 3) Use indirection, similar to the debian 'alternatives', ie: /bin/bash -> /etc/alternatives/bash ..and one of .. /etc/alternatives/bash -> /bin/ash ..or.. /etc/alternatives/bash -> /usr/bin/bash With this method, you can make a 'clean' backup of both initrd.lrp *AND* bash.lrp, with the change required to select whether to use ash or bash as /bin/bash saved in a third package (either etc or a seperate alternates pacakge). ...or you can just ignore the whole mess, and don't backup initrd or bash (or manually remove /bin/bash from one package list file if you need to backup the other). Realistically, it shouldn't generally be required to backup the bash package (for anyone other than the maintainer), and it's only rarely necessary to backup initrd.lrp, so this is the option -- Charles Steinkuehler [EMAIL PROTECTED] --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Leaf.cfg
Erich Titl wrote: Charles after moving from lrpkg.cfg to leaf.cfg and the new linuxrc, which I hopefully did right... I found something weird in my backdisk file after manually loading bash using lrpkg -i /disk/bash (/disk being the mount point of my CF) mhttpd=-t msdos /dev/hda1 webconf=-t msdos /dev/hda1 bash=-t console=ttyS0,38400 It looks like lrpkg did not handle the file system and the device correctly. The reason I believe lies in the lrpkg command which scans for the boot parameter in the command line and tries to find the boot.fstype file too. Is there a more recent version available? This is a known bug, resulting from the elimination of the boot.fstype file. It's considered 'cosmetic' (and hasn't been fixed by me) for a few reasons: - If you actually want to backup a manually installed package, you'll have to specify a backup target. It's not possible for lrpkg to know which of the available targets you'll want to use to backup the pacakge. You could default to the first entry in /var/lib/lrpkg/pkgpath.disks, which should be right most of the time, but might not be the right thing to do all the time. - Currently, if you try to backup a manually installed package, you get an error (due to the malformed backdisk entry), 'prompting' the user to select an appropriate backup path. - As soon as you manually specify a backup path in lrcfg, the backdisk file is corrected. - I haven't had time to re-work lrpkg to extract the backup information from pkgpath.disks if boot.fstype doesn't exist. There's no newer version available that I'm aware of. If manually setting a backup destination is enough of a problem, feel free to hack on lrpkg. I'll help as time allows. -- Charles Steinkuehler [EMAIL PROTECTED] --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Leaf.cfg
Hi Charles another little problem showed up using the bash package, apparently bash is included in initdr.lrp (or at least in initrd.list) this prevents bash being backed up using lrcfg. cheers Erich --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Leaf.cfg
Charles after moving from lrpkg.cfg to leaf.cfg and the new linuxrc, which I hopefully did right... I found something weird in my backdisk file after manually loading bash using lrpkg -i /disk/bash (/disk being the mount point of my CF) mhttpd=-t msdos /dev/hda1 webconf=-t msdos /dev/hda1 bash=-t console=ttyS0,38400 It looks like lrpkg did not handle the file system and the device correctly. The reason I believe lies in the lrpkg command which scans for the boot parameter in the command line and tries to find the boot.fstype file too. Is there a more recent version available? Thanks Erich --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Leaf.cfg
Erich Titl wrote: Charles Thanks, the README seemed to make it clear Unfortunately linuxrc died, so I had to open my box, pry the CF out and add what's needed here is the resulting error LINUXRC: Bering - Initrd - V1.2 Using /boot/lib/modules/ide-core.o Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx Using /boot/lib/modules/ide-detect.o hda: 3SYSTEM SSSCF032MAA, CFA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Using /boot/lib/modules/ide-disk.o hda: attached ide-disk driver. hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_no_data_intr: error=0x04 { DriveStatusError } hda: 63488 sectors (33 MB) w/2KiB Cache, CHS=496/4/32 Partition check: hda: hda1 hda2 hda3 Using /boot/lib/modules/natsemi.o natsemi dp8381x driver, version 1.07+LK1.0.17, Sep 27, 2002 originally by Donald Becker <[EMAIL PROTECTED]> http://www.scyld.com/network/natsemi.html 2.4.x kernel port by Jeff Garzik, Tjeerd Mulder eth0: NatSemi DP8381[56] at 0xc4827000, 00:0d:b9:00:6d:f4, IRQ 10. eth1: NatSemi DP8381[56] at 0xc4829000, 00:0d:b9:00:6d:f5, IRQ 11. .: Kernel panic: Attempted to kill init! Can't open /var/ lib/lrpkg/root.blk.mk The problem appears to be /var/lib/lrpkg/initrd.list which was missing the entry for /var/ lib/lrpkg/root.blk.mk. Maybe you want to add this to the README for poor fools like me. Hmm...it sounds like you've got broken version of the initrd package. If this is the initrd.lrp directly from Bering, it sounds like there's a bug. /me ...wanders off and checks the initrd.lrp package on my custom-built CD-ROM package, which exhibits this error, so it sounds like a bug. -- Charles Steinkuehler [EMAIL PROTECTED] --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Leaf.cfg
Charles Charles Steinkuehler wrote: The problem appears to be /var/lib/lrpkg/initrd.list which was missing the entry for /var/ lib/lrpkg/root.blk.mk. Maybe you want to add this to the README for poor fools like me. Hmm...it sounds like you've got broken version of the initrd package. If this is the initrd.lrp directly from Bering, it sounds like there's a bug. /me ...wanders off and checks the initrd.lrp package on my custom-built CD-ROM package, which exhibits this error, so it sounds like a bug. No no, I initially forgot to add this to /var/lib/lrpkg/initrd.list, backed initrd up using lrcfg, so no surprise. Erich --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] Leaf.cfg
Hi Erich; AFAIK Charles wrote the leaf.cfg with Bering in mind - so it should work with Bering. I am not aware of any more docs as provided in the README and the linuxrc. Loading modules is similar as in Dachstein; you may want to have a look in the Bering-uClibc docs - I've tried to add as much as needed and as much I understood. kp Am Mittwoch, 15. Dezember 2004 09:29 schrieb Erich Titl: > Hi folks > > does anyone know of a description fot the transition from _classic_ > lrpkg.cfg to leaf.cfg, e.g. to the new linuxrc and module > initialisation. > > Thanks > Erich > > > --- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. Discover which products truly live up to the hype. Start > reading now. http://productguide.itmanagersjournal.com/ > > ___ > leaf-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-devel --- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel