1 |
On Tue, Feb 4, 2014 at 5:27 PM, walt <w41ter@×××××.com> wrote: |
2 |
> On 02/04/2014 02:29 PM, gottlieb@×××.edu wrote: |
3 |
>> On Tue, Feb 04 2014, Daniel Campbell wrote: |
4 |
>> |
5 |
>>> On 02/04/2014 01:58 PM, Joseph wrote: |
6 |
>>>> Is it possible to go from "systemd" to "udev"? |
7 |
>>>> |
8 |
>>>> I don't like the way systemd works. I have a problem with mounting USB |
9 |
>>>> sick (it mounts as root:root) and I can not even change the permission. |
10 |
>>>> I am receiving Hylafax fax transmission reports (email) on all incoming |
11 |
>>>> faxes and now these emails are empty. |
12 |
>>>> It all start happening after switching to systemd :-( |
13 |
>>>> |
14 |
>>> |
15 |
>>> systemd and udev are part of the same project, so I believe what you |
16 |
>>> meant was switching from systemd to OpenRC. I've not made such a switch, |
17 |
>>> but if you remember the steps you took, you can generally just reverse |
18 |
>>> them. That is, emerge openrc again, change the kernel line in GRUB to |
19 |
>>> point to regular init instead of systemd's init, reboot, and things |
20 |
>>> *should* fall into place. |
21 |
>>> |
22 |
>>> USB drives mounting as root sounds like a udev thing rather than a |
23 |
>>> systemd thing, and switching to OpenRC for your init won't fix it afaik. |
24 |
>>> For the devices that you need this behavior for, it might be worth |
25 |
>>> looking into writing some udev rules. You can get a start by consulting |
26 |
>>> `lsusb` output and Googling for 'udev rules' to get a wide variety of |
27 |
>>> guides for writing udev rules. Despite the recent changes to udev by the |
28 |
>>> systemd team, udev still functions mostly the same and most guides will |
29 |
>>> be accurate. |
30 |
>>> |
31 |
>>> I hope this helps! |
32 |
>>> |
33 |
>>> ~Daniel |
34 |
>> |
35 |
>> There are changes in USE. -systemd +consolekit |
36 |
>> If you switched to a systemd profile, switch back. |
37 |
> |
38 |
> I'm sure that unsetting the consolekit useflag (when I switched to systemd) |
39 |
> resulted in some non-MicroSoft behavior, e.g. I now need to authenticate as |
40 |
> root when plugging or ejecting a USB stick, and yet again when I poweroff or |
41 |
> reboot the machine |
42 |
|
43 |
This does not happen with GNOME 3. At all. The only time I'm asked for |
44 |
my root password is when I add or remove a printer, and |
45 |
app-admin/system-config-printer-gnome has been doing this since the |
46 |
very beginning. I'm still hoping that someone fix that thing. |
47 |
|
48 |
> Being the only user of this machine, I could work up some outrage over this |
49 |
> new PITA -- but I've decided not to be outraged. I pretend to be a sysadmin |
50 |
> and imagine how I would feel if an arbitrary user demanded the ability to |
51 |
> plug any arbitrary USB stick into his corporate workstation. |
52 |
> |
53 |
> Well, I'm not a corporate sysadmin, and never will be, but I think I'd be |
54 |
> reluctant to let him do it. |
55 |
> |
56 |
> Any official sysadmins out there have an infallible opinion to offer? |
57 |
|
58 |
With GNOME+systemd (and therefore, logind), the seat0 user gets |
59 |
ownership of all removable devices (except printers, see above), and |
60 |
the hardware buttons (poweroff, reset, suspend, etc.) No root password |
61 |
asked. Ever. |
62 |
|
63 |
You can see your seat with loginctl; if your seat is not seat0, that's |
64 |
why your password is being asked. If it's seat0, then something else |
65 |
is going on. Do you have pam_systemd.so enabled in /etc/pam.d? |
66 |
|
67 |
Regards. |
68 |
-- |
69 |
Canek Peláez Valdés |
70 |
Posgrado en Ciencia e Ingeniería de la Computación |
71 |
Universidad Nacional Autónoma de México |