You are not logged in.
I just updated systemd and noticed the changes to logind.conf. I had been using
HandleLidSwitch=tty-session
to prevent systemd from trying to handle lid close when I'm using KDM/KDE. Reading the updated man page, I can't see any equivalent functionality. Do I just have to use "ignore' and have systemd never handle it or has this functionality moved elsewhere? (I took a look in the other .conf files under /etc/systemd but didn't find anything which looked promising.)
This has been changed, now you can only choose between ignoring or handling it with a chosen action in all cases. For fine graned control you'll have to use acpid.
http://www.mail-archive.com/systemd-dev … 06449.html
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
Thanks for the link. I guess I'll just have to switch the functionality in systemd off for now, at least. Seems a shame! Maybe KDE will work with this in the future but that doesn't seem to have been part of the plan so I guess it will take a while. (The description concentrates on gnome without mentioning KDE.)
Last edited by cfr (2012-09-27 22:59:41)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Since most of the systemd inquiries are being made in this thread I think it would be a good idea to mark it as sticky at least for the next couple of months until the transition from initscripts fades away and systemd isn't anymore the new stranger in the block.
Enjoying i3wm w/ lifebar + j4-dmenu-desktop + tab_windows / fish shell / Emacs / tmux / Konsole / KDE apps
Arch + Linux-libre kernel: ParabolaGNULinux.org
Offline
Since most of the systemd inquiries are being made in this thread I think it would be a good idea to mark it as sticky at least for the next couple of months until the transition from initscripts fades away and systemd isn't anymore the new stranger in the block.
Stranger? It's been around for 2 years in Arch. We've already suffered one 50+ page thread about it.
Offline
msx wrote:Since most of the systemd inquiries are being made in this thread I think it would be a good idea to mark it as sticky at least for the next couple of months until the transition from initscripts fades away and systemd isn't anymore the new stranger in the block.
Stranger? It's been around for 2 years in Arch. We've already suffered one 50+ page thread about it.
Well yeah, I mean until it's widely installed on the vast majority of Arch systems.
Btw I read about the Google thing the other day, congratz & enjoy!
Enjoying i3wm w/ lifebar + j4-dmenu-desktop + tab_windows / fish shell / Emacs / tmux / Konsole / KDE apps
Arch + Linux-libre kernel: ParabolaGNULinux.org
Offline
Now that systemd is included in the installation media could someone knowledgeable school the noob plebeians about the systemd-nspawn chroot method??
Offline
Now that systemd is included in the installation media could someone knowledgeable school the noob plebeians about the systemd-nspawn chroot method??
Short version: Whenever you used chroot /path/to/some/linux/installation before, you now type systemd-nspawn instead of chroot.
Offline
Should I still follow the "beginners' guide" wiki for new installations using the "2012.10.06" iso or will the "beginners' guide" wiki be updated as time goes with regards to those new to using systemd?
Offline
Should I still follow the "beginners' guide" wiki for new installations using the "2012.10.06" iso or will the "beginners' guide" wiki be updated as time goes with regards to those new to using systemd?
For the time being the fact that systemd is used on the install media does not matter. initscripts will still be installed on your target system (unless you speficy otherwise).
Offline
89c51 wrote:Now that systemd is included in the installation media could someone knowledgeable school the noob plebeians about the systemd-nspawn chroot method??
Short version: Whenever you used chroot /path/to/some/linux/installation before, you now type systemd-nspawn instead of chroot.
So it goes somehow like:
# mkdir /mnt/resc-arch
# mount /dev/sda3 /mnt/resc-arch
# mount ... (whatever needed)
# cd /mnt/resc-arch
# mount -t proc proc proc/
# mount -t sysfs sys sys/
# mount -o bind /dev dev/
# mount -t devpts pts dev/pts/
#systemd-nspawn -D /mnt/resc-arch
Do magic stuff
#reboot
???
Offline
The bind mounts of proc, dev etc are no longer needed. Same for resolv.conf, timezone etc.
Offline
The bind mounts of proc, dev etc are no longer needed. Same for resolv.conf, timezone etc.
reroll:
# mkdir /mnt/resc-arch
# mount /dev/sda3 /mnt/resc-arch
# mount ... (whatever needed)
# cd /mnt/resc-arch
#systemd-nspawn -D /mnt/resc-arch
Magic happens
exit
You end systemd-nspawn with exit right?
# umount /mnt/resc-arch
# reboot
Offline
Offline
I just want to address the topic systemd and upower as far as its dependency to pm-utils is concerned: Did anyone test if pm-utils is still needed after upower got this tweak? I´d love to get rid of pm-utils, therefore I´m a little bit impatient.
Last edited by tyr0 (2012-10-11 09:17:20)
Offline
I rebuilt upower without pm-utils, everything still works. I'm using the testing repo, not sure if that makes a difference here.
Offline
I´m sorry, this patch has been already applied to the upower package. Nevertheless I rebuilt it without pm-utils dependency and removed pm-utils packages and everthing works fine (suspend, hibernate, reboot, shutdown) despite not using testing.
Last edited by tyr0 (2012-10-11 11:16:58)
Offline
Last night I finally updated to systemd. After reading about all of the drama related to sysvinit and systemd, here is my opinion:
Holy moley, the Arch Linux developers and community made the upgrade process incredibly easy. Also, the more I learned about sysvinit (while uninstalling it) the more I realized it's not quite as "simple" as I thought it was.
Next up: moving from GRUB 1.998783 to GRUB 2!
Offline
Next up: moving from GRUB 1.998783 to GRUB 2!
Noooo, drcouzelis, don't don't this! GRUB 2 will do something horrible to your pet capybara! ;-)
BTW, grub-legacy is 0.97, not 1.something ;P
Offline
BTW, grub-legacy is 0.97, not 1.something
Gosh darn it, I screwed up the joke! Well, at least people can laugh at me...
Noooo, drcouzelis, don't don't this! GRUB 2 will do something horrible to your pet capybara!
But... But, I thought newer meant it was better!
...On that note, I also recently decided to upgrade from EXT3 to EXT4. Then after learning more about it I un-decided to upgrade to EXT4.
Offline
...On that note, I also recently decided to upgrade from EXT3 to EXT4. Then after learning more about it I un-decided to upgrade to EXT4.
Not sure if you're serious here. Are you talking about converting an existing ext3 partition to ext4? I like ext4 much more than ext3.
It's OT, so maybe just e-mail me if you want, because I'm curious as to why you think upgrading to ext4 is bad.
Last edited by karol (2012-10-11 16:35:55)
Offline
... or he could post it publicly so other people may be able to evaluate his argument?
Offline
drcouzelis wrote:...On that note, I also recently decided to upgrade from EXT3 to EXT4. Then after learning more about it I un-decided to upgrade to EXT4.
Not sure if you're serious here.
I think he's still joking. Note to self: never try to make a joke about systemd, grub, or file systems.
Offline
getting very close to TGN territory
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
karol and I already had our email discussion.
My reasons basically came down to Ext3 being incredibly stable and incredibly does everything I need. Even so, I'd like to upgrade to Ext4 after studying a little more. I dual boot Haiku, which can read and write to Ext3. I think it can do the same to Ext4, but I'm not positive yet.
Note to self: never try to make a joke about systemd, grub, or file systems.
No way, jokes are great! Watch this: Keeping in the tradition of the monolithic nature of the Linux kernel, the Arch Linux developers are working on a new unified init system, boot loader, and file system called "systextrubd4". It's coming along great, but they've encountered minor issues. The boot loader is configured using symlinks, which link to a partition that hasn't been mounted yet (but Allan pointed out that it does boot incredibly fast, if you ignore the fact that the computer is entirely unusable). Half of the developers are complaining that the new method of loading daemons using a MySQL database of services may, in fact, go against the Arch Way. And Theodore Ts'o is disappointed in it, saying it's "based on old technology, and should instead be modeled after "SyslilobtrV".
Offline
The official joke thread is this way......
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline