head	1.6;
access;
symbols
	RELENG_8_4:1.6.0.2
	RELENG_9_1_0_RELEASE:1.3.16.1.4.2
	RELENG_9_1:1.3.16.1.0.4
	RELENG_9_1_BP:1.3.16.1
	RELENG_8_3_0_RELEASE:1.3.10.1.8.1
	RELENG_8_3:1.3.10.1.0.8
	RELENG_8_3_BP:1.3.10.1
	RELENG_9_0_0_RELEASE:1.3.16.1.2.1
	RELENG_9_0:1.3.16.1.0.2
	RELENG_9_0_BP:1.3.16.1
	RELENG_9:1.3.0.16
	RELENG_9_BP:1.3
	RELENG_7_4_0_RELEASE:1.3.14.1
	RELENG_8_2_0_RELEASE:1.3.10.1.6.1
	RELENG_7_4:1.3.0.14
	RELENG_7_4_BP:1.3
	RELENG_8_2:1.3.10.1.0.6
	RELENG_8_2_BP:1.3.10.1
	RELENG_8_1_0_RELEASE:1.3.10.1.4.1
	RELENG_8_1:1.3.10.1.0.4
	RELENG_8_1_BP:1.3.10.1
	RELENG_7_3_0_RELEASE:1.3.12.1
	RELENG_7_3:1.3.0.12
	RELENG_7_3_BP:1.3
	RELENG_8_0_0_RELEASE:1.3.10.1.2.1
	RELENG_8_0:1.3.10.1.0.2
	RELENG_8_0_BP:1.3.10.1
	RELENG_8:1.3.0.10
	RELENG_8_BP:1.3
	RELENG_7_2_0_RELEASE:1.3.8.1
	RELENG_7_2:1.3.0.8
	RELENG_7_2_BP:1.3
	RELENG_7_1_0_RELEASE:1.3.6.1
	RELENG_6_4_0_RELEASE:1.1.2.1.6.1
	RELENG_7_1:1.3.0.6
	RELENG_7_1_BP:1.3
	RELENG_6_4:1.1.2.1.0.6
	RELENG_6_4_BP:1.1.2.1
	RELENG_7_0_0_RELEASE:1.3
	RELENG_6_3_0_RELEASE:1.1.2.1
	RELENG_7_0:1.3.0.4
	RELENG_7_0_BP:1.3
	RELENG_6_3:1.1.2.1.0.4
	RELENG_6_3_BP:1.1.2.1
	RELENG_7:1.3.0.2
	RELENG_7_BP:1.3
	RELENG_6_2_0_RELEASE:1.1.2.1
	RELENG_6_2:1.1.2.1.0.2
	RELENG_6_2_BP:1.1.2.1
	RELENG_6:1.1.0.2;
locks; strict;
comment	@# @;


1.6
date	2012.11.17.01.54.12;	author svnexp;	state Exp;
branches
	1.6.2.1;
next	1.5;

1.5
date	2012.06.07.09.14.28;	author bz;	state Exp;
branches;
next	1.4;

1.4
date	2011.12.30.00.04.11;	author uqs;	state Exp;
branches;
next	1.3;

1.3
date	2006.11.01.01.25.49;	author julian;	state Exp;
branches
	1.3.2.1
	1.3.6.1
	1.3.8.1
	1.3.10.1
	1.3.12.1
	1.3.14.1
	1.3.16.1;
next	1.2;

1.2
date	2006.10.30.19.47.05;	author julian;	state Exp;
branches;
next	1.1;

1.1
date	2006.09.20.22.24.17;	author julian;	state Exp;
branches
	1.1.2.1;
next	;

1.6.2.1
date	2012.11.17.01.54.12;	author svnexp;	state dead;
branches;
next	1.6.2.2;

1.6.2.2
date	2013.03.28.13.05.59;	author svnexp;	state Exp;
branches;
next	;

1.3.2.1
date	2012.11.17.08.08.17;	author svnexp;	state Exp;
branches;
next	;

1.3.6.1
date	2008.11.25.02.59.29;	author kensmith;	state Exp;
branches;
next	;

1.3.8.1
date	2009.04.15.03.14.26;	author kensmith;	state Exp;
branches;
next	;

1.3.10.1
date	2009.08.03.08.13.06;	author kensmith;	state Exp;
branches
	1.3.10.1.2.1
	1.3.10.1.4.1
	1.3.10.1.6.1
	1.3.10.1.8.1;
next	1.3.10.2;

1.3.10.2
date	2012.11.17.10.37.15;	author svnexp;	state Exp;
branches;
next	;

1.3.10.1.2.1
date	2009.10.25.01.10.29;	author kensmith;	state Exp;
branches;
next	;

1.3.10.1.4.1
date	2010.06.14.02.09.06;	author kensmith;	state Exp;
branches;
next	;

1.3.10.1.6.1
date	2010.12.21.17.09.25;	author kensmith;	state Exp;
branches;
next	;

1.3.10.1.8.1
date	2012.03.03.06.15.13;	author kensmith;	state Exp;
branches;
next	1.3.10.1.8.2;

1.3.10.1.8.2
date	2012.11.17.08.25.48;	author svnexp;	state Exp;
branches;
next	;

1.3.12.1
date	2010.02.10.00.26.20;	author kensmith;	state Exp;
branches;
next	;

1.3.14.1
date	2010.12.21.17.10.29;	author kensmith;	state Exp;
branches;
next	1.3.14.2;

1.3.14.2
date	2012.11.17.08.17.41;	author svnexp;	state Exp;
branches;
next	;

1.3.16.1
date	2011.09.23.00.51.37;	author kensmith;	state Exp;
branches
	1.3.16.1.2.1
	1.3.16.1.4.1;
next	1.3.16.2;

1.3.16.2
date	2012.11.17.11.37.36;	author svnexp;	state Exp;
branches;
next	;

1.3.16.1.2.1
date	2011.11.11.04.20.22;	author kensmith;	state Exp;
branches;
next	1.3.16.1.2.2;

1.3.16.1.2.2
date	2012.11.17.08.37.33;	author svnexp;	state Exp;
branches;
next	;

1.3.16.1.4.1
date	2012.08.05.23.54.33;	author kensmith;	state Exp;
branches;
next	1.3.16.1.4.2;

1.3.16.1.4.2
date	2012.11.17.08.48.24;	author svnexp;	state Exp;
branches;
next	;

1.1.2.1
date	2006.09.28.21.09.07;	author julian;	state Exp;
branches
	1.1.2.1.6.1;
next	1.1.2.2;

1.1.2.2
date	2012.11.17.07.45.31;	author svnexp;	state Exp;
branches;
next	;

1.1.2.1.6.1
date	2008.10.02.02.57.24;	author kensmith;	state Exp;
branches;
next	;


desc
@@


1.6
log
@Switching exporter and resync
@
text
@# $FreeBSD: head/tools/tools/tinybsd/README 236707 2012-06-07 09:14:28Z bz $

- TinyBSD

You must read this to know how to build embedded systems with TinyBSD.

- TinyBSD files

TinyBSD's creation conf files are available under /usr/src/tools/tools/tinybsd/conf 
and the script are available under /usr/src/tools/tools/tinybsd/tinybsd.

The system has been entirely based on the ease of image customization from
PicoBSD, and the compilation script based on NanoBSD's.

# ls /usr/src/tools/tools/tinybsd/conf
bridge/   default/  firewall/ minimal/  vpn/      wireless/  wrap/

We have these six pre configured images to build. On each directory we have 3 
main files in there. Let's see what each of them are:

# ls /usr/src/tools/tools/tinybsd/conf/default
TINYBSD            etc/               tinybsd.basefiles

TINYBSD: Just like PicoBSD had its kernel previously compiled, we call ours
TINYBSD.

# more TINYBSD

machine         i386
cpu             I486_CPU
cpu             I586_CPU
cpu             I686_CPU
ident           TINYBSD

#To statically compile in device wiring instead of /boot/device.hints
#hints          "GENERIC.hints"         #Default places to look for devices.
...

As you can see, it's a kernel file identical to your system's, leaving only
the task of enabling or disabling options, according to your needs.

tinybsd.basefiles: Just like PicoBSD had its crunch.conf file to define which
files we'd want the new system to have, in this one we'll have all files to be
put into our embedded system, already having all available files for running
the system well. Put in or take out the files you need according to your
needs. Let's see it:

