1 |
Mike Frysinger wrote: |
2 |
|
3 |
> On Wednesday 11 April 2012 12:10:05 Steven J Long wrote: |
4 |
>> William Hubbs wrote: |
5 |
>> > Another issue to consider is binaries that want to access things in |
6 |
>> > /usr/share/*. |
7 |
>> |
8 |
>> I'm ignorant of which binaries do that? |
9 |
> |
10 |
> off the top of my head: |
11 |
|
12 |
Ah thanks, this is what I was after: interested in which ones make use of a |
13 |
rescue-shell or initramfs more difficult. |
14 |
|
15 |
> - this is why /etc/localtime is no longer a symlink to |
16 |
> /usr/share/zoneinfo/ |
17 |
- don't think that makes any difference to rescue situation. |
18 |
|
19 |
> - this is why we have copies for a few terminals in /etc/terminfo from |
20 |
> /usr/share/terminfo/ ... hopefully the one you're using is listed there |
21 |
- while unfortunate, I'd say ditto since user can always copy any required |
22 |
file themselves for their particular setup. |
23 |
|
24 |
> - this is why we have to delay running keymap and consolefont init.d |
25 |
> scripts until after /usr has been mounted (/usr/share/keymaps |
26 |
> /usr/share/consolefont /usr/share/consoletrans) |
27 |
|
28 |
- this is one that really is annoying; having your keyboard switched to US |
29 |
layout. It's not totally insurmountable from a UK keyboard, but I'd imagine |
30 |
eg a Dvorak user would have trouble. |
31 |
|
32 |
du -hs here, shows: |
33 |
1.1M /usr/share/keymaps |
34 |
1000K /usr/share/consolefonts |
35 |
504K /usr/share/consoletrans |
36 |
|
37 |
..which is nothing I personally would mind on rootfs, if it meant my rescue- |
38 |
shell used my keyboard layout. |
39 |
|
40 |
> - anything locale related doesn't work until /usr is mounted |
41 |
> (/usr/lib/locale /usr/share/locale) |
42 |
|
43 |
This doesn't affect me as I'm fine with en_US vs en_GB. |
44 |
1.7M /usr/lib/locale |
45 |
53M /usr/share/locale |
46 |
..is a lot heavier, though. |
47 |
|
48 |
(Sorry, I'm not stating that anyone is going to want to maintain this, I'm |
49 |
just scoping out how much data we're talking about, and how it important it |
50 |
is. While latter might change according to user as here, it would be cool if |
51 |
it were nothing more than setting up a few symlinks during install.) |
52 |
|
53 |
> - passwd changing relying on cracklib dicts won't work |
54 |
> (/usr/lib/cracklib_dict* /usr/share/misc/) |
55 |
> |
56 |
I can see you might want the option after an attack on a host. NFC how |
57 |
viable moving and linking is (not sure what it uses in /usr/share/misc but I |
58 |
for one would love the pci and usb stuff [just over 1M] in rootfs. kk I know |
59 |
it's not going to happen officially ;) but libs are less than 300k here. |
60 |
|
61 |
>> (It's understood that you might not |
62 |
>> have manpages in rescue-mode.) OT, it's odd that nano is in /usr/bin but |
63 |
>> on my system at least it only links to /lib64. |
64 |
> |
65 |
> /usr/bin/nano is a symlink |
66 |
ah d'oh, ta; i see it was switched back in 2004. |
67 |
|
68 |
>> > If a binary in /{bin,sbin} needs to access something in |
69 |
>> > /usr/share/*, you have two choices. move the binary to /usr or move the |
70 |
>> > thing it wants to access to / somewhere which would involve creating |
71 |
>> > /share. Actually there is another choice, but I don't want to go there. |
72 |
>> > That would be writing patches. |
73 |
|
74 |
Yeah, based on above, I'd feel okay about /lib/share/foo personally, linked |
75 |
to from /usr/share/foo on both bare rootfs with no mounts, and standard |
76 |
/usr. (Similar for /usr/lib/foo to /lib/foo.) If it's in |
77 |
/usr/{share,lib}/dir/* then the possibility at least of moving it fairly |
78 |
simply, exists. Otherwise you're into dealing with a build-system of one |
79 |
sort or another. |
80 |
|
81 |
Regards, |
82 |
Steve. |
83 |
-- |
84 |
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-) |