-- simply by hitting ctrl-P each time I get gparted to show info about a different "device"; it does give all different names with both thumb sticks and the SD card inserted.

But I'm drawing a blank on posting. For instance, do I have to attach each one (assuming I do take them successfully) as I ...

You asked :

> I suppose booting to the hard disk hdc and > using grub files and menu.lst on hdc1 is the > best way to manage the booting for all your > other Linux installations.

> Make sense?

Isn't that what I've been doing?

I tried with and without the 1 GB and the 8 GB geeksticks, singly ...

I got into grub.conf one more time; there were no extra lines above the EeDora line. I disremember now whether it was showing (hd0,1) or (hd1,0) ; but I reversed it to the other one, unmounted, and rebooted. Now at least I get a new (and very enigmatic, if not contradictory) error message.

Invalid ...

.... with mp, making only a single change, (hd0,1) instead of (hd0,0) for EeeDora.

It failed.

I notice, though, that there's an extra blank line or two above the word EeeDora. Could *that* be the problem? Grub giving up before it finds the direction??

Or am I barking up the wrong tree yet ...

# mount -t ext3 /dev/hdc1 /TEST
mount: mounting /dev/hdc1 on /TEST failed
# cd
# umount /TEST
# mount -t ext3 /dev/hdc1 /TEST
# cd /TEST
# ls
config-2.6.23.14-107.fc8 lost+found System.map-2.6.23.14-107.fc8
grub memtest86+-1.70 vmlinuz-2.6.23.14-107.fc8
initrd-2.6.23.14-107.fc8.img puppy301Eee
# cd ...

> Various comments:

> hd0 means the first disk GRUB finds, usually it corresponds with Linux /dev/hda, but in your case hd0 would correspond with Linux /dev/hdc. At least that's what it appears from you probepart output, but there is no accounting for anything more than two Linux partitions on ...

-- and to judge from ifconfig listing both ath0 and wifi0, I suppose it may well be running both the ethernet cable connection *and* the wireless connection to my router.

Fwiw, something called binky on the panel seems to be saying much the same.

But when I open a terminal and try to ssh between ...

... the post between the last *written* by me and this one *is* the requested output fromthe EeePC.

# fdisk -l

Disk /dev/hdc: 4001 MB, 4001292288 bytes
255 heads, 63 sectors/track, 486 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdc1 * 1 25 200781 83 Linux
/dev/hdc2 26 486 3702982+ 83 Linux

Disk /dev/sdb: 1021 MB, 1021125120 bytes
32 ...

Since I can't scp between my PC and the EeePC, and also can't do serious typing on the latter, here -- maybe -- is an awkward workaround.

I have the EeePC also logged into this thread. I'll open a reply with it,and then -- I hope -- c&p the results of fdisk -l. With nothing else. Even highlighting ...

Meanwhile, I'm working on the rest of it -- and that raises a Zwischenfrage. ('Intermediate question' is about the closest Engliish has.)

To do this properly, I ought to be putting up a lot of stuff by c&p from the EeePC directly, not trying to retype it. But my trifocal fingers and arthritic ...

> Presuming Fedora?

Yes. I've been trying to cut it down enough to run on this machine; I have it installed on an 8 GB thumb drive -- which was not in the machine at the time I ran the probe.

> Presuming it boots to the GUI and you want it to boot to the TUI

Worse than that.When I put the ...

If I can save it to a file, maybe I can scp it to this machine, and then paste it into a message here. Maybe. Ssh and scp between this machine and the EeePC are none to happy ...

# probepart
/dev/hdc1|ext3|401562
/dev/hdc2|ext2|7405964
/dev/sdb1|vfat|1993576
/dev/sda1|swap|2054554
/dev/sda2|ext2|5898060
/dev/sr0|iso9660|0
#

That is with Puppy on the 1 GB USB stick, and with a 4GB SD card in the right front corner. It's supposed to be the swap.

I did try editing hd(x,0) and sd(x,o) in the various combinations. No joy.

I also tried, from the grub command line, 'find /boot/vmlinuz' with variations leaving out one thing or another, or using initrd instead of vmlinuz. Also no joy.

I have it booting to Puppy now, to try the probepart and ...

You don't just type a command. I can get the list of commands, all right, with the tab key from a grub command line.

But that doesn't help.

Most of them seem to need parameters, or flags, or objects, or something. With no hint what -- you're supposed to know.

And yes, I've tried once again to ...

Many thanks! Worked like a charm. What's more, once my ancient eyeballs spotted the Ctrl-a hint, it was all easy. (I'm doing this on an EeePC, as I may have mentioned : *tiny* fonts!)

Now all I have to do is figure out what grub is calling the main partition of the hard drive -- and I can get ...

The boot partition lets me boot either to Fedora 8 (on an 8 GB thumbstick) or to Puppy 3.01ee frugal (on a 1GB thumbstick); I *think* the hard drive now has EeeDora on it -- it should.

But F8 is messed up; I need to boot it init3 (I think) and can't figure how.

I might be able to manage in ...

Several of the various distros I've tried on the 4 GB EeePC have installed but failed to connect -- most probably, I'm told, for want of a working driver (atl2?) on this very new hardware.

Puppy must therefore have such a driver -- I think. Right?

Can I simply copy it into F8? How?

Or is F8 ...

All I did was launch that wizard. It found the drive, and named it as the only option
in all three of its places.

Then I ran the installer again. It installed Puppy -- in a tiny little space on hdc1 (called sda1 in F8 -- less than 200 MB total, including F8's boot sector). It connected to the Net ...