[hacktree] README.md: Some more notes about upgrading
- From: Colin Walters <walters src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [hacktree] README.md: Some more notes about upgrading
- Date: Sun, 16 Oct 2011 18:25:30 +0000 (UTC)
commit 25f06eb52c7bd129a5e708e163fdb1f5474671a8
Author: Colin Walters <walters verbum org>
Date: Sun Oct 16 14:24:56 2011 -0400
README.md: Some more notes about upgrading
README.md | 14 ++++++++++++++
1 files changed, 14 insertions(+), 0 deletions(-)
---
diff --git a/README.md b/README.md
index 48cc404..a9e5d85 100644
--- a/README.md
+++ b/README.md
@@ -199,6 +199,20 @@ difference internally), we simply check out a new tree into
/gnomeos-b90ae4763 for example, then swap the symbolic link, then
remove the old tree.
+But does this mean you have to "reboot" for OS upgrades? Very likely,
+yes - and this is no different from RPM/deb or whatever. They just
+typically lie to you about it =) But read on.
+
+Let's consider a security update to a shared library. We can download
+the update to the repository, build a new tree and atomically swap it
+as above, but what if a process has the old shared library in use?
+
+Here's where we will probably need to inspect which processes are
+using the library - if any are, then we need to trigger either a
+logout/login if it's just the desktop shell and/or apps, or a
+"fastboot" if not. A fastboot is dropping to "init 1" effectively,
+then going back to "init 5".
+
Configuration Management
------------------------
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]