public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Hergl <weehawk@weehawk.de>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Installing 1.0-rc6-r9 on Vaio Laptop
Date: Thu Sep  6 15:17:02 2001	[thread overview]
Message-ID: <3B97E875.4060302@weehawk.de> (raw)
In-Reply-To: 20010905093702.D23173@cvs.gentoo.org

Hi Daniel,

Daniel Robbins wrote

> OK: PCMCIA support currently isn't tested or fully enabled.  Also, we *do* have
> support for every filesystem on the boot CD; however, you need to "insmod" the
> modules with -r9 and earlier.  Things should be much easier with -r10, which
> includes modprobe.


Well, the pcmcia modules worked for me as provided in the build =) But 
short noted about how to insmod/modprobe the pcmcia or the filesystem 
modules. Can save fuzz, I suppose.


> 
> pcmcia-cs seems to choke when you use certain configuration options.  What
> config options did you use?  We made our options more correct, and all of
> the sudden the builds started dying.


Hmm, tried a standart thing, really! Just erased the lvm and lm-sensors 
from the USE-Variabe, as it is of no use on my laptop. I manually copied 
the pcmcia-cs startup script over, and seems to work, but I suppose 
that'S one of the ebuilds that is not r6 ready, as it copied stuff to 
rc.d/config, or at least should?


> 
> A Gentoo Linux version of the pcmcia startup script (with dependencies) is
> currently in development.


I will try to learn the new startupscripts, but was discussing with 
darks today earlier: is it possible to update savely the bootstraps?
BEcause I have V 1.6.1 AND 1.6.2 in var/db/pkg... (last time I 
deinstalled a double package, I killed the system, it was the glibc.... 
yes, I'm playfull)


> 
> What do you mean by "mount/umount and du don't work"?


Ah ja, worked wit Darks on that again. Seems like my startup scripts are wacko behaving.

My /etc/mtab is a file of length 0. When I do 'ln -s /proc/mounts /etc/mtab', mount and 

df and booting works fine. Till.... yeah, the next reboot. Then I got a file of length 

0 again =P
Some script of the r9 is messing this up, searching for it....


> 
>>6. Yah, and with the yesterday's version of the portage tree I can't 
>>compile Xfree. Period, any version. Is that knowen yet? If not, tell me 
>>and I look up the exact lines where it bounces out (short after the 
>>depencies calculation, I guess)
>>
> 
> Yes, please post the error dump.


Eh, sue me, with the latest rsync and latest xfree ebuild things worked. 
  Kde2.2 is up and running. Though I get compile errors with 
kdemultimedia....

Sound is working. The desktop doku might need to be updated for the new scripts?

Like, starting kde at bootup and stuff. =P


To speak about ebuilds getting reworked... is there any chance to mark 
the reworked ebuilds for r6? Just like .... ebuildxyz_r6-rx.ebuild? I'm 
confused now which might work and which not.... OR should I just wait 
three weeks and all is done then?

Thanks for your answer, is fun to work with Gentoo,


Christian




      reply	other threads:[~2001-09-06 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05  2:42 [gentoo-dev] Installing 1.0-rc6-r9 on Vaio Laptop Christian Hergl
2001-09-05  6:41 ` Jerry A!
2001-09-05  9:38 ` Daniel Robbins
2001-09-06 15:17   ` Christian Hergl [this message]

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=3B97E875.4060302@weehawk.de \
    --to=weehawk@weehawk.de \
    --cc=gentoo-dev@cvs.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