On Monday 03 April 2006 04:21, Neil Bothwick wrote:
> On Sun, 2 Apr 2006 16:34:01 -0600, Peter Kelly wrote:
> > I only see the [broken] message when I use `rc-status -s`.
> > If I just type 'rc-status', I get a correct response for the default
> > runlevel.
>
> There's a bug files here: http://bugs
On Sun, 2 Apr 2006 16:34:01 -0600, Peter Kelly wrote:
> I only see the [broken] message when I use `rc-status -s`.
> If I just type 'rc-status', I get a correct response for the default
> runlevel.
There's a bug files here: http://bugs.gentoo.org/show_bug.cgi?id=113755
I see the same now, I was
On Saturday 01 April 2006 19:22, Jeremy Olexa wrote:
> Peter Kelly wrote:
> > Now, it shows that every service is [broken], but the advice to remove
> > the broken service using rc-update -d (service) and add it in again does
> > nothing. Everything is still [broken].
> >
> > Anyone seen this, and
Peter Kelly wrote:
Now, it shows that every service is [broken], but the advice to remove the
broken service using rc-update -d (service) and add it in again does nothing.
Everything is still [broken].
Anyone seen this, and have an idea how to fix it?
Hmm, I had this happen once to me befor
Hola!
After a recent rebuild starting with a failed hard drive, I think I've got
everything nailed down... except
root ~ $ rc-status -s default
Runlevel: all
alsasound [ broken ]
apmd[ broken ]
...
xdm
5 matches
Mail list logo