Re: Newbie custom config questions

Dario Freni <[email protected]>
Newsgroups gmane.os.freebsd.freesbie
Message-ID <[email protected]>
Lee J. Imber wrote:
> 
> On Dec 29, 2005, at 4:35 PM, Dario Freni wrote:
> 
>> Lee J. Imber wrote:
>>
>>> Hi All,
>>>
>>> First off thanks for the cool project. After playing with this for a
>>> few days, lots a useful ideas are jumping out at me!
>>>
>>>
>>> Here is my situation.
>>>
>>> I have box in a colo that is on the West coast that has recently died
>>> (HD). I am in NY.
>>> I need to get that box up asap with minimal configuration.
>>>
>>> These are my requirements.
>>>
>>> 1. /etc/passwd pre-configured with my accounts.
>>> 2. /etc/resolv.conf
>>> 3. ifconfig_fxp0
>>> 4. defaultrouter
>>> 5. sshd to start at boot time.
>>> 6. Set hostname
>>> 7. NTPD
>>>
>>> I first started with 1.1 and was able to build working iso's fine   (way
>>> cool)
>>> I was able to get #3,4,5,6,7 of my list to end up on my working iso.
>>> I could not get a /etc/resolv.conf file to be created in the image  and
>>> I also tried to copy a working /etc/passwd and /etc/master.passwd to
>>> my image and still no go.
>>>
>>> I then tried version 2. I am currently in the "building  everything" 
>>> stage
>>> so I have not had any experience with it yet. I do see the adduser
>>> scripts in the
>>> extra config, but not sure how these work until I start playing.
>>
>>
>> You can find some documentation on http://wiki.freesbie.org/freesbie2.
>> Follow the links to have the configuration parameters explained. At  the
>> moment you have to enable at least etcmfs to have a working image.
>>
>> The customroot plugin allows you to add your own files to the image
>> during the build phase. All the content of freesbie2/extra/customroot/
>> dir will be copied to the / dir of livefs as is. For example, if you
>> create freesbie2/extra/customroot/etc/resolv.conf it will be copied to
>> /etc/resolv.conf.
> 
> 
> OK cool, how is this done in the 1.1 tree? I know its not being 
> developed anymore
> but I currently have that version installed and building fine. I  tried
> 2 and I keep getting
> build errors (no time to debug)  A hint on how 1.1 handles this very 
> function
> will be very helpful.

The latest version in CVS (freesbie module, not freesbie2) have a
files/custom/ directory. It has the same meaning of extra/customroot/ one.

>> To set root password you can set it the first time the way Marco said:
>>
>> chroot /usr/local/freesbie-fs /usr/bin/passwd root
>>
>> If you don't want to set it everytime you rebuild your iso, you can  put
>> /usr/local/freesbie-fs/etc/passwd and
>> /usr/local/freesbie-fs/etc/master.passwd to
>> freesbie2/extra/customroot/etc/. The login db is recreated  automatically
>> by customroot plugin.
>>
> 
> Sweet. Seems to have worked fine.
> 
>>
>>> One other thing. Unfortunately I do not remember what the  interface  is
>>> on my box
>>> on the west coast. I *think* its fxp0 but not 100%. I saw in the
>>> rc.conf on the 1.1 install
>>> a neat script to sorta do a dhcp on all the interfaces it finds.  Is  it
>>> possible for me
>>> to take advantage of the script and set the static IP for every
>>> interface it finds.
>>
>>
>> Adding ifconfig_DEFAULT="DHCP" in /etc/rc.conf SHOULD work, as this is
>> what devd looks for if it doesn't find a specifical variable set  for the
>> interface. Make also sure devd is starting by adding devd_enable="YES"
>>
>> Remember you can also add those to freesbie2/extra/customroot/etc/
>> rc.conf
>>
> 
> OK, this is true if it's a static IP that will be assigned? Can I  just
> change
> the "DHCP" to "inet foo netmask bar" ?

According to /etc/network.subr source this should work also with static
ips. The _ifconfig_getargs function uses $ifconfig_DEFAULT if
$ifconfig_xx0 is not set.

Are you using FreeBSD 6?

-- 
Dario Freni ([email protected])
FreeSBIE developer (http://www.freesbie.org)
GPG Public key at http://www.saturnero.net/saturnero.asc
-- 
FreeSBIE mailing list (http://www.freesbie.org)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.