Text 6217, 117 rader
Skriven 2006-06-04 20:08:26 av Maurice Kinal (1:140/13.1)
   Kommentar till text 6216 av Paul Rogers (1:105/360.0)
Ärende: You gotta smile
=======================
Hey Paul!

Jun 04 13:01 06, Paul Rogers wrote to Maurice Kinal:

 PR> I didn't get very far, but it was a reasonably profitable
 PR> evening & morning.  With your indulgence, this will help me
 PR> consolidate my recollections.

I am all ears.

 PR> I wrote the two 300+MB tarballs to CDRW's.  (The one difference
 PR> between the twin systems is one has a Memorex/Wearnes [,1]622
 PR> CDRW, and the other has a Hitachi CDR.  n.b. The first one was
 PR> where the HD got hosed.)

Okay.  I've had problems with CDRW's in the past depending on the CD-ROM, which
in itself shouldn't account for errors but has, also depending on the machine
it was wired into ... sometimes.

 PR> Prepped Trinux boot/package floppies for working over an ext2
 PR> fs, ignoring the network setup.  VFAT & Minix are its "native"
 PR> fs's.  Can't insmod the ext-fs modules I found, because they
 PR> were compiled for 2.4.19 and the kernel was 2.4.21.

Right.  Normally you would have to copy the modules for 2.4.21 to the rootfs's
(initrd, whatever) /lib/module directory before moving it over to the proper
directory before burning.  I find that to be the easiest (relatively speaking
of course) way of handling that issue.  Either that or not bother with modules
but sometimes that ideology can fail in cases where you are attempting to cover
all the potential targets. 

 PR> Website
 PR> is somewhat neglected & not very complete.

Understood.

 PR> Tom's RTBT does ext2.  Tried copying a CD to the clean HD, got
 PR> READY, SEEK errors, then TRAY OPEN, etc., ~240MB into the copy.
 PR> Same place on 2 trys.  Swap it all over to the CDR box, but the
 PR> CDR can't read/mount the (steel gray) CDRW disk.

Right.  I've seen that happen.

 PR>    (Hmm, suggests the chipset SouthBridge IDE controller may be
 PR>    going south!  Maybe I got good disks, maybe not, but the CDRW
 PR>    & HD share it.  The tray WASN'T open!)

Possibly.  I don't trust CD's or their needed drives to tell the tale.  Too
many variables to really get a good handle on what exactly is wrong.  If I have
to guess I always suspect the media, in this case CD(RW)'s and try booting them
from the burner if I really want to know.  If the CD-ROM has no trouble booting
well known media and only the burner can boot the suspect media then that
particular media becomes a new coffee coaster.  I have lots of those but have
taken to giving them the complete heave-ho as of late, including not bothering
with drives anymore.  Stinkin' cheap plastic spinney thingies!

 PR> Knoppix is out as far as the CD's go--competition for the drive.

Hm.

 PR> But I could use the file server.  Won't boot on the CDRW box!
 PR> (More evidence!)

I could never get Knoppix to work on any machine here, no matter what the
media.  It cannot handle the harware here.  Not really Knoppix's fault as I
tend to do weird things.  No big deal to me personally.

 PR> Swap over to the CDR twin.  There I can insmod
 PR> 3c509.o, ifconfig, telnet/ftp to the file server.

Perfect!  That should work out fine.  I trust that more then a CD install.

 PR> Download the
 PR> tarballs.  Unball them.  Try the clone script.  Several errors &
 PR> oversights sequentially discovered, including not anticipating a
 PR> one-liner script, startover.  Having to use vim.  8-[

<EG>  Gotta love it!!!

 PR> Got to the point where I'm cloning relative to a mounted fs, but
 PR> I want to run some of the build scripts which normally run in a
 PR> chroot environment.

That should work once the base is installed.  Are you mounting the chroot
enviroment's /proc after chrooting into it?  You'll need to do that if you want
to access any of the hardware while chrooted.  I forget if the network will
absolutely require this to happen in 2.4 kernels but even if it doesn't you
should still see some error when doing an 'ifconfig' about the ethernet not
being setup properly even though it works.  Sometimes you can get away with not
mounting /proc wrt networking.

 PR> Setting up /etc/{hosts,fstab}, sysadmin
 PR> account, lilo/grub/MBR, et al.  This is very near the end, when
 PR> almost all of the target base is installed, so chroots might
 PR> work.

It should.  If it doesn't then something is definetly wrong.

 PR> But it's time to take care of some chores outside.

Sounds like a plan.

 PR> In any event, you gotta give me points for persistence!

For sure!  You got it bud.

 PR> But as
 PR> far as a cloning event anybody else might be able to use--so far
 PR> a complete failure.

There is no such thing ... unless you give up on it.

Life is good,
Maurice

--- Msged/LNX 6.2.0
 * Origin: The Pointy Stick Society XIX - Simplify man! (1:140/13.1)