Re: Compiling new kernel fails on 7.0RC3
Did you comment device scbus and device da in your kernel config file, device umass require them Luke Jee Prevantage Inc. On 2008-2-25, at 上午6:34, E. J. Cerejo [EMAIL PROTECTED] wrote: After having a few problems with Fbsd 6.3 stable I decided to try 7.0 which impressed me right away because I noticed right away that it performed better on my computer. Now I decided to build my own custom kernel and after running the first command: %buildkernel KERNCONF=mykernel I get this error after it runs for about 15 minutes: linking kernel.debug vpo.o(.text+0x6b): In function `vpo_attach': /usr/src/sys/dev/ppbus/vpo.c:159: undefined reference to `cam_simq_alloc' vpo.o(.text+0xc2):/usr/src/sys/dev/ppbus/vpo.c:164: undefined reference to `cam_sim_alloc' vpo.o(.text+0xd1):/usr/src/sys/dev/ppbus/vpo.c:168: undefined reference to `cam_simq_free' vpo.o(.text+0xef):/usr/src/sys/dev/ppbus/vpo.c:172: undefined reference to `xpt_bus_register' vpo.o(.text+0x106):/usr/src/sys/dev/ppbus/vpo.c:173: undefined reference to `cam_sim_free' vpo.o(.text+0x14d):/usr/src/sys/dev/ppbus/vpo.c:196: undefined reference to `xpt_periph' vpo.o(.text+0x15c):/usr/src/sys/dev/ppbus/vpo.c:196: undefined reference to `xpt_create_path' vpo.o(.text+0x18f):/usr/src/sys/dev/ppbus/vpo.c:203: undefined reference to `xpt_setup_ccb' vpo.o(.text+0x1ac):/usr/src/sys/dev/ppbus/vpo.c:207: undefined reference to `xpt_action' vpo.o(.text+0x422): In function `vpo_action': /usr/src/sys/dev/ppbus/vpo.c:357: undefined reference to `xpt_done' vpo.o(.text+0x463):/usr/src/sys/dev/ppbus/vpo.c:383: undefined reference to `xpt_done' vpo.o(.text+0x48c):/usr/src/sys/dev/ppbus/vpo.c:396: undefined reference to `xpt_done' vpo.o(.text+0x4af):/usr/src/sys/dev/ppbus/vpo.c:402: undefined reference to `xpt_done' vpo.o(.text+0x4c3):/usr/src/sys/dev/ppbus/vpo.c:408: undefined reference to `xpt_done' vpo.o(.text+0x57a):/usr/src/sys/dev/ppbus/vpo.c:434: more undefined references to `xpt_done' follow udbp.o(.text+0x47): In function `ng_udbp_disconnect': /usr/src/sys/dev/usb/udbp.c:857: undefined reference to `ng_rmnode_self' udbp.o(.text+0xab): In function `udbp_detach': /usr/src/sys/dev/usb/udbp.c:450: undefined reference to `ng_rmnode_self' udbp.o(.text+0xc0):/usr/src/sys/dev/usb/udbp.c:452: undefined reference to `ng_unref_node' udbp.o(.text+0x742): In function `udbp_attach': /usr/src/sys/dev/usb/udbp.c:375: undefined reference to `ng_newtype' udbp.o(.text+0x770):/usr/src/sys/dev/usb/udbp.c:381: undefined reference to `ng_make_node_common' udbp.o(.text+0x7b7):/usr/src/sys/dev/usb/udbp.c:384: undefined reference to `ng_name_node' udbp.o(.text+0x7cc):/usr/src/sys/dev/usb/udbp.c:385: undefined reference to `ng_unref_node' udbp.o(.text+0x91f): In function `ng_udbp_rcvmsg': /usr/src/sys/dev/usb/udbp.c:705: undefined reference to `M_NETGRAPH_MSG' udbp.o(.text+0x9d9):/usr/src/sys/dev/usb/udbp.c:733: undefined reference to `ng_address_ID' udbp.o(.text+0x9f2):/usr/src/sys/dev/usb/udbp.c:733: undefined reference to `ng_snd_item' udbp.o(.text+0xa01):/usr/src/sys/dev/usb/udbp.c:733: undefined reference to `ng_free_item' udbp.o(.text+0xa0d):/usr/src/sys/dev/usb/udbp.c:734: undefined reference to `M_NETGRAPH_MSG' udbp.o(.text+0xa85): In function `udbp_in_transfer_cb': /usr/src/sys/dev/usb/udbp.c:531: undefined reference to `ng_package_data' udbp.o(.text+0xaaa):/usr/src/sys/dev/usb/udbp.c:531: undefined reference to `ng_address_hook' udbp.o(.text+0xabe):/usr/src/sys/dev/usb/udbp.c:531: undefined reference to `ng_snd_item' udbp.o(.text+0xc81): In function `ng_udbp_rmnode': /usr/src/sys/dev/usb/udbp.c:815: undefined reference to `ng_unref_node' udbp.o(.text+0xc94):/usr/src/sys/dev/usb/udbp.c:817: undefined reference to `ng_make_node_common' udbp.o(.text+0xccd):/usr/src/sys/dev/usb/udbp.c:820: undefined reference to `ng_name_node' udbp.o(.text+0xcde):/usr/src/sys/dev/usb/udbp.c:821: undefined reference to `ng_unref_node' udbp.o(.text+0xd25): In function `ng_udbp_rcvdata': /usr/src/sys/dev/usb/udbp.c:752: undefined reference to `ng_free_item' udbp.o(.rodata+0x20): In function `ng_udbp_disconnect': /usr/src/sys/dev/usb/udbp.c:851: undefined reference to `ng_parse_int32_type' udbp.o(.rodata+0x3c):/usr/src/sys/dev/usb/udbp.c:855: undefined reference to `ng_parse_struct_type' udbp.o(.rodata+0x64): In function `udbp_detach': /usr/src/sys/dev/usb/udbp.c:434: undefined reference to `ng_parse_int32_type' udbp.o(.rodata+0x70):/usr/src/sys/dev/usb/udbp.c:440: undefined reference to `ng_parse_int32_type' umass.o(.text+0x1c): In function `umass_cam_detach_sim': /usr/src/sys/dev/usb/umass.c:2694: undefined reference to `xpt_bus_deregister' umass.o(.text+0x38):/usr/src/sys/dev/usb/umass.c:2695: undefined reference to `cam_sim_free' umass.o(.text+0x40c): In function `umass_cam_quirk_cb': /usr/src/sys/dev/usb/umass.c:3236: undefined reference to `xpt_done' umass.o(.text+0x424):/usr/src/sys/dev/usb/umass.c:3245:
Re: Compiling new kernel fails on 7.0RC3
On Mon, 25 Feb 2008 00:00:40 +0100 Erik Trulsson [EMAIL PROTECTED] wrote: On Sun, Feb 24, 2008 at 05:34:20PM -0500, E. J. Cerejo wrote: After having a few problems with Fbsd 6.3 stable I decided to try 7.0 which impressed me right away because I noticed right away that it performed better on my computer. Now I decided to build my own custom kernel and after running the first command: %buildkernel KERNCONF=mykernel I get this error after it runs for about 15 minutes: linking kernel.debug vpo.o(.text+0x6b): In function `vpo_attach': /usr/src/sys/dev/ppbus/vpo.c:159: undefined reference to `cam_simq_alloc' vpo.o(.text+0xc2):/usr/src/sys/dev/ppbus/vpo.c:164: undefined reference to `cam_sim_alloc' [snip] umass.o(.text+0x24ba): In function `umass_cam_rescan': /usr/src/sys/dev/usb/umass.c:2644: undefined reference to `xpt_periph' umass.o(.text+0x24c9):/usr/src/sys/dev/usb/umass.c:2644: undefined reference to `xpt_create_path' umass.o(.text+0x24f7):/usr/src/sys/dev/usb/umass.c:2651: undefined reference to `xpt_setup_ccb' umass.o(.text+0x2514):/usr/src/sys/dev/usb/umass.c:2655: undefined reference to `xpt_action' [snip} Can anyone make anything out of this? My USB section on my kernel file looks like this: # USB support device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device usb # USB Bus (required) device udbp# USB Double Bulk Pipe devices device ugen# Generic device uhid# Human Interface Devices device ukbd# Keyboard device ulpt# Printer device umass # Disks/Mass storage - Requires scbus and da Well, do you have 'device scbus' and 'device da' in your kernel config? If not, I suggest you add them back. You were right! I deleted them by mistake! I just edited the kernel file and added them in, now do I have to clean any directory or just run the buildkernel KERNCONF=mykernel again? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiling new kernel fails on 7.0RC3
add device scbus or remove vpo On Sun, 24 Feb 2008, E. J. Cerejo wrote: After having a few problems with Fbsd 6.3 stable I decided to try 7.0 which impressed me right away because I noticed right away that it performed better on my computer. Now I decided to build my own custom kernel and after running the first command: %buildkernel KERNCONF=mykernel I get this error after it runs for about 15 minutes: linking kernel.debug vpo.o(.text+0x6b): In function `vpo_attach': /usr/src/sys/dev/ppbus/vpo.c:159: undefined reference to `cam_simq_alloc' vpo.o(.text+0xc2):/usr/src/sys/dev/ppbus/vpo.c:164: undefined reference to `cam_sim_alloc' vpo.o(.text+0xd1):/usr/src/sys/dev/ppbus/vpo.c:168: undefined reference to `cam_simq_free' vpo.o(.text+0xef):/usr/src/sys/dev/ppbus/vpo.c:172: undefined reference to `xpt_bus_register' vpo.o(.text+0x106):/usr/src/sys/dev/ppbus/vpo.c:173: undefined reference to `cam_sim_free' vpo.o(.text+0x14d):/usr/src/sys/dev/ppbus/vpo.c:196: undefined reference to `xpt_periph' vpo.o(.text+0x15c):/usr/src/sys/dev/ppbus/vpo.c:196: undefined reference to `xpt_create_path' vpo.o(.text+0x18f):/usr/src/sys/dev/ppbus/vpo.c:203: undefined reference to `xpt_setup_ccb' vpo.o(.text+0x1ac):/usr/src/sys/dev/ppbus/vpo.c:207: undefined reference to `xpt_action' vpo.o(.text+0x422): In function `vpo_action': /usr/src/sys/dev/ppbus/vpo.c:357: undefined reference to `xpt_done' vpo.o(.text+0x463):/usr/src/sys/dev/ppbus/vpo.c:383: undefined reference to `xpt_done' vpo.o(.text+0x48c):/usr/src/sys/dev/ppbus/vpo.c:396: undefined reference to `xpt_done' vpo.o(.text+0x4af):/usr/src/sys/dev/ppbus/vpo.c:402: undefined reference to `xpt_done' vpo.o(.text+0x4c3):/usr/src/sys/dev/ppbus/vpo.c:408: undefined reference to `xpt_done' vpo.o(.text+0x57a):/usr/src/sys/dev/ppbus/vpo.c:434: more undefined references to `xpt_done' follow udbp.o(.text+0x47): In function `ng_udbp_disconnect': /usr/src/sys/dev/usb/udbp.c:857: undefined reference to `ng_rmnode_self' udbp.o(.text+0xab): In function `udbp_detach': /usr/src/sys/dev/usb/udbp.c:450: undefined reference to `ng_rmnode_self' udbp.o(.text+0xc0):/usr/src/sys/dev/usb/udbp.c:452: undefined reference to `ng_unref_node' udbp.o(.text+0x742): In function `udbp_attach': /usr/src/sys/dev/usb/udbp.c:375: undefined reference to `ng_newtype' udbp.o(.text+0x770):/usr/src/sys/dev/usb/udbp.c:381: undefined reference to `ng_make_node_common' udbp.o(.text+0x7b7):/usr/src/sys/dev/usb/udbp.c:384: undefined reference to `ng_name_node' udbp.o(.text+0x7cc):/usr/src/sys/dev/usb/udbp.c:385: undefined reference to `ng_unref_node' udbp.o(.text+0x91f): In function `ng_udbp_rcvmsg': /usr/src/sys/dev/usb/udbp.c:705: undefined reference to `M_NETGRAPH_MSG' udbp.o(.text+0x9d9):/usr/src/sys/dev/usb/udbp.c:733: undefined reference to `ng_address_ID' udbp.o(.text+0x9f2):/usr/src/sys/dev/usb/udbp.c:733: undefined reference to `ng_snd_item' udbp.o(.text+0xa01):/usr/src/sys/dev/usb/udbp.c:733: undefined reference to `ng_free_item' udbp.o(.text+0xa0d):/usr/src/sys/dev/usb/udbp.c:734: undefined reference to `M_NETGRAPH_MSG' udbp.o(.text+0xa85): In function `udbp_in_transfer_cb': /usr/src/sys/dev/usb/udbp.c:531: undefined reference to `ng_package_data' udbp.o(.text+0xaaa):/usr/src/sys/dev/usb/udbp.c:531: undefined reference to `ng_address_hook' udbp.o(.text+0xabe):/usr/src/sys/dev/usb/udbp.c:531: undefined reference to `ng_snd_item' udbp.o(.text+0xc81): In function `ng_udbp_rmnode': /usr/src/sys/dev/usb/udbp.c:815: undefined reference to `ng_unref_node' udbp.o(.text+0xc94):/usr/src/sys/dev/usb/udbp.c:817: undefined reference to `ng_make_node_common' udbp.o(.text+0xccd):/usr/src/sys/dev/usb/udbp.c:820: undefined reference to `ng_name_node' udbp.o(.text+0xcde):/usr/src/sys/dev/usb/udbp.c:821: undefined reference to `ng_unref_node' udbp.o(.text+0xd25): In function `ng_udbp_rcvdata': /usr/src/sys/dev/usb/udbp.c:752: undefined reference to `ng_free_item' udbp.o(.rodata+0x20): In function `ng_udbp_disconnect': /usr/src/sys/dev/usb/udbp.c:851: undefined reference to `ng_parse_int32_type' udbp.o(.rodata+0x3c):/usr/src/sys/dev/usb/udbp.c:855: undefined reference to `ng_parse_struct_type' udbp.o(.rodata+0x64): In function `udbp_detach': /usr/src/sys/dev/usb/udbp.c:434: undefined reference to `ng_parse_int32_type' udbp.o(.rodata+0x70):/usr/src/sys/dev/usb/udbp.c:440: undefined reference to `ng_parse_int32_type' umass.o(.text+0x1c): In function `umass_cam_detach_sim': /usr/src/sys/dev/usb/umass.c:2694: undefined reference to `xpt_bus_deregister' umass.o(.text+0x38):/usr/src/sys/dev/usb/umass.c:2695: undefined reference to `cam_sim_free' umass.o(.text+0x40c): In function `umass_cam_quirk_cb': /usr/src/sys/dev/usb/umass.c:3236: undefined reference to `xpt_done' umass.o(.text+0x424):/usr/src/sys/dev/usb/umass.c:3245: undefined reference to `xpt_done' umass.o(.text+0x449): In function `umass_cam_sense_cb': /usr/src/sys/dev/usb/umass.c:3136: undefined reference to `xpt_done'
Re: Compiling new kernel fails on 7.0RC3
On Sun, Feb 24, 2008 at 05:34:20PM -0500, E. J. Cerejo wrote: After having a few problems with Fbsd 6.3 stable I decided to try 7.0 which impressed me right away because I noticed right away that it performed better on my computer. Now I decided to build my own custom kernel and after running the first command: %buildkernel KERNCONF=mykernel I get this error after it runs for about 15 minutes: linking kernel.debug vpo.o(.text+0x6b): In function `vpo_attach': /usr/src/sys/dev/ppbus/vpo.c:159: undefined reference to `cam_simq_alloc' vpo.o(.text+0xc2):/usr/src/sys/dev/ppbus/vpo.c:164: undefined reference to `cam_sim_alloc' [snip] umass.o(.text+0x24ba): In function `umass_cam_rescan': /usr/src/sys/dev/usb/umass.c:2644: undefined reference to `xpt_periph' umass.o(.text+0x24c9):/usr/src/sys/dev/usb/umass.c:2644: undefined reference to `xpt_create_path' umass.o(.text+0x24f7):/usr/src/sys/dev/usb/umass.c:2651: undefined reference to `xpt_setup_ccb' umass.o(.text+0x2514):/usr/src/sys/dev/usb/umass.c:2655: undefined reference to `xpt_action' [snip} Can anyone make anything out of this? My USB section on my kernel file looks like this: # USB support device uhci# UHCI PCI-USB interface device ohci# OHCI PCI-USB interface device usb # USB Bus (required) device udbp# USB Double Bulk Pipe devices device ugen# Generic device uhid# Human Interface Devices device ukbd# Keyboard device ulpt# Printer device umass # Disks/Mass storage - Requires scbus and da Well, do you have 'device scbus' and 'device da' in your kernel config? If not, I suggest you add them back. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compiling chrooted kernel makes drive unbootable
On 10/30/05, Dave [EMAIL PROTECTED] wrote: Hi, Thanks for your reply. I've not lost any data yet doing a reinstall would not be possible at this point. It's a matter of time which i don't have a lot of. As i said i've not lost data, on the drive, just the motherboard died, i think it overheated. The board that went was a pentium i think 2 or 3 600 mhz, the new system is a p4 2.4 ghz, both intel not one being amd they're both the same processor make. I thought i could just put the new board in, plug everything in, and go, i got an error that the processor type wasn't supported, What was that error? P4's features are a strict superset to those of P2 or P3. This error might have to do with something completely different like faulty hardware or damaged data. It was unnecessary to chroot, I think. Try the DESTDIR option: cd /usr/src make world DESTDIR=/path/to/mnt cd /usr/src make kernel DESTDIR=/path/to/mnt mergemaster -D /path/to/mnt You'll also need to set the disk active. Try something like fdisk -a /dev/ad1, but I'm not experienced in this wizardry. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compiling chrooted kernel makes drive unbootable
On 10/30/05, Dave [EMAIL PROTECTED] wrote: Hello, I've got a box that has died. The data on it is rather important and a reinstall is not feasible. I put the hard drive in a test box, mounted all the partitions of the previous drive under /mnt then did a chroot /mnt and compiled a generic kernel. The processor on this board is different so i felt i had to. The compilation and installation of the chrooted kernel went fine, putting the drive in the new system yields an unbootable drive. I've checked the data and kernel are there. Any ideas why this procedure didn't give me a bootable drive? Thanks. Dave. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Any more info, please? What exactly has died? Has any data been lost? Why did you have to recompile the kernel? Did you recompile the world, too? How different are the processors on the dead system, the one you've recompiled on and the new one? You can always run a fresh install without formatting your drives and thus losing only some system configuration files. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: compiling the kernel
I have a 4.9R installed on my system. ANd I want to patch the existing system. I have downloaded those patches, I have done exactly as is written in those advisories. And the make command fails (I use the traditional way of compiling). Please, could you take a look at my kernel config file? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com V Description: V ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiling the kernel
On Saturday 06 November 2004 14:19, Valerian Galeru wrote: Could there appear any problems if the /usr/src/sys tree is not completely updated(I mean I started updating , but I didn`t finish) ? If you mean: can cvsup be stopped, and started again? the answer is yes it can. If you mean that you started upgrading your source, but then decided against rebuilding, then the answer is that it doesn't matter that your source is inconsistent, until you build. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Compiling the kernel
Could there appear any problems if the /usr/src/sys tree is not completely updated(I mean I started updating , but I didn`t finish) ? __ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiling the kernel
On Sat, Nov 06, 2004 at 06:19:26AM -0800, Valerian Galeru wrote: Could there appear any problems if the /usr/src/sys tree is not completely updated(I mean I started updating , but I didn`t finish) ? Yes, of course. Kris pgpeADVJXcFms.pgp Description: PGP signature
Re: compiling a kernel on a different machine
Rowdy told a big fish story including the following on 12/23/2003 1:31 PM: Greetings, My attempts to compile a (5.1-RELEASE) kernel on a very old PC take around 5 hours (of compile time), while a much faster machine sits by idle. It would be great to be able to compile the kernel on the faster machine and transfer it to the older machine. Would I be correct in thinking that the simplest way to do this would be to execute the compile AND the install on the fast PC, then copy the /boot/kernel directory from the fast PC to the old PC? I realise I would need to rename /boot/kernel.old back to /boot/kernel on the fast PC so it would boot again. Or is there a better way without disrupting /boot on the fast PC? Apologies if this get posted as html. I'm trying a new mail client and may not have it configured correctly yet. Anyway, there is a better way. I briefly looked through the TOC of the handbook but could not find the page I was looking for. However, I know I've seen it somewhere. The basic procedure is to have your fast machine do the make buildworld and make buildkernel steps and then mount /usr/src and /usr/obj from the fast machine to the slow machine. Then do the make installkernel and make installworld steps on the slow machine, thus copying the files that were built on the fast machine. Maybe someone else will post the link to the detailed steps that I can't find at the moment. HTH a little, Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compiling a kernel on a different machine
On Tuesday 23 December 2003 21:31, Rowdy wrote: Greetings, My attempts to compile a (5.1-RELEASE) kernel on a very old PC take around 5 hours (of compile time), while a much faster machine sits by idle. It would be great to be able to compile the kernel on the faster machine and transfer it to the older machine. Would I be correct in thinking that the simplest way to do this would be to execute the compile AND the install on the fast PC, then copy the /boot/kernel directory from the fast PC to the old PC? I realise I would need to rename /boot/kernel.old back to /boot/kernel on the fast PC so it would boot again. Or is there a better way without disrupting /boot on the fast PC? Set the DESTDIR environment variable to the directory where the new kernel should go into. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compiling a kernel on a different machine
On Tue, Dec 23, 2003 at 02:31:38PM -0800, Drew Tomlinson wrote: Rowdy told a big fish story including the following on 12/23/2003 1:31 PM: My attempts to compile a (5.1-RELEASE) kernel on a very old PC take around 5 hours (of compile time), while a much faster machine sits by idle. It would be great to be able to compile the kernel on the faster machine and transfer it to the older machine. Or is there a better way without disrupting /boot on the fast PC? Anyway, there is a better way. I briefly looked through the TOC of the handbook but could not find the page I was looking for. However, I know I've seen it somewhere. I think that page that you're thinking of has undergone some changes. I would refer to it myself when doing buildworld on a faster machine, then installing to the slower, target. The newer pagee, if I'm correct, is here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/small-lan.html Essentially it's the same procedure, but the step by step instructions for getting the nfs mount is gone. An editorial decision reflecting the notion that this wasn't the place for an nfs howto(?). OK, hang on. Here it is in an older handbook I have. Appearing as: 19.4.15.5. Can I use one machine as a master to upgrade lots of machines (NFS)?, a question at the bottom of the handbook's makeworld.html. That could likely be searched for and retrieved somewhere in this vast internet of ours, -- Christmas Cheers, Sean ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compiling a kernel on a different machine
On Tue, Dec 23, 2003 at 06:04:09PM -0800, Sean Ellis wrote: On Tue, Dec 23, 2003 at 02:31:38PM -0800, Drew Tomlinson wrote: OK, hang on. Here it is in an older handbook I have. Appearing as: 19.4.15.5. Can I use one machine as a master to upgrade lots of machines (NFS)?, a question at the bottom of the handbook's makeworld.html.i Oops, I'm sorry. Having fired off that last post I've realized that this is not the page that I thought I was remembering ; ) The christmas cheers part stands, however, -- Sean ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compiling a kernel on a different machine
Sean Ellis wrote: On Tue, Dec 23, 2003 at 06:04:09PM -0800, Sean Ellis wrote: On Tue, Dec 23, 2003 at 02:31:38PM -0800, Drew Tomlinson wrote: OK, hang on. Here it is in an older handbook I have. Appearing as: 19.4.15.5. Can I use one machine as a master to upgrade lots of machines (NFS)?, a question at the bottom of the handbook's makeworld.html.i Oops, I'm sorry. Having fired off that last post I've realized that this is not the page that I thought I was remembering ; ) I can't think of a better way to install a kernel than to copy /boot/kernel to the new machine or set the DESTDIR environment var. If you're installing world then it's a different story, but kernels are fairly self contained. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiling the kernel
On Mon, 1 Dec 2003 06:12:53 -0800 (PST) Valerian Galeru [EMAIL PROTECTED] wrote: I want to build a new kernel. I have edit the GENERIC file (like is written into the documentation). And when i run /usr/sbin/config /root/kernels/MYKERNEL(this is my kernel) i get a lot of errors Command not found. What is made wrong??? Try to provide us more info as we can not guess what you console is printing. Copy / paste the output. Also uname -a output. If you want you could join the [EMAIL PROTECTED] mailling list. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiling the kernel
I want to build a new kernel. I have edit the GENERIC file (like is written into the documentation). And when i run /usr/sbin/config /root/kernels/MYKERNEL(this is my kernel) i get a lot of errors Command not found. What is made wrong??? First of all, I presume you really used one line as /usr/sbin/config /root/kernels/MYKERNEL Not two separate command lines as it appears in your message. Secondly, did you make your copy of GENERIC in to the same directory as GENERIC?That is the best idea. Third, on any of the FreeBSD systems I have worked on there is no /root/kernels directory. (If this is something new with 5.x I am off on this as I haven't built a 5.x yet) The kernel config files are in: /usr/src/sys/i386/conf (or did you set up some homebrew link?) So, I would expect that there is a file: /usr/src/sys/i386/conf/MYKERNEL and the best way to run things is to cd /usr/src/sys/i386/conf cp GENERIC MYKERNEL vi MYKERNEL(make whatever changes you need and write+exit vi) /usr/sbin/config MYKERNEL cd ../../compile/MYKERNEL make depend make [make install] Only if you want the present kernel replaced Now if you have CVSUPed and etc, then you will want to follow those instructions instead of merely building a kernel. Doing it the above way is only if you are just changing the kernel config and then recompiling. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiling the kernel
What happened to make buildkernel KERNCONF=KERNEL make installkernel KERNCONF=KERNEL did this change in newer version or something? I thought the above was the new way of rebuilding a kernel. Am I not up to date? - Original Message - From: Jerry McAllister [EMAIL PROTECTED] To: Valerian Galeru [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, December 01, 2003 9:13 AM Subject: Re: Compiling the kernel I want to build a new kernel. I have edit the GENERIC file (like is written into the documentation). And when i run /usr/sbin/config /root/kernels/MYKERNEL(this is my kernel) i get a lot of errors Command not found. What is made wrong??? First of all, I presume you really used one line as /usr/sbin/config /root/kernels/MYKERNEL Not two separate command lines as it appears in your message. Secondly, did you make your copy of GENERIC in to the same directory as GENERIC?That is the best idea. Third, on any of the FreeBSD systems I have worked on there is no /root/kernels directory. (If this is something new with 5.x I am off on this as I haven't built a 5.x yet) The kernel config files are in: /usr/src/sys/i386/conf (or did you set up some homebrew link?) So, I would expect that there is a file: /usr/src/sys/i386/conf/MYKERNEL and the best way to run things is to cd /usr/src/sys/i386/conf cp GENERIC MYKERNEL vi MYKERNEL(make whatever changes you need and write+exit vi) /usr/sbin/config MYKERNEL cd ../../compile/MYKERNEL make depend make [make install] Only if you want the present kernel replaced Now if you have CVSUPed and etc, then you will want to follow those instructions instead of merely building a kernel. Doing it the above way is only if you are just changing the kernel config and then recompiling. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiling the kernel
What happened to make buildkernel KERNCONF=KERNEL make installkernel KERNCONF=KERNEL did this change in newer version or something? I thought the above was the new way of rebuilding a kernel. Am I not up to date? I think this is newer and what I posted is the old tried and true way if you are only changing kernel config stuff and not any source. jerry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiling the kernel
On Mon, Dec 01, 2003 at 09:34:43AM -0600, Kenzo wrote: What happened to make buildkernel KERNCONF=KERNEL make installkernel KERNCONF=KERNEL did this change in newer version or something? I thought the above was the new way of rebuilding a kernel. Am I not up to date? No, what you describe is the new way. However, the old way still works for those that want to use it. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
RE: Compiling the kernel
I'm a newbie. I built the kernel the first time yesterday There is a new way to build the kernel documented here http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-b uilding.html It worked for me. I do not really sure what the difference is. Hope it helps -sundeep -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Valerian Galeru Sent: Monday, December 01, 2003 7:43 PM To: [EMAIL PROTECTED] Subject: Compiling the kernel I want to build a new kernel. I have edit the GENERIC file (like is written into the documentation). And when i run /usr/sbin/config /root/kernels/MYKERNEL(this is my kernel) i get a lot of errors Command not found. What is made wrong??? __ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
