Between 6.2 and 7 /boot has grown from 45 MB to 114 MB. That poses a significant issue for those of us who have been running production systems for many years. I have the root partition set to 200 MB which has been more than enough. Its no longer usable. 7.0 beta will not install properly as it runs out of space. Basically this forces you to repartition the drive. That requires an extensive down time for servers. Far beyond what I can justify to users. Also, 7.0 beta3 has login compiled with libutil.so.5 and libc.so.6 neither of which are on the distribution cd. I had to point those to the existing libs to get login to work.
On Thu, Dec 06, 2007 at 05:32:41PM -0800 I heard the voice of Doug Hardie, and lo! it spake thus:> > Between 6.2 and 7 /boot has grown from 45 MB to 114 MB. That poses > a significant issue for those of us who have been running production > systems for many years. I have the root partition set to 200 MB > which has been more than enough.Well, 200 meg has been pretty tight and rather small for a couple versions now. My 194 meg / partition set up in 3-CURRENT days is pretty tight these days 8-} rm'ing away all the .symbols files from the kernel dir did the trick for me, though (I did have to do it in another terminal while `installkernel` was running to get it to complete... there's probably a flag I can pass to make): Filesystem Size Used Avail Capacity Mounted on /dev/da0s1a 194M 65M 113M 36% / -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
Doug Hardie wrote:> Between 6.2 and 7 /boot has grown from 45 MB to 114 MB. That poses a > significant issue for those of us who have been running production > systems for many years. I have the root partition set to 200 MB which > has been more than enough. Its no longer usable. 7.0 beta will not > install properly as it runs out of space. Basically this forces you to > repartition the drive. That requires an extensive down time for > servers. Far beyond what I can justify to users.src/UPDATING: 20060118: This actually occured some time ago, but installing the kernel now also installs a bunch of symbol files for the kernel modules. This increases the size of /boot/kernel to about 67Mbytes. You will need twice this if you will eventually back this up to kernel.old on your next install. If you have a shortage of room in your root partition, you should add -DINSTALL_NODEBUG to your make arguments or add INSTALL_NODEBUG="yes" to your /etc/make.conf. -- WBR, Andrey V. Elsukov
On Dec 7, 2007, at 02:25, Andrey V. Elsukov wrote:> Doug Hardie wrote: >> Between 6.2 and 7 /boot has grown from 45 MB to 114 MB. That poses >> a significant issue for those of us who have been running >> production systems for many years. I have the root partition set >> to 200 MB which has been more than enough. Its no longer usable. >> 7.0 beta will not install properly as it runs out of space. >> Basically this forces you to repartition the drive. That requires >> an extensive down time for servers. Far beyond what I can justify >> to users. > > src/UPDATING: > 20060118: > This actually occured some time ago, but installing the kernel > now also installs a bunch of symbol files for the kernel modules. > This increases the size of /boot/kernel to about 67Mbytes. You > will need twice this if you will eventually back this up to > kernel.old on your next install. > If you have a shortage of room in your root partition, you > should add -DINSTALL_NODEBUG to your make arguments or add > INSTALL_NODEBUG="yes" to your /etc/make.conf.Thanks. That must have been after 6.2 came out as I never had that occur with it. Anyway, since I am installing from CD I discovered that during the install, VT4 has a working shell that lets you cd to / boot/GENERIC and delete the symbol files before the disk overflows. I will have to add the line above to make.conf though as I do minor updates from the source.