1 |
Justin Vander Ziel wrote: |
2 |
|
3 |
> The following were included with a message that I e-mailed directly to |
4 |
> Daniel Robbins and he asked me to post. BUG report in order of |
5 |
> (percieved) importance (Gentoo 1.0rc3 ISO image). |
6 |
> 1. the modprobe line in the modules init file in /etc/rc.d/init.d/ |
7 |
> does not |
8 |
> parse the entire line which it should do especially for the alsa-sound |
9 |
> |
10 |
> module. I fixed the line that reads "modprobe ${1}" to read "modprobe |
11 |
> ${*}" |
12 |
> and that seems to have fixed it for me; my alsa-sound modules load |
13 |
> now. |
14 |
> ** this one has already been fixed in the CVS tree by Daniel according |
15 |
> to his response. |
16 |
> 2. dependency check in the alsa-libs package requires kernel |
17 |
> >2.4.0-test11 |
18 |
> which will obviously not work with the recommended and included |
19 |
> configuration. |
20 |
> 3. the automount daemon dies as soon as it is loaded.the error message |
21 |
> from /var/log/daemon.log is: |
22 |
> "lookup(file):cannot open parse modules sun |
23 |
> (/usr/lib/autofs//parse_sun.so: cannot open shared object file: no |
24 |
> such file or directory)" |
25 |
> * I was unable to locate the parse_sun.so file anywhere on my system.* |
26 |
> the autofs4 daemon requires the alias "alias autofs autofs4" to be in |
27 |
> the modules.conf according to Jeremy Fitzhardings' readme in the |
28 |
> autofs download page (see http://www.goop.org/~jeremy/autofs ). |
29 |
> However inserting the alias did not fix the above problem for me |
30 |
> assuming for some strange reason that the missing file complaint was |
31 |
> misguided. There is a newer daemon package version |
32 |
> autofs-4.0.0pre9.tar.gz in the above directory which I hope to try |
33 |
> out.Question about Portage, et al. |
34 |
> |
35 |
> This is fixed now !! |
36 |
> |
37 |
> Use autofs-3.1.7-r1.ebuild and it works. |
38 |
> |
39 |
> Bye Achim |
40 |
> |
41 |
> After having read through some comparisons of the various software |
42 |
> management options here http://kitenet.net/~joey/pkg-comp/ , here |
43 |
> http://vip.hpnc.com/~cbbrowne/linuxsysconfig.html and finally in the |
44 |
> freshmeat article I feel like I have at least a general idea of where |
45 |
> Portage is going. I have a couple of questions I am hoping someone in |
46 |
> this list would answer for me* I have a slow dialup connection and I |
47 |
> often download the software I need at work where I have a T1 and |
48 |
> either carry it home on a Syquest 200Mb cartridge or burn a CD for |
49 |
> myself there (which is how I got Gentoo in the first place). I'm not |
50 |
> sure I am ever going to want to rsync my distro because I don't see a |
51 |
> way of determining how long it's going to take without running an |
52 |
> audit of my system. Any suggestions?* What is the difference between |
53 |
> Portage and e-build? Where does one begin and the other start? I'm |
54 |
> familiar with Daniel's article that was posted on IBM about the |
55 |
> e-build system |
56 |
> (http://www-106.ibm.com/developerworks/library/bash3.html)* Perhaps |
57 |
> I'm thinking in Microsoft mode here. My question is, is there an |
58 |
> uninstall script ready now for ebuild? The autofs included with rc3 |
59 |
> seems to be missing the pars_sun.so library file so I wanted to |
60 |
> uninstall it and install the later version from the source code. I |
61 |
> could list the files from the tbz2 file and do it by hand or I've even |
62 |
> considered writing a script to do it for me but this seems to be a |
63 |
> logical piece of the puzzle that is missing. (is that why this is |
64 |
> called a beta release? B ) From the Digest Jerry A! |
65 |
> <jerry@×××××××.org> wrote: |
66 |
> >Can we please have pcmcia support in the default kernel? It's a real |
67 |
> |
68 |
> >pain having to install off the CD and then build a new kernel, put it |
69 |
> on |
70 |
> >floppy and then move to that to the machine in question. It'll be a |
71 |
> >bigger pain if that laptop ends up being my only working machine. |
72 |
> 8( Unless you're thinking of modules, I think it would be better to |
73 |
> include a few kernel variations and the dd command in the boot cd. I |
74 |
> thought it was odd that this was omitted anyways. I had to create a |
75 |
> boot disk in Windows using rawrite. (well actually, I learned later |
76 |
> that I really was able to install grub from the grub prompt on the CD. |
77 |
> Since I had never used GRUB and always LILO, this business was all new |
78 |
> to me then.) Thomas Flavel <thomasfl@××××××××××××.uk> wrote: |
79 |
> >Glad to see there's finally a mailing list, now I can bug everyone |
80 |
> and |
81 |
> >not just Daniel personally... ;)Ditto for me.>Hmm, I recall asking if |
82 |
> rc3 could have gcc and the kernel source |
83 |
> >available from the boot cd - I see the kernel source code is in the |
84 |
> >packages directory, but I think there may have been a |
85 |
> >mis-communication...Actually I may be looking in the wrong place, but |
86 |
> all that I found in /usr/src/linux were the kernel headers which were |
87 |
> installed with sys.tbz2 - but no source code. Actually, I did not find |
88 |
> source code ANYWHERE which surprised me given the idea behind this |
89 |
> distro to roll your own. Or perhaps I misunderstood and the idea is to |
90 |
> UPDATE with source code?? (See my first question) Or perhaps, even |
91 |
> worse, I'm more of a newbie than I think. >I actually meant that gcc |
92 |
> be executable from boot.img so that a kernel can be compiled directly |
93 |
> from the boot cd |
94 |
> >(onto ramfs presumably, unless you mount anything else) without |
95 |
> having to install anything to a hard disk - I for one would find >this |
96 |
> very useful, and I'm surprised I haven't seen any other distros do |
97 |
> this. This sounds like a logical extension of the Portage system and a |
98 |
> good idea to me, too. Nuff said, perhaps too much. Justin Vander |
99 |
> Zielmailto:zielot@××××××××××.com |