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]"
Re: FreeBSD diskless workstation boot over Linux PXE server
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 ___ 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 /etc/rc.conf and /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]"
