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