From: mike <mike@kevino.org>
To: linux-newbie@vger.kernel.org
Subject: Re: partitons and proper order
Date: Sun, 31 Oct 2004 19:45:18 -0700 [thread overview]
Message-ID: <4185A33E.4090202@kevino.org> (raw)
In-Reply-To: <5.1.0.14.1.20041031143246.01f2be00@celine>
Ray Olszewski wrote:
> At 03:14 PM 10/31/2004 -0700, mike wrote:
>
>> [...]
>> I do use lilo. I have also been running a dual boot box with M$ and
>> lilo has been writing to the master boot record. But this time it's
>> all going to be Linux. I have a 30 gig harddrive so I would assume I
>> would be safe if I kept the /boot partition within the first 500
>> megabytes of the drive.
>
>
> That's a good bet, but the mappings on modern hard drives are so hard to
> follow, and so idiosyncratic, that it's not a sure thing. It''s hard to
> figure out where the BIOS thinks track 1024 ends ... and aside from
> access to the kernel, know of no special benefit any partition gets
> from being at the beginning of the drive.
>
> My practice ... which has worked 100% reliably for me with drives up to
> 120 GB or so (I think I've even made it work with a 180 GB drive, and
> drives over 134 GB or so have real BIOS problems)... is to make
> partitions in this order:
>
> hda1 = /boot
> hda2 = swap
> hda3 = / (root)
> hda4 = /home
>
> I'm not partial to using separate /var, /tmp, and /usr partitions ...
> but if I were, I'd put them and /home in the extended partitions at hda5
> and up.
>
>
Hi Ray,
The reason I made /var a seperate partion is when I first started I
had a small drive and read somewhere that /var/log could grow so big
from logs (from miss a missconfigured system, which being a newbie's
newbie at the time could likely happen to me :-) that it could
render my system unuseable. I think I just made the others /usr,/tmp
seperate because I made /var seperate.Which is probably not needed
anymore now that I am more experienced (in some things anyways).
Thanks,
Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-11-01 2:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 19:22 partitons and proper order mike
2004-10-31 20:02 ` Thorsten Alge
2004-10-31 22:14 ` mike
2004-10-31 22:39 ` Ray Olszewski
2004-11-01 2:45 ` mike [this message]
2004-11-01 5:18 ` Ray Olszewski
2004-11-01 7:07 ` Peter
2004-11-01 17:14 ` Ray Olszewski
2004-11-01 19:33 ` Richard Adams
2004-10-31 23:37 ` simon
2004-11-01 2:54 ` mike
2004-11-25 22:22 ` lindax newbie
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=4185A33E.4090202@kevino.org \
--to=mike@kevino.org \
--cc=linux-newbie@vger.kernel.org \
/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