| 1 |
On Thu, 12 Dec 2013 17:49:01 -0800, Grant wrote: |
| 2 |
|
| 3 |
> What if the push is done while no one is logged in to the system(s) |
| 4 |
> being updated? I could also exclude /dev, /sys, /proc, and /run and |
| 5 |
> reboot after the update. If that's not good enough, what if I boot |
| 6 |
> the systems being updated into read-only mode before updating them? |
| 7 |
> I'm hoping to keep the process as simple as possible. |
| 8 |
|
| 9 |
The problem with such home brewed systems is that they may start simple |
| 10 |
but you keep adding more conditions, like these, making them anything but |
| 11 |
simple. Now you're considering rebooting just to make an update, even |
| 12 |
Windows doesn't need that (well, not all the time). |
| 13 |
|
| 14 |
Alan's point about network connectivity is also important. What happens |
| 15 |
if you unplug your laptop and leave the office while someone is mid-sync? |
| 16 |
With emerge -b, the package is downloaded before anything is installed, |
| 17 |
so losing contact with the package host would be less critical. It could |
| 18 |
still cause problems if it happened while updating some inter-dependent |
| 19 |
packages, which is why I would prefer to use a static package repository. |
| 20 |
|
| 21 |
|
| 22 |
-- |
| 23 |
Neil Bothwick |
| 24 |
|
| 25 |
If Yoda so strong in force is, why words in right order he cannot put? |
Archives