From: sdoma <sdoma@karneval.cz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Wow, this is what I call stable! ;-)
Date: Sat, 23 Sep 2006 20:51:58 +0200 [thread overview]
Message-ID: <1159037518.4619.14.camel@localhost> (raw)
In-Reply-To: <1159008325.9333.24.camel@frankies>
Uff,
... all went well :oD
I've re-emerged shadow, logged out and logged in and even rebooted the
system and (otherwise I wouldn't be able to send this post) all is
living again.
Thank you guys for the hints and for this system (:oD)
Frank
PS: Just a minor issue: Is there a way to use "normal" SysV booting on
Gentoo? What I mean is the booting style with the [0-9][0-9]something
in /etc/[init.d/]rc[0-9] what usuelly are links to /etc/init.d instead
of this simpleinit (?) style booting?
Xcuse me, I'm mostly working on AIX, HP-UX, Solaris, Dynix and Tru64, so
the Gentoo boot style is an annoying one for me. .. I'm not saying that
it is a bad one with this stating ;o)
I started on Linux with Slackware. They use BSD style booting. THERE it
was easy to replace this. How on Gentoo?
On Sat, 2006-09-23 at 12:45 +0200, sdoma wrote:
> Thanks for the hint. I've unmerged shadow AND pam just now.
>
> emerge failed on glibc, saying the new version is nplt-only (I don't get
> the picture here ... I use nplt on my system). Well restarting emerge
> (no resume, just a new emerge -u world, which says it will rebuild 48
> further packages) continues. Let's see if (and whwere) it fails and if
> everything is working afterwards.
>
> So I'll remerge shadow after this if all goes well.
>
> Frank
>
>
> On Sat, 2006-09-23 at 09:24 +0200, Remy Blank wrote:
> > sdoma wrote:
> > > emerge -u says, that pam-login is blocked (blocked by shadow)...
> > > I ``emerge -C shadow'' ...... and emerge tells me, that pam-login is
> > > blocked by shadow.
> > > I unmerge pam-login, and emerge tells me, that openal is blocked by
> > > amother package ... ``emerge --pretend openal'' doesn't show any
> > > blockers. BTW, I will NOT uninstall openal.
> > >
> > > What's going on?
> >
> > You only had to unmerge pam-login and update shadow. The functionality
> > of pam-login is now provided by shadow, so that the former is no longer
> > needed.
> >
> > Hint: Don't logout between the unmerge and the update, or you'll be
> > locked out.
> >
> > Hint 2: This question has been asked (and answered) several times on
> > this mailing list and in the forums. Please search the archives before
> > posting.
> >
> > -- Remy
> >
> >
> > Remove underscore and suffix in reply address for a timely response.
> >
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-23 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-23 6:33 [gentoo-user] Wow, this is what I call stable! ;-) sdoma
2006-09-23 7:18 ` sdoma
2006-09-23 9:47 ` Greg Bur
2006-09-23 10:36 ` sdoma
2006-09-23 7:24 ` [gentoo-user] " Remy Blank
2006-09-23 10:45 ` sdoma
2006-09-23 18:51 ` sdoma [this message]
2006-09-23 19:24 ` Arturo 'Buanzo' Busleiman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1159037518.4619.14.camel@localhost \
--to=sdoma@karneval.cz \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox