[Sisuite-users] /dev empty

2005-10-19 Thread John Stile
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 image server: 
 systemimager-3.2.3, 
 tftpd-hpa-0.40-4.1, 
 tftp-hpa-0.40-4.1 
 pxe-1.4.2-1.   
On the client:
 systemimager-3.2.3.



---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [Sisuite-users] mk2fs and bytes per inode

2005-10-19 Thread Daniel Widyono
> 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, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [Sisuite-users] /dev empty

2005-10-19 Thread John Jolet
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 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 image server:
 systemimager-3.2.3,
 tftpd-hpa-0.40-4.1,
 tftp-hpa-0.40-4.1
 pxe-1.4.2-1.
On the client:
 systemimager-3.2.3.



---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,  
discussions,

and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users





---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


[Sisuite-users] how to rsync on non-standard port

2005-10-19 Thread John Stile
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://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [Sisuite-users] /dev empty

2005-10-19 Thread John Stile
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 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 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 image server:
> >  systemimager-3.2.3,
> >  tftpd-hpa-0.40-4.1,
> >  tftp-hpa-0.40-4.1
> >  pxe-1.4.2-1.
> > On the client:
> >  systemimager-3.2.3.
> >
> >
> >
> > ---
> > This SF.Net email is sponsored by:
> > Power Architecture Resource Center: Free content, downloads,  
> > discussions,
> > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > ___
> > Sisuite-users mailing list
> > Sisuite-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/sisuite-users
> >
> 
> 
> 
> ---
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> ___
> Sisuite-users mailing list
> Sisuite-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sisuite-users



---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [Sisuite-users] /dev empty

2005-10-19 Thread John Jolet
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 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 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 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 image server:
 systemimager-3.2.3,
 tftpd-hpa-0.40-4.1,
 tftp-hpa-0.40-4.1
 pxe-1.4.2-1.
On the client:
 systemimager-3.2.3.



---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,
discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users






---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,  
discussions,

and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users





---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,  
discussions,

and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users





---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


[Sisuite-users] message.txt menu not displaying

2005-10-19 Thread John Stile
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/X86PC/UNDI/linux-install/pxelinux.cfg/syslinux.cfg
looks like this:
BEGIN syslinux.cfg
DEFAULT rebuild
LABEL localhost
  LOCALBOOT 0
LABEL rebuild
  DISPLAY message.txt
  PROMPT 1
  TIMEOUT 50
  KERNEL ../X86PC/UNDI/linux-install/kernel
  APPEND vga=extended initrd=../X86PC/UNDI/linux-install/initrd.img
root=/dev/ram tmpfs_size=800M
END syslinux.cfg
BEGIN message.txt
01=
0e
0c  Welcome to John's SystemImager Image server
0e
0e  To boot the OS choose 'local' or just wait.
0e
0e  Your boot options are:
0e local  --> Boot from local kernel
0e rebuild--> Rebuild with
0e
0e  questions?? --> [EMAIL PROTECTED]
0e
01=0b
END message.txt



---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [Sisuite-users] /dev empty

2005-10-19 Thread John Stile
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 found anything
that would exclude all tmpfs mounts.

On Wed, 2005-10-19 at 17:32 -0500, John Jolet wrote:
> 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 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 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 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 image server:
> >>>  systemimager-3.2.3,
> >>>  tftpd-hpa-0.40-4.1,
> >>>  tftp-hpa-0.40-4.1
> >>>  pxe-1.4.2-1.
> >>> On the client:
> >>>  systemimager-3.2.3.
> >>>
> >>>
> >>>
> >>> ---
> >>> This SF.Net email is sponsored by:
> >>> Power Architecture Resource Center: Free content, downloads,
> >>> discussions,
> >>> and more. http://solutions.newsforge.com/ibmarch.tmpl
> >>> ___
> >>> Sisuite-users mailing list
> >>> Sisuite-users@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users
> >>>
> >>>
> >>
> >>
> >>
> >> ---
> >> This SF.Net email is sponsored by:
> >> Power Architecture Resource Center: Free content, downloads,  
> >> discussions,
> >> and more. http://solutions.newsforge.com/ibmarch.tmpl
> >> ___
> >> Sisuite-users mailing list
> >> Sisuite-users@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/sisuite-users
> >>
> >
> >
> >
> > ---
> > This SF.Net email is sponsored by:
> > Power Architecture Resource Center: Free content, downloads,  
> > discussions,
> > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > ___
> > Sisuite-users mailing list
> > Sisuite-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/sisuite-users
> >
> 
> 
> 
> ---
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> ___
> Sisuite-users mailing list
> Sisuite-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sisuite-users



