On Friday, September 16, 2011 11:21:12 PM Pandu Poluan wrote:
> On Sep 16, 2011 11:00 PM, "Dale" <[email protected]> wrote:
> > Canek Peláez Valdés wrote:
> >> On Fri, Sep 16, 2011 at 5:29 AM, Pandu Poluan<[email protected]>  wrote:
> >>> Speaking of fsck, didn't someone lamented the fact that fsck can no
> 
> longer
> 
> >>> be statically linked, thus making initr* 'blew up' in size?
> >>> 
> >>> When more and more utilities go the non-statically-linked way...
> >>> congratulations! You now have an initr* that's practically a
> >>> cpio-ized
> >>> version of /
> >> 
> >> Now, common: that's an exaggeration. My dracut generated initramfs
> >> (with systemd, plymouth, udev, and I don't remember what many things
> >> more) is 5 Mb. That's a little less than my several-gigabytes /.
> >> 
> >> Regards.
> > 
> > Give it time.  Something will need /home on the root partition next. 
> > Like
> someone else posted, we are headed towards windows land with this.  I won't
> be surprised if /boot will have to be on / next too.
> 
> 
> Heh. If it's only limited to 'everything in /' it's still acceptable. MIGHTY
> annoying, and most likely an admin hell, but workable.

Would it? :)
If there would be a filesystem that reads from the "in-memory-part" and only 
accesses the disk for write-actions, then the / can be a ramdisk... :)

> Now, if everything needs to go into initr* (yes, I'm exaggerating, but...)

Like a live-dvd?

--
Joost

Reply via email to