This email was mistakenly delivered to Positive Telecom, Inc. and
is being forwarded to the intended recipient as a courtesy.
Administrator
[EMAIL PROTECTED]
-----------------------------------------------------------------
Raider wrote:
> On Wed, 3 Mar 1999, Klaus Drechsler wrote:
> > > Try making a small partition for windoze (200-300M) than a Linux
> > >native partition (about 100M) which will be the /boot or /. Than you are
> > >free to partition your hard drive any way you want it.
> > wow that is going to be a problem. I already installed so many software on,
> > that it would be a hard work to do it all again ...
>
> Well... sorry. I assumed you just did that partitioning so there
> was no problem with this.
>
> > but I have another idea. it is possible to boot linux from dos via
> > "loadlin". I tried it and it worked so far, but I have still some problems.
>
> Of course. That is one of the main purposes/advantages of
> loadlin over Lilo. Because it doesn't involve BIOS and it's boot problem.
>
> > the distribution I use is based on kernel 2.0.29. so there is no FAT32
> > suppurt (I tried to mount my first windows partition with "mount -t vfat
> > /dev/hda1 /win", but it then says "bad fs ...").
>
> There is a patch somewhere for older kernels. But the best idea
> seems to be just to get a newer kernel.
>
> > what I need is a little tool for linux to access /dev/hda1. because if I
> > can access this drive I can copy the new kernel-2.2.2 (I downloaded it with
> > windows) from that partition to my linux partition.
>
> Yup. It's pretty easy to do, but it will take some time. I mean
> you have to put the source on floppies. And it will take about 10 pieces.
> You will have to use arj or pkzip to make an archive with multiple
> volumes. Don't use winzip! winzip has a very idiot way of making
> multiple volumes. And besides, it's volumes aren't readable by unzip from
> *nix. pkzip follows the zip standard. Eventually it will make a dos
> archive (names in 8.3 format), but this isn't a real problem because you
> transport only one file. Same thing with arj - on every distribution CD
> there is an unarj utility I guess. Here you can use any archiver that has
> a version for dos and one for Linux and which can make multiple volumes.
> Now the rest of the idea. You should use msdos formated floppies
> so they could be seen from dos/win. Than you'll make the volumes with the
> archiver of your choice. The next step would be to boot Linux. Than you
> will do something like:
> # mount -t msdos /dev/fd0 /mnt_point
> I assume you have msdos fs format compiled and that /dev/fd0 is
> your floppy drive. mnt_point is a directory of your choice where you'll
> mount the floppy. You will copy the file from the /mnt_point to another
> location, ex: /tmp. Than you'll give:
> # umount /mnt_point
> Here you'll change the floppy in the drive (the order of the
> floppies isn't relevant) and remount the disk. And again those steps till
> you have all volumes stored on your Linux partition. You'll extract the
> kernel source tree as tar.gz, remove the volumes and from this point
> you'll have to follow the instructions from Kernel-HOWTO in order to have
> the new kernel.
>
> Warning: Are you sure you want a 2.2.x kernel. I mean I have
> RH4.2 with the 2.0.30 kernel (which is newer than yours by the way) and
> besides bash, I have to upgrade every important pack on my system in order
> to work with a 2.2.x kernel. Did you read the requirements for it? Maybe
> you should donload the 2.0.36 kernel.
>
> > > Any kernel, older than 2.0.33 will see fat32 as long as you have
> > >vfat support compiled.
> > you mean "newer", aren�t you ? :-)
>
> Oops! Yup. That was what I meant.
>
> Raider
> --
> ``Liberate tu-temet ex inferis''
