Date: Tue, 19 Oct 2004 08:10:29 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Rob <spamrefuse@yahoo.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: I deleted /stand/, but I need it again for diskless boot... Message-ID: <20041019151029.GA17285@odin.ac.hmc.edu> In-Reply-To: <4174AE86.5000906@yahoo.com> References: <20041013172834.81984.qmail@web54008.mail.yahoo.com> <65140.208.4.77.15.1098123461.squirrel@208.4.77.15> <41746CC6.4030407@yahoo.com> <200410190345.20487.josemi@freebsd.jazztel.es> <417475E2.8020202@gamersimpact.com> <4174AE86.5000906@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 19, 2004 at 03:04:54PM +0900, Rob wrote: > Ryan Sommers wrote: > >Jose M Rodriguez wrote: > > > >>If You try to path /etc/rc.d/initdiskless, try not remove *.cpio.gz > >> > >>expand using /stand, but add *.tar expand using /bin/pax. > >> > >>You may also try some auto detection and use what is present between=20 > >>/stand/cpio, /stand/gzip, /rescue/tar, /rescue/gzip ... > >> > >>Don't try moving gzip/libgzip from /usr to rootfs. It's really a big=20 > >>change. > >> > >/rescue/* aren't the right tools for the job in my opinion. Neither are= =20 > >/stand/*. I posted this to arch@ [1] and between that and this thread,= =20 > >among others on current@, the overwhelming majority of responses have=20 > >been to get rid of /stand. I'm not sure I understand your argument for= =20 > >leaving /stand as part of the root filesystem; other than as you say=20 > >your 250gb drives don't mind the extra 3.5mb. In my opinion it's useless= =20 > >for both diskless and regular systems, with the exception of 2% of it's= =20 > >space. It's not updated as part of world, which means no bug fixes get= =20 > >populated to it. It's a crunchgen binary which means trying to fix small= =20 > >bugs in single programs either means rebuilding the binary or replacing= =20 > >that hardlink with an individual binary. >=20 > Sorry, I have changed my mind concerning patching my 5.3 system wrt. > this /stand vs. /rescue issue. I'd rather wait until this discussion > is resolved and moreover, until 5.3 has become STABLE and 6.0 has > become CURRENT. >=20 > For now, I will populate the /conf/base directory with the plain files > (not using zipped cpio-archives), in which case I do not need /stand. >=20 > The disk space used is then: > 324K using etc and var as cpio.gz archives in /conf/base > 1.8M using etc and var as plain files in /conf/base > 2.3M /stand >=20 > *.cpio.gz + /stand =3D 2.6M > plain files - /stand =3D 1.8M >=20 > For now, with 5.3, I'll go for the plain files without /stand. > I can wait until 6-Stable for this to get reduced to 324K :). You also may want to remember that the plain files have one hugh advantage, they can be modified directly rather then having to rebuild the tarball every time. Most of the time, I can't see how the cpio archives would be worth the trouble. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --DocE+STaALJfprDB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBdS5kXY6L6fI4GtQRAiZ9AJ9HwA/9EXgcv3gM5WvqxjnQ3fP0eQCdGQF0 Q6SAglAEycg0Pd9yXJQRctI= =HGGA -----END PGP SIGNATURE----- --DocE+STaALJfprDB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041019151029.GA17285>