freebsd builds

Subhro subhro.kar at
Fri Sep 3 09:25:22 PDT 2004

On Fri, 3 Sep 2004 07:48:17 -0400, Andrew <tacoboy24 at> wrote:
> Hi,
> Building kernels I am comfortable with. I have been doing it a while for SUSE.
> Now I wanted to try freebsd 5.1.  So I have some questions about freebsd
> builds.
> Some of the questions may sound dumb but I want to make sure I don't do
> something catostrophic based on a past experience with SUSE. So...
> make clean - simply cleans objects, executables in the work area /usr/src.
> Nothing else
> make buildkernel - simply builds the kernel, support modules, and so on in the
> work area only /usr/src. The biilt kernel is located in
> /usr/obj/usr/src/....../kernel.
> make installkernel - once this is done, that which was in the work area is
> placed in working directories of the installed system.

Bang on target till here....

> For SUSE I used GRUB or lilo to write the boot block. For freebsd I use
> bsdlabel?

Nopes bsdlabel is for something else. By default the new kernel gets
installed. No need to update anything in the boot block. If you ned to
boot the old kernel then Hit any other key when it says:

hit [Enter] key to boot kernel

Type unload
then boot /kernel.old

And you will be back with your previous kernel.

> I am targeting the kernel for a Soekris 4511. The 4511 has a national
> semiconductor ethernet chip. On SUSE I add the configuration parameter
> NATSEMI=Y to build the ethernet driver. What is the configruation parameter
> for Freebsd ethernet driver.

Refer to /usr/src/sys/i386/conf/NOTES and /usr/src/sys/NOTES if you
are on 5.* and /usr/src/sys/i386/conf/LINT for the driver.

> I was reading a notes file on a technique of building a jail sandbox. The
> sandbox becomes something like freebsd inside freebsd. The purpose was to
> allow someone to make major modifications to the kernel and not affect the
> working operating system components.

Well hard luck. Jail is something like FBSD inside FBSD but it is not
completely FBSD inside FBSD. They run the same kernel and not two
separate copies of it. What you need is vmware.

> Per the notes file, the sandbox is set by:
> perform a customer install.
> During the install change the installation location to point to the sandbox.
> chroot <sandbox>
> Do a build in the sandbox
> I create the folder, changed the destintation to be the sandbox in the
> installation options, and installed freebsd in the sandbox folder. Then I:
> chroot to the sandbox
> To verify my sandbox install was correct, I tried to rebuild the GENERIC
> kernel in the sandbox.
> An error occured in makefile.inc1 line 139. That line has a make command
> dealing with CPUTYPE. The error was its value not being zero.
> I then exited the sandbox (command shell) and reexecuted the make command to
> rebuild the GENERIC kernel in the standard /usr/src location. It worked fine.
> So it is not the installation kit.
> The problem is something I have not  done or did improperly in creating the
> sandbox. Thoughts.

I guess you know the reason by now

> A


Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091

More information about the freebsd-questions mailing list