Re: Re: uname -v shows no difference after buildkernel and installkernel etc
On Wed, 25 Aug 2004 13:32:19 +1000, August Simonelli [EMAIL PROTECTED] wrote: On Tue, 24 Aug 2004 22:11:47 -0500, Donald J. O'Neill [EMAIL PROTECTED] wrote: August, I've been following this thread today. It's very interesting. It appears to me, you mentioned your mistake in your first post. did a mergemaster and didn't accept any changes (it was a fresh system) rebooted and logged in Without accepting those changes, you kept what you had. It wasn't a This is what is confusing me about mergemaster. Isn't it just for comparing and deciding which config files one wants kept? That is, if I have a modifed pkgtools.conf or rc.conf or whatever I should be able to merge it up with the newly rebuilt system (which would have fresh versions of such files). Or I could just tell it to keep my old config files cause they have all my modifications. I do get that the new conf files may have changes we need, so merging is better. Now, why am i babbling about this? Cause when doing the mergemaster on this system my fingers got really fat and I'm not sure how I answered. Maybe this lead to my problem. Would that cause a) the wrong kernel to be installed or just b) the wrong kernel to be reported (ie did i screw up the update of the file that stores the kernel details?). Also, just for clarification, it WAS a fresh system, so, in theory, mergemaster would not have had any changes to make (except if it updates some text string somwhere that is the basis for the uname -v, as in my and b options above). Sorry if this is painfully ignorant; I'm learning slowly! :-) fresh system and needed the information from mergemaster. If you didn't clear out /usr/obj, it might be possible to rerun mergemaster and accept the changes. I would keep MYCUSTOM somewhere other than /root/kernels. Personally, I use /home/save4rebuild, and keep a copy of everything else I think I might need. I've had to reinstall /, /var, /tmp, /usr, but I always manage to keep /home safe. This seems to be what most people are saying ... and i think it makes more sense. I have officially adopted save4rebuild for my systems! :-) back to me rebuild (celeron 433 is a bit slw). well, the rebuild has worked fine. i think my symlinking was indeed messed up. i followed everyone's advice and didn't use a symlink; I kept my custom config in the same location as GENERIC and just copied it elsewhere for backup purposes. one last question for those tracking the this thread: can i now delete the custom kernel config file i created in /usr/src/sys/i386/src/ ? or does the system need it there to boot? i would guess not, more that the file is only used in building and installing ... thanks again for all the good advice ... august ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: uname -v shows no difference after buildkernel and installkernel etc
On Wed, Aug 25, 2004 at 04:40:50PM +1000, August Simonelli wrote: snip well, the rebuild has worked fine. i think my symlinking was indeed messed up. i followed everyone's advice and didn't use a symlink; I kept my custom config in the same location as GENERIC and just copied it elsewhere for backup purposes. one last question for those tracking the this thread: can i now delete the custom kernel config file i created in /usr/src/sys/i386/src/ ? or does the system need it there to boot? i would guess not, more that the file is only used in building and installing ... thanks again for all the good advice ... august Yes, you can safely delete the custom kernel config file if you want to. It is only used when the kernel is being built. Though, you'd do well to keep a copy of it somewhere for later reference, and it sounds as if you have already made a backup copy somewhere anyway. Nathan -- PGP Public Key: pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD8527E49 pgpKQ0kTcQHif.pgp Description: PGP signature
Re: Re: uname -v shows no difference after buildkernel and installkernel etc
On 2004-08-25 16:40, August Simonelli [EMAIL PROTECTED] wrote: well, the rebuild has worked fine. i think my symlinking was indeed messed up. i followed everyone's advice and didn't use a symlink; I kept my custom config in the same location as GENERIC and just copied it elsewhere for backup purposes. I usually keep my kernel configs in another location and symlink the one that is going to be used at build time under `/usr/src/sys/i386/conf'. Something like this: $ ( cd /usr/src/sys/i386/conf ; /bin/ls -lF CELERON SOLERO ) lrwxr-xr-x 1 root wheel 31 May 14 2003 CELERON@ - /a/kernconf/CELERON lrwxr-xr-x 1 root wheel 30 Aug 14 01:49 SOLERO@ - /a/kernconf/SOLERO one last question for those tracking the this thread: can i now delete the custom kernel config file i created in /usr/src/sys/i386/src/ ? or does the system need it there to boot? i would guess not, more that the file is only used in building and installing ... thanks again for all the good advice ... The kernel config file is used only at compile time, to build the new kernel image. You don't need to keep it if you don't want to rebuild a kernel with the same options. I would probably keep it around just in case I need to rebuild a kernel with the same set of options though. After all, it's just a text file: $ ls -ld /usr/src/sys/i386/conf/GENERIC -rw-r--r-- 1 root wheel - 10250 Aug 13 22:08 /usr/src/sys/i386/conf/GENERIC The extra time it's going to take to copy GENERIC, edit and recreate a custom config file isn't worth the trouble IMHO just to save 10-20 KB of disk space. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
uname -v shows no difference after buildkernel and installkernel etc
Hi all, I recently did the following: installed FreeBSD 5.2.1 from the iso cvsup'd the source (using tag=RELENG_5_2) followed section 19 of the handbook followed section 8 for the kernel rebuild and did a custom kernel (placing in /root/kernels and linking it, as per section 8.3) everything went well did a mergmaster and didn't accept any changes (it was a fresh system) rebooted and logged in did uname -v and got the same output as before all the above (Feb build date (5.2.1, right?), reference to GENERIC kernel not my custom kernel - my search of the list archives tells me it should show the local machine and a recent date in this output) Do I need to update somewhere to tell the system to boot the new kernel? If so, I totally missed that in the handbook (whoops). This also leads me to ask how one best confirms the system has changed? Thanks in advance for any help, August ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: uname -v shows no difference after buildkernel and installkernel etc
On Tue, Aug 24, 2004 at 08:20:51PM +1000, August Simonelli wrote: Hi all, I recently did the following: installed FreeBSD 5.2.1 from the iso cvsup'd the source (using tag=RELENG_5_2) followed section 19 of the handbook followed section 8 for the kernel rebuild and did a custom kernel (placing in /root/kernels and linking it, as per section 8.3) everything went well did a mergmaster and didn't accept any changes (it was a fresh system) rebooted and logged in did uname -v and got the same output as before all the above (Feb build date (5.2.1, right?), reference to GENERIC kernel not my custom kernel - my search of the list archives tells me it should show the local machine and a recent date in this output) Do I need to update somewhere to tell the system to boot the new kernel? If so, I totally missed that in the handbook (whoops). This also leads me to ask how one best confirms the system has changed? Thanks in advance for any help, August What does your symlink look like? So you put the newly built kernel in /root/kernels, then did something like?: # ln -s /root/kernels/mykernel /boot/kernel/kernel Nathan -- PGP Public Key: pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD8527E49 pgpFzABVfReyJ.pgp Description: PGP signature
Re: uname -v shows no difference after buildkernel and installkernel etc
August What does your symlink look like? So you put the newly built kernel in /root/kernels, then did something like?: # ln -s /root/kernels/mykernel /boot/kernel/kernel I followed the example in 8.3: # cd /usr/src/sys/i386/conf # mkdir /root/kernels # cp GENERIC /root/kernels/MYKERNEL # ln -s /root/kernels/MYKERNEL so now I have the following symlink: /usr/src/sys/i386/conf/MYCUSTOM - /root/kernels/MYCUSTOM and I built and installed with that as my KERNCONF value. I do still have GENERIC sitting in that directory. Does it use GENERIC first by default? Thanks again, august ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: uname -v shows no difference after buildkernel and installkernel etc
On Wed, Aug 25, 2004 at 08:32:48AM +1000, August Simonelli wrote: August What does your symlink look like? So you put the newly built kernel in /root/kernels, then did something like?: # ln -s /root/kernels/mykernel /boot/kernel/kernel I followed the example in 8.3: # cd /usr/src/sys/i386/conf # mkdir /root/kernels # cp GENERIC /root/kernels/MYKERNEL # ln -s /root/kernels/MYKERNEL so now I have the following symlink: /usr/src/sys/i386/conf/MYCUSTOM - /root/kernels/MYCUSTOM and I built and installed with that as my KERNCONF value. I do still have GENERIC sitting in that directory. Does it use GENERIC first by default? Thanks again, august I apologize, when you said: ... did a custom kernel (placing in /root/kernels ... I took it too literally, thinking that for some odd reason you had put the actual built (binary) kernel into /root/kernels and were symlinking from /boot/kernel to that directory, as opposed to simply putting the kernel config file there. However, is it just a typing mistake that you say you link to MYKERNEL, but you say the actual links points to MYCUSTOM? Also, what does an `ls -l /boot/kernel/kernel` reveal? Does the modification time coincide with the time you actually built your custom kernel? Nathan Side note - I once tried the advice to put custom kernel config files at a subdirectory of /root, but personally found this more confusing in the long run. In about 5 years of running FreeBSD and building custom kernels I have never deleted the entire /usr/src directory and subsequently realized I had blasted my only copy of a custom kernel config. I personally found it to be one more layer of indirection that hassled me from time to time, and it was one more thing I had to remember. If I were worried about the possibility of deleting my custom kernel config files accidentally while one day recursively removing /usr/src, then I would personally prefer to just copy that kernel config to some other location for safe keeping. It's just my personal preference. One of the things that is so distressing to me about certain GNU/Linux distros is all the levels of indirection and seeming complexity - symlinks pointing to symlinks and things of that nature. -- PGP Public Key: pgp.mit.edu:11371/pks/lookup?op=getsearch=0xD8527E49 pgpmAI2l9MNw5.pgp Description: PGP signature
Re: uname -v shows no difference after buildkernel and installkernel etc
I apologize, when you said: ... did a custom kernel (placing in /root/kernels ... I took it too literally, thinking that for some odd reason you had put the actual built (binary) kernel into /root/kernels and were symlinking from /boot/kernel to that directory, as opposed to simply putting the kernel config file there. However, is it just a typing mistake that you say you link to MYKERNEL, but you say the actual links points to Nah, just me being sloppy in my syntax; I got the names right (luckily) during the actual build (or did i ... interesting ...). MYCUSTOM? Also, what does an `ls -l /boot/kernel/kernel` reveal? Does the modification time coincide with the time you actually built your custom kernel? 94214 -r-xr-xr-x 1 root wheel 5940286 Feb 24 2004 /boot/kernel/kernel So it's the old one ... now, this is good, because on my other test system the kernel date is correct and uname -v is correct ... so, i've done something wrong and am gonna try it again ... i'm doing it at work and probably too distracted by my annoying users! :-) thanks for you help ... wish me luck on my second attempt! august ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: uname -v shows no difference after buildkernel and installkernel etc
August, I've been following this thread today. It's very interesting. It appears to me, you mentioned your mistake in your first post. did a mergemaster and didn't accept any changes (it was a fresh system) rebooted and logged in Without accepting those changes, you kept what you had. It wasn't a fresh system and needed the information from mergemaster. If you didn't clear out /usr/obj, it might be possible to rerun mergemaster and accept the changes. I would keep MYCUSTOM somewhere other than /root/kernels. Personally, I use /home/save4rebuild, and keep a copy of everything else I think I might need. I've had to reinstall /, /var, /tmp, /usr, but I always manage to keep /home safe. Don == On Tuesday 24 August 2004 08:08 pm, August Simonelli wrote: Does the modification time coincide with the time you actually built your custom kernel? 94214 -r-xr-xr-x 1 root wheel 5940286 Feb 24 2004 /boot/kernel/kernel So it's the old one ... now, this is good, because on my other test system the kernel date is correct and uname -v is correct ... so, i've done something wrong and am gonna try it again ... i'm doing it at work and probably too distracted by my annoying users! :-) thanks for you help ... wish me luck on my second attempt! august ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: uname -v shows no difference after buildkernel and installkernel etc
On Tue, 24 Aug 2004 22:11:47 -0500, Donald J. O'Neill [EMAIL PROTECTED] wrote: August, I've been following this thread today. It's very interesting. It appears to me, you mentioned your mistake in your first post. did a mergemaster and didn't accept any changes (it was a fresh system) rebooted and logged in Without accepting those changes, you kept what you had. It wasn't a This is what is confusing me about mergemaster. Isn't it just for comparing and deciding which config files one wants kept? That is, if I have a modifed pkgtools.conf or rc.conf or whatever I should be able to merge it up with the newly rebuilt system (which would have fresh versions of such files). Or I could just tell it to keep my old config files cause they have all my modifications. I do get that the new conf files may have changes we need, so merging is better. Now, why am i babbling about this? Cause when doing the mergemaster on this system my fingers got really fat and I'm not sure how I answered. Maybe this lead to my problem. Would that cause a) the wrong kernel to be installed or just b) the wrong kernel to be reported (ie did i screw up the update of the file that stores the kernel details?). Also, just for clarification, it WAS a fresh system, so, in theory, mergemaster would not have had any changes to make (except if it updates some text string somwhere that is the basis for the uname -v, as in my and b options above). Sorry if this is painfully ignorant; I'm learning slowly! :-) fresh system and needed the information from mergemaster. If you didn't clear out /usr/obj, it might be possible to rerun mergemaster and accept the changes. I would keep MYCUSTOM somewhere other than /root/kernels. Personally, I use /home/save4rebuild, and keep a copy of everything else I think I might need. I've had to reinstall /, /var, /tmp, /usr, but I always manage to keep /home safe. This seems to be what most people are saying ... and i think it makes more sense. I have officially adopted save4rebuild for my systems! :-) back to me rebuild (celeron 433 is a bit slw). august ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