# more tinybsd.basefiles
# contents of ${WORKDIR}/boot
boot/boot0
boot/boot1
boot/boot2
boot/defaults/loader.conf
boot/device.hints
...
# contents of ${WORKDIR}/bin
bin/[:bin/test
bin/cat
bin/chflags
bin/chio
bin/chmod
...

And so on. In case you'd want to add the binary "setkey", sitting on
/usr/sbin, you'd only need to add the following line inside the /usr/sbin part
of the file, like this:

usr/sbin/pw
usr/sbin/pwd_mkdb
usr/sbin/setkey

tinybsd.ports: Here you can add the applications from the FreeBSD Ports Collection 
which you want TinyBSD ports system to install in your embedded system. You whould 
list one application per line, mentioning its category and name, like the examples:
www/mini_httpd
net-mgmt/rate 

etc/: This is the directory where you can put your custom /etc configuration.

# ls /usr/src/tools/tools/tinybsd/tinybsd
tinybsd

tinybsd: This is the script that builds the entire system. You'll hardly
need to modify it at all. The idea is for it to create a temporary work
directory for it to create the entire system tree. Once done, it'll copy all
files listed in tinybsd.basefiles to this tree, then it'll compile a new
kernel using the definitions in the TINYBSD file, and finally copy the library
dependencies the binaries will have. We'll then populate /etc on that
temporary tree and put in a few important default configurations inside on
/usr/src/tools/tools/tinybsd/conf/YOURCHOICE/etc/ like rc.conf, fstab and others.

Finally, we create an empty image, according to your media's specifications,
passed on to the script on the command line, and copy the entire temporary
work tree into the image mounted on /mnt.

- Running TinyBSD

Now that we know how it works, it's time for us to build our own image. Let's
do that step-by-step.

1) Choose what pre-configured image you want.

2) Edit the TINYBSD kernel file and add/remove all options you'll need.

3) Edit the tinybsd.basefiles file and add/remove all binaries you'll need on
your system.

4) Copy all your /etc configuration which you want to conf/YOURIMAGE/etc/.

5) Gather the right information on your destination media. To do that, plug in
the device on the system and fetch the information using diskinfo(8):

# diskinfo -v /dev/ad2
ad2
        512             # sectorsize
        20060135424     # mediasize in bytes (19G)
        39179952        # mediasize in sectors
        38869           # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.

To create my image, I'll need to know the media size in sectors, Heads
according to firmware and Sectors according to firmware. Optionally, you may
define the name of the generated image's file, but if you don't, it'll be
named tinybsd.bin. Now that we have gathered these informations through
diskinfo, all we need to do is run tinybsd. Remember that it has 3
parameters plus 1 optional, and if you don't pass on the required ones, the
script will warn you about it:

# /usr/src/tools/tools/tinybsd/tinybsd
Woops!
   Usage: tinybsd <mediasize in sectors> <heads according to firmware> 
   <sectors according to firmware> <conf> [<tinybsd image name>]

   Example: tinybsd 62592 4 32

	or

   /usr/src/tools/tools/tinybsd/tinybsd 62592 4 32 wireless

   Run diskinfo(8) -v against your CF device to get correct information
   about your disk.

Passing on the parameters correctly:

# /usr/src/tools/tools/tinybsd/tinybsd 39179952 16 63 wireless
Creating directory hierarchy...
./bin missing (created)
./boot missing (created)
./boot/defaults missing (created)
./boot/kernel missing (created)
./boot/modules missing (created)
./dev missing (created)
./etc missing (created)
...

In the end, we have the generated tinybsd.bin image. Now we have to copy it to
its final destination:

# dd if=/usr/src/tools/tools/tinybsd/tinybsd.bin of=/dev/ad2

Boot up your new embedded system and log on it. If you're ever going to modify
it, you must first remount the root slice as read-write, as it operates by
default on read-only mode, saving disk writes and preventing data-loss in case
of power failures. To mount it for read-write, use mount:

# mount -u -o rw /

Once you're done, return it to read-only mode:

# mount -u -o ro /

The first thing you need to do after logging for the first time, is to set a
root password. By default, it's created with no root password.

