On Fri, 2014-11-07 at 08:26 +0100, Martin Pitt wrote:
Patrick Häcker [2014-11-05 16:55 +0100]:
I you want to have permanent power saving activated for your devices, the
recommended way is to use udev (e.g.
https://wiki.archlinux.org/index.php/Power_saving#USB_autosuspend). Some
[...]
On Fri, 2014-11-07 at 12:55 +0100, Lennart Poettering wrote:
On Fri, 07.11.14 09:23, Oliver Neukum (oneu...@suse.de) wrote:
It is inconsistent. That is at least partially to the inability to find
general rules.
So what would you recommend we do?
Experiment with turning auto-suspend
On Sun, 2014-11-09 at 22:39 +0100, Patrick Häcker wrote:
I really don't know. Some other operating system relies on a whitelist
due to all of the horrible devices out there that can't handle suspend
(keyboards and mice are notorious for being bad.)
Thanks for your input. Do you know
On Thu, 2015-01-15 at 15:47 +0100, Robert Milasan wrote:
... which leads me to the question: why don't we just call the
actual
eject program? Just to avoid that dependency?
Yes, we could do this, I didn't think of it :)
I can confirm this to work and it is better than
duplicating ejecting
On Thu, 2015-01-15 at 11:38 +0100, Martin Pitt wrote:
Oliver Neukum [2015-01-15 11:31 +0100]:
No, the events are generated. And it is processed.
There is just no unmounting.
That sounds like a bug/missing feature in cdrom_id --eject-media then.
You could try and replace it with /usr/bin
On Thu, 2015-01-15 at 09:03 +0100, Martin Pitt wrote:
- udev rules (60-cdrom_id.rules) picks that up and calls eject
/dev/srX on the device; the eject program takes care to unmount
everything before physical ejection.
Note that the kernel will *not* generate DISK_EJECT_REQUEST uevents
On Mon, 2015-02-16 at 14:52 -0800, Hans Scholze wrote:
Hi,
I'm not sure if this is considered a problem but I noticed some
spurious error messages during boot. The source appears to be:
1. a USB media card reader is plugged in at boot
2. the device node exists regardless of whether a
On Mon, 2015-01-12 at 04:46 -0800, Greg KH wrote:
Let me rephrase. Is this desirable?
Probably not. But with some hardware, as you have seen, you need to run
some type of userspace daemon to poll the device to handle media removal
issues when the hardware itself does not report media
On Mon, 2015-01-12 at 04:15 -0800, Greg KH wrote:
On Mon, Jan 12, 2015 at 09:39:30AM +0100, Robert Milasan wrote:
Hello, a while back, around 2011, in cdrom_id was added --eject-media,
--lock-media and --unlock-media for not much explanation.
Now, recently some people noticed that this
On Sun, 2016-09-25 at 23:57 +0200, Reindl Harald wrote:
>
> Am 25.09.2016 um 23:52 schrieb Sergei Franco:
> > I am looking at correct way to disable the "feature" of emergency mode
> > when systemd encounters missing block device entires in fstab.
> >
> > For example:
> >
> > the following entry
Am Mittwoch, den 11.01.2017, 16:01 +0100 schrieb Lars Knudsen:
> If it can be invoked via DBus - what is the harm to only do the scan
> for the greylisted (in this case webusb) modems when the user
> actually wants to search for a modem (like a printer) - and leave the
> poor devices alone
On Tue, 2017-01-10 at 19:55 +0100, Lars Knudsen wrote
> And we're quite happy to keep blacklisting specific VID/PID
> combos we
> know are not modems. Another possible solution is to greylist
> devices
> that happen to have webusb descriptors, such that
Am Montag, den 10.07.2017, 12:57 +0200 schrieb Reindl Harald:
>
> Am 10.07.2017 um 12:55 schrieb Lennart Poettering:
> >
> >
> > The "nobody" user has special semantics on Linux: it's where things
> > are mapped to that can't be mapped otherwise. It's used by user
> > namspacing, by NFS and
Am Mittwoch, den 05.07.2017, 20:10 +1000 schrieb Michael Chapman:
> I'm pretty sure you'll find that it does. Specifically, it will fail when
> the child process for the command being executed attempts to map the
> username to a UID.
>
> The issue being discussed here is that systemd considers
Am Donnerstag, den 29.06.2017, 11:45 +0200 schrieb Reindl Harald:
>
> Am 29.06.2017 um 10:05 schrieb Oliver Neukum:
> >
> > Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering:
> > >
> > > Well, it's a service manager. As such it keeps
Am Mittwoch, den 28.06.2017, 13:29 +0200 schrieb Lennart Poettering:
> Well, it's a service manager. As such it keeps track of services,
> knows when they are started and when they aren't. Why would it stop
> services that aren't started?
Because you command it to do so.
The check systemd does
Am Donnerstag, den 01.03.2018, 15:17 +0100 schrieb Lennart Poettering:
> On Do, 01.03.18 14:40, Thomas Blume (thomas.bl...@suse.com) wrote:
> > As a proof of concept, I have created below udev rule and helper script,
> > which
> > works on my testmachine.
> > Obviously, like that it isn't
On Fri, 2018-03-02 at 10:18 +0100, Lennart Poettering wrote:
> But why wouldn't that be a kernel option? I mean, so far the goal was
> to encode "reasonable defaults" in the kernel itself, so that
> userspace is only used when those "reasonable defaults" do not apply
> onto one local case.
>
>
18 matches
Mail list logo
