1 |
On Fri, 2004-11-19 at 11:47 -0800, Chris Barker wrote: |
2 |
> Being the user who "inattentively clobbered something vital", and then |
3 |
> started this thread, I can say: |
4 |
> |
5 |
> 1) I'm a newbie at gentoo and udev (as is everyone), but not a Linux |
6 |
> newbie. I've been hand editing my fstab on various distributions for |
7 |
> over ten years. |
8 |
> |
9 |
> 2) If I made this mistake, probably someone else has or will too. |
10 |
> |
11 |
> So, perhaps it's useful to know why I made the mistake (by the way, I |
12 |
> did keep my old fstab around, so it was easy to put back, and the reason |
13 |
> I got confused was that the system worked fine with the borked fstab, |
14 |
> except for errors trying to run fschk on boot. It's still a mystery to |
15 |
> me how the system ran with that fstab!) |
16 |
|
17 |
The system would still boot to your root partition thanks to the root= |
18 |
line when booting your kernel. It would just start freaking out after |
19 |
that. You probably also did not have any swap when you booted. |
20 |
|
21 |
> Anyway, the reason I got confused was that the fstab that came with the |
22 |
> udev package had "BOOT", "ROOT", and "SWAP" in it with NO explanation |
23 |
> that those were placeholders. They looked to me like they might be magic |
24 |
> names that udev figured out for you. The fact that my system worked |
25 |
> reinforced this idea. So: |
26 |
|
27 |
fstab is provided by baselayout. It is actually just coincidence that |
28 |
you were changing to udev at the same time. |
29 |
|
30 |
> if there were a single, simple comment it that file, I would not have |
31 |
> made the mistake. Something like: |
32 |
> |
33 |
> # This is a template of an example fstab file. Replace "BOOT", "ROOT", |
34 |
> # and "SWAP" with the appropriate drive devices for you system, for |
35 |
> # example: "/dev/hda3" for the third partition of the first IDE drive. |
36 |
|
37 |
This is commented almost verbatim in the handbook when you created your |
38 |
fstab way back when you first installed Gentoo. Now, I am sure you |
39 |
don't remember this one detail from your install, and I don't expect you |
40 |
to remember it. Personally, I think we should *never* provide system |
41 |
files such as fstab in an ebuild, especially one as ominous as |
42 |
baselayout. |
43 |
|
44 |
> Another thought: Is there a way for portage to tell the difference |
45 |
> between an install and an upgrade? and if an upgrade, what version is |
46 |
> being upgraded from? In an upgrade, there is no need install a new |
47 |
|
48 |
Nope. |
49 |
|
50 |
This functionality is being worked on, however. There is also |
51 |
functionality being worked on to know if a file has been edited since |
52 |
merge, and to auto-merge the new file if it has not been changed (md5 |
53 |
and mtime match) since merge. |
54 |
|
55 |
> config file unless the features or syntax of that config file has |
56 |
> changed. In this case, I can think of no reason that I would ever have |
57 |
> needed a new fstab after upgrading udev, and a BIG reason to keep the |
58 |
> old one. It would be nice of portage could figure this out for me and |
59 |
> not make me figure it out myself. Indeed, if there has been a change in |
60 |
> features or syntax, I'd love to know what those changes are, in some |
61 |
> easy to access place. |
62 |
|
63 |
...like etc-update? |
64 |
|
65 |
I mean, portage did not overwrite your fstab, you did. You would have |
66 |
had to have run etc-update and told it to overwrite. Now, what would |
67 |
make this so much easier is when portage is able to automatically update |
68 |
files that you have *not* changed. This will mean that *everything* in |
69 |
etc-update will be something that you have modified, and therefore, |
70 |
something you will want to look at and determine if you want to update, |
71 |
discard, or merge. The current situation definitely is not the most |
72 |
optimal and action is being taken to rectify it, but changes to portage |
73 |
itself are becoming increasingly slow-moving due to there being many |
74 |
more features to test and retest before deploying them on the masses. |
75 |
|
76 |
-- |
77 |
Chris Gianelloni |
78 |
Release Engineering - Operational/QA Manager |
79 |
Games - Developer |
80 |
Gentoo Linux |