If you run df(1), you'll see the following partitions:

# df
Filesystem 1K-blocks  Used Avail Capacity  Mounted on
/dev/ad0a      29359 19446  7565    72%    /
devfs              1     1     0   100%    /dev
procfs             4     4     0   100%    /proc
/dev/md0        3694   114  3286     3%    /var
/dev/md1        19566    6 17996     0%    /tmp 

As you can see, /var and /tmp are mounted on /dev/md0 and /dev/md1
respectively, using memory disk devices. That's because both /var and /tmp are
write-intensive, and as our system works mostly on read-only mode, we'd suffer
with writing problems there, so the memory disk approach works fine. On the
other hand, whenever you reboot the system, those directories' contents
(including logs on /var/log) will be lost. If you need to keep the contents of
those directories, I suggest you to always upload them to another box.

The configuration line that fires up the system script to create /var as a
memory disk partition is "varmfs="YES"", inside
/etc/rc.conf. Besides mounting /var as a memory disk device, it also populates
its tree with the necessary subdirectories. Initially, /var is created on
memory using only 32MB of space, and that's usually enough. Although, if you
find it necessary to tweak that configuration, you may edit this line of
/etc/rc.conf:

varsize="32m"

Change 32m to whatever value you see fit (in MBytes). Take care of not using
your entire memory for /var.

- Ports and TinyBSD

You can also install ports on the new system via ports. For that, you'll need
to set the PREFIX environment variable to the image's destination path. Let's
assume you want to install apache on the newly-created image. For that, I'd do
this:

# mdconfig -a -t vnode -f /usr/src/tools/tools/tinybsd/tinybsd.bin -u 0

That uses mdconfig to enable the memory disk 0.

# mount /dev/md0a /mnt

Now we've mounted the image on the temporary directory /mnt. Let's then
install apache via ports:

# cd /usr/ports/www/apache13
# make install PREFIX=/mnt/usr/local
===>  Vulnerability check disabled
>> apache_1.3.31.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
>> Attempting to fetch from http://www.apache.org/dist/httpd/.
...
      This port has installed the following startup scripts which may cause
      these network services to be started at boot time.
/mnt/usr/local/etc/rc.d/apache.sh
....

Once the install is finished, let's verify that apache has indeed been
properly installed under our /mnt directory:

# cd /mnt/usr/local/sbin
# ls -lga httpd
-rwxr-xr-x  1 root  wheel  252439 Jul 14 15:31 httpd

Our software has been successfully installed. You must notice that at the end
of the install, it shows the full path for the PREFIX variable we passed it.
The problem with that is that at boot-time, your system is going to look for
it under /mnt instead of /usr. So we need to edit apache's initialization
script under /usr/local/etc/rc.d (apache.sh) and remove all instances of
"/mnt" in it.

WARNING: A very important thing to care about are dependencies. Before
installing anything, check to see if it has any dependencies, and that you'll
have enough disk space on the destination system for both the application
you're installing and its dependencies.

- Script download

TinyBSD is still a project under heavy development, both the script itself and
its documentation. 

In case you'd like to try or use the BETA version of the script, feel free to
download it from the project's official site at http://code.google.com/p/tinybsd/.
@


1.6.2.1
log
@file README was added on branch RELENG_8_4 on 2013-03-28 13:05:59 +0000
@
text
@d1 259
@


1.6.2.2
log
@## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/248810
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
@
text
@a0 259
# $FreeBSD: releng/8.4/tools/tools/tinybsd/README 163854 2006-11-01 01:25:51Z julian $

- TinyBSD

You must read this to know how to build embedded systems with TinyBSD.

- TinyBSD files

TinyBSD's creation conf files are available under /usr/src/tools/tools/tinybsd/conf 
and the script are available under /usr/src/tools/tools/tinybsd/tinybsd.

The system has been entirely based on the ease of image customization from
PicoBSD, and the compilation script based on NanoBSD's.

# ls /usr/src/tools/tools/tinybsd/conf
bridge/   default/  firewall/ minimal/  vpn/      wireless/  wrap/

We have these six pre configured images to build. On each directory we have 3 
main files in there. Let's see what each of them are:

