Hi
On Wed, Oct 19, 2005 at 04:09:05PM -0500, John Jolet wrote:
> on my systems it does the same thing, I assumed it was because gentoo
> uses udev. I put a step in my autoinstall script that rsyncs /dev/*
> right before the chroot step.
add devfs=mount to the kernel options
Jan
--
.~.
Solved. A soft link caused wrong path, so message.txt was not found.
This directory:
/var/lib/tftpboot/X86PC/UNDI/linux-install/pxelinux.cfg
was a soft link to:
/var/lib/tftpboot/pxelinux.cfg
Both my pxelinux script and message.txt were in there.
The client would see read the pxelinux script b
On Oct 19, 2005, at 6:40 PM, John Stile wrote:
My clients installing via PXE, but do not display the message.txt menu.
The pxe/syslinux site, http://syslinux.zytor.com/pxe.php says
"Note that all filename references are relative to the directory
pxelinux.0 lives in. PXELINUX generally requi
It's never displayed it for me, eitherbut that's not real high on
my list of things to worry about, so I never looked into it.
On Oct 19, 2005, at 5:40 PM, John Stile wrote:
My clients installing via PXE, but do not display the message.txt
menu.
After the timeout, they boot what ever th
This worked:
getimage --golden-client my_golden_client:5004 \
--image 192.168.0.50 \
--ip-assignment REPLICANT \
--post-install reboot
On Wed, 2005-10-19 at 14:24 -0700, John Stile wrote:
> Ihere an option to getimage to make it use extra rsync switches? Su
On the client, I only see reference to '/dev ' in the client.
/etc/systemimager/mounted_filesystems
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
Once the client is running, and I run 'mount -l', /dev does not show up
as mounted tmpfs.
I've searched for tmpfs in the other scripts, but haven't
My clients installing via PXE, but do not display the message.txt menu.
After the timeout, they boot what ever the DEFAULT image is set to.
They are hooked up to a standard lcd. Where would I find an error log
for this stage?
Below I have included my the .cfg and message.txt
My /var/lib/tftpboot
I'm trying to recall... I believe I saw an explicit ignore of /dev
somewhere...it would be maybe in the client-side prepareclient stuff.
On Oct 19, 2005, at 5:23 PM, John Stile wrote:
That is strange. rsync shouldn't ignore /dev, unless configured to do
so. Do you know where getimage read i
That is strange. rsync shouldn't ignore /dev, unless configured to do
so. Do you know where getimage read it's rsync config options?
On Wed, 2005-10-19 at 16:09 -0500, John Jolet wrote:
> on my systems it does the same thing, I assumed it was because gentoo
> uses udev. I put a step in my aut
Ihere an option to getimage to make it use extra rsync switches? Such as
changing the port or adding '-e ssh'
---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solu
on my systems it does the same thing, I assumed it was because gentoo
uses udev. I put a step in my autoinstall script that rsyncs /dev/*
right before the chroot step.
On Oct 19, 2005, at 2:05 PM, John Stile wrote:
My golden client images have an empty /dev directory.
This causes many prob
> Now that I've made a spectacular introduction, I'm going to sheepishly
> go hide. Thanks to you both John and Brian!
Welcome!
:)
Dan W.
---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, dis
My golden client images have an empty /dev directory.
This causes many problems when the newly imaged system tries to boot. I
can hack around it by coppying /dev from another system, but each time I
'getimage' dev is empty.
I couldn't find an 'exclude /dev' in all the configs.
Any ideas?
On the
13 matches
Mail list logo
