home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbnewsj!nhc
- From: nhc@cbnewsj.cb.att.com (n.h.chandler)
- Subject: Re: Two Hard drives?
- Organization: AT&T
- Date: Thu, 23 Jul 1992 03:40:14 GMT
- Message-ID: <1992Jul23.034014.6506@cbnewsj.cb.att.com>
- Summary: Linux BOOT.SYS BOOTUTIL
- References: <63992@hydra.gatech.EDU> <Brt6Lz.7Fp@news.udel.edu> <1992Jul22.233242.22228@rs6000.cmp.ilstu.edu>
- Lines: 40
-
- In article <1992Jul22.233242.22228@rs6000.cmp.ilstu.edu>, jliddle@rs6000.cmp.ilstu.edu (Jean Liddle) writes:
- > In article <Brt6Lz.7Fp@news.udel.edu> radel@bach.udel.edu (Todd Radel) writes:
- > >OK, folks, here it is: How to keep Linux entirely (err, almost) on a
- > >second hard disk and still be able to boot without a floppy. Here's
- > >what you do:
- > >
- > > [ ... ]
- > >
- > >1. Backup everything.
- > >2. Repartition your primary hard disk (drive C:) and add a 1mb partition
- > > somewhere. My 119mb drive looks like this:
- > >
- > > DOS partition /dev/hda1 118mb
- > > Linux boot /dev/hda2 1mb
- > >
- >
- > This week I completely repartitioned my hard drives, giving LINUX the
- > Lions Share of space. To be on the safe side, I mirrored my entire
- > bootable Linux installation on a partition on the second hard drive and
- > recompiled the kernel with my ROOT device set to sdb2. Using mcopy
- > I copied the resulting Image to the C: drive, from which bootlin4 can
- > execute it. I rebooted and Linux worked fine from D:, with absolutely
- > no reference to anything on C: beyond the initial BOOT.SYS and BOOTLIN
- > calls. If your using DOS on your C: drive anyway, this approach would
- > let you avoid having to create an extraneous 1 MB parition.
- >
- > Using this approach I was able to mess around with the partitioning
- > scheme on /dev/sda with no fear of reprisal, beyond having to reinstall
- > my DOS stuff from floppy backups. Worked like a charm.
- >
- > Jean.
- > --
-
- Same here!! This arrangement also allows easy testing of new images.
- One can move the new kernel image to C, modify the CONFIG.SYS file
- to add another menu item for the new kernel image. If the new image
- bombs, reboot the system and select the original kernel.
-
- Neville Chandler
- nhc@mtdcr.att.com
-