Re: securelevel problems
On Wed, Nov 05, 2003 at 07:06:42PM +1300, Jonathan Chen wrote: On Tue, Nov 04, 2003 at 08:25:57PM +, Wayne Pascoe wrote: [...] however a make installworld is still failing with: Stop in /usr/src/include. *** Error code 1 It's debatable whether this is a securelevel problem. I would remove /usr/obj/* and rebuild again. I've tried this, and I'm now having a whole new range of problems... A make buildworld no longer works. I've redone my cvsup, removed /usr/obj and done make clean in /usr/src I then run make buildworld, and after quite some time, I get: cc -O -pipe -march=i686 -march=pentiumpro -I. -static -DIN_GCC \ -DHAVE_CONFIG_H -DPREFIX=\/usr\ \ -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools \ -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools \ -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc \ -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config \ -D__FBSDID=__RCSID -c \ /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/gengenrtl.c \ cc -O -pipe -march=i686 -march=pentiumpro -I. -static -DIN_GCC \ -DHAVE_CONFIG_H -DPREFIX=\/usr\ \ -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools \ -I/usr/src/gnu/usr.bin/cc/cc_tools/../cc_tools \ -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc \ -I/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config \ -D__FBSDID=__RCSID -o gengenrtl gengenrtl.o \ ./gengenrtl genrtl.h genrtl.c *** Signal 4 Stop in /usr/src/gnu/usr.bin/cc/cc_tools. *** Error code 1 Stop in /usr/src. *** Error code 1 The above has been linewrapped for courtesy sake.. If I cd to /usr/src/gnu/usr.bin/cc/cc_tools and do make, it starts building ok, but then I get ./genattr /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config/i386/i386.md insn-attr.h Illegal instruction (core dumped) *** Error code 132 (Apologies for no line wrapping, but I couldn't wrap it and keep context clear) The machine is a Pentium 166, and my make.conf has the following: CPUTYPE=i586 CFLAGS= -O -pipe -march=i586 NO_BIND=true NO_I4B= true NO_FORTRAN= true NO_LPR= true NO_SENDMAIL=true NO_X= true NOGAMES=true NOLIBC_R= true NOPROFILE= true NO_OBJC=true IPFW2=TRUE I'm getting close to just migrating everything off of this machine and re-installing from scratch, but as we've successfully upgraded every other box in the farm to 4.9, I'd really like to try and fix this :( Regards, -- Wayne Pascoe There are no stupid questions, only stupid people. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: securelevel problems
Wayne Pascoe [EMAIL PROTECTED] writes: I'm trying to upgrade a 4.7-RELEASE machine to 4.9. The make buildworld has gone ok, but installworld failed. You should have built and installed the kernel in between, then rebooted under the new kernel. If this was not what you did, please read the Handbook section on Building the World (carefully) before trying again. At first, it appeared that this was because the machine was running in securelevel 1. I had the following in /etc/rc.conf: kern_securelevel_enable=YES kern_securelevel=1 I changed that to kern_securelevel_enable=NO kern_securelevel=-1 and rebooted the machine. sysctl -a | grep secure shows kern.securelevel: -1 however a make installworld is still failing with: Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. The actual errors were a few lines earlier. If they don't make sense to you, please post them for the rest of us to help you there. I then tried touching my kernel, which also fails, with: # touch kernel touch: kernel: Operation not permitted Right. The schg flag is normally set on the kernel to keep it from being modified. I'm at a bit of a loss as to how to proceed as the only thing I could think to do was to disable securelevel in /etc/rc.conf :( Right. With a raised securelevel, you can't change the file flags. With the securelevel kept low, you can change them, but you need to do so (with chflags(1)). [make installkernel normally does this for you] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: securelevel problems
On Tue, 4 Nov 2003 20:25:57 + Wayne Pascoe [EMAIL PROTECTED] wrote: Hi all, I'm trying to upgrade a 4.7-RELEASE machine to 4.9. The make buildworld has gone ok, but installworld failed. At first, it appeared that this was because the machine was running in securelevel 1. I had the following in /etc/rc.conf: kern_securelevel_enable=YES kern_securelevel=1 I changed that to kern_securelevel_enable=NO kern_securelevel=-1 and rebooted the machine. sysctl -a | grep secure shows kern.securelevel: -1 however a make installworld is still failing with: Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I then tried touching my kernel, which also fails, with: # touch kernel touch: kernel: Operation not permitted I'm at a bit of a loss as to how to proceed as the only thing I could think to do was to disable securelevel in /etc/rc.conf :( does anyone know what I may have missed or how I might rectify this issue ? Thanks, -- Wayne Pascoe 'tis far easier to get forgiveness than it is to get permission - probably someone famous, but more often, my Dad. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You must reset all the flags. Securelevel=-1 itself does not toggle off (invalidate) any flags. So, setting flags at securelevel=-1 still makes some sense. horio shoichi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
securelevel problems
Hi all, I'm trying to upgrade a 4.7-RELEASE machine to 4.9. The make buildworld has gone ok, but installworld failed. At first, it appeared that this was because the machine was running in securelevel 1. I had the following in /etc/rc.conf: kern_securelevel_enable=YES kern_securelevel=1 I changed that to kern_securelevel_enable=NO kern_securelevel=-1 and rebooted the machine. sysctl -a | grep secure shows kern.securelevel: -1 however a make installworld is still failing with: Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I then tried touching my kernel, which also fails, with: # touch kernel touch: kernel: Operation not permitted I'm at a bit of a loss as to how to proceed as the only thing I could think to do was to disable securelevel in /etc/rc.conf :( does anyone know what I may have missed or how I might rectify this issue ? Thanks, -- Wayne Pascoe 'tis far easier to get forgiveness than it is to get permission - probably someone famous, but more often, my Dad. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: securelevel problems
On Tue, Nov 04, 2003 at 08:25:57PM +, Wayne Pascoe wrote: [...] however a make installworld is still failing with: Stop in /usr/src/include. *** Error code 1 It's debatable whether this is a securelevel problem. I would remove /usr/obj/* and rebuild again. I then tried touching my kernel, which also fails, with: # touch kernel touch: kernel: Operation not permitted This is 'cos there is an immutable flag set on this file. ie: no one gets to alter it. chflags(1) for more info. Cheers. -- Jonathan Chen [EMAIL PROTECTED] -- Build a man a fire, and he'll be warm for a day. Set a man on fire, and he'll be warm for the rest of his life. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
