Re: [systemd-devel] 'Offline System Updates' examination
Hi Lennart. 2012/6/21 Lennart Poettering lenn...@poettering.net On Wed, 20.06.12 22:23, Antonio Trande (anto.tra...@gmail.com) wrote: 'Offline System Updates' will come as feature for Fedora 18. Reading your official page http://freedesktop.org/wiki/Software/systemd/SystemUpdates: The system update script now creates a btrfs snapshot (if possible), then installs all RPMs. After completion (regardless whether the update succeeded or failed) the /system-update symlink is removed. In addition, on failure it reverts to the old btrfs state (modulo the aforementioned symlink), on success it leaves the newly made changes in place. BTRFS ? Will 'Offline Updates' be available only with BTRFS ? Nope. But on btrfs we'll make a snapshot of the old system state. On non-btrfs we won't. Maybe BTRFS will be the default filesystem in Fedora 18, therefore all that make sense. If i use EXT4, are snapshots (that are a guarantee if update fails) not available ? This automation of updates could be difficulty manageable. How will be managed all kernel modules come from extra Fedora repositories (like RPMFusion) ? I no way different thn the Fedora packages. Explain myself: could happen that updates from extra repos are not syncronized with Fedora repositories. This could thwart often the 'Offline updates' result. Will be possible disable completely 'Offline System Updates' ? It's how pkgkit will do upgrades. THis has no effect on yum or anything else, it will continue to work as before. 1 The system is rebooted twice. This is a very inconvenient. The short boot times obtained with systemd are useless if every update (frequent in Fedora) needs of twice reboot. Well, whether the system is rebooted once or twice is hardly noticable i would argue... To get back my desktop to work after one reboot is not the same thing compared to the twice reboot. :) Are you disagree ? -- *Antonio Trande Fedora Ambassador **mail*: mailto:sagit...@fedoraproject.org sagit...@fedoraproject.org *Homepage*: http://www.fedora-os.org *Sip Address* : sip:sagitter AT ekiga.net *Jabber http://jabber.org/* :sagitter AT jabber.org *GPG Key: 19E6DF27* ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] 'Offline System Updates' examination
'Offline System Updates' will come as feature for Fedora 18. Reading your official page http://freedesktop.org/wiki/Software/systemd/SystemUpdates: The system update script now creates a btrfs snapshot (if possible), then installs all RPMs. After completion (regardless whether the update succeeded or failed) the /system-update symlink is removed. In addition, on failure it reverts to the old btrfs state (modulo the aforementioned symlink), on success it leaves the newly made changes in place. BTRFS ? Will 'Offline Updates' be available only with BTRFS ? How will be managed all kernel modules come from extra Fedora repositories (like RPMFusion) ? Will be possible disable completely 'Offline System Updates' ? Disadvantages of this approach over in-system updates: 1 The system is rebooted twice. This is a very inconvenient. The short boot times obtained with systemd are useless if every update (frequent in Fedora) needs of twice reboot. Regards. -- *Antonio Trande Fedora Ambassador **mail*: mailto:sagit...@fedoraproject.org sagit...@fedoraproject.org *Homepage*: http://www.fedora-os.org *Sip Address* : sip:sagitter AT ekiga.net *Jabber http://jabber.org/* :sagitter AT jabber.org *GPG Key: 19E6DF27* ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd services handling
Certainly that's what I've seen from: systemctl status fedora-storage-init.service fedora-storage-init.service - Initialize storage subsystems (RAID, LVM, etc.) Loaded: loaded (/lib/systemd/system/fedora- storage-init.service; static) ... See the word static there? That means it cannot be disabled. This is because, the initscripts package contains: /lib/systemd/system/local-fs.target.wants/fedora-storage-init-late.service /lib/systemd/system/local-fs.target.wants/fedora-storage-init.service i.e. the local-fs.tartget is statically configured to run these scripts. Exactly. In fact: $ systemctl status fedora-storage-init.service fedora-storage-init.service - Initialize storage subsystems (RAID, LVM, etc.) Loaded: loaded (/usr/lib/systemd/system/fedora-storage-init.service; static) Active: active (exited) since Wed, 25 Apr 2012 11:36:30 +0200; 8min ago Process: 436 ExecStart=/lib/systemd/fedora-storage-init (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/fedora-storage-init.service Therefore, are these services (apparently useless) bonded indirectly to the local filesystem requests ? -- *Antonio Trande Fedora Ambassador **mail*: mailto:sagit...@fedoraproject.org sagit...@fedoraproject.org *Homepage*: http://www.fedora-os.org *Sip Address* : sip:sagitter AT ekiga.net *Jabber http://jabber.org/* :sagitter AT jabber.org *GPG Key: 19E6DF27* ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd services handling
-- Forwarded message -- From: Antonio Trande anto.tra...@gmail.com Date: 2012/4/24 Subject: Re: [systemd-devel] systemd services handling To: Lennart Poettering lenn...@poettering.net Hi Lennart. Thank for your elucidation. Another my question about the services. In particular the fedora-storage-init.service (together to * fedora-storage-init-late.service* and *fedora-wait-storage.service *), according to systemctl command, is used to Initialize storage subsystems (RAID, LVM, etc.); ok, what does etc. mean ? Which are others ? :) I don't use neither LVM or RAID, if i disable fedora-storage-init-*.service, then they automatically restart itself at boot. I don't understand. 2012/4/24 Lennart Poettering lenn...@poettering.net On Tue, 24.04.12 17:21, Antonio Trande (anto.tra...@gmail.com) wrote: Hello ! In my Fedora 17, i see some systemd service's errors like these: $ systemctl --all | grep error exim.service error inactive dead exim.service libvirtd.service error inactive dead libvirtd.service postfix.service error inactive dead postfix.service tgtd.service error inactive dead tgtd.service ypbind.serviceerror inactive dead ypbind.service dbus.target error inactive dead dbus.target Actually i don't use any of that listed above but i can't disable them or if i try to find the related packages ( to remove them), really they aren't installed. Why ? How i can manage this type of services with sytemd ? They are referenced from another unit but not available locally. That's completely OK, which is why we hide them in the normal output. However you specified --all which basically means you asked for them to be shown anyway... Lennart -- Lennart Poettering - Red Hat, Inc. -- *Antonio Trande Fedora Ambassador **mail*: mailto:sagit...@fedoraproject.org sagit...@fedoraproject.org *Homepage*: http://www.fedora-os.org *Sip Address* : sip:sagitter AT ekiga.net *Jabber http://jabber.org/* :sagitter AT jabber.org *GPG Key: 19E6DF27* -- *Antonio Trande Fedora Ambassador **mail*: mailto:sagit...@fedoraproject.org sagit...@fedoraproject.org *Homepage*: http://www.fedora-os.org *Sip Address* : sip:sagitter AT ekiga.net *Jabber http://jabber.org/* :sagitter AT jabber.org *GPG Key: 19E6DF27* ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
