From: WaLyong Cho
We can specify firmware path using "--with-firmware-path" configure
option.
In some of system, firmware can be located in subdirectories of the
firmware path.
If there are many firmware directories in below specified path then we
have to define those to "--with-firmware-path".
T
Lennart Poettering [2013-06-17 2:52 +0200]:
> The file is supposed to be be built on the installed system so that
> other packages or the admin can drop in additional hwdb files. And yes,
> it is not a package manager controlled file, which is precisely why I am
> saying it belongs to /etc, not /u
Hello Tom,
replying on-list again, if you don't mind.
Tom Gundersen [2013-06-16 22:52 +0200]:
> On Sun, Jun 16, 2013 at 10:32 PM, Martin Pitt wrote:
> > We actually generate the hwdb during package build and ship hwdb.bin
> > statically.
>
> The problem with that is that local configuration in
В Sun, 16 Jun 2013 19:18:45 +0100
David Greaves пишет:
> On 06/06/13 08:33, Lennart Poettering wrote:
> > On Sat, 18.05.13 23:44, Michael Scherer ([email protected]) wrote:
> >> So I planned to warn if the unit are directly in /lib, but I know there
> >> is some distribution that didn't choose this p
Am 16.06.2013 23:58, schrieb Ross Lagerwall:
>> The problem Zbigniew describes is that if one adds config options with
>> predictable network names used, and we do not apply the stuff at
>> "move", we will never apply them.
>>
> OK, thanks. But my testing shows otherwise: I created a .conf file
Am 16.06.2013 22:32, schrieb Martin Pitt:
>> Of course /etc isn't particularly beautiful for this either, since it
>> doesn't match *conceptually* what else is stored on that partition, but
>> at least it has the right *availability*, *shareability* and *access*
>> guarantees.
>
> /lib has exactly
On Sun, 16.06.13 22:32, Martin Pitt ([email protected]) wrote:
>
> Hello Lennart,
>
> Lennart Poettering [2013-06-16 8:36 +0200]:
> > As Tom pointed out, /usr is package manager territory and exactly the
> > same on all machines (with the same set of package installed at
> > least).
>
> I
On Sun, Jun 16, 2013 at 11:58 PM, Ross Lagerwall
wrote:
> OK, thanks. But my testing shows otherwise: I created a .conf file with:
> net.ipv4.conf.enp1s0.forwarding=1
> (where eth0 is the old name, enp1s0 is the new, predictable name)
> It *correctly* sets /proc/sys/net/ipv4/conf/enp1s0/forwardin
On Sun, Jun 16, 2013 at 07:42:03PM +0200, Kay Sievers wrote:
> > Yes. Currently, systemd-sysctl is run twice when a network device is
> > added, *both* times with the new name as the prefix, like:
> > systemd-sysctl --prefix=/proc/sys/net/ipv4/conf/enp0s1f3 ... (with the new
> > name)
> >
> > Onc
Hello Lennart,
Lennart Poettering [2013-06-16 8:36 +0200]:
> As Tom pointed out, /usr is package manager territory and exactly the
> same on all machines (with the same set of package installed at
> least).
I wrote "libdir", but what the patch actually uses "udevlibdir, i. e.
/lib/udev/.
> It's
I've also found another issue regarding this (it's a small issue but still...)
Using "nofail" (and implied "auto") works as expected but if the
device is not there at boot time, systemd will try to mount it anyway
and fail after a certain timeout.
Problem is, if I happen to shutdown my machine bef
On 06/06/13 08:33, Lennart Poettering wrote:
> On Sat, 18.05.13 23:44, Michael Scherer ([email protected]) wrote:
>> So I planned to warn if the unit are directly in /lib, but I know there
>> is some distribution that didn't choose this path yet. So when /usr is
>> not merged, what is the canonical loc
Hello,
I'm learning (and appreciating) the new systemd; and I'm currently trying to
make it work to load some firmware, in the most generic way.
The hardware needing that firmware is a cheap bluetooth usb dongle;
so cheap that without loading the firware it just plain doesn't work.
So, the idea
On Fri, Jun 14, 2013 at 3:39 PM, Ross Lagerwall wrote:
> On Fri, Jun 14, 2013 at 02:44:23PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
>> On Thu, Jun 13, 2013 at 10:45:12AM +0100, Ross Lagerwall wrote:
>> > Otherwise, when a network device is renamed, systemd-sysctl is run twice
>> > with the same
14 matches
Mail list logo
