Re: /etc/fstab question (problem)?
On Sat 22 Apr 2023 at 18:51:26 (-0700), David Christensen wrote:
> On 4/22/23 08:24, David Wright wrote:
> > On Fri 21 Apr 2023 at 15:46:30 (-0700), David Christensen wrote:
> > > On 4/21/23 08:12, Max Nikulin wrote:
> > > > On 20/04/2023 04:03, David Christensen wrote:
> > > > > * What if root attempts to remove everything under /etc, in
> > > > > anticipation of mounting a file system at /etc, when one or
> > > > > more programs have one or more open temporary files?
> >
> > With one exception, I've not seen root (whichever process that
> > refers to) doing anything like that in anticipation of mounting
> > a filesystem, so I wondered where that realisation came from.
> > The exception (which I haven't actually observed) is run-init
> > tearing down the initramfs before the true root is mounted.
>
>
> You're right; what I wrote makes no sense -- because it is wrong:
>
> On 4/21/23 08:12, Max Nikulin wrote:
> > David, you were wrote /etc instead of /tmp in several messages
>
> On 4/21/23 15:46, David Christensen wrote:
> > I apologize for the errors. :-(
I had seen your correction, but my point wasn't dependent on any
particular choice of directory, but with mounting filesystems
in general—onto any mountpoint.
> "Back in the day", people running Linux had computers with limited
> amounts of storage and memory. I imagine an initial ramdisk seemed
> like an good trade-off/ work-around at that time.
>
> But today, this is my Linux daily driver:
> Total online memory: 32G
That must be nice. I don't know what it might have cost. I'm afraid
I only use cast-offs. The oldest has ½GB memory.
> # ls -l /boot/initrd.img-5.10.0-21-amd64 /boot/vmlinuz-5.10.0-21-amd64
> -rw-r--r-- 1 root root 47837534 Mar 18 19:23
> /boot/initrd.img-5.10.0-21-amd64
> -rw-r--r-- 1 root root 7019136 Jan 21 06:35 /boot/vmlinuz-5.10.0-21-amd64
> The Linux kernel is ~7 MB and initrd.img is ~48 MB. My daily driver
> is complete overkill.
I think your kernel is probably more like 12.3MB of code. Your initrd
is larger than mine: I'd have to see inside to tell why, but no matter.
> Even my 2007 laptop has 2 GB of memory an a 1 GB boot partition/
> filesystem. Still overkill.
Overkill for what? I don't understand.
> I would gladly accept a 48 MB vmlinuz to be rid of initrd.img and its
> complexities.
>
> The resource hogs today are the apps, not the OS. Give me a KISS OS.
I can't understand why one would want to load all that kernel code
just to not use it. OK, for some reason you find the initrd complex.
(I don't any details about how freeBSD boots up as I haven't used it.)
I know you not interested in how it works or what it's for. I don't
see any sign that you've had difficulties in setting it up; it's just
there. It gets generated by the installer, and updated at various
times, like kernel upgrades. So what are you here for? To tell us
you're confused? To debate its name? To campaign for its abolition?
To throw mud? To say WTF to yourself again?
Cheers,
David.
Reply to: