1 |
[reordered the paragraphs] |
2 |
|
3 |
> Unless you have specific suggestions for me to |
4 |
> try out, you might want to stand by until I've had a chance to take a |
5 |
> shot at the problem with the newer kernel. |
6 |
|
7 |
I do have a few. I hope you'll make a good use of them to make your |
8 |
life more productive. |
9 |
|
10 |
> > And I need to see your conf to discover such potential |
11 |
> > mistakes. As for `emerge --info`, it may uncover problems relevant in |
12 |
> > this case too. |
13 |
> |
14 |
> "emerge --info" is the the stock Gentoo system profile, and I'll be |
15 |
> happy to share it, but in this case I'm looking at what's almost a |
16 |
> "pre-Gentoo" issue, involving the kernel and the boot-up. |
17 |
|
18 |
This sounds like you're sure that there is nothing interesting to |
19 |
see in `emerge --info`. Well, let's change it into something more |
20 |
correct: according to your knowledge there is nothing interesting to |
21 |
see. But your knowledge isn't perfect (just like anyone's). Keeping |
22 |
that in mind while consulting with others is the first of my specific |
23 |
suggestions into the future. It will save your+our time and may get you |
24 |
the solution faster. |
25 |
|
26 |
> > Please, cooperate with those whom you'd asked for help. Writing these |
27 |
> > several paragraphs worth of e-mail text as a reply was a waste of time |
28 |
> > for you - it clearly hasn't produced any help at all regarding your |
29 |
> > booting issue. |
30 |
> |
31 |
> Taking the desktop system off-line, re-emerging udev, bringing it up |
32 |
> into its failure mode with a newer kernel and pulling the necessary |
33 |
> pieces together, then backing out and putting everything back so the |
34 |
> system is actually fairly usable is a major hassle. I have had _zero_ |
35 |
> time to work on this problem since I posted this morning, but will be |
36 |
> able to take another run at it this evening, hopefully. Writing is no |
37 |
> effort for me, and doesn't disable my desktop ;) |
38 |
|
39 |
The second of my specific suggestions into a more fruitful future is: |
40 |
read what people ask of you. Sending me what I'd asked for would've |
41 |
taken about a few dozen seconds (I suppose you have the config for |
42 |
2.6.29 stored somewhere). It certainly wouldn't entail taking your |
43 |
desktop offline, reemerging udev, etc. etc. It's just attaching two |
44 |
text files to a piece of e-mail. So if your current attempt at 2.6.36 |
45 |
(was it?) fails, you know what to do right away. |
46 |
|
47 |
> > And some of those are relatively serious security holes and it'd take a |
48 |
> > really special handling of the system to avoid them. And I'm talking |
49 |
> > about handling that'd probably render an Internet-connected desktop box |
50 |
> > with a web browser unusable. |
51 |
> |
52 |
> This desktop box is on an RFC-1918 masqueraded network. It has zero |
53 |
> exposure to the Internet, except insofar as the firewall will permit |
54 |
> traffic from related and established connections, as per the firewall |
55 |
> NAT rules. The only other person on the LAN is my sweetie, and as far |
56 |
> as I know I can trust her not to black-hat hack my desktop system :-) |
57 |
> All my professional work is done via VPNs to my client's systems. |
58 |
|
59 |
The third suggestion is probably the most important one: being NAT'd |
60 |
and being behind any iptables configuration (that allows for operations |
61 |
such as sending mail and browsing the web) doesn't make your PC |
62 |
invulnerable or anything near that. In other words, active break-in |
63 |
attempts via open ports is by far not the only option hackers have. |
64 |
|
65 |
> Rather than |
66 |
> posting my entire kernel .config, emerge --info and /etc/fstab to this |
67 |
> list, which I consider questionable netiquette, I'll put it on my |
68 |
> personal file space on one of my servers and post the URL. |
69 |
|
70 |
In fact, some people who've appeared on this list over the years would |
71 |
consider it unacceptably bad netiquette not to include `emerge --info`. |
72 |
I also recall people who would consider it bad netiquette, but would |
73 |
still answer your questions (perhaps with some remarks). And I suppose |
74 |
most others consider it at least a good idea and a potential time-saver |
75 |
to include it, unless the topic in question is "what laptop should I |
76 |
buy to run Gentoo". So there goes my last specific suggestion to help |
77 |
you make a more efficient use of this list: include your `emerge |
78 |
--info` and relevant config files, if any, in the opening post to a |
79 |
mailinglist. It's not like you're telling us your card number. |
80 |
|
81 |
-rz |