# ls /usr/src/tools/tools/tinybsd/conf/default
TINYBSD            etc/               tinybsd.basefiles

TINYBSD: Just like PicoBSD had its kernel previously compiled, we call ours
TINYBSD.

# more TINYBSD

machine         i386
cpu             I486_CPU
cpu             I586_CPU
cpu             I686_CPU
ident           TINYBSD

#To statically compile in device wiring instead of /boot/device.hints
#hints          "GENERIC.hints"         #Default places to look for devices.
...

As you can see, it's a kernel file identical to your system's, leaving only
the task of enabling or disabling options, according to your needs.

tinybsd.basefiles: Just like PicoBSD had its crunch.conf file to define which
files we'd want the new system to have, in this one we'll have all files to be
put into our embedded system, already having all available files for running
the system well. Put in or take out the files you need according to your
needs. Let's see it:

# more tinybsd.basefiles
# contents of ${WORKDIR}/boot
boot/boot0
boot/boot1
boot/boot2
boot/defaults/loader.conf
boot/device.hints
...
# contents of ${WORKDIR}/bin
bin/[:bin/test
bin/cat
bin/chflags
bin/chio
bin/chmod
...

And so on. In case you'd want to add the binary "setkey", sitting on
/usr/sbin, you'd only need to add the following line inside the /usr/sbin part
of the file, like this:

usr/sbin/pw
usr/sbin/pwd_mkdb
usr/sbin/setkey

tinybsd.ports: Here you can add the applications from the FreeBSD Ports Collection 
which you want TinyBSD ports system to install in your embedded system. You whould 
list one application per line, mentioning its category and name, like the examples:
www/mini_httpd
net-mgmt/rate 

etc/: This is the directory where you can put your custom /etc configuration.

# ls /usr/src/tools/tools/tinybsd/tinybsd
tinybsd

tinybsd: This is the script that builds the entire system. You'll hardly
need to modify it at all. The idea is for it to create a temporary work
directory for it to create the entire system tree. Once done, it'll copy all
files listed in tinybsd.basefiles to this tree, then it'll compile a new
kernel using the definitions in the TINYBSD file, and finally copy the library
dependencies the binaries will have. We'll then populate /etc on that
temporary tree and put in a few important default configurations inside on
/usr/src/tools/tools/tinybsd/conf/YOURCHOICE/etc/ like rc.conf, fstab and others.

Finally, we create an empty image, according to your media's specifications,
passed on to the script on the command line, and copy the entire temporary
work tree into the image mounted on /mnt.

- Running TinyBSD

Now that we know how it works, it's time for us to build our own image. Let's
do that step-by-step.

1) Choose what pre-configured image you want.

2) Edit the TINYBSD kernel file and add/remove all options you'll need.

3) Edit the tinybsd.basefiles file and add/remove all binaries you'll need on
your system.

4) Copy all your /etc configuration wich you want to conf/YOURIMAGE/etc/.

5) Gather the right information on your destination media. To do that, plug in
the device on the system and fetch the information using diskinfo(8):

# diskinfo -v /dev/ad2
ad2
        512             # sectorsize
        20060135424     # mediasize in bytes (19G)
        39179952        # mediasize in sectors
        38869           # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.

To create my image, I'll need to know the media size in sectors, Heads
according to firmware and Sectors according to firmware. Optionally, you may
define the name of the generated image's file, but if you don't, it'll be
named tinybsd.bin. Now that we have gathered these informations through
diskinfo, all we need to do is run tinybsd. Remember that it has 3
parameters plus 1 optional, and if you don't pass on the required ones, the
script will warn you about it:

# /usr/src/tools/tools/tinybsd/tinybsd
Woops!
   Usage: tinybsd <mediasize in sectors> <heads according to firmware> 
   <sectors according to firmware> <conf> [<tinybsd image name>]

   Example: tinybsd 62592 4 32

	or

   /usr/src/tools/tools/tinybsd/tinybsd 62592 4 32 wireless

   Run diskinfo(8) -v against your CF device to get correct information
   about your disk.

Passing on the parameters correctly:

# /usr/src/tools/tools/tinybsd/tinybsd 39179952 16 63 wireless
Creating directory hierarchy...
./bin missing (created)
./boot missing (created)
./boot/defaults missing (created)
./boot/kernel missing (created)
./boot/modules missing (created)
./dev missing (created)
./etc missing (created)
...

