8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I compiled new kernel in linux 10.04 called linux-2.6.26.8-xenomai, it runs alongside the other kernel, but when I want to boot it I get an error message saying:
Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/sda5 does not exist.
After making the modules and headers
I made the... (4 Replies)
Discussion started by: mdop
4 Replies
2. UNIX for Dummies Questions & Answers
hi guys
I got something I haven't been able to fix
I configure a Linux Suse 10 box, added static IP, DNS (resolv), gateway (routes) but I am not able to ping other servers by name but nslookup works and the server can navigate on internet
check below
the problematic server is server-host20
... (4 Replies)
Discussion started by: kopper
4 Replies
3. AIX
Hello:
NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies
4. UNIX for Dummies Questions & Answers
I'm trying to install Fedora 9 on a Dell OptiPlex GX300 machine. The instalation runs properly, but when the computer restarts after the instalation, it simply won't boot, like there's no OS installed.
I tried diffrent Linux distributions, but nothing works.
This are the partitions, maybe it's... (12 Replies)
Discussion started by: teis
12 Replies
5. Solaris
I just was given an Ultra 60 that I'm trying to get started so that I can re-load the system with Solaris 10. I can't seem to get the system to boot past the initial memory check. I've tried to do an Stop-A to get to the eeprom, but can't do that. My next step is to try to send a break from the... (0 Replies)
Discussion started by: zosojohnny
0 Replies
6. Solaris
I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies
7. AIX
Hi all ,
i was trying to upgrade firmware on machine 7028-6E4 and it failed .
Now machine does not boot anymore , i can not get SMC menu either ...
What are my options ?
Thanks,
Rahim (1 Reply)
Discussion started by: rahim
1 Replies
8. Solaris
Hi,
I've just bought an Ultra 60 running solaris 9 (or so I've been led to believe). When I start up, it looks for a (presumably) domain/network to hook up to and the following messages are displayed:
Boot device: net file and args:
Network link setup failed
Please check cable and try... (3 Replies)
Discussion started by: alarmcall
3 Replies
LEARN ABOUT HPUX
systemd.offline-updates
SYSTEMD.OFFLINE-UPDATES(7) systemd.offline-updates SYSTEMD.OFFLINE-UPDATES(7)
NAME
systemd.offline-updates - Implementation of offline updates in systemd
IMPLEMENTING OFFLINE SYSTEM UPDATES
This man page describes how to implement "offline" system updates with systemd. By "offline" OS updates we mean package installations and
updates that are run with the system booted into a special system update mode, in order to avoid problems related to conflicts of libraries
and services that are currently running with those on disk. This document is inspired by this GNOME design whiteboard[1].
The logic:
1. The package manager prepares system updates by downloading all (RPM or DEB or whatever) packages to update off-line in a special
directory /var/lib/system-update (or another directory of the package/upgrade manager's choice).
2. When the user OK'ed the update, the symlink /system-update is created that points to /var/lib/system-update (or wherever the directory
with the upgrade files is located) and the system is rebooted. This symlink is in the root directory, since we need to check for it
very early at boot, at a time where /var is not available yet.
3. Very early in the new boot systemd-system-update-generator(8) checks whether /system-update exists. If so, it (temporarily and for this
boot only) redirects (i.e. symlinks) default.target to system-update.target, a special target that pulls in the base system (i.e.
sysinit.target, so that all file systems are mounted but little else) and the system update units.
4. The system now continues to boot into default.target, and thus into system-update.target. This target pulls in all system update units.
Only one service should perform an update (see the next point), and all the other ones should exit cleanly with a "success" return code
and without doing anything. Update services should be ordered after sysinit.target so that the update starts after all file systems
have been mounted.
5. As the first step, an update service should check if the /system-update symlink points to the location used by that update service. In
case it does not exist or points to a different location, the service must exit without error. It is possible for multiple update
services to be installed, and for multiple update services to be launched in parallel, and only the one that corresponds to the tool
that created the symlink before reboot should perform any actions. It is unsafe to run multiple updates in parallel.
6. The update service should now do its job. If applicable and possible, it should create a file system snapshot, then install all
packages. After completion (regardless whether the update succeeded or failed) the machine must be rebooted, for example by calling
systemctl reboot. In addition, on failure the script should revert to the old file system snapshot (without the symlink).
7. The upgrade scripts should exit only after the update is finished. It is expected that the service which performs the upgrade will
cause the machine to reboot after it is done. If the system-update.target is successfully reached, i.e. all update services have run,
and the /system-update symlink still exists, it will be removed and the machine rebooted as a safety measure.
8. After a reboot, now that the /system-update symlink is gone, the generator won't redirect default.target anymore and the system now
boots into the default target again.
RECOMMENDATIONS
1. To make things a bit more robust we recommend hooking the update script into system-update.target via a .wants/ symlink in the
distribution package, rather than depending on systemctl enable in the postinst scriptlets of your package. More specifically, for your
update script create a .service file, without [Install] section, and then add a symlink like
/lib/systemd/system-update.target.wants/foobar.service -> ../foobar.service to your package.
2. Make sure to remove the /system-update symlink as early as possible in the update script to avoid reboot loops in case the update
fails.
3. Use FailureAction=reboot in the service file for your update script to ensure that a reboot is automatically triggered if the update
fails. FailureAction= makes sure that the specified unit is activated if your script exits uncleanly (by non-zero error code, or
signal/coredump). If your script succeeds you should trigger the reboot in your own code, for example by invoking logind's Reboot()
call or calling systemctl reboot. See logind dbus API[2] for details.
4. The update service should declare DefaultDependencies=false, Requires=sysinit.target, After=sysinit.target, and explicitly pull in any
other services it requires.
SEE ALSO
systemd(1), systemd.generator(7), systemd-system-update-generator(8), dnf.plugin.system-upgrade(8)
NOTES
1. GNOME design whiteboard
https://wiki.gnome.org/Design/OS/SoftwareUpdates
2. logind dbus API
https://www.freedesktop.org/wiki/Software/systemd/logind
systemd 237 SYSTEMD.OFFLINE-UPDATES(7)