From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: * X-Spam-Status: No, score=1.2 required=5.0 tests=DMARC_NONE,MAILING_LIST_MULTI, RDNS_NONE autolearn=no autolearn_force=no version=4.0.0 Received: from mail.cpt.saharapc.co.za (unknown [196.41.29.142]) by chiba.3jane.net (Postfix) with ESMTP id 39C772015DD3 for ; Mon, 4 Mar 2002 09:46:15 -0600 (CST) Received: (from root@localhost) by mail.cpt.saharapc.co.za (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id g24HkGn04919 for gentoo-dev@gentoo.org; Mon, 4 Mar 2002 19:46:16 +0200 Received: from workshop.saharact.lan (ws050.saharact.lan [10.0.4.50]) by mail.cpt.saharapc.co.za (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id g24HkDN04889 for ; Mon, 4 Mar 2002 19:46:14 +0200 Subject: Re: [gentoo-dev] Re: ideas/bugs From: Martin Schlemmer To: gentoo-dev@gentoo.org In-Reply-To: <20020304133446.A23286@matrix.netsoc.tcd.ie> References: <20020301183916.A13540@matrix.netsoc.tcd.ie> <20020304133446.A23286@matrix.netsoc.tcd.ie> X-scanner: scanned by Sistech VirusWall 2.3/cpt Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/1.0.1 Date: 04 Mar 2002 17:49:00 +0200 Message-Id: <1015256941.12551.5.camel@workshop.saharact.lan> Mime-Version: 1.0 Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 1b71aa0b-5512-4fbf-ba6b-402c06c69ad2 X-Archives-Hash: c4711423ec46682c97095f17bd19e704 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