In the end, we have the generated tinybsd.bin image. Now we have to copy it to
its final destination:

# dd if=/usr/src/tools/tools/tinybsd/tinybsd.bin of=/dev/ad2

Boot up your new embedded system and log on it. If you're ever going to modify
it, you must first remount the root slice as read-write, as it operates by
default on read-only mode, saving disk writes and preventing data-loss in case
of power failures. To mount it for read-write, use mount:

# mount -u -o rw /

Once you're done, return it to read-only mode:

# mount -u -o ro /

The first thing you need to do after logging for the first time, is to set a
root password. By default, it's created with no root password.

If you run df(1), you'll see the following partitions:

# df
Filesystem 1K-blocks  Used Avail Capacity  Mounted on
/dev/ad0a      29359 19446  7565    72%    /
devfs              1     1     0   100%    /dev
procfs             4     4     0   100%    /proc
/dev/md0        3694   114  3286     3%    /var
/dev/md1        19566    6 17996     0%    /tmp 

As you can see, /var and /tmp are mounted on /dev/md0 and /dev/md1
respectively, using memory disk devices. That's because both /var and /tmp are
write-intensive, and as our system works mostly on read-only mode, we'd suffer
with writing problems there, so the memory disk approach works fine. On the
other hand, whenever you reboot the system, those directories' contents
(including logs on /var/log) will be lost. If you need to keep the contents of
those directories, I suggest you to always upload them to another box.

The configuration line that fires up the system script to create /var as a
memory disk partition is "varmfs="YES"", inside
/etc/rc.conf. Besides mounting /var as a memory disk device, it also populates
its tree with the necessary subdirectories. Initially, /var is created on
memory using only 32MB of space, and that's usually enough. Although, if you
find it necessary to tweak that configuration, you may edit this line of
/etc/rc.conf:

varsize="32m"

Change 32m to whatever value you see fit (in MBytes). Take care of not using
your entire memory for /var.

- Ports and TinyBSD

You can also install ports on the new system via ports. For that, you'll need
to set the PREFIX environment variable to the image's destination path. Let's
assume you want to install apache on the newly-created image. For that, I'd do
this:

# mdconfig -a -t vnode -f /usr/src/tools/tools/tinybsd/tinybsd.bin -u 0

That uses mdconfig to enable the memory disk 0.

# mount /dev/md0a /mnt

Now we've mounted the image on the temporary directory /mnt. Let's then
install apache via ports:

# cd /usr/ports/www/apache13
# make install PREFIX=/mnt/usr/local
===>  Vulnerability check disabled
>> apache_1.3.31.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
>> Attempting to fetch from http://www.apache.org/dist/httpd/.
...
      This port has installed the following startup scripts which may cause
      these network services to be started at boot time.
/mnt/usr/local/etc/rc.d/apache.sh
....

Once the install is finished, let's verify that apache has indeed been
properly installed under our /mnt directory:

# cd /mnt/usr/local/sbin
# ls -lga httpd
-rwxr-xr-x  1 root  wheel  252439 Jul 14 15:31 httpd

Our software has been successfully installed. You must notice that at the end
of the install, it shows the full path for the PREFIX variable we passed it.
The problem with that is that at boot-time, your system is going to look for
it under /mnt instead of /usr. So we need to edit apache's initialization
script under /usr/local/etc/rc.d (apache.sh) and remove all instances of
"/mnt" in it.

WARNING: A very important thing to care about are dependencies. Before
installing anything, check to see if it has any dependencies, and that you'll
have enough disk space on the destination system for both the application
you're installing and its dependencies.

- Script download

TinyBSD is still a project under heavy development, both the script itself and
its documentation. 

In case you'd like to try or use the BETA version of the script, feel free to
download it from the project's official site at http://www.tinybsd.org.
@


1.5
log
@SVN rev 236707 on 2012-06-07 09:14:28Z by bz

TinyBSD now seems to be hosted elsewhere.
@
text
@d1 1
a1 1
# $FreeBSD$
@


1.4
log
@SVN rev 228975 on 2011-12-30 00:04:11Z by uqs

