Re: Unable to run pxesconfig from a 2.6 based system?

On Thu, 2004-03-11 at 23:07, Diego Torres Milano wrote:
> Then, the problem should be in PxesconfigModel::check_fstab, try adding
> DEBUG.

DEBUG=4

Results:
# pxesconfig
PxesconfigModel::new
PxesconfigModel::new: blessing
PxesconfigModel::read_configuration_file(/etc/pxes/pxesconfig.conf,0)
PxesconfigModel::hashFromFile(/etc/pxes/pxesconfig.conf, 0)
PxesconfigModel::read_configuration_file(/root/.pxesconfig.conf,0)
PxesconfigModel::hashFromFile(/root/.pxesconfig.conf, 0)
changed drived by kernel_arch = i586 at
/usr/lib/perl5/vendor_perl/5.8.0/Pxesconfig/PxesconfigModel.pm line 482.
PxesconfigModel::initial_checks()
PxesconfigModel::is_mounted()
PxesconfigModel::check_fstab()
PxesconfigModel::check_fstab:
        searching for
'^/tmp/pxes.initrd\s+/tmp/pxes\s+ext2\s+loop,noauto,user,owner'
        returning 0
self=PxesconfigModel=HASH(0x89e3124) at
/usr/lib/perl5/vendor_perl/5.8.0/Pxesconfig/PxesconfigModel.pm line 559.
Unmounting initial ramdisk.
PxesconfigModel::is_mounted()
Fatal error:
Needed entry missing from /etc/fstab.
Add an entry like:
/tmp/pxes.initrd        /tmp/pxes       ext2    loop,noauto,user,owner 
0 0

> On Thu, 2004-03-11 at 18:34, Chris Gianelloni wrote:
> > On Thu, 2004-03-11 at 15:32, Diego Torres Milano wrote:
> > > Yes, of course.
> > > But we're sure now that /etc/fstab is read and correct.
> > > Try:
> > > # dd if=/dev/zero of=/tmp/pxes.initrd bs=1024 count=1024
> > > # /sbin/mke2fs -F /tmp/pxes.initrd
> > > # mount /tmp/pxes
> > 
> > No error... and...
> > 
> > # mount
> > /tmp/pxes.initrd on /tmp/pxes type ext2
> > (rw,noexec,nosuid,nodev,loop=/dev/loop0)
> > 
> > > On Thu, Mar 11, 2004 at 02:50:49PM -0500, Chris Gianelloni wrote:
> > > > On Thu, 2004-03-11 at 11:42, Diego Torres Milano wrote:
> > > > > Have you tested the mount manually ?
> > > > > i.e:
> > > > > # touch /tmp/pxes.initrd
> > > > > # mount /tmp/pxes
> > > > 
> > > > This results in:
> > > > # touch pxes.initrd
> > > > # mount pxes.initrd
> > > > mount: wrong fs type, bad option, bad superblock on /dev/loop0,
> > > >        or too many mounted file systems
> > > >        (could this be the IDE device where you in fact use
> > > >        ide-scsi so that sr0 or sda or so is needed?)
> > > > 
> > > > Would I not need to make a file-system on it, first?
> > > > 
> > > > > 
> > > > > On Thu, Mar 11, 2004 at 10:26:23AM -0500, Chris Gianelloni wrote:
> > > > > > I have having trouble running pxesconfig from my 2.6 system.  For some
> > > > > > reason, it thinks I do not have the fstab entries for the loop that PXES
> > > > > > needs, but I do.
> > > > > > 
> > > > > > Has anyone come across this sort of problem?
> > > > > > 
> > > > > > # pxesconfig
> > > > > > Fatal error:
> > > > > > Needed entry missing from /etc/fstab.
> > > > > > Add an entry like:
> > > > > > /tmp/pxes.initrd        /tmp/pxes       ext2    loop,noauto,user,owner 
> > > > > > 0 0
> > > > > > 
> > > > > > # grep pxes /etc/fstab
> > > > > > /tmp/pxes.initrd        /tmp/pxes       ext2    loop,noauto,users,owner 
> > > > > > 0 0
> > > > > > 
> > > > > > 
> > > > > > -- 
> > > > > > Chris Gianelloni
> > > > > > Developer, Gentoo Linux
> > > > > > Games Team
> > > > > > 
> > > > > > Is your power animal a pengiun?
> > > > -- 
> > > > Chris Gianelloni
> > > > Developer, Gentoo Linux
> > > > Games Team
> > > > 
> > > > Is your power animal a pengiun?
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> pxes-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pxes-devel
-- 
Chris Gianelloni
Developer, Gentoo Linux
Games Team

Is your power animal a pengiun?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBAUcvfkT4lNIS36YERApLAAKCmdMbxAFg9TAe+0Qa9IDYTjs3qOACfbpf8
opagzmUZ4qi0S+xLfBjb6lY=
=CQo/
-----END PGP SIGNATURE-----