Re: dumb question 'Bad system call' after make world
On Fri, 21 Nov 2003, Barney Wolff wrote: Does make world build a kernel? I didn't think so, and OP's message indicates that make world is all he did. I suspect re-install is the best answer now. Will somebody please tell me when make world is ever correct in the environment of the last several years? I've been unable to understand its continued existence as a target. I'd call it hysterical raisins, but there are some decomposed targets, which I use regularly: buildworld buildkernel installworld installkernel -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dumb question 'Bad system call' after make world
Hello, On Fri, Nov 21, 2003 at 09:44:17PM -0500, Barney Wolff wrote: Does make world build a kernel? I didn't think so, and OP's message indicates that make world is all he did. I suspect re-install is the best answer now. Yes, make world does not build or install kernels. I'd also go for reinstall, provided the OP has not yet put a lot of work into customising the install... Will somebody please tell me when make world is ever correct in the environment of the last several years? I've been unable to understand its continued existence as a target. One of it's last hideouts seems to be the make release target... -- Regards: Szilveszter ADAM Budapest Hungary ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dumb question 'Bad system call' after make world
On Fri, 21 Nov 2003, Barney Wolff wrote: Will somebody please tell me when make world is ever correct in the environment of the last several years? I've been unable to understand its continued existence as a target. From my normal world-building script: DESTDIR=/c/z/root \ MAKEOBJDIRPREFIX=/c/z/obj \ time -l make -s world /tmp/world.out 21 Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dumb question 'Bad system call' after make world
On Sat, Nov 22, 2003 at 11:42:04PM +1100, Bruce Evans wrote: On Fri, 21 Nov 2003, Barney Wolff wrote: Will somebody please tell me when make world is ever correct in the environment of the last several years? I've been unable to understand its continued existence as a target. From my normal world-building script: DESTDIR=/c/z/root \ MAKEOBJDIRPREFIX=/c/z/obj \ time -l make -s world /tmp/world.out 21 Oh, so it's only correct when you're not really installing world on the system you're building on? Would replacing this with ( make buildworld make installworld ) really be a hardship? Must we continue to invite innocents to clobber their systems? -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: dumb question 'Bad system call' after make world
From: Barney Wolff [mailto:[EMAIL PROTECTED] Sent: Saturday, November 22, 2003 1:14 PM To: Bruce Evans Cc: [EMAIL PROTECTED] Subject: Re: dumb question 'Bad system call' after make world On Sat, Nov 22, 2003 at 11:42:04PM +1100, Bruce Evans wrote: On Fri, 21 Nov 2003, Barney Wolff wrote: Will somebody please tell me when make world is ever correct in the environment of the last several years? I've been unable to understand its continued existence as a target. From my normal world-building script: DESTDIR=/c/z/root \ MAKEOBJDIRPREFIX=/c/z/obj \ time -l make -s world /tmp/world.out 21 Oh, so it's only correct when you're not really installing world on the system you're building on? Would replacing this with ( make buildworld make installworld ) really be a hardship? Must we continue to invite innocents to clobber their systems? For interest, in case this happens to someone else, i 'fixed' it by booting from the mini iso disk, inserting disk 2 (live), going to a shell, and copying all of /bin, /usr/bin, /usr/lib, /usr/libexec, /lib over to the hd, rebooting, and then doing the rest of the normal steps. --don ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dumb question 'Bad system call' after make world
On Fri, 21 Nov 2003, Don Bowman wrote: So i have a machine freshly installed from 5.1 mini iso. I did a cvs co of latest current sources, and accidentally did a 'make world' instead of 'make buildworld'. Now i just get 'Bad system call' when i try to do anything. i need to get the correct kernel on there, does anyone have a suggestion for how to fix this? --don Probably the easiest thing will be to start over with a fresh 5.1 install, then follow the steps in UPDATING of make buildworld make kernel reboot to single user make installworld mergemaster reboot Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dumb question 'Bad system call' after make world
On Fri, 21 Nov 2003, Don Bowman wrote: So i have a machine freshly installed from 5.1 mini iso. I did a cvs co of latest current sources, and accidentally did a 'make world' instead of 'make buildworld'. Now i just get 'Bad system call' when i try to do anything. i need to get the correct kernel on there, does anyone have a suggestion for how to fix this? If you have it, boot off of the mini iso, pull down and burn CD 2, then use the fixit facility to start a fixit shell with teh CD. From there manually install the new kernel (it'll be in /usr/obj/usr/src/sys/KERNELNAME/kernel) and boot from it. From there you should be able to finish the installworld. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dumb question 'Bad system call' after make world
On Fri, Nov 21, 2003 at 05:35:59PM -0800, Doug White wrote: On Fri, 21 Nov 2003, Don Bowman wrote: So i have a machine freshly installed from 5.1 mini iso. I did a cvs co of latest current sources, and accidentally did a 'make world' instead of 'make buildworld'. Now i just get 'Bad system call' when i try to do anything. i need to get the correct kernel on there, does anyone have a suggestion for how to fix this? If you have it, boot off of the mini iso, pull down and burn CD 2, then use the fixit facility to start a fixit shell with teh CD. From there manually install the new kernel (it'll be in /usr/obj/usr/src/sys/KERNELNAME/kernel) and boot from it. From there you should be able to finish the installworld. Does make world build a kernel? I didn't think so, and OP's message indicates that make world is all he did. I suspect re-install is the best answer now. Will somebody please tell me when make world is ever correct in the environment of the last several years? I've been unable to understand its continued existence as a target. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A quick, dumb, question...
George V. Neville-Neil wrote: Is there a single document, or small set of documents, that describes getting started kernel hacking on FreeBSD? How about a set of URLs? I would like something that tells me about (in no particular order) 1) debugging over the serial line, and remote debugging in general Use the handbook description. The only caveat is that you need to tell it to break to gdb before you start the GDB on the debugging system, or you'll get serial synchornization errors; this isn't documented in the handbook, but it is nevertheless true. 2) Building for 5.0 on 4.x (if possible though I suspect I should not do this) Avoid doing this if you can. If you can't, then use a chroot'ed image of CDROM #2 to do the job. You should also copy in the ps, w, /kernel, etc. and other libkvm-using programs if you plan on using them, and make sure that you copy in /dev (in 5.0, there would be a devfs, and you don't have onw) and mount the procfs in the chroot environment. 3) Best practices for dealing with my own versions of files while also working with cvsup. Keep a seperate repository of your own stuff. Some people will tell you to trust the magic numbers for revision tags, which are poorly documented in a couple of places, but really, you want to maintain full revision history, and have a lesser problem merging, so you're better off importing the kernel (if you are hacking the kernel), and anything else you are hacking, into a private repository, by bringing it in on a vendor branch. See the CVS FAQ. If you also want to risk CVSup with the magic tags, look for the documentation that John Polstra has written (I think there is also a Daemon News article, FWIW). Those are a good start for now. BTW If none exists I will try to write this up in the form of a tutorial and post it at some point. If you want to write it up as something like Building a FreeBSD derived System or something like that, it would make a good Dameon News article. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
A quick, dumb, question...
Is there a single document, or small set of documents, that describes getting started kernel hacking on FreeBSD? How about a set of URLs? I would like something that tells me about (in no particular order) 1) debugging over the serial line, and remote debugging in general 2) Building for 5.0 on 4.x (if possible though I suspect I should not do this) 3) Best practices for dealing with my own versions of files while also working with cvsup. Those are a good start for now. BTW If none exists I will try to write this up in the form of a tutorial and post it at some point. Thanks, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A quick, dumb, question...
Date: Sun, 17 Feb 2002 17:43:55 -0800 From: George V. Neville-Neil [EMAIL PROTECTED] Is there a single document, or small set of documents, that describes getting started kernel hacking on FreeBSD? How about a set of URLs? I would like something that tells me about (in no particular order) 1) debugging over the serial line, and remote debugging in general You might start with http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html. (Sorry about the line-wrapping.) 2) Building for 5.0 on 4.x (if possible though I suspect I should not do this) Sure: set up a 4.x system, clear /usr/src, populate /usr/src with the HEAD of the tree (cvs co), then follow the instructions in /usr/src/UPDATING. 3) Best practices for dealing with my own versions of files while also working with cvsup. What I do is use CVSup to mirror the CVS repository (vs. a working directory), then use cvs update (well, after an initial cvs co) to update the sources. I do this within script, so I get a record of what was done, and I can grep the typescript file for various weirdnesses, such as conflicts to be resolved. (I also do the make buildworld friends under script, so if something weird happens during the build, I don't need to record it: that's been done. Well, if it's a panic, that may not capture everything -- but a serial console can be helpful in that case.) (I've been tracking both -STABLE and -CURRENT daily, on each of a build machine and my laptop, for several months. I've also been testing patches for folks, so being able to revert patches or generate new ones is a definite advantage of having the CVS repository handy.) Those are a good start for now. Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A dumb question.
"Arthur H. Johnson II" [EMAIL PROTECTED] wrote: When I try to compile the kernel, I get this error at the end: ../../pci/if_xl.c ../../pci/if_xl.c:133: miibus_if.h: No such file or directory *** Error code 1 Stop in /usr/src/sys/compile/ARTHUR. You must first build a kernel first. *** Error code 1 Stop in /usr/src/sys/compile/ARTHUR. What happened to this file? You may have to add: controller miibus0 to you kernel config file. See LINT for details. -- Nathan AhlstromFreeBSD: http://www.FreeBSD.org/ [EMAIL PROTECTED] PGP Key ID: 0x67BC9D19 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: A dumb question.
Thanks. Arthur H. Johnson II http://www.linuxberg.com Linuxberg Manager [EMAIL PROTECTED] On Wed, 1 Sep 1999, Nathan Ahlstrom wrote: "Arthur H. Johnson II" [EMAIL PROTECTED] wrote: When I try to compile the kernel, I get this error at the end: ../../pci/if_xl.c ../../pci/if_xl.c:133: miibus_if.h: No such file or directory *** Error code 1 Stop in /usr/src/sys/compile/ARTHUR. You must first build a kernel first. *** Error code 1 Stop in /usr/src/sys/compile/ARTHUR. What happened to this file? You may have to add: controller miibus0 to you kernel config file. See LINT for details. -- Nathan AhlstromFreeBSD: http://www.FreeBSD.org/ [EMAIL PROTECTED] PGP Key ID: 0x67BC9D19 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