Spelling fixes for tools/

Add some $FreeBSD$ tags so svn will allow the commit.
@
text
@d259 1
a259 1
download it from the project's official site at http://www.tinybsd.org.
@


1.3
log
@Reworking of how to add ports.

submitted by: Jean Milanez Melo
@
text
@d108 1
a108 1
4) Copy all your /etc configuration wich you want to conf/YOURIMAGE/etc/.
@


1.3.2.1
log
@Switch importer
@
text
@d1 1
a1 1
# $FreeBSD: stable/7/tools/tools/tinybsd/README 163854 2006-11-01 01:25:51Z julian $
@


1.3.16.1
log
@SVN rev 225736 on 2011-09-23 00:51:37Z by kensmith

Copy head to stable/9 as part of 9.0-RELEASE release cycle.

Approved by:	re (implicit)
@
text
@@


1.3.16.2
log
@## SVN ##
## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/ 242902
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
## SVN ##
## SVN ## ------------------------------------------------------------------------
## SVN ## r242902 | dteske | 2012-11-11 23:29:45 +0000 (Sun, 11 Nov 2012) | 10 lines
## SVN ##
## SVN ## Fix a regression introduced by SVN r211417 that saw the breakage of a feature
## SVN ## documented in usr.sbin/sysinstall/help/shortcuts.hlp (reproduced below):
## SVN ##
## SVN ## If /usr/sbin/sysinstall is linked to another filename, say
## SVN ## `/usr/local/bin/configPackages', then the basename will be used
## SVN ## as an implicit command name.
## SVN ##
## SVN ## Reviewed by:	adrian (co-mentor)
## SVN ## Approved by:	adrian (co-mentor)
## SVN ##
## SVN ## ------------------------------------------------------------------------
## SVN ##
@
text
@d1 1
a1 1
# $FreeBSD: stable/9/tools/tools/tinybsd/README 163854 2006-11-01 01:25:51Z julian $
@


1.3.16.1.4.1
log
@SVN rev 239080 on 2012-08-05 23:54:33Z by kensmith

Copy stable/9 to releng/9.1 as part of the 9.1-RELEASE release process.

Approved by:	re (implicit)
@
text
@@


1.3.16.1.4.2
log
@Switch importer
@
text
@d1 1
a1 1
# $FreeBSD: releng/9.1/tools/tools/tinybsd/README 163854 2006-11-01 01:25:51Z julian $
@


1.3.16.1.2.1
log
@SVN rev 227445 on 2011-11-11 04:20:22Z by kensmith

Copy stable/9 to releng/9.0 as part of the FreeBSD 9.0-RELEASE release
cycle.

Approved by:	re (implicit)
@
text
@@


1.3.16.1.2.2
log
@Switch importer
@
text
@d1 1
a1 1
# $FreeBSD: releng/9.0/tools/tools/tinybsd/README 163854 2006-11-01 01:25:51Z julian $
@


1.3.14.1
log
@SVN rev 216618 on 2010-12-21 17:10:29Z by kensmith

Copy stable/7 to releng/7.4 in preparation for FreeBSD-7.4 release.

Approved by:	re (implicit)
@
text
@@


1.3.14.2
log
@Switch importer
@
text
@d1 1
a1 1
# $FreeBSD: releng/7.4/tools/tools/tinybsd/README 163854 2006-11-01 01:25:51Z julian $
@


1.3.12.1
log
@SVN rev 203736 on 2010-02-10 00:26:20Z by kensmith

Copy stable/7 to releng/7.3 as part of the 7.3-RELEASE process.

Approved by:	re (implicit)
@
text
@@


1.3.10.1
log
@SVN rev 196045 on 2009-08-03 08:13:06Z by kensmith

Copy head to stable/8 as part of 8.0 Release cycle.

Approved by:	re (Implicit)
@
text
@@


