public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: going from systemd to udev
Date: Tue, 4 Feb 2014 18:10:00 -0600	[thread overview]
Message-ID: <CADPrc83E7hjEaDpHSVeojtPsE+HkMP1gP1ijXV_7EjnmEvwHWg@mail.gmail.com> (raw)
In-Reply-To: <52F1777B.9080200@gmail.com>

On Tue, Feb 4, 2014 at 5:27 PM, walt <w41ter@gmail.com> wrote:
> On 02/04/2014 02:29 PM, gottlieb@nyu.edu wrote:
>> On Tue, Feb 04 2014, Daniel Campbell wrote:
>>
>>> On 02/04/2014 01:58 PM, Joseph wrote:
>>>> Is it possible to go from "systemd" to "udev"?
>>>>
>>>> I don't like the way systemd works.  I have a problem with mounting USB
>>>> sick (it mounts as root:root) and I can not even change the permission.
>>>> I am receiving Hylafax fax transmission reports (email) on all incoming
>>>> faxes and now these emails are empty.
>>>> It all start happening after switching to systemd :-(
>>>>
>>>
>>> systemd and udev are part of the same project, so I believe what you
>>> meant was switching from systemd to OpenRC. I've not made such a switch,
>>> but if you remember the steps you took, you can generally just reverse
>>> them. That is, emerge openrc again, change the kernel line in GRUB to
>>> point to regular init instead of systemd's init, reboot, and things
>>> *should* fall into place.
>>>
>>> USB drives mounting as root sounds like a udev thing rather than a
>>> systemd thing, and switching to OpenRC for your init won't fix it afaik.
>>> For the devices that you need this behavior for, it might be worth
>>> looking into writing some udev rules. You can get a start by consulting
>>> `lsusb` output and Googling for 'udev rules' to get a wide variety of
>>> guides for writing udev rules. Despite the recent changes to udev by the
>>> systemd team, udev still functions mostly the same and most guides will
>>> be accurate.
>>>
>>> I hope this helps!
>>>
>>> ~Daniel
>>
>> There are changes in USE.   -systemd +consolekit
>> If you switched to a systemd profile, switch back.
>
> I'm sure that unsetting the consolekit useflag (when I switched to systemd)
> resulted in some non-MicroSoft behavior, e.g. I now need to authenticate as
> root when plugging or ejecting a USB stick, and yet again when I poweroff or
> reboot the machine

This does not happen with GNOME 3. At all. The only time I'm asked for
my root password is when I add or remove a printer, and
app-admin/system-config-printer-gnome has been doing this since the
very beginning. I'm still hoping that someone fix that thing.

> Being the only user of this machine, I could work up some outrage over this
> new PITA -- but I've decided not to be outraged.  I pretend to be a sysadmin
> and imagine how I would feel if an arbitrary user demanded the ability to
> plug any arbitrary USB stick into his corporate workstation.
>
> Well, I'm not a corporate sysadmin, and never will be, but I think I'd be
> reluctant to let him do it.
>
> Any official sysadmins out there have an infallible opinion to offer?

With GNOME+systemd (and therefore, logind), the seat0 user gets
ownership of all removable devices (except printers, see above), and
the hardware buttons (poweroff, reset, suspend, etc.) No root password
asked. Ever.

You can see your seat with loginctl; if your seat is not seat0, that's
why your password is being asked. If it's seat0, then something else
is going on. Do you have pam_systemd.so enabled in /etc/pam.d?

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México


  reply	other threads:[~2014-02-05  0:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 19:58 [gentoo-user] going from systemd to udev Joseph
2014-02-04 21:42 ` Daniel Campbell
2014-02-04 22:29   ` gottlieb
2014-02-04 23:27     ` [gentoo-user] " walt
2014-02-05  0:10       ` Canek Peláez Valdés [this message]
2014-02-05  1:30         ` Poncho
2014-02-05  1:34           ` Canek Peláez Valdés
2014-02-06  0:22         ` walt
2014-02-06  2:25           ` Canek Peláez Valdés
2014-02-07  1:21             ` walt
2014-02-07  1:38               ` Canek Peláez Valdés
2014-02-07 21:52                 ` walt
2014-02-07 22:32                   ` Canek Peláez Valdés
2014-02-07 23:25                     ` walt
2014-02-08  0:43                       ` Canek Peláez Valdés
2014-02-08  1:38                         ` walt
2014-02-05  6:21       ` Alan McKinnon
2014-02-05  9:27         ` J. Roeleveld
2014-02-05  0:03 ` [gentoo-user] " Canek Peláez Valdés
2014-02-05  0:24   ` Joseph
2014-02-05  0:38     ` Canek Peláez Valdés
2014-02-05  1:26       ` Joseph
2014-02-05  1:28       ` Joseph
2014-02-05  1:33         ` Canek Peláez Valdés
2014-02-05  2:01           ` Joseph
2014-02-05  2:06             ` Canek Peláez Valdés
2014-02-05  2:12               ` Joseph
2014-02-05  1:38   ` Joseph
2014-02-05  1:50     ` Canek Peláez Valdés
2014-02-06 19:22     ` Pavel Volkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADPrc83E7hjEaDpHSVeojtPsE+HkMP1gP1ijXV_7EjnmEvwHWg@mail.gmail.com \
    --to=caneko@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox