From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: ideas/bugs
Date: 04 Mar 2002 17:49:00 +0200 [thread overview]
Message-ID: <1015256941.12551.5.camel@workshop.saharact.lan> (raw)
In-Reply-To: <20020304133446.A23286@matrix.netsoc.tcd.ie>
On Mon, 2002-03-04 at 15:34, Christian Loitsch wrote:
> here some updates:
>
> After some grepping I found the /etc/rc.conf file.
> I then made some research on the net to find the best consolefonts, and
> read in the french-howto that I should use the iso15-latin9 font.
> Couldn't find it :(
> On freshmeat.net/kbd somebody mentioned that kbd was more up to date
> then console-tools and surprise surprise: kbd has this font (at least I
> think it's the right one: lat9w-16).
>
> > * depscan is maybe not called with the right params in the boot-scripts:
> > depscan: Usage depscan ....
> Even though it gives this usage-message, the script seems to be executed
> without any errors.
>
> > * why do you ask users in you manual to execute depmod, if it is in 1 of
> > your boot-scripts?
> it is not a big deal, but at least I did not print the manual, but read
> it with less. And when I rebootet (of course a little bit nervous ;),
> it just made me even more nervous to focus on not forgetting to execute
> something later on...
> > * I guess the best way to avoid "broken" Gentoos because of forgetting
> > the -w option with nano, would be to make an alias right at the
> > beginning. (like nanow)
> I agree with Martin that in that it's better to educate, but let's be
> honest, who uses nano? At least all editors I use normally (ok, that's
> only vim ;) don't have this problem.
>
> > * because of wrong parameters the pcmcia-boot-script failed. But there
> > was no message. like [ FAIL ]
> hope nobody got this wrong. The reason the script failed, was that I
> moved the modules to another place, because I did not (and still don't)
> understand why cardmgr... loaded modules I compiled into the kernel. (
> as stars and not as M odules)
> Nevertheless there is something wrong with the PCMCIA-package.
>
> 1) cardmgr is a daemon and because my machine is sooooo slow, it doesn't
> have enough time to load all modules for my network-card.
> If I add a sleep 2 inside my net.eth0 everything works fine.
> I have _no_ idea how this could easily be fixed. (unless you let
> cardmgr call the right scripts, which of course is correct, but "ugly")
> 2) the pcmcia "-script" , even though in /etc/runlevels/default, does
> not produce a link in /dev/shm/.init.d/started. There is a directory in
> /dev/shm/.init.d/use/pcmcia containing a link to net.eth0 though.
> 3) obviously because of (2) the pcmcia script is called twice. Once for
> the net.eth0 script and another time after (on the screen even the last
> one)
Strange one. It should create the /dev/shm/.init.d/started/pcmcia link
if the script executed properly. If it do not have the green ok, it
means 2 things: 1) no 'eend' is present in the script. 2) it fails and
should give you a red '!!'
Other posiblity is a bug in the runscript.sh script. It however sounds
like the script fails, as there was a bug with the previous baselayout
that caused a script to start multiple times if it keeps failing. This
is fixed in the latest baselayout.
So, back to the pcmcia script. I can check it for syntax errors, but
the how and innerworkings of pcmcia is not known to me as I do not use
a notebook.
If possible, update to the latest baselayout (1.7.2 .. maybe 1.7.2-r1 or
1.7.3 that should come out tonight), and give feedback again. If you
can debug the problem, so the better.
> 4) the pcmcia-script does not "produce" a green star and no ok.
> It also is closed because of sending the term-signal to everyone
> and not because of calling pcmcia stop.
>
> Ignore my last untested point! (from the original mail)
> Everything is fine. I did not imagine that the scripts were this
> clever, and would insert them into /dev/shm/.init.d/started, even
> when called manually.
>
> At the moment I tend to fill out 2 bug-reports:
> 1) no ok for the pcmcia-script
> 2) race-condition
>
> Anything else?
>
> Christian
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
--
Martin Schlemmer
Gentoo Linux Developer, Desktop Team
Cape Town, South Africa
next prev parent reply other threads:[~2002-03-04 15:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 18:39 [gentoo-dev] ideas/bugs Christian Loitsch
2002-03-01 23:02 ` Martin Schlemmer
2002-03-04 13:34 ` [gentoo-dev] ideas/bugs Christian Loitsch
2002-03-04 15:49 ` Martin Schlemmer [this message]
2002-03-05 4:05 ` Chad M. Huneycutt
2002-03-05 12:15 ` Christian Loitsch
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=1015256941.12551.5.camel@workshop.saharact.lan \
--to=azarah@gentoo.org \
--cc=gentoo-dev@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