Thanks and good luck with the vpn work.I'll be
expecting to hear from you tommorow then.

--- John Jolet <[EMAIL PROTECTED]> wrote:

> I'll try to get to that tomorrow.  boss  is going
> out of town tonight and 
> wants the vpn up before he leaves...considering it's
> on my desk at the 
> moment, and not in the datacenter, I have a hill to
> climb.
> 
> On Monday 14 November 2005 13:29, Jide Osatuyi
> wrote:
> > Hi John,
> > I tried to modify the autoinstallscript to use lvm
> but
> > I guess I did a bad job at that.I will appreciate
> if I
> > can see the autoinstallscript you use for lvm
> > autoinstalls.
> > Thanks.
> >
> > --- John Jolet <[EMAIL PROTECTED]> wrote:
> > > yeah, but that machine's on an isolated network.
> > > I'll try to get ahold of it
> > > next week.
> > > On Friday 11 November 2005 07:07, Jide Osatuyi
> > >
> > > wrote:
> > > > Can I see the autoinstallscript you use for
> lvm
> > > > autoinstalls maybe I could use it or at least
> > >
> > > compare
> > >
> > > > with mine.
> > > > Thanks
> > > >
> > > > --- John Jolet <[EMAIL PROTECTED]> wrote:
> > > > > If you used lvm on that volume, you have a
> whole
> > > > > other set of issues to deal
> > > > > with.  email me your autoinstall script as
> an
> > > > > attachment and I'll look at it
> > > > > and compare it to the one I use for lvm
> > > > > autoinstalls.
> > > > >
> > > > > One gotcha is you MUST make sure the kernel
> > > > > downloaded out of tftpboot is
> > > > > compiled with the proper lvm options.  If
> you
> > > > > installed them as modules, they
> > > > > should be in the initrd, but will not be
> > > > > automatically loaded without some
> > > > > gymnastics.  I prefer to compile those
> pieces
> > >
> > > into
> > >
> > > > > the kernel.
> > > > > On Wednesday 09 November 2005 08:12, Jide
> > >
> > > Osatuyi
> > >
> > > > > wrote:
> > > > > > Thanks that worked.I eidted the
> autoinstall
> > > > >
> > > > > script.
> > > > >
> > > > > > now it says
> > > > > > SGI XFS with no debug enabled
> > > > > > mks2fs -j /dev/VolGroup00/LogVol00 ||
> shellout
> > > > > > could not stat /dev/VolGroup00/LogVol00
> -No
> > >
> > > such
> > >
> > > > > file
> > > > >
> > > > > > or directory
> > > > > >
> > > > > > The device appraently does not exist; did
> you
> > > > >
> > > > > specify
> > > > >
> > > > > > i correctly?
> > > > > >
> > > > > > --- John Jolet <[EMAIL PROTECTED]> wrote:
> > > > > > > control-c and get a shell.  fdisk -l, if
> you
> > > > >
> > > > > can.
> > > > >
> > > > > > > the hard drive has just
> > > > > > > moved.  when you find it, just edit the
> > > > >
> > > > > autoinstall
> > > > >
> > > > > > > script and change hdc to
> > > > > > > hda, or whatever.
> > > > > > > On Tuesday 08 November 2005 09:10, Jide
> > >
> > > Osatuyi
> > >
> > > > > > > wrote:
> > > > > > > > I copied kernel and initrd.img from
> the
> > >
> > > root
> > >
> > > > > and
> > > > >
> > > > > > > > /systemimager/i386/boot....
> respectively
> > >
> > > and
> > >
> > > > > it
> > > > >
> > > > > > > works
> > > > > > >
> > > > > > > > fine.
> > > > > > > > I'm at the autoinstall stage now and
> I'm
> > > > >
> > > > > getting
> > > > >
> > > > > > > > this;
> > > > > > > > get_arch
> > > > > > > > Partitioning /dev/hdc...
> > > > > > > > Old partition table for /dev/hdc:
> > > > > > > > Error: Could not stat device /dev/hdc
> - No
> > > > >
> > > > > such
> > > > >
> > > > > > > file
> > > > > > >
> > > > > > > > or directory.
> > > > > > > > parted -s -- /dev/hdc mklabel msdos ||
> > > > >
> > > > > shellout
> > > > >
> > > > > > > > any ideas what's going on here and how
> i
> > >
> > > can
> > >
> > > > > fix
> > > > >
> > > > > > > it?
> > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > --- John Jolet <[EMAIL PROTECTED]> wrote:
> > > > > > > > > On Monday 07 November 2005 15:24,
> Jide
> > > > >
> > > > > Osatuyi
> > > > >
> > > > > > > > > wrote:
> > > > > > > > > > here's a copy of the output after
> I
> > > > >
> > > > > changed
> > > > >
> > > > > > > some
> > > > > > >
> > > > > > > > > > permissions:
> > > > > > > > > > [EMAIL PROTECTED] ~]# ls -lR /tftpboot/
> > > > > > > > > > /tftpboot/:
> > > > > > > > > > total 36
> > > > > > > > > > -r-xr-xr-x  2 root root     0 Nov 
> 2
> > >
> > > 13:18
> > >
> > > > > > > > > initrd.img
> > > > > > > > >
> > > > > > > > > > -r-xr-xr-x  2 root root     0 Nov 
> 4
> > >
> > > 08:31
> > >
> > > > > > > kernel
> > > > > > >
> > > > > > > > > ummmm, kernel and initrd.img are
> zero
> > > > >
> > > > > length?
> > > > >
> > > > > > > > > I think for the kernel to run, and
> > >
> > > initrd to
> > >
> > > > > > > load
> > > > > > >
> > > > > > > > > they need contents....
> > > > > > > > >
> > > > > > > > > > -rw-r--r--  1 root root 11822 Sep
> 28
> 
=== message truncated ===



        
                
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Sisuite-users mailing list
Sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to