---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [Sisuite-users] how to rsync on non-standard port

2005-10-19 Thread John Stile
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? 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://solutions.newsforge.com/ibmarch.tmpl
> ___
> Sisuite-users mailing list
> Sisuite-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sisuite-users



---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [Sisuite-users] message.txt menu not displaying

2005-10-19 Thread John Jolet
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 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/X86PC/UNDI/linux-install/pxelinux.cfg/ 
syslinux.cfg

looks like this:
BEGIN syslinux.cfg
DEFAULT rebuild
LABEL localhost
  LOCALBOOT 0
LABEL rebuild
  DISPLAY message.txt
  PROMPT 1
  TIMEOUT 50
  KERNEL ../X86PC/UNDI/linux-install/kernel
  APPEND vga=extended initrd=../X86PC/UNDI/linux-install/initrd.img
root=/dev/ram tmpfs_size=800M
END syslinux.cfg
BEGIN message.txt
01 
=

0e
0c  Welcome to John's SystemImager Image server
0e
0e  To boot the OS choose 'local' or just wait.
0e
0e  Your boot options are:
0e local  --> Boot from local kernel
0e rebuild--> Rebuild with
0e
0e  questions?? --> [EMAIL PROTECTED]
0e
01 
=0b

END message.txt



---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads,  
discussions,

and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users





---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [Sisuite-users] message.txt menu not displaying

2005-10-19 Thread Charles Galpin


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 requires that filenames 
(including any relative path) are 127 characters or shorter in length."


I don't have pxelinux.0, but I found message.txt displays if I put it 
in /tftboot (where I have pxelinux.bin)


That site has other cool info, like how you can define files to display 
when you press F1,F2, etc too!


hth
charles



---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [Sisuite-users] message.txt menu not displaying

2005-10-19 Thread John Stile
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 but fail to see
message.txt 

FIX: 
1. Moved message.txt to:
  /var/lib/tftpboot/X86PC/UNDI/linux-install/ 

2. Changed DISPLAY line in syslinux.cfg:
  DISPLAY  ../X86PC/UNDI/linux-install/message.txt


Ultimately, I'd like to figure out how to make everything look at
just /var/lib/tftpboot/pxelinux.cfg/, but I need to learn about
pxe.config.  With PXE, TFTP, and systemimager all looking for this
directory in different places, it gets really confusing.

On Wed, 2005-10-19 at 15:40 -0700, John Stile wrote: 
> 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/X86PC/UNDI/linux-install/pxelinux.cfg/syslinux.cfg
> looks like this:
> BEGIN syslinux.cfg
> DEFAULT rebuild
> LABEL localhost
>   LOCALBOOT 0
> LABEL rebuild
>   DISPLAY message.txt
>   PROMPT 1
>   TIMEOUT 50
>   KERNEL ../X86PC/UNDI/linux-install/kernel
>   APPEND vga=extended initrd=../X86PC/UNDI/linux-install/initrd.img
> root=/dev/ram tmpfs_size=800M
> END syslinux.cfg
> BEGIN message.txt
> 01=
> 0e
> 0c  Welcome to John's SystemImager Image server
> 0e
> 0e  To boot the OS choose 'local' or just wait.
> 0e
> 0e  Your boot options are:
> 0e local  --> Boot from local kernel
> 0e rebuild--> Rebuild with
> 0e
> 0e  questions?? --> [EMAIL PROTECTED]
> 0e
> 01=0b
> END message.txt
> 
> 
> 
> ---
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> ___
> Sisuite-users mailing list
> Sisuite-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sisuite-users



---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [Sisuite-users] /dev empty

2005-10-19 Thread Jan Groenewald
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
-- 
   .~.
   /V\ Jan Groenewald
  /( )\www.aims.ac.za
  ^^-^^


---
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
___
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users