Re: [Leaf-user] libz on Dach-CD
I certainly have to defer to Charles and Michael - but if you want an example, here's how I did it, based on Charles instructions in the Dachstein CD notes. Feedback or suggestions for improvement of my setup are welcome! I have an ancient 486DX with a mere 16Mb of ram for my firewall, boot off a floppy, then read the CDROM for modules. I added the floppy drive to the PKGPATH in syslinux.cfg on the boot floppy, and libz.lrp to lrpkg.cfg as well, with the search order R (reverse search of PKGPATH, stop on first match). Here's the content of the files: # mount -t msdos /dev/fd0u1680 /mnt mount: /dev/fd0u1680 is write-protected, mounting read-only firewall: -root- # cat /mnt/syslinux.cfg display syslinux.dpy timeout 0 default linux append=load_ramdisk=1 initrd=root.lrp initrd_archive=minix ramdisk_size=12288 root=/dev/ram0 boot=/dev/fd0u1680,msdos PKGPATH=/dev/cdrom:iso9660,/dev/fd0u1680:msdos LRP=etc,ramlog,local,modules,dhclient,dhcpd,dnscache,weblet firewall: -root- # cat /mnt/lrpkg.cfg etc,ramlog,local,modules,dhclient,dhcpd,dnscache,weblet,ifconfig,mawk,ipsec, sshd,libz:R,tcpdump On boot, only the libz.lrp from the floppy is loaded. Now, if I can just figure out what kind of memory to put in this ancient box, I'll get enough to load bash... Looks good, except for the floppy disk in PKGPATH, which should be unnecessary. I think if you trim PKGPATH to simply PKGPATH=/dev/cdrom:iso9660, everything will continue to work properly. As it stands now, you're probably loading the floppy contents twice... Using the :R switch for libz is a good idea. As long as you've got the *ENTIRE* package (and not just configuration data) on the floppy, this is probably the best way to implement an upgrade. If you simply have two libz packages (one on the CD, and one on the floppy), and don't use the :R option, the CD-ROM libz is loaded first, then the floppy libz is loaded on top of that. While this shouldn't normally cause any problems (things would only get wierd if the CD-ROM package contained files not present in the floppy version, which wouldn't be deleted, and would likely wind up orphened, becomming part of the root package), it's cleaner to use the :R switch, and avoid loading the CD-ROM version of the package entirely. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
[Leaf-user] libz on Dach-CD
Hi All, Am I correct in assuming that Dachstein-CD will use the libz.lrp from the floppy if I copy it there, rather than the one burned onto the CD? I am also assuming J. Nilo's updated libz is suitable for this use -- is that the case? Thanks, Dan -- Optimum Networks, Inc. Small Business IT Services Serving Minneapolis/St. Paul Metro ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] libz on Dach-CD
Am I correct in assuming that Dachstein-CD will use the libz.lrp from the floppy if I copy it there, rather than the one burned onto the CD? I am also assuming J. Nilo's updated libz is suitable for this use -- is that the case? Short answer: yes Longer answer: If you have a libz.lrp on your boot= device (typically the floppy), Dachstein CD will unzip this *LAST*, over-writing any pre-existing files, assuming you haven't over-ridden the default search order for the package in question (details on this behavior are in the CD README file). This functionality was specifically designed to allow local modification of packages you might not have write access to (ie on a network server, CD-ROM drive, or similar), and is quite handy for software updates, if you don't want to burn a new CD... Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] libz on Dach-CD
Just for clarification, if my system boots from the CD, it will still give precedence to the libz.lrp from the floppy? Thanks again, Dan - Original Message - From: Charles Steinkuehler [EMAIL PROTECTED] To: [EMAIL PROTECTED]; Scott C. Best [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, March 21, 2002 4:47 PM Subject: Re: [Leaf-user] libz on Dach-CD Longer answer: If you have a libz.lrp on your boot= device (typically the floppy), Dachstein CD will unzip this *LAST*, over-writing any pre-existing files, assuming you haven't over-ridden the default search order for the package in question (details on this behavior are in the CD README file). ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] libz on Dach-CD
dgilleece wrote: Just for clarification, if my system boots from the CD, it will still give precedence to the libz.lrp from the floppy? Thanks again, Dan - Original Message - From: Charles Steinkuehler [EMAIL PROTECTED] To: [EMAIL PROTECTED]; Scott C. Best [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, March 21, 2002 4:47 PM Subject: Re: [Leaf-user] libz on Dach-CD Longer answer: If you have a libz.lrp on your boot= device (typically the floppy), Dachstein CD will unzip this *LAST*, over-writing any pre-existing files, assuming you haven't over-ridden the default search order for the package in question (details on this behavior are in the CD README file). [1] First, it will install that version on the CD; then [2] It will install that version on the floppy. If both versions contain only filenames that are on the other media, then it is actually only the floppy version running on your system. However, if filenames differ, then ... it depends ; -- Best Regards, mds mds resource 888.250.3987 Dare to fix things before they break . . . Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
Re: [Leaf-user] libz on Dach-CD
I certainly have to defer to Charles and Michael - but if you want an example, here's how I did it, based on Charles instructions in the Dachstein CD notes. Feedback or suggestions for improvement of my setup are welcome! I have an ancient 486DX with a mere 16Mb of ram for my firewall, boot off a floppy, then read the CDROM for modules. I added the floppy drive to the PKGPATH in syslinux.cfg on the boot floppy, and libz.lrp to lrpkg.cfg as well, with the search order R (reverse search of PKGPATH, stop on first match). Here's the content of the files: # mount -t msdos /dev/fd0u1680 /mnt mount: /dev/fd0u1680 is write-protected, mounting read-only firewall: -root- # cat /mnt/syslinux.cfg display syslinux.dpy timeout 0 default linux append=load_ramdisk=1 initrd=root.lrp initrd_archive=minix ramdisk_size=12288 root=/dev/ram0 boot=/dev/fd0u1680,msdos PKGPATH=/dev/cdrom:iso9660,/dev/fd0u1680:msdos LRP=etc,ramlog,local,modules,dhclient,dhcpd,dnscache,weblet firewall: -root- # cat /mnt/lrpkg.cfg etc,ramlog,local,modules,dhclient,dhcpd,dnscache,weblet,ifconfig,mawk,ipsec,sshd,libz:R,tcpdump On boot, only the libz.lrp from the floppy is loaded. Now, if I can just figure out what kind of memory to put in this ancient box, I'll get enough to load bash... Ken At 04:35 PM 03/21/2002 -0600, [EMAIL PROTECTED] wrote: Hi All, Am I correct in assuming that Dachstein-CD will use the libz.lrp from the floppy if I copy it there, rather than the one burned onto the CD? I am also assuming J. Nilo's updated libz is suitable for this use -- is that the case? Thanks, Dan -- Optimum Networks, Inc. Small Business IT Services Serving Minneapolis/St. Paul Metro ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user == J. Kenneth Gentle (Ken) | Phone: (610) 255-0361 FAX:(610) 255-0418 Gentle Software, LLC | Email: [EMAIL PROTECTED] == ___ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
