On 4/10/06, Richard Fish <[EMAIL PROTECTED]> wrote:
> On 4/10/06, Daevid Vincent <[EMAIL PROTECTED]> wrote:
> > *sigh*
> >
> > Why is there always something breaking?
>
> Maybe a ~x86 system just isn't for you....

I'll second this one... You don't seem prepared for the testing tree...

>
> > * Dependancy info is missing! Please run
> > *   #/sbin/depscan.sh
> > * to fix this.
>
> This message is generated by /lib/rcscripts/sh/rc-services.sh.  It
> tries to read /var/lib/init.d/deptree, and looks for a specific
> variable to be set that indicates the dependacy information was read.
>
> Does /var/lib/init.d/deptree exist on your system?  It should have
> several hundred lines in the form of:
>
> RC_DEPEND_TREE[0]=69
> RC_DEPEND_TREE[10]="consolefont"
> RC_DEPEND_TREE[10+2]="keymaps localmount"
> RC_DEPEND_TREE[10+3]=
> RC_DEPEND_TREE[10+4]=
> RC_DEPEND_TREE[10+5]=
> RC_DEPEND_TREE[10+6]="local"
>
> You can also try running depscan.sh with the --debug option to see
> what, exactly, it does.
>
> My best guess at this point though is that /var/lib/init.d no longer
> exists for some reason.  Is /var a separate filesystem?  Did it get
> mounted?

Yes, that's my bet too, maybe a baselayout update followed by a wrong
etc-update?! I once had to remove the file and reemerge the app so it
would update the configuration.

To do that, I booted the livecd, chrooted and reemerged the failing
app, you could do that for your system, you'll probably get networking
without mess with ifconfig or iwconfig (because you seem unfamiliar
with these tools). There you could reemerge it all, even update it,
but sincerely, you should not need network to reemerge something
already emerged once (don't clean your distfiles before being sure you
don't need them anymore).

--
Daniel da Veiga
Computer Operator - RS - Brazil
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V-
PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++
------END GEEK CODE BLOCK------

-- 
[email protected] mailing list

Reply via email to