nanobsd Post: 302717223

Sponsored Content

Operating Systems BSD nanobsd Post 302717223 by DGPickett on Wednesday 17th of October 2012 05:56:24 PM

10-17-2012

Registered User

Code:

The configuration file consists of configuration options, which override the default values. The most important directives are: NANO_NAME  Name of build (used to construct the workdir names).
 NANO_SRC  Path to the source tree used to build the image.
 NANO_KERNEL  Name of kernel configuration file used to build kernel.
 CONF_BUILD  Options passed to the buildworld stage of the build.
 CONF_INSTALL  Options passed to the installworld stage of the build.
 CONF_WORLD  Options passed to both the buildworld and the installworld stage of the build.
 FlashDevice  Defines what type of media to use. Check the FlashDevice.sub file for more details.

A list of the WITHOUT_'s (used to be NO_'s) and their meaning is here:Man Page for src.conf (all Section 0) - The UNIX and Linux Forums

I suppose picobsd is smaller.

This User Gave Thanks to DGPickett For This Post:

DGPickett

View Public Profile for DGPickett

Find all posts by DGPickett

We Also Found This Discussion For You

1. BSD

nanobsd problem

hi i have some problems with nanobsd still. whether i set lots of WITHOUT s in CONF_WORLD or a few WITHOUT s , the image file's volume is about 600MB ... what should i do in order to have a very light image ?? thanks ...

LEARN ABOUT MOJAVE

perlfreebsd5.18

PERLFREEBSD(1)						 Perl Programmers Reference Guide					    PERLFREEBSD(1)

NAME

       perlfreebsd - Perl version 5 on FreeBSD systems

DESCRIPTION

       This document describes various features of FreeBSD that will affect how Perl version 5 (hereafter just Perl) is compiled and/or runs.

   FreeBSD core dumps from readdir_r with ithreads
       When perl is configured to use ithreads, it will use re-entrant library calls in preference to non-re-entrant versions.	There is a bug in
       FreeBSD's "readdir_r" function in versions 4.5 and earlier that can cause a SEGV when reading large directories. A patch for FreeBSD libc
       is available (see http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/30631 ) which has been integrated into FreeBSD 4.6.

   $^X doesn't always contain a full path in FreeBSD
       perl sets $^X where possible to a full path by asking the operating system. On FreeBSD the full path of the perl interpreter is found by
       using "sysctl" with "KERN_PROC_PATHNAME" if that is supported, else by reading the symlink /proc/curproc/file. FreeBSD 7 and earlier has a
       bug where either approach sometimes returns an incorrect value (see http://www.freebsd.org/cgi/query-pr.cgi?pr=35703 ).	In these cases
       perl will fall back to the old behaviour of using C's argv[0] value for $^X.

AUTHOR

       Nicholas Clark <nick@ccl4.org>, collating wisdom supplied by Slaven Rezic and Tim Bunce.

       Please report any errors, updates, or suggestions to perlbug@perl.org.

perl v5.18.2							    2013-11-04							    PERLFREEBSD(1)

We Also Found This Discussion For You

1. BSD

nanobsd problem

Discussion started by: turner

LEARN ABOUT MOJAVE

perlfreebsd5.18