1 |
tuxic@××××××.de wrote: |
2 |
> Hi, |
3 |
> |
4 |
> currentlu I am setting up a new PC for my 12-years old one, |
5 |
> which has reached the limits of its "computational power" :) |
6 |
> |
7 |
> SSDs are a common replacement for HDs nowaday -- but I still trust my |
8 |
> HDs more than this "flashy" things...call me retro or oldschool, but |
9 |
> it my current "Bauchgefühl" (gut feeling). |
10 |
> |
11 |
> To reduce write cycles to the SSD, which are quite a lot when using |
12 |
> UNIX/Limux (logging etc) and especially GENTOO (compiling sources |
13 |
> instead of using binary packages -- which is GOOD!), I am planning |
14 |
> the following setup: |
15 |
> |
16 |
> The sustem will boot from SSD. |
17 |
> |
18 |
> The HD will contain the whole system including the complete root |
19 |
> filesustem. Updateing, installing via Gentoo tools will run using |
20 |
> the HD. If that process has ended, I will rsync the HD based root |
21 |
> fileystem to the SSD. |
22 |
> |
23 |
> Folders, which will be written to by the sustem while running will |
24 |
> be symlinked to the HD. |
25 |
> |
26 |
> This should work...? |
27 |
> |
28 |
> Or is there another idea to setup a system which will benefit from |
29 |
> the advantages of a SSD by avoiding its disadvantages? |
30 |
> |
31 |
> Background: I am normally using a PC a long time and try to avoid |
32 |
> buying things for reasons like being more modern or being newer. |
33 |
> |
34 |
> Any idea to setup such a sustem is heardly welcone -- thank you |
35 |
> very much in advance! |
36 |
> |
37 |
> Cheers! |
38 |
> Meino |
39 |
> |
40 |
|
41 |
I don't have a SDD here but may one day. Here's my thinking. Set up a |
42 |
chroot or a virtual machine thingy on a regular hard drive. Copy your |
43 |
OS to that, do the updates and then copy packages over to your running |
44 |
system. Then you just emerge -k <whatever options you use> world and |
45 |
all it does is install binaries on the running system using the SSD. |
46 |
The other benefit of this is a much faster update on the running |
47 |
system. Also, if you get part way through a update, qt or KDE for |
48 |
example, you don't end up with a running system with mismatched versions |
49 |
and possibly a system that doesn't function correctly or won't let you |
50 |
do anything at all, or login even. You can fix the build problems in |
51 |
the chroot/VM and use the running system in the meantime. |
52 |
|
53 |
I started doing this recently because I ran into issues where |
54 |
KDE/qt/something else was not completely updated due to failed compiles |
55 |
that stopped the updates. Some programs I needed wouldn't start or no |
56 |
longer would work correctly if already started. It saves me some grief |
57 |
but would keep the larger writes off your SSD and on a HDD. Oh, if the |
58 |
HDD were to fail, no loss there either. Replace it and start over. |
59 |
|
60 |
I have some scripts, that's a VERY generous use of the word, that I use |
61 |
to mount the chroot, copy the updates over and copy the packages over |
62 |
when compiling is done. I'm still perfecting this but so far, it is |
63 |
working nicely and should work for you as well. Someone else may have a |
64 |
even better idea tho. |
65 |
|
66 |
Dale |
67 |
|
68 |
:-) :-) |