Wait, what? Just yesterday David Cantrell told me it should still be
running, because not everything has moved into dracut. Certainly things
are not all right in pure dracut land. I'm a big confused here and need
some guidance.
--
Jesse Keating
Fedora -- Freedom² is a feature!
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
05-11-2012, 04:51 PM
Dan Horák
linuxrc.s390 is dead in anaconda
Jesse Keating pÃ*Å¡e v Pá 11. 05. 2012 v 09:31 -0700:
> On 05/11/2012 04:10 AM, Dan Horák wrote:
> > ## s390-specific setup
> > %if basearch in ("s390", "s390x"):
> > - remove sbin/init
> > - move usr/share/anaconda/linuxrc.s390 sbin/init
>
> Wait, what? Just yesterday David Cantrell told me it should still be
> running, because not everything has moved into dracut. Certainly things
> are not all right in pure dracut land. I'm a big confused here and need
> some guidance.
Oh, I'm confused then, but I had to do this change today to get f17
installation start with the latest dracut and lorax and co. The
installer started to ask for network setting although everything was set
via dracut parameters and already set in the VM.
Dan
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
05-11-2012, 05:13 PM
David Cantrell
linuxrc.s390 is dead in anaconda
On Fri, May 11, 2012 at 09:31:38AM -0700, Jesse Keating wrote:
> On 05/11/2012 04:10 AM, Dan Horák wrote:
> > ## s390-specific setup
> > %if basearch in ("s390", "s390x"):
> >- remove sbin/init
> >- move usr/share/anaconda/linuxrc.s390 sbin/init
>
> Wait, what? Just yesterday David Cantrell told me it should still
> be running, because not everything has moved into dracut. Certainly
> things are not all right in pure dracut land. I'm a big confused
> here and need some guidance.
I should have clarified what I meant. My statement was based on what was or
should still be happening the nightlies. It's close enough to dead it
should just be removed from the image and then we fill in the blanks for any
missing parts. s390x lacks the ability for an elegant transition in the
case of the initrd. Much more is changing on s390x than on other
architectures.
--
David Cantrell <dcantrell@redhat.com>
Supervisor, Installer Engineering Team
Red Hat, Inc. | Westford, MA | EST5EDT
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
05-11-2012, 05:16 PM
Jesse Keating
linuxrc.s390 is dead in anaconda
On 05/11/2012 09:51 AM, Dan Horák wrote:
Oh, I'm confused then, but I had to do this change today to get f17
installation start with the latest dracut and lorax and co. The
installer started to ask for network setting although everything was set
via dracut parameters and already set in the VM.
That is true, linuxrc.s390 is doing too much currently. However without
it being used I'm seeing things like sshd not being started, dasd
devices not being detected in anaconda, and who knows what else. So I
think we're broken either way :/
--
Jesse Keating
Fedora -- Freedom² is a feature!
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
05-11-2012, 05:41 PM
Dan Horák
linuxrc.s390 is dead in anaconda
Jesse Keating pÃ*Å¡e v Pá 11. 05. 2012 v 10:16 -0700:
> On 05/11/2012 09:51 AM, Dan Horák wrote:
> > Oh, I'm confused then, but I had to do this change today to get f17
> > installation start with the latest dracut and lorax and co. The
> > installer started to ask for network setting although everything was set
> > via dracut parameters and already set in the VM.
>
> That is true, linuxrc.s390 is doing too much currently. However without
> it being used I'm seeing things like sshd not being started, dasd
> devices not being detected in anaconda, and who knows what else. So I
> think we're broken either way :/
I had network and dasds initialized with dracut leading to a successful
install and successful reboot afterwards. The sshd probably needs more
investigation because even with sshd=1 (suggested by Jan Stodola from
RTT) it didn't come up. What can be missing in my understanding is a
compatibility layer with the "old way" of setting things on s390x, but
that's not directly necessary for Fedora 17.
Dan
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list