[Before you read my response, one comment] I'm not sure you're taking a great approach here. There's a very well tested set of scripts in boot-floppies for creating a debian base tarball. I intended to use those when the last missing binaries are dealt with.
Dan On Thu, Jul 23, 1998 at 05:00:11PM -0600, John McCorquodale wrote: > I guess that would be me. Hi, guys. > > IMPORTANT: Somebody tell me where to get a working "mount" et al. You can > ignore the rest of this message if you like. ;-) That would be me. Thanks for reminding me - I just got home. I will now pause and write the rest of my response once mount is uploaded. There. Richard Braakman tells me it will be installed tomorrow, and I'm not sure how often ftp.debian.org/pub/debian/Incoming updates. > Basically, I've got a script that'll take the i386 hamm tarball, extract it, > overlay the slink/PPC base/* packages on it, then look through the resulting > mess for surviving 80386 binaries and either pull them from Red Hat (which > no longer works with the new libc) or delete them altogether. > > It does not currently generate bootable tarballs, mainly due to the fact that > I can't find a working mount. (init and shells and stuff work fine). I saw > something go by that a working mount would be going up soon to "Incoming"? > Which "Incoming" is this? As soon as I get it, I can make progress on the > tarball again. Also not working would be getty. Also uploaded tonight if I'm lucky will be getty. > I also really need a working rdev. Where do I get source? Or has somebody > built one for the new libc? rdev is platform specific - there IS no PPC rdev, as far as I know. Er - looking at linuxppc, that's not true. I'll work on it. Along with getty, more, and hwclock (still broken), it's in util-linux. > At first glance, it looks like everything in net/netbase is in the hamm > tarball and just things like telnet and ftp from net/netstd are in > the hamm tarball. I'll try to emulate this from the slink/PPC packages (which > I assume are happy with the new libc?) If net/netbase is in the base tarball, > shouldn't it really be base/netbase? And should'nt telnet & tcp be in it? > > Ie: shouldn't everything in the tarball be in base/* somewhere? Or am I > guessing the wrong meaning of "base"? > > Once we get a working tarball, we can pare it down to something more minimal, > as it's looking like it'll come in around 10Mb when I get all these binaries. That's the meaning of Essential: more than base/ AFAIK. netstd I just uploaded; netbase is working in slink I believe. > Missing Binaries snarfed from RedHat: (all libc1.99, so they don't work) I deleted ones I have already accounted for. > /sbin/kbdrate It's there...it doesn't seem to DO anything though. This is also a util-linux program, and I'm still working on it. > /sbin/cfdisk > /sbin/fdisk Don't belong there. There's pmac-fdisk instead. > /usr/sbin/cytune > /usr/sbin/rdev Don't belong there and/or being worked on. Unsure, see above. > Missing Binaries which were removed: (didn't have 'em in RedHat) > /bin/ae > /bin/fdflush > /sbin/insmod > /sbin/lsmod > /sbin/ksyms > /sbin/modinfo > /sbin/genksyms > /sbin/modprobe > /sbin/depmod > /sbin/kerneld > /sbin/kdstat Modutils is my next project after util-linux. > /sbin/hwclock > /sbin/sfdisk One dubious, one almost certainly didn't belong. > /sbin/plipconfig Dunno if it supports the hardware, but it's there. > /sbin/lilo Better gone. > /sbin/ipfwadm > /sbin/ipchains > /sbin/activate > /sbin/pnpdump > /sbin/isapnp Kill these > /sbin/cardmgr > /sbin/cardctl > /sbin/ifport > /sbin/scsi_info > /sbin/probe > /sbin/ftl_format > /sbin/ftl_check > /usr/bin/elvis-tiny > /usr/bin/resizecons > /usr/bin/syslinux > /usr/sbin/tunelp > /usr/sbin/ipautofw > /usr/sbin/chat > /usr/sbin/pppd > /usr/sbin/pppstats > /lib/ld.so > /usr/lib/lddstub > /tmp/basesystem/usr/lib/dpkg/methods/mountable/logcmd > /usr/lib/perl5/i386-linux/5.004/auto/IO/IO.so > /usr/lib/perl5/i386-linux/5.004/auto/Socket/Socket.so > /usr/lib/libnewt.so.0.21 > /usr/lib/whiptcl.so Assorted. See other discussions and recent packages for some; others i have no idea. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
