From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Grub, gpt partitions and BIOS, not uefi thing.
Date: Thu, 02 May 2024 11:46:16 +0100 [thread overview]
Message-ID: <6042053.lOV4Wx5bFT@cube> (raw)
In-Reply-To: <14aad0fe-06ff-577a-de92-d27a34c8a357@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On Thursday, 2 May 2024 00:45:29 BST Dale wrote:
> Grant Edwards wrote:
> > OK, so 'boot' is for the Linux /boot directory. I was just curious
> > since I had never used one.
When I started using Linux, the received wisdom was to keep a separate /boot,
and leave it unmounted during normal operation. The idea was that a successful
hacker would not, supposedly, be able to corrupt the kernel ready for a reboot
into their system.
Old habits die hard, though, and besides, a separate /boot has been handy in
the copious reinstallations I've been through.
> I've used one ever since I started using Linux and it's as much habit as
> anything. Given the size of drives nowadays, I have started putting
> /usr and /var on the root partition. When I build my new rig tho, odds
> are /var will be on its own partition. That way if a log file goes
> wonky, it can fill it up and not really do any harm.
I do that too. It also helps with backups and new installations.
--
Regards,
Peter.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-05-02 10:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-27 16:53 [gentoo-user] Grub, gpt partitions and BIOS, not uefi thing Dale
2024-04-27 16:59 ` Wojciech Kuzyszyn
2024-04-27 17:48 ` Mark Knecht
2024-04-27 18:33 ` Michael
2024-04-28 5:24 ` Dale
2024-04-28 9:14 ` Michael
2024-04-28 17:13 ` [gentoo-user] " Grant Edwards
2024-04-28 17:40 ` Grant Edwards
2024-04-28 18:39 ` Dale
2024-04-28 20:31 ` Michael
2024-04-28 21:08 ` Dale
2024-04-28 21:32 ` Dale
2024-05-01 19:36 ` Dale
2024-05-01 20:03 ` Grant Edwards
2024-05-01 20:20 ` Dale
2024-05-01 20:25 ` Grant Edwards
2024-05-01 23:45 ` Dale
2024-05-02 9:35 ` Michael
2024-05-02 10:43 ` Dale
2024-05-15 7:39 ` Wols Lists
2024-05-02 10:46 ` Peter Humphrey [this message]
2024-05-15 7:42 ` Wols Lists
2024-05-15 10:40 ` Peter Humphrey
2024-05-15 17:38 ` Wols Lists
2024-05-15 17:57 ` Grant Edwards
2024-05-15 23:54 ` Peter Humphrey
2024-05-16 0:10 ` karl
2024-05-16 8:26 ` Michael
2024-05-16 9:22 ` Nuno Silva
2024-05-16 16:41 ` Dr Rainer Woitok
2024-05-16 16:46 ` Michael
2024-05-18 9:16 ` Dr Rainer Woitok
2024-04-28 22:42 ` Wol
2024-04-27 19:21 ` [gentoo-user] " Wols Lists
2024-04-28 8:43 ` Mickaël Bucas
2024-04-28 12:57 ` Dale
2024-04-28 13:10 ` Michael
2024-04-28 13:17 ` Dale
2024-05-05 6:31 ` Dale
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=6042053.lOV4Wx5bFT@cube \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.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