1 |
First of all, thanks to everybody for sharing your experiences, very |
2 |
helpful information indeed, specially now that i need some guidance. |
3 |
For now, the conclusion i can reach is that Gentoo is perfectly adequate |
4 |
to use on a server with the only downside of the need to have special care |
5 |
with updates. |
6 |
Ricardo, i find really encouraging the fact that your lab uses Gentoo for |
7 |
their servers. Nevertheless it would be great if you could tell us a little |
8 |
about your lab's experience with updates, which seems to be the only issue |
9 |
when using Gentoo on a server. |
10 |
Another thing i noticed is that some of you recommend to have a secondary |
11 |
server to perform tests, i totally agree with this. Unfortunately i do not |
12 |
think that having such thing will be possible since the server will be |
13 |
charged to a client and i do not think they will agree to buy a second |
14 |
server (even if its the right thing to do, which i believe so), in such |
15 |
case, would you still recommend Gentoo?. |
16 |
|
17 |
Again, thanks to everybody for the information. |
18 |
|
19 |
2007/11/29, Billy Holmes <billy@××××××.net>: |
20 |
> |
21 |
> Robert Spahr wrote: |
22 |
> > I have been running these gentoo servers since 2003, with very few |
23 |
> > problems. Although I am conservative in doing my updates. |
24 |
> > |
25 |
> |
26 |
> I've run gentoo on several servers from dual intels running dns, squid, |
27 |
> routing, to web servers, to quad opterons running as terminal servers. |
28 |
> |
29 |
> The secret to all of that is what Robert said.. update conservatively. |
30 |
> |
31 |
> The update from apache 1.x to 2.x broke some things (good idea to follow |
32 |
> the update faqs, or as I did, rebuild the config files by hand), as did |
33 |
> when the gentoo apache package managers decided to change the config |
34 |
> file layout to better match other distros. |
35 |
> |
36 |
> Also, beware of some of the library updates. They can break other things |
37 |
> that revdep-rebuild will have to fix. |
38 |
> |
39 |
> It's a good idea to look up via google or whatever to figure out what's |
40 |
> being updated and why (read the changelog). |
41 |
> |
42 |
> It will take a bit to get used to, but after awhile you'll just eyeball |
43 |
> it and know which packages are non-issues, and which should be looked |
44 |
> closely. |
45 |
> |
46 |
> It's also a good idea to have a staging server where you can test the |
47 |
> updates and trash it if you need to (virtualization will help with this |
48 |
> a lot). |
49 |
> |
50 |
> Also, some updates don't fully manifest themselves till you restart all |
51 |
> the processes or restart the machine. Processes that were running before |
52 |
> a library update still have an internal image of the previous version's |
53 |
> library. |
54 |
> -- |
55 |
> gentoo-user@g.o mailing list |
56 |
> |
57 |
> |