1.3.10.2
log
@## SVN ##
## SVN ## Exported commit - http://svnweb.freebsd.org/changeset/base/ 242909
## SVN ## CVS IS DEPRECATED: http://wiki.freebsd.org/CvsIsDeprecated
## SVN ##
## SVN ## ------------------------------------------------------------------------
## SVN ## r242909 | dim | 2012-11-12 07:47:19 +0000 (Mon, 12 Nov 2012) | 20 lines
## SVN ##
## SVN ## MFC r242625:
## SVN ##
## SVN ## Remove duplicate const specifiers in many drivers (I hope I got all of
## SVN ## them, please let me know if not).  Most of these are of the form:
## SVN ##
## SVN ## static const struct bzzt_type {
## SVN ##       [...list of members...]
## SVN ## } const bzzt_devs[] = {
## SVN ##       [...list of initializers...]
## SVN ## };
## SVN ##
## SVN ## The second const is unnecessary, as arrays cannot be modified anyway,
## SVN ## and if the elements are const, the whole thing is const automatically
## SVN ## (e.g. it is placed in .rodata).
## SVN ##
## SVN ## I have verified this does not change the binary output of a full kernel
## SVN ## build (except for build timestamps embedded in the object files).
## SVN ##
## SVN ## Reviewed by:	yongari, marius
## SVN ##
## SVN ## ------------------------------------------------------------------------
## SVN ##
@
text
@d1 1
a1 1
# $FreeBSD: stable/8/tools/tools/tinybsd/README 163854 2006-11-01 01:25:51Z julian $
@


1.3.10.1.8.1
log
@SVN rev 232438 on 2012-03-03 06:15:13Z by kensmith

Copy stable/8 to releng/8.3 as part of 8.3-RELEASE release cycle.

Approved by:	re (implicit)
@
text
@@


1.3.10.1.8.2
log
@Switch importer
@
text
@d1 1
a1 1
# $FreeBSD: releng/8.3/tools/tools/tinybsd/README 163854 2006-11-01 01:25:51Z julian $
@


1.3.10.1.6.1
log
@SVN rev 216617 on 2010-12-21 17:09:25Z by kensmith

Copy stable/8 to releng/8.2 in preparation for FreeBSD-8.2 release.

Approved by:	re (implicit)
@
text
@@


1.3.10.1.4.1
log
@SVN rev 209145 on 2010-06-14 02:09:06Z by kensmith

Copy stable/8 to releng/8.1 in preparation for 8.1-RC1.

Approved by:	re (implicit)
@
text
@@


1.3.10.1.2.1
log
@SVN rev 198460 on 2009-10-25 01:10:29Z by kensmith

Copy stable/8 to releng/8.0 as part of 8.0-RELEASE release procedure.

Approved by:	re (implicit)
@
text
@@


1.3.8.1
log
@SVN rev 191087 on 2009-04-15 03:14:26Z by kensmith

Create releng/7.2 from stable/7 in preparation for 7.2-RELEASE.

Approved by:	re (implicit)
@
text
@@


1.3.6.1
log
@SVN rev 185281 on 2008-11-25 02:59:29Z by kensmith

Create releng/7.1 in preparation for moving into RC phase of 7.1 release
cycle.

Approved by:	re (implicit)
@
text
@@


1.2
log
@Add some code to support including files ffrom packages in the image.

Submitted by: Jeremie Le Hen and tested by Jean Milanez Melo.
@
text
@d72 5
a76 3
tinybsd.localfiles: Similar to tinybsd.basefiles but for /usr/local/.  The
difference is that directories will have to be created by TinyBSD because
they are not handle by mtree(1).
@


1.1
log
@In the spirit of nanoBSD and PicoBSD, add TinyBSD.
Submitted by jmeloatfreebsdbrasil,com-br
(Jean Milanez Melo)
As PicoBSD becomes slightly less useful, TinyBSD fills the gap below nanoBSD.
@
text
@d72 4
@


1.1.2.1
log
@MFC: Make the tinybsd framework a peer of nanobsd and picobsd in the tree
Some patches to come.
Approved by: re (ken)
@
text
@@


1.1.2.2
log
@Switch importer
@
text
@d1 1
a1 1
# $FreeBSD: stable/6/tools/tools/tinybsd/README 162748 2006-09-28 21:09:10Z julian $
@


1.1.2.1.6.1
log
@SVN rev 183531 on 2008-10-02 02:57:24Z by kensmith

Create releng/6.4 from stable/6 in preparation for 6.4-RC1.

Approved by:	re (implicit)
@
text
@@


