-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Aaron wrote:
> Lew Pitcher <Lew.Pitcher@td.com> wrote in message news:<aES6d.23609$tT2.1337683@news20.bellglobal.co m>...
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Here's how I would do it...
>>
>>1) obtain TomsRootBoot (in ZIP form) from the site I pointed you at
>>2) In MSWindows, build a TomsRootBoot diskette from the contents of
>> the tomsrtbt zip file
>>3) Boot tomsrtbt; you are now running linux
>
>
> Done.
>
>
>>4) In tomsrtbt, mount your Linux partition to /mnt
>
>
> Step by step directions of what to type are really what I need. This
> is what seems to really be frustrating me about Linux. In order to
> get to an "easy" to use GUI like KDE, you have to know command line
> things. I realize that this isn't true in most installation
> scenarios, but still...

Naturally, this is frustrating, but it is unusual for most 'modern'
distributions. However, even MSWindows installs (I've done a few) sometimes
require commandline knowledge.

> Anyway, if you could list the things to type,
> it would be quite helpful. I am familiar with DOS and have read about
> using the Linux command line, but there is quite a lot. So, how to
> mount?

Assuming that your MSWindows filesystem is the first partition of the master IDE
drive on the primary channel (the likeliest case), then
mount -t vfat /dev/hda1 /mnt
should take care of it.

>>5) chroot yourself into your Linux system
>> cd /mnt
>> chroot . /bin/bash
>
>
> Hmm, maybe these are the directions I was looking for. My apologies.
> Still, the above argument is applicable.

Usually, installs go smoother than yours did, and these sorts of instructions
are unnecessary. Of course, in the analogous MSWindows situation, you'd /have/
to reinstall the OS, because there would be no other way to fix the problem.
Here, a simple set of commands can fix the problem in less than 5 minutes.

>>6) run lilo to build a Linux boot floppy
of course, this assumes that your /etc/lilo.conf was properly set up in
first place. You might want to copy it out and post it here, and we can
tell you what (if anything) to change. The only risk (now) is that, if your
lilo.conf file is incorrect, you won't be able to boot Linux from the LILO
floppy you are about to build.
>> lilo -b /dev/fd0
>>7) exit your chroot environment
at the commandline prompt, type
exit

>>8) umount your hard drive
at the commandline prompt, type
umount /mnt

>>9) reboot, using the lilo boot disk you just built
<ctrl><alt><delete> will do here.

>>- From that point on, you can just insert the lilo boot disk into your floppy disk
>>drive and reboot to get to your (current) Linux installation.
>
>
> That would be the best case scenario.

FWIW, I booted Linux this way for about 3 months before I trusted lilo to
properly build my MBR. It was a pita, but it did reassure me in the stability of
my Linux setup.

- --
Lew Pitcher
IT Consultant, Enterprise Data Systems,
Enterprise Technology Solutions, TD Bank Financial Group

(Opinions expressed are my own, not my employers')
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQFBXGFNagVFX4UWr64RAstFAKDO+Co6+yV0NcnxFs5gdp L2G/XAhQCgm8db
rDITp7gG0QJ2Pe2nOfZyYTw=
=RLKK
-----END PGP SIGNATURE-----