Re: Launching anaconda on an already-installed system ...B

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2002-02-08 at 10:58, Panu Matilainen wrote:
> On Fri, 2002-02-08 at 17:36, ext Bill Crawford wrote:
> > On 8 Feb 2002, Panu Matilainen wrote:
> > 
> > > On Fri, 2002-02-08 at 16:55, ext Bill Crawford wrote:
> > > > On 8 Feb 2002, Panu Matilainen wrote:
> > > >
> > > > > On Fri, 2002-02-08 at 16:27, ext Bill Crawford wrote:
> > > > ...
> > > > > >  I've not been able to get this to work.  It launches OK (and I'm
> > > > > > quite impressed with the speed and whatnot of it running under the
> > > > > > real X server and not on the framebuffer) but then bombs out after
> > > > > > it gets to the "partitioning" dialog ... should that not be skipped
> > > > > > when I've specified a root to install to?
> > > >
> > > > > It still tries to *read* the partition tables on each drive you have
> > > > > present so you'll need to run it as root. It'd be nice to have at least
> > > > > a command line switch to turn the whole partitioning code off for these
> > > > > kind of purposes...
> > > >
> > > >  I want to run as non-root because I'm running it on a system I use
> > > > for all my work here.  I daren't break it.  I only have one working
> > > > box at home, too, so it's pretty much critical I don't damage it.
> > >
> > > Yup.. know the feeling :)
> > >
> > > >
> > > >  I'll have another poke aroung in Anaconda to see if I can switch
> > > > this off.  Or add YAOTDTDB (yet another option to disable the default
> > > > behaviour :o)
> > >
> > > Another way of course is to give yourself read access to /dev/hda &
> > > friends.
> > 
> >  Alas and alack, that doesn't work anyway; I'll have to run as root
> > (which makes me *very* nervous :o) :-
> > 
> > Traceback (most recent call last):
> >   File "/home/bill/rpm/tmp/anaconda-7.2.90//usr/lib/anaconda/gui.py", line 426, in nextClicked
> >     self.dispatch.gotoNext()
> >   File "/home/bill/rpm/tmp/anaconda-7.2.90//usr/lib/anaconda/dispatch.py", line 145, in gotoNext
> >     self.moveStep()
> >   File "/home/bill/rpm/tmp/anaconda-7.2.90//usr/lib/anaconda/dispatch.py", line 210, in moveStep
> >     rc = apply(func, self.bindArgs(args))
> >   File "/home/bill/rpm/tmp/anaconda-7.2.90//usr/lib/anaconda/partitioning.py", line 1900, in partitionObjectsInitialize
> >     partitions.setFromDisk(diskset)
> >   File "/home/bill/rpm/tmp/anaconda-7.2.90//usr/lib/anaconda/partitioning.py", line 1067, in setFromDisk
> >     labels = diskset.getLabels()
> >   File "/home/bill/rpm/tmp/anaconda-7.2.90//usr/lib/anaconda/partitioning.py", line 1517, in getLabels
> >     label = isys.readExt2Label(node)
> >   File "/usr/lib/anaconda/isys.py", line 365, in readExt2Label
> >     makeDevInode(device, "/tmp/disk")
> >   File "/usr/lib/anaconda/isys.py", line 237, in makeDevInode
> >     _isys.mkdevinode(name, fn)
> 
> 
> Aw.. forgot about that one :(
> 
> > SystemError: (1, 'Operation not permitted')
> > 
> >  I'm also a little concerned by those filenames (picked up from the
> > package build process, for some reason) ...
> 
> Anyway FWIW I've run anaconda in test & chroot install modes plenty of
> times and it hasn't eaten my boxes (yet :)
> 
> 	- Panu -

Me too.  I've done a lot of chroot installs without any problems.


Cheers,
  Brent


> 
> 
> 
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/anaconda-devel-list






[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux