From: Frank Carmickle <frankiec@braille.uwo.ca>
To: "'speakup@braille.uwo.ca'" <speakup@braille.uwo.ca>
Subject: RE: linux on old system
Date: Mon, 23 Jul 2001 18:59:52 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0107231858040.17508-100000@localhost> (raw)
In-Reply-To: <E041C927721AD51196B800508BAE8CDA5115EF@ntexch02.ahcccs.state.az.us>
You should be able to just use a small 10mb partision at the begining of
the disk to put all of your kernel images in. No need for another drive.
On Mon, 23 Jul 2001, Holmes, Steve wrote:
> I have an old 486 with a 2 gig hard drive in it and Lilo won't boot the
> thing at all. What I ended up doing is install an old 40 meg hard disk and
> set my boot stuff there and mount the 2 gig as an entire single linux
> partition. Once running, linux will see the entire drive as one partition
> if you want. It got a bit complicated the way I'm doing it but it is
> working good right now. I first discovered this when I upgraded the disk
> drive in this thing from a 420 meg to this 2 gig and then the machine
> wouldn't boot anymore. I could always boot from a floppy and then mount the
> 2 gig as a new partition or I could have the boot disk actually call up the
> other drive so I just kind of moved the floppy based boot system to this
> little 40 meg drive as I mentioned above. Amazing but it works.
>
> -----Original Message-----
> From: Gregory Nowak [mailto:romualt@megsinet.net]
> Sent: Sunday, July 22, 2001 2:55 AM
> To: speakup@braille.uwo.ca
> Subject: linux on old system
>
>
> Hi all,
>
> I'm preparing to reinstall Linux on my pentium 3.
> I also tried to compile a c++ program
> on an old 486 I've got, and got the same errors.
> Whatever I screwed up, I was sure consistent about it.
> Guess I'll have to compile code step by step
> of the install and upgrade to kernel 2.4.6 so that I can figure out what
> goes wrong where on the way.
> Anyway, my question is this.
> The bios of the 486 doesn't support 32-bit lba.
> Consequently, the bios only sees 504 mb of the drive.
> However, in this machine's past, someone had replaced
> it's original drive with a 814 mb one.
> Since lilo had trouble booting the entire drive,
> I made the boot partition on the first 504 mb,
> used 128 mb for swap, and mounted the rest under /usr/src
> since source code takes up the most space (or so I thought).
> Appearently, my / partion is currently 100% full,
> and /usr/src/ is 93% full.
> When I do the reinstall, what is the best place to mount
> the second partion at?
> Or, what is the best way to setup the drive so that Ican still
> boot it and get the most out of its capcity?
> Thanks for any help in advance.
> Greg
--
Frank Carmickle
phone: 412 761-9568
email: frankiec@dryrose.com
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Holmes, Steve
` Gregory Nowak
` Steve Holmes
` Frank Carmickle [this message]
-- strict thread matches above, loose matches on Subject: below --
Gregory Nowak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0107231858040.17508-100000@localhost \
--to=frankiec@braille.uwo.ca \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).