1 |
Duncan wrote: |
2 |
|
3 |
|
4 |
> Did you try md-mod,start_dirty_degraded=1 (AFAIK this applies to |
5 |
> RAID-4/5/6 only)? |
6 |
> |
7 |
> |
8 |
No |
9 |
|
10 |
> What about listing the appropriate component devices, as so: |
11 |
> md=d1,/dev/sda1,/dev/sdb1,/dev/sdc1... ? |
12 |
> |
13 |
Yes. I had it by default. Without it never seemed to work. |
14 |
With it, it worked _sometimes_. |
15 |
|
16 |
|
17 |
Initramfs seem to be superior solution. With it there is more stuff I |
18 |
can do, like trying to rebuild array, fsck filesystems thoroughly etc. |
19 |
|
20 |
In fact, this is what it does now. Amongst other things, it checks |
21 |
/etc/fstab, gets filesystem types for "/boot" and "/" and e2fscks them, |
22 |
if needed. |
23 |
|
24 |
Being early adopter of ext4 I was many times in situation when boot-time |
25 |
e2fsck found some serious errors but demanded to be rerun on unmounted |
26 |
media to be able to finish. Without initramfs, only way to do this is |
27 |
through CD, but kernel there doesn't recognise disks on my Dell. Besides |
28 |
that it is tedious. |
29 |
|
30 |
This way, machine can do it by itself in MacGyver style ;o) |
31 |
|
32 |
> That's true, but my point is, by the time you setup all that complexity, |
33 |
> you're almost setting up AND CONFIGURING a whole little mini-distribution |
34 |
> inside your initramfs/initrd. |
35 |
> |
36 |
> |
37 |
That thingie is _definitely_ very useful and I plan to make it permanent. |
38 |
|
39 |
I had completed the script that does the packing in maybe two hours ( I |
40 |
don't remeber anymore ) and it needs maybe a few minutes to make initrd, |
41 |
copy it to /boot/initrd and old one to /boot/initrd_old. |
42 |
Also, if I need one more package in the initrd ( say new version of gcc |
43 |
or python etc), it is only matter of adding package name in one line... |
44 |
|
45 |
But I will do something much more compact in C. With maybe an option to |
46 |
do "DefCon 4" style boot from USB key toolshed. |
47 |
|
48 |
I found USB keys to be useful for that role, when opened and with |
49 |
soldered "in-line" conenctor. With it it becomes small dongle that is |
50 |
plugged directly into motherboard and so practically part of the machine. |
51 |
|
52 |
Tha way, you get "Terminator style" sturdy machine that is capable of |
53 |
reboot no matter what just as motherboard, CPU and PSU stay functional. ;o) |
54 |
|
55 |
|
56 |
> What I mean is that periodically, I snapshot/copy off my root (which |
57 |
> includes everything that portage installs and its database so most of / |
58 |
> usr and some of /var, all installed system binaries, scripts, and config) |
59 |
> to an identically sized rootbak partition. (In this case it's another |
60 |
> partition on the mdp/RAID, thus the weakness implied above if it should |
61 |
> not be bootable by any available kernel, even with the appropriate |
62 |
> options.) I can then continue updating the working root partition as I |
63 |
> normally would. |
64 |
> |
65 |
Yeah, but what do you do if your raid becomes non-functional for some |
66 |
reason ? |
67 |
|
68 |
I have four disks and two RAIDs. First is boot bartition RAID-1, which |
69 |
ebncompasess firs 1GB of each disk, second is RAID-5, which has the rest |
70 |
of the capacity. |
71 |
|
72 |
All partitions are typed as "fd"- self-detect RAID. On boot it doesn't |
73 |
matter. BIOS and GRUB see first partitions as if they were ordinary |
74 |
partitions with ext2 that happen to have exactly the same content. |
75 |
|
76 |
So, if one or more of the disks failed, I could boot with initrd from |
77 |
whatever disk is left... |
78 |
|
79 |
While in initramfs, I check and assemble both arrays and exec |
80 |
"make-init" ( or whatever its name it is- that util in klibc- it is |
81 |
effectively thingie that erases everything in /rootfs, remounts new root |
82 |
to / and starts init ) |
83 |
|
84 |
|
85 |
> I won't be doing nVidia any time soon. Not until they come around to |
86 |
> properly cooperating with the FLOSS community. YMMV and I know a lot of |
87 |
> gamers especially value their games above their freedom. That's not my |
88 |
> life and not my systems and therefore not my call, but what I run here |
89 |
> IS, and if I wanted to be stuck with proprietaryware, I'd have not |
90 |
> bothered dumping a decade's worth of experience on MS to start over with |
91 |
> Linux! |
92 |
> |
93 |
> |
94 |
Well, at least every fresh version of their driver is available on |
95 |
Gentoo at the same instant it gets out. |
96 |
Even without it, nvidia's own installer can figure things out. |
97 |
|
98 |
Not so with Radeon. I needed 9.1 version of driver when latest in gentoo |
99 |
tree was 8.1. |
100 |
I downloaded the thing and died wrestling with damn scripts halfway |
101 |
through. |
102 |
|
103 |
I don't get what kind of machine did they write that thing for- it sure |
104 |
as hell wasn't anything like mine. |
105 |
Also, when it comes to OpenGL performance, nVidia is still the king as I |
106 |
understand. |
107 |
|
108 |
But for 2D stuff AMD seems to work fine. I managed to install ATI |
109 |
Catalyst controll center for GPU in my Foxconn A7DA-S ( chipset AMD |
110 |
790GX + SB750 - HD3300 inbuilt GPU with 128MB cache RAM) it seems very |
111 |
good, even on on-board GPU. |
112 |
|
113 |
I have upgraded my dual setup to three-monitor setup ( 3x Samsung 204B, |
114 |
3x1600x1200) and have had to add elcheapo 9400 card to existing dual-DVI |
115 |
8800GT. |
116 |
|
117 |
Do you know about AMD/ATI Linux drivers- do they do such kind of stuff |
118 |
without extra wizardry ? |
119 |
|
120 |
|
121 |
> Plus, I can blame you and those like you for holding up progress on xorg |
122 |
> and the desktop environments, among other things, since there's a |
123 |
> continual drag placed on further progress due to the delay in support |
124 |
> from the proprietaryware graphics vendors. It's not my system and not my |
125 |
> decision, and I know people have their reasons, but I also know the |
126 |
> delays the popularity of the proprietaryware vendors means, and believe |
127 |
> in calling it as I see it -- due to their popularity, they hold |
128 |
> freedomware progress ransom to their whims. Honestly speaking but |
129 |
> nothing personal, if I had my way, freedomware would NOT hold up its |
130 |
> progress for them, even if it meant they were stuck back with xfree86 |
131 |
> vintage X because that's all the proprietary folks decided to support. |
132 |
> |
133 |
> |
134 |
Well, you can hardly blame me, since I have bought so much of AMD's |
135 |
stuff that there is part of me in Hector's house ;o) |
136 |
|
137 |
Seriously, stop being a child. |
138 |
Open stuff is fine, but at some point you are forced to show some effect |
139 |
and use the stuff that works, even if it isn't open. |
140 |
|
141 |
That said, y next card might very well be from AMD, especially since |
142 |
they started opening the specs, but NOT if they continue to cherish us |
143 |
with crappy drivers. |
144 |
|
145 |
And WRT to 3D drivers- as Alan Cox said, that stuff is not so trivial. |
146 |
It has been available to OS people for quite some time, but no one came |
147 |
up with drivers worth using. |