similar to: 2 questions on diskless client setup.

Im trying to get a diskless boot set up under CentOS 5.2, and having no luck at all. I am to the point of running system-config-netboot, and whatever information I put in, I get an error message. Responding to the 2nd button on the first popup, which asks for NFS info, I put in the IP address of the current machine (the machine that will hold the boot images for the diskless machine) and the

Hi folks, I've followed a set of instructions I found on http://www.linuxtopia.org/online_books/centos_linux_guides/centos_enterprise_linux_sysadmin_guide/ch-diskless.htmli which describes using system-config-netboot to set up PXE booting. I used a CentOS-4.3 install (custom, all options de-selected, then anaconda-busybox installed after the fact) as a reference/base. I followed the

Hello all, I have a customer that insists of using upstream vendor's diskless (system-config-netboot) rather than LTSP. The reason is that he wants to use a 100% packages from the vendor, not from LTSP or any other party. I try the vendor's diskless system, and although it's very simple to setup, it lacks the support and/or documentation whereas LTSP is very good in it. Another

OK, I did this once, several years ago, but I have to do it again, and I cant figure out what this stupid error message is trying to say. I am executing system-config-netboot trying to create a diskless client for a diskless boot I constantly get a popup, with different error messages. I try to 'fix' something, and I get a different popup. The current one says: You

I'm trying to setup a simple NFSv4 mount between two x86_64 hosts. On the server, I have this in /etc/exports: /export $CLIENT(ro,fsid=0) /export/qb3 $CLIENT(rw,nohide) ON $CLIENT, I mount via: mount -t nfs4 $SERVER:/qb3 /usr/local/sge62/qb3 However: $ touch /usr/local/sge62/qb3/foo touch: cannot touch `/usr/local/sge62/qb3/foo': Read-only file system I'd really

I have been trying all sorts of things to get this working. nfsv4 works fine if I just use the nfs-v3 form of export i.e. /nfs4exports 192.168.230.237/24(ro,fsid=0,sync,insecure,no_root_squash,no_subtree_check,squash_uids=0-99) /nfs4exports/NDG 192.168.230.237/24(rw,insecure,no_subtree_check,nohide,sync,no_root_squash,squash_uids=0-99) but this is inherently open to all on this machine. so then

Hi, This is slightly offtopic, but I have been trying to resolve that problem for two days now without much success. It looks like this may be something that works with CENTOS5, but not with CENTOS6! I have two machines, fileserver1 and server5. fileserver1 runs on CENTOS6 (virtualized, if this is important), server5 runs on Centos5. Both are running with the most recent updates. Server5 is a

Max, Would you please zip up the contents of /tftpboot/linux-install/pxelinux.cfg. You can send it to <jses27 at gmail.com>. After you use the Nettboot Tool to configure the diskless client it will not update the pertinate files to do so. So in saying it will not boot the default OS. Maybe this could be an error of mine.. But then again there was a post related to this issue this week.

I created a centos 7 docker container in which I want to mount a NFS share in. Said share is owned by user virtual with uid 1200. So I do some exporting (docker container is in 172.17.0.0/16): spindizzy> cat /etc/exports /export 10.0.0.0/24(ro,fsid=0,no_subtree_check,sync) 172.17.0.0/16(ro,fsid=0,no_subtree_check,sync) [...] /export/mail 172.17.0.0/16(rw,root_squash,no_subtree_check,sync)

Hi, I hope someone could give me help with following problem on centos 5.8 kernel and nfs4. On server i have bind mounted directory shared to the client with following setup: mounted directory: /srv/nfs/imagetest on /exports/imagetest type none (rw,bind) /etc/exports file: /exports 10.0.4.0/24(ro,insecure,sync,wdelay,no_subtree_check,no_root_squash,fsid=0,crossmnt)

Is there any chance the system-config-netboot* rpms upstream removed from CentOS6 could be provided in extras? The CentOS5 SRPM builds cleanly under CentOS6, and upstream's workaround is insufficient as it only covers diskless clients, not helpful if you need pxeos.

Hi. I'm having trouble accessing a shared directory over NFSv4 on a CentOS 4.5 machine. My export file reads /test 10.0.0.0/255.0.0.0(ro,async,insecure,nohide,no_subtree_check) Running the mount command with NFSv4 as the filesystem gives me a permission denied error. [root at pebble-anoop ~]# mount -v -t nfs4 pebble-anoop:/test/ /mnt/ mount: pinging: prog 100003 vers 4 prot tcp port

Hi everyone Version 4.0.0alpha18-GIT-bfc7481 openSUSE 12.1 Conventional nfs4 export works fine, but I'm having trouble kerberizing it for Samba 4 for my Samba 4 users. I've setup the nfs4 pseudo stuff like this: hh3:/ # mkdir /export hh3:/ # mkdir /export/home hh3:/ # mount --bind /home /export/home Here is /etc/exports: /export

Hi All, I'm having a bit of difficulty getting a CentOS 5.5 Kerberized NFSv4 server working. This server is configured as a Winbind client to a Windows 2003 Active Directory. I've successfully bound it to AD and I am able to authenticate. I've successfully created a NFSv4 entry in /etc/exports to export the /exports directory and I can successfully mount a non-Kerberized NFSv4

How to configure Diskless environment in CentOS 5.1. Please help me out Regards, Gopinath M Signal Networks Pvt. Ltd. Smile... it increases your face value! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20080410/bf9d216c/attachment-0001.html>

Hi there, we are using a couple of Diskless Linux Workstations in conjunction with PXE capabable Network cards to boot the system. This works fine using pxelinux. However, there are a few workstations left, which are not able to boot via PXE and thus this workstations need a Kernel on a floppy disk and an additional initrd image. The Problem with is, that both of them don't fit on a floppy

Using the 2.0.6 demo cd image, I booted the supplied freebsd image and rsync''d the file system to an NFS server. However I don not seem to be able to succesfully boot from it the system just hangs here: xn0: bpf attached xn0: Ethernet address: aa:00:00:61:1c:d4 lo0: bpf I have modified /sbin/start_freebsd.sh and /etc/xen/freebsd.py to generate the following configuration: xendemo:~#

I think this is an NFS or ext4 question, but wanted to post this here for a sanity check. :) I've been searching for over a week for a solution and have turned up nil. I'm trying to rsync with options -AX over an NFSv4 mount TO an ext4 drive FROM an ext4 drive and both have acl and user_xattr enabled. The command: rsync -aAX /data/ /mnt/back/data results in: rsync:

I'm trying to boot RedHat 9.0 on a diskless PC from a head machine running Redhat 9.0. The network appears to be setup correctly. I can boot the installation disk image fine using pxelinux. What I am trying to setup is a number of different Linux systems each with its own root directory on the head machine. I am hoping that I don't have to modify the kernel for any of these systems.

Does anyone have any good how-to's or documentation on setting up read only root NFS for pxe booting diskless computers? A few months ago I stumbled upon an official Redhat doc through a google search(not hosted by redhat and I cannot find it anywhere on the Redhat site) written by Dave Kline named "Configuring diskless clients with Red Hat Enterprise Linux" from 2011. It seemed to