how to pass nfs nolock option in /etc/fstab
Hello all, I have come across an issue where I attempted to mount my NFSroot FS with a nolock option in order to support a database application. In an attempt to do so, I edited my /etc/fstab as follows: 192.168.17.1:/export/images/00A0D1E35B7E/freebsd7_x64 / nfs rw,nolock 0 0 When I attempt to re-mount, I get the following error: mount -a mount_nfs: -o lock: option not supported ... Upon googling folks suggested to use the -L option ... but mention that this is not possible to pass on to /etc/fstab My question: is it possible to mount an NFSroot on FreeBSD and at the SAME time pass the nolock parameter? thanks in advance...! -- best, Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD PXE client not getting netmask config from DHCP server
Hello Erik,
Thanks for the response. I have followed your recommendation as follows:
1. In effect my dhcpd.conf now looks like this:
ddns-update-style interim;
ignore client-updates;
subnet 192.168.16.0 netmask 255.255.240.0 {
option routers 192.168.16.1;
option subnet-mask 255.255.240.0;
range dynamic-bootp 192.168.16.10 192.168.16.30;
default-lease-time 21600;
max-lease-time 43200;
host r02s01 {
hardware ethernet 00:A0:D1:E3:58:38;
fixed-address 192.168.17.11;
filename pxeboot;
option root-path 192.168.17.1:/export/images/NFSroot_gold/freebsd7_x64;
option host-name r02s01;
}
}
next-server 192.168.17.1;
2. Thereafter, I restarted the dhcpd service, and then rebooted my
freebsd client (r02s01) . Upon logging in, I checked its
configuration, and still the netmask reflects the 255.255.255.0
subnet:
r02s01# ifconfig -a
nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu
1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4
ether 00:a0:d1:e3:58:38
inet 192.168.17.11 netmask 0xff00 broadcast 192.168.17.255
inet6 fe80::2a0:d1ff:fee3:5838%nfe0 prefixlen 64 scopeid 0x1
media: Ethernet autoselect (1000baseTX full-duplex,flag2)
** netmask 0xff00 - which means this, right:
Name Example
CIDR /24
Netmask255.255.255.0
Netmask (hex) 0xff00
Wilcard Bits 0.0.0.255
*sigh* ... am I missing something in my client side?
thanks in advance!
On Wed, Mar 26, 2008 at 4:24 AM, Erik Norgaard [EMAIL PROTECTED] wrote:
vincenzo romero wrote:
Hello all,
I wanted to check and test my PXE clients - where I have:
- Cent OS 5.1 - PXE/DHCP/TFTP/NFS server with the root-NFS-images
- client - FreeBSD 7:
uname -a
FreeBSD r02s01 7.0-RELEASE FreeBSD 7.0-RELEASE #1: Mon Mar 3 21:52:54
PST 2008 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/CUSTOMKRNL
amd64
...
1. My /etc/dhcpd.conf server has defined a gateway/router and subnet mask
cat /etc/dhcpd.conf
ddns-update-style interim;
ignore client-updates;
subnet 192.168.16.0 netmask 255.255.240.0 {
# --- default gateway
option routers 192.168.16.1;
option subnet-mask 255.255.240.0;
range dynamic-bootp 192.168.16.10 192.168.16.30;
default-lease-time 21600;
max-lease-time 43200;
}
2. freebsd test server parameters defined as such:
host r02s01 {
hardware ethernet 00:A0:D1:E3:58:38;
fixed-address 192.168.17.11;
filename pxeboot;
option root-path 192.168.17.1:/export/images/NFSroot_gold/freebsd7_x64;
option host-name r02s01;
}
3. PROBLEM - when the client boots and I login . i notice that
the netmask it is configured with is 255.255.255.0 ...
Am I missing something in my configuration? I am not having these
issues (i think) with my diskless Fedora, Ubuntu clients ...
Any help will be greatly appreciated
If your host declaration is outside the subnet declation the subnet
parameters are not sent, the client should then default to the netmask
/24 since 192.168 is in the old class C network range. Place the host
declaration inside the subnet declaration.
BR, Erik
--
Erik Nørgaard
Ph: +34.666334818 http://www.locolomo.org
--
best,
Vince
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD PXE client not getting netmask config from DHCP server
I'd like to add another datapoint:
1. It seems that a fedora PXE client, honors the netmask parameter
passed by the DHPC server:
ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:A0:D1:E3:57:CA
inet addr:192.168.16.12 Bcast:192.168.31.255 Mask:255.255.240.0
inet6 addr: fe80::2a0:d1ff:fee3:57ca/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:74171 errors:0 dropped:0 overruns:0 frame:0
TX packets:45164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:64499323 (61.5 MiB) TX bytes:8111327 (7.7 MiB)
Interrupt:23 Base address:0x2000
2. However, the FreeBSD server, stubbornly insists towards the
255.255.255.0 subnet
Both clients boot against the same DHCP server.
Any thoughts?
- thanks in advance.
On Wed, Mar 26, 2008 at 9:25 AM, vincenzo romero [EMAIL PROTECTED] wrote:
Hello Erik,
Thanks for the response. I have followed your recommendation as follows:
1. In effect my dhcpd.conf now looks like this:
ddns-update-style interim;
ignore client-updates;
subnet 192.168.16.0 netmask 255.255.240.0 {
option routers 192.168.16.1;
option subnet-mask 255.255.240.0;
range dynamic-bootp 192.168.16.10 192.168.16.30;
default-lease-time 21600;
max-lease-time 43200;
host r02s01 {
hardware ethernet 00:A0:D1:E3:58:38;
fixed-address 192.168.17.11;
filename pxeboot;
option root-path 192.168.17.1:/export/images/NFSroot_gold/freebsd7_x64;
option host-name r02s01;
}
}
next-server 192.168.17.1;
2. Thereafter, I restarted the dhcpd service, and then rebooted my
freebsd client (r02s01) . Upon logging in, I checked its
configuration, and still the netmask reflects the 255.255.255.0
subnet:
r02s01# ifconfig -a
nfe0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu
1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4
ether 00:a0:d1:e3:58:38
inet 192.168.17.11 netmask 0xff00 broadcast 192.168.17.255
inet6 fe80::2a0:d1ff:fee3:5838%nfe0 prefixlen 64 scopeid 0x1
media: Ethernet autoselect (1000baseTX full-duplex,flag2)
** netmask 0xff00 - which means this, right:
Name Example
CIDR /24
Netmask255.255.255.0
Netmask (hex) 0xff00
Wilcard Bits 0.0.0.255
*sigh* ... am I missing something in my client side?
thanks in advance!
On Wed, Mar 26, 2008 at 4:24 AM, Erik Norgaard [EMAIL PROTECTED] wrote:
vincenzo romero wrote:
Hello all,
I wanted to check and test my PXE clients - where I have:
- Cent OS 5.1 - PXE/DHCP/TFTP/NFS server with the root-NFS-images
- client - FreeBSD 7:
uname -a
FreeBSD r02s01 7.0-RELEASE FreeBSD 7.0-RELEASE #1: Mon Mar 3 21:52:54
PST 2008 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/CUSTOMKRNL
amd64
...
1. My /etc/dhcpd.conf server has defined a gateway/router and subnet
mask
cat /etc/dhcpd.conf
ddns-update-style interim;
ignore client-updates;
subnet 192.168.16.0 netmask 255.255.240.0 {
# --- default gateway
option routers 192.168.16.1;
option subnet-mask 255.255.240.0;
range dynamic-bootp 192.168.16.10 192.168.16.30;
default-lease-time 21600;
max-lease-time 43200;
}
2. freebsd test server parameters defined as such:
host r02s01 {
hardware ethernet 00:A0:D1:E3:58:38;
fixed-address 192.168.17.11;
filename pxeboot;
option root-path
192.168.17.1:/export/images/NFSroot_gold/freebsd7_x64;
option host-name r02s01;
}
3. PROBLEM - when the client boots and I login . i notice that
the netmask it is configured with is 255.255.255.0 ...
Am I missing something in my configuration? I am not having these
issues (i think) with my diskless Fedora, Ubuntu clients ...
Any help will be greatly appreciated
If your host declaration is outside the subnet declation the subnet
parameters are not sent, the client should then default to the netmask
/24 since 192.168 is in the old class C network range. Place the host
declaration inside the subnet declaration.
BR, Erik
--
Erik Nørgaard
Ph: +34.666334818 http://www.locolomo.org
--
best,
Vince
--
best,
Vince
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD PXE client not getting netmask config from DHCP server
Hello all,
I wanted to check and test my PXE clients - where I have:
- Cent OS 5.1 - PXE/DHCP/TFTP/NFS server with the root-NFS-images
- client - FreeBSD 7:
uname -a
FreeBSD r02s01 7.0-RELEASE FreeBSD 7.0-RELEASE #1: Mon Mar 3 21:52:54
PST 2008 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/CUSTOMKRNL
amd64
...
1. My /etc/dhcpd.conf server has defined a gateway/router and subnet mask
cat /etc/dhcpd.conf
ddns-update-style interim;
ignore client-updates;
subnet 192.168.16.0 netmask 255.255.240.0 {
# --- default gateway
option routers 192.168.16.1;
option subnet-mask 255.255.240.0;
range dynamic-bootp 192.168.16.10 192.168.16.30;
default-lease-time 21600;
max-lease-time 43200;
}
2. freebsd test server parameters defined as such:
host r02s01 {
hardware ethernet 00:A0:D1:E3:58:38;
fixed-address 192.168.17.11;
filename pxeboot;
option root-path 192.168.17.1:/export/images/NFSroot_gold/freebsd7_x64;
option host-name r02s01;
}
3. PROBLEM - when the client boots and I login . i notice that
the netmask it is configured with is 255.255.255.0 ...
Am I missing something in my configuration? I am not having these
issues (i think) with my diskless Fedora, Ubuntu clients ...
Any help will be greatly appreciated
--
best,
Vince
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD pxeboot unable to mount NFSroot
Hello all,
I would like to find out if the following is a known and documented
issue, and if so, can someone please point me to a link where I can
further understand the problem and cause.
I have encountered an issue where in a certain case a diskless client
is unable to mount NFSroot. Here is the explanation:
PXE/DHCP/TFTP and NFS server - CentOS 5.1
- Multiple clients NFSroot mount exported on a per host basis. One of
the clients is an NFS root mount image of FreeBSD 7
Configuration and Summary:
PXE/Server 192.168.16.x network; subnet: 255.255.240.0
Clients
-- when clients are configured and defined in /etc/dhcpd.conf with
an assigned address in 192.168.16.x then it is able to boot
successfully - for all types of clients -(ie., FreeBSD and linux
flavors):
eg.:
host testclient1 {
hardware ethernet 00:A0:DD:EF:5B:7E;
fixed-address 192.168.16.39;
filename pxeboot;
option root-path 192.168.16.5:/export/images/00A0DDEF5B7E/freebsd7_x64;
option host-name testclient1;
-- when we attempt to assign a FreeBSD client with an IP address
within the 192.168.17.x --- it is unable to mount its NFSroot export:
host testclient2{
hardware ethernet 00:A0:DD:EF:57:CA;
fixed-address 192.168.17.2;
filename pxeboot;
option root-path 192.168.16.5:/export/images/00A0DDEF57CA/freebsd7_x64;
option host-name testclient2;
}
The clients' bootup process stops when attempting to mount the NFSroot
and drops into a mount prompt, forcing the user to enter a local
device to mount root. Other linux flavor clients are able to boot
successfully, these clients use the pxelinux binary as opposed to
pxeboot that freeBSD clients use.
My question: is there any known issue vis a vis the pxeboot
implementation so that it's unable to figure out that my 192.168.17.x
has a subnet of 255.255.240.0 and should be able to mount and talk
to its NFS server that is in 192.168.16.x?
Any advise would be greatly appreciated.
--
best,
Vince
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
JDK for FreeBSD 7
A quick question: 1. Based on the following available downloads: http://www.freebsdfoundation.org/downloads/java.shtml seems like there is no SW available for the FreeBSD 7 stable release?... pls confirm? 2. Is there a way of (sorry for the naive question) running the latest for FBSD6 into 7? kind of like downloading source and compiling? if so, any pointers to where I can get source and instructions? -- best, Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD diskless workstation boot over Linux PXE server
Did you modify rc.conf, fstab and resolv.conf as described in
http://www.locolomo.org/pub/pxeboot/diskless.html?
yes:
1. fstab:
cat fstab
# DeviceMountpoint FStype
Options DumpPass#
192.168.16.5:/export/images/freeBSD / nfs
rw 0 0
proc/proc procfs
rw 0 0
** Note - it is for our test/dev environment - it's ok to have entire
root RW for us; no need to secure the environment.
2. rc.conf: (I am assuming, the above mentioned note indicates to
edit the /etc/rc.conf file (not the /etc/defaults/rc.conf)
cat rc.conf
# -- sysinstall generated deltas -- # Mon Mar 3 09:08:29 2008
# Created: Mon Mar 3 09:08:29 2008
# Enable network daemons for user convenience.
# Please make all changes to this file, not to /etc/defaults/rc.conf.
# This file now contains just the overrides from /etc/defaults/rc.conf.
hostname=Freebsdtest
ifconfig_nfe0=DHCP
inetd_enable=YES
moused_enable=YES
sshd_enable=YES
rc.conf for diskless clients
#
# System daemons:
#
sendmail_submit_enable=NO # Do not enable local delivery or outbound
sendmail_outbound_enable=NO # sendmail daemon. This disables sendmail
sendmail_msp_queue_enable=NO # completely on the client.
cron_enable=NO# Cron should run on the server
#
# File systems
#
# root_rw_mount=NO # Root is exported read only
background_fsck=NO# NEVER run fsck on nfs mounted partitions
nfs_client_enable=YES # The diskless client is an NFS client
tmpmfs=NO # We mount /var and /tmp as NFS partitions
varmfs=NO #
cleanvar_enable=YES # Clean the /var directory (this is default)
clear_tmp_enable=YES # Clear /tmp at startup.
clear_tmp_X=YES # Clear and recreate X11-related directories
#
# Scripts run at startup only
#
newsyslog_enable=NO # Logging to server
update_motd=NO# Root file system is read only
#
**Note: I also comment'ed out the root_rw_mounted = NO - because I
would like to export root as RW - assuming default is YES; or should
I have just changed NO value to YES (will try that too).
And what's hiding
behind etc. etc.?
Basically, I just meant to say, etcetera vis a vis the console error
messages to reiterate, the console messages where initial error
occurs appears are follows:
NFS ROOT: 192.168.16.5:/export/images/freeBSD
nfe0: link state change to UP
Interface nfe0 IP_Address 192.168.16.5 ... . . . . ..
Loading Configuration files.
rc.conf: not found
No Suitable dump device was found .
Entropy harvesting: interrupts ethernet point_to_point kickstart.
Starting file system checks:
mount_nfs: can't update /var/db/mounttab for 192.168.16.5:/export/images/freeBSD
Setting hostuuid: .
Setting hostid:
Mounting local file systems.
Setting hostname:
net.inet6.ip6.net_unlocal: 1-0
rc.conf: not found
|
|
3. Yes, resolv.conf points to our DNS; it contains same as other
working hosts within our lab.
. Thank you for the response and patience; I truly appreciate all
the help and pointers.
Thanks in advanced.
Erik
On Tue, Mar 4, 2008 at 2:10 AM, Erik Cederstrand [EMAIL PROTECTED] wrote:
vincenzo romero wrote:
Thank you for the input from a couple of folks. After a few research
and readings I am able to boot off a diskless client; and have a
little error encountered. To clarify the environment:
1. PXE/DHCP/NFS/TFTP servers is a linux host
2. DHCP - server - dhcpd.conf file shows the following: (for my
freeBSD diskless client testing scenario)
filename pxeboot;
next-server 192.168.16.5;
option root-path 192.168.16.5:/export/images/freeBSD;
-- pxeboot is the freeBSD /boot/pxeboot file I copied over to my
/tftpboot directory.
-- next server IP is the PXE/TFTPD/DHCP server ...
-- the NFS root is exported by the NFS server as such.
The client seems to boot properly - acquires an IP address;
downloads and reads the /tftpboot/pxeboot file; a message also
appears that indicates it mounted the root File system: (snippet of
console messages:)
NFS ROOT: 192.168.16.5:/export/images/freeBSD
nfe0: link state change to UP
Interface nfe0 IP_Address 192.168.16.5 ... . . . . ..
Loading Configuration files.
rc.conf: not found
No Suitable dump device was found .
|
etc.
etc.
--
best,
Vince
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Solved: FreeBSD diskless workstation boot over Linux PXE server
Hello Erik and all,
thank you for all the help; all my issues are resolved, mostly
stemming from silly misconfigurations and typos:
1. rc.conf file is missing - was caused by a typo - missing # from
a comment line that began with the string rc.conf.
2. i had some getty errors - bec. my /usr directory was not
completely tar'ed or cpio'ed into my NFS root export.
When I have iron'ed out and ensured that I followed Erik's instructions below:
http://www.locolomo.org/pub/pxeboot/diskless.html
I was fine.
thanks again.
- V.
On Tue, Mar 4, 2008 at 2:10 AM, Erik Cederstrand [EMAIL PROTECTED] wrote:
vincenzo romero wrote:
Thank you for the input from a couple of folks. After a few research
and readings I am able to boot off a diskless client; and have a
little error encountered. To clarify the environment:
1. PXE/DHCP/NFS/TFTP servers is a linux host
2. DHCP - server - dhcpd.conf file shows the following: (for my
freeBSD diskless client testing scenario)
filename pxeboot;
next-server 192.168.16.5;
option root-path 192.168.16.5:/export/images/freeBSD;
-- pxeboot is the freeBSD /boot/pxeboot file I copied over to my
/tftpboot directory.
-- next server IP is the PXE/TFTPD/DHCP server ...
-- the NFS root is exported by the NFS server as such.
The client seems to boot properly - acquires an IP address;
downloads and reads the /tftpboot/pxeboot file; a message also
appears that indicates it mounted the root File system: (snippet of
console messages:)
NFS ROOT: 192.168.16.5:/export/images/freeBSD
nfe0: link state change to UP
Interface nfe0 IP_Address 192.168.16.5 ... . . . . ..
Loading Configuration files.
rc.conf: not found
No Suitable dump device was found .
|
etc.
etc.
Did you modify rc.conf, fstab and resolv.conf as described in
http://www.locolomo.org/pub/pxeboot/diskless.html? And what's hiding
behind etc. etc.?
Erik
--
best,
Vince
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD diskless workstation boot over Linux PXE server
Thank you for the input from a couple of folks. After a few research and readings I am able to boot off a diskless client; and have a little error encountered. To clarify the environment: 1. PXE/DHCP/NFS/TFTP servers is a linux host 2. DHCP - server - dhcpd.conf file shows the following: (for my freeBSD diskless client testing scenario) filename pxeboot; next-server 192.168.16.5; option root-path 192.168.16.5:/export/images/freeBSD; -- pxeboot is the freeBSD /boot/pxeboot file I copied over to my /tftpboot directory. -- next server IP is the PXE/TFTPD/DHCP server ... -- the NFS root is exported by the NFS server as such. The client seems to boot properly - acquires an IP address; downloads and reads the /tftpboot/pxeboot file; a message also appears that indicates it mounted the root File system: (snippet of console messages:) NFS ROOT: 192.168.16.5:/export/images/freeBSD nfe0: link state change to UP Interface nfe0 IP_Address 192.168.16.5 ... . . . . .. Loading Configuration files. rc.conf: not found No Suitable dump device was found . | etc. etc. IT seems like the root is mounted but it cannot find the rc.conf file; my root contains the following directories (including nfsroot/etc/rc.conf and nfsroot/etc/defaults/rc.conf ... freeBSD# ls bin boot dev etc home lib libexec sbin swap tmp usr var I must be missing something silly or apparent. Any help and/or suggestions would be greatly appreciated. I have attempted to painstakingly google this issue, to no avail. thanks in advanced. On Sat, Feb 23, 2008 at 2:45 AM, Erik Norgaard [EMAIL PROTECTED] wrote: vincenzo romero wrote: Hello, Am new to FreeBSD and relatively new to linux; I have a CentOS 5.1 PXE/tftpd/dhcpd server; I'd like it to be the build/PXE server where a bunch of 1U clients could PXE boot and run: 1. diskless over NFS-Root In googling, seems like there is a clone script that preps and lets you generate a root file system structure and let your clients boot off the network. I found the docs I could find on the internet way obsolete back in 2005 when I played with it, and I am not aware that these has been updated. I wrote my own guide to make up for this, however, this may now also be obsolete as it's been some time since I played with this. My main problem with diskless is that FreeBSD mounts memory backed filesystems for /var and /tmp which waste a lot of precious RAM if you have restricted memory. And a feature, useless in diskless operation, prevents mounting /var and /tmp from a server. I checked the Free BSD Handbook (Chapter 29) where extensive documentation on setup is outlined, but it assumes that the PXE/TFTP/NFS/DHCPd servers are FreeBSD; mine is a CentOS; just want to support diskless PXE boot for my clients. Section 29.7.2.9.2 9Usning a Non-FreeBSD server - just indicates that do a tar/cpio of root; but ensure that special files in /dev are taken care of ... There is no problem serving files from a non-FreeBSD server, however things are easier, as you need to build all applications served via NFS for FreeBSD. This mainly affects you if you want diskless clients, you need to keep these updated. For installation this is not a concern. The /dev is not a problem, the diskless client mounts a /dev locally, it is not a real file system. - does anyone have this type of scenario setup? if so, can you please share with me your insights/cheat-sheet-how to? http://www.locolomo.org/pub/pxeboot/index.html - i'd be interested in understanding the setup of how you handled copying the /dev files into your exported ROOT directorty ... Are there any other recommendations ? If you want to do network installation rather than diskless, avoid NFS, it is much easier to set up installation over ftp. Cheers, Erik -- Erik Nørgaard Ph: +34.666334818 http://www.locolomo.org -- best, Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD diskless workstation and over the network installation via PXE
Hello, Am new to FreeBSD and relatively new to linux; I have a CentOS 5.1 PXE/tftpd/dhcpd server; I'd like it to be the build/PXE server where a bunch of 1U clients could PXE boot and run: 1. diskless over NFS-Root In googling, seems like there is a clone script that preps and lets you generate a root file system structure and let your clients boot off the network. I checked the Free BSD Handbook (Chapter 29) where extensive documentation on setup is outlined, but it assumes that the PXE/TFTP/NFS/DHCPd servers are FreeBSD; mine is a CentOS; just want to support diskless PXE boot for my clients. Section 29.7.2.9.2 9Usning a Non-FreeBSD server - just indicates that do a tar/cpio of root; but ensure that special files in /dev are taken care of ... my question - - does anyone have this type of scenario setup? if so, can you please share with me your insights/cheat-sheet-how to? - i'd be interested in understanding the setup of how you handled copying the /dev files into your exported ROOT directorty ... Are there any other recommendations ? thanks in advance! -- best, Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
