1 |
On 2012-01-05 13:08, Alan McKinnon wrote: |
2 |
|
3 |
> I don't claim any special deep knowledge of these things, but a |
4 |
> superficial glance over the packages tells you a lot. udev is designed |
5 |
> to deal with any realistic device needs on modern systems - it's the |
6 |
> kitchen sink. |
7 |
^^^^^^^^^^^^ |
8 |
Fully agree... :-/ |
9 |
|
10 |
> mdev has a much narrower scope where things are considerably more |
11 |
> static. |
12 |
|
13 |
Currently it does have a more narrow scope, yes, but that can change, |
14 |
no? Although I'm not entirely convinced that a userspace dev manager is |
15 |
needed (yes, devfs on Linux was an utter failure but Solaris, Mac OS X, |
16 |
*BSDs use it[1] and done properly in Linux it should work just as fine)... |
17 |
|
18 |
1: https://en.wikipedia.org/wiki/Devfs#devfs |
19 |
|
20 |
> As for re-arranging the fs layout, I think it was Canek in the last |
21 |
> thread that gave an excellent example of why this is needed. When |
22 |
> devices hotplug, or need to become active early on in the boot process, |
23 |
> they need to run code that can be located almost anywhere. It wouldn't |
24 |
> be fun trying to get a wireless keyboard going when it's start-up |
25 |
> script needs to get into /usr/lib/firmware and /usr isn't mounted yet. |
26 |
|
27 |
Yes, I understand the need for this but... how does a wireless keyboard |
28 |
work under bios/firmware (*efi)? Never tried one and never will... A |
29 |
computer without ports should handle such connections in firmware |
30 |
(analogy: You don't need software to drive a cable). |
31 |
|
32 |
> I do agree with collapsing the executable code in /usr into /, or |
33 |
> having /usr on the root partition. A separate /usr/{,s}bin is pretty |
34 |
> pointless and was never done for safety or maintenance reasons. It was |
35 |
> done way way way back when disks were small and a convenient hack was |
36 |
> to keep the OS on the boot device and user apps somewhere else on |
37 |
> bigger but slower storage (which often was remote). |
38 |
|
39 |
Hm... I find it quite elegant and flexible with the separation of / and |
40 |
it's various underlying directories. I guess we can agree on disagreeing |
41 |
here... although, I'm a bit surprised to see you as an admin defending |
42 |
the "new" way... Windows does have such a philosophy with putting |
43 |
everything system related into a directory (\WINDOWS)... Ultimately one |
44 |
can argue why use anything else besides Windows, it does the job |
45 |
reasonably well. |
46 |
|
47 |
> If /usr is local, what really is the point of having it separate |
48 |
> from /? Have you ever found a Linux system in any condition that could |
49 |
> not start just because the stuff in /usr was available? I haven't. |
50 |
> |
51 |
> Even the split between bin and sbin is arbitrary. It's only there so |
52 |
> that users can take sbin out of PATH and not have the screen cluttered |
53 |
> with endless junk when they tab-tab. It makes much more sense to me to |
54 |
> just have one single bin and lib location and shove everything into it. |
55 |
|
56 |
I'm not an admin of a large organization so what do I know... but, I |
57 |
still can appreciate the flexibility and "tidyness" it[2] gives you in a |
58 |
multi-user system. I also can see this from a security point of view |
59 |
("keep the cool toys from the children")... I personally like it for my |
60 |
very local computer as well for the above reasons (flex./tidy). |
61 |
|
62 |
2: https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard |
63 |
|
64 |
What you are basically saying is that everything "we" have learned about |
65 |
computer systems should be abolished and we adapt the monolithic, "black |
66 |
box" philosophy of newish systems like Windows. That's how I interpret |
67 |
what you're saying (yes, I do know hardware has changed since the 60'ies |
68 |
but not that radically, IMO)... I tend to think of Unix as "Lego" where |
69 |
you have lots of little bits with clean(ish) interfaces with which you |
70 |
can build whatever you want. With the new philosophy it's more like |
71 |
buying an Audi A2 (for those who don't know it, basically all you can do |
72 |
is fill it up with petrol, oil and window fluid; anything else you need |
73 |
to take it to an Audi workshop). Maybe I suck at car analogies... :-P |
74 |
|
75 |
> Dunno about lazy old fart, but splog (snarky pedantic lazy old git) |
76 |
> definitely is. I think we decided that Neil is the lazy old fart :-) |
77 |
|
78 |
:-D |
79 |
|
80 |
Oh... I'm not that far behind unfortunately... so, I'm a "lazy, |
81 |
pedantic, oldish, ???". ;-) |
82 |
|
83 |
Best regards |
84 |
|
85 |
Peter K |