16.04.2016 03:14, Reindl Harald пишет:
>
>
> Am 15.04.2016 um 21:06 schrieb Xen:
>> If you cannot give me a default mapping automatically, why not allow me
>> to generate one easily? Is there a tool that can take the current device
>> and produce the list I proposed?
>
> just use
Am 15.04.2016 um 21:06 schrieb Xen:
If you cannot give me a default mapping automatically, why not allow me
to generate one easily? Is there a tool that can take the current device
and produce the list I proposed?
just use network.service aka /etc/init.d/network, enter the MAC and you
are
On 04/15/2016 10:47 PM, Michael Biebl wrote:
> 2016-04-15 19:33 GMT+02:00 Daniel Mack :
>> On 04/15/2016 07:03 PM, Mike Gilbert wrote:
>>> On Fri, Apr 15, 2016 at 11:43 AM, Daniel Mack wrote:
On 04/15/2016 03:55 PM, Mike Gilbert wrote:
>>
> I'm happy
2016-04-15 19:33 GMT+02:00 Daniel Mack :
> On 04/15/2016 07:03 PM, Mike Gilbert wrote:
>> On Fri, Apr 15, 2016 at 11:43 AM, Daniel Mack wrote:
>>> On 04/15/2016 03:55 PM, Mike Gilbert wrote:
>
I'm happy to move it if others want to utilize it. I will
Andrei Borzenkov schreef op 13-04-16 05:39:
> Yes. And I do not see how all this information is expected to be stuffed
> into 14 characters available for interface name, or even less if we
> account to VLAN numbers.
>
> I am not aware of any OS that tries to do it. All of them maintain
>
Greg KH schreef op 13-04-16 05:04:
> On Wed, Apr 13, 2016 at 02:42:29AM +0200, Xen wrote:
>> When you say that probing on the PCI bus never ends, and if we are
>> talking not about some form of hotplugging, then I really wonder what
>> you're on about ;-) because I do think the kernel has a
On Fri, Apr 15, 2016 at 1:33 PM, Daniel Mack wrote:
> On 04/15/2016 07:03 PM, Mike Gilbert wrote:
>> On Fri, Apr 15, 2016 at 11:43 AM, Daniel Mack wrote:
>>> On 04/15/2016 03:55 PM, Mike Gilbert wrote:
>
I'm happy to move it if others want to utilize
On 04/15/2016 07:03 PM, Mike Gilbert wrote:
> On Fri, Apr 15, 2016 at 11:43 AM, Daniel Mack wrote:
>> On 04/15/2016 03:55 PM, Mike Gilbert wrote:
>>> I'm happy to move it if others want to utilize it. I will need someone
>>> to set me up with access to push the code, however.
On Fri, Apr 15, 2016 at 11:43 AM, Daniel Mack wrote:
> On 04/15/2016 03:55 PM, Mike Gilbert wrote:
>> On Fri, Apr 15, 2016 at 6:42 AM, Daniel Mack wrote:
>>> Nice, thanks for working on this! What's still missing in that is the
>>> other side, the client
Reindl Harald schreef op 15-04-16 18:06:
>
>
> Am 15.04.2016 um 18:02 schrieb Xen:
>> Reindl Harald schreef op 15-04-16 17:55:
> so 3 seconds is unacceptable and the idea ist a joke in general
> because
> you wait for something possibly happen while you don't know how
> long you
Reindl Harald schreef op 14-04-16 12:02:
>
>
> Am 14.04.2016 um 11:45 schrieb Jetchko Jekov:
>> On Thu, Apr 14, 2016 at 10:57 AM Reindl Harald > > can iterate over.
>> >
>> > $ ip -o a | awk '{print $2}' | uniq
>>
>> blub - gives a (incomplete) list of
Am 15.04.2016 um 18:02 schrieb Xen:
Reindl Harald schreef op 15-04-16 17:55:
so 3 seconds is unacceptable and the idea ist a joke in general because
you wait for something possibly happen while you don't know how long you
have to wait and jsut hope for luck - that's not a good design and
Reindl Harald schreef op 15-04-16 17:55:
>
>
> Am 15.04.2016 um 17:48 schrieb Xen:
>> Reindl Harald schreef op 13-04-16 10:24:
>>> 4xHDD raid-10, hardware from 2011
>>> Startup finished in 660ms (kernel) + 5.380s (initrd) + 12.769s
>>> (userspace) = 18.810s
>>>
>>> os on sd-card
>>> Startup
Am 15.04.2016 um 17:42 schrieb Xen:
Greg KH schreef op 13-04-16 05:04:
You are lying to me and trying to lead me in the woods.
The stuff you say is stuff people say that in the end don't end up being
true. It does not even agree with the reality of how the system works
currently.
They are
Am 15.04.2016 um 17:54 schrieb Xen:
Reindl Harald schreef op 13-04-16 10:26:
What are you on about?
Just because I don't have a superfast system, I cannot say anything?
no beause of "hmm let wait 3 seconds for something we don't know if it
ever appears and how long it would take to appear"
Am 15.04.2016 um 17:48 schrieb Xen:
Reindl Harald schreef op 13-04-16 10:24:
4xHDD raid-10, hardware from 2011
Startup finished in 660ms (kernel) + 5.380s (initrd) + 12.769s
(userspace) = 18.810s
os on sd-card
Startup finished in 375ms (kernel) + 4.306s (initrd) + 8.323s
(userspace) =
Reindl Harald schreef op 13-04-16 10:26:
>
>
> Am 13.04.2016 um 03:08 schrieb Xen:
>> Reindl Harald schreef op 13-04-16 02:06:
>>>
>>> Am 13.04.2016 um 01:20 schrieb Xen:
Greg KH schreef op 13-04-16 01:16:
> On Wed, Apr 13, 2016 at 12:39:37AM +0200, Xen wrote:
>> All you need to do
Reindl Harald schreef op 13-04-16 10:24:
>
>
> Am 13.04.2016 um 02:42 schrieb Xen:
>> Greg KH schreef op 13-04-16 01:29:
>>> On Wed, Apr 13, 2016 at 01:20:05AM +0200, Xen wrote:
>>
>>> All execpt for 4-socket and larger servers. They take tens of minutes
>>> in the BIOS and then less than a
On 04/15/2016 03:55 PM, Mike Gilbert wrote:
> On Fri, Apr 15, 2016 at 6:42 AM, Daniel Mack wrote:
>> Nice, thanks for working on this! What's still missing in that is the
>> other side, the client that talks to the initctl socket. I have patches
>> to remove the initctl bits
Greg KH schreef op 13-04-16 05:04:
> On Wed, Apr 13, 2016 at 02:42:29AM +0200, Xen wrote:
>> When you say that probing on the PCI bus never ends, and if we are
>> talking not about some form of hotplugging, then I really wonder what
>> you're on about ;-) because I do think the kernel has a
On Fri, Apr 15, 2016 at 6:42 AM, Daniel Mack wrote:
> Nice, thanks for working on this! What's still missing in that is the
> other side, the client that talks to the initctl socket. I have patches
> to remove the initctl bits from the systemd repo, and add a callout from
>
Hi Mike,
On 04/01/2016 10:11 PM, Mike Gilbert wrote:
> On Wed, Feb 24, 2016 at 10:42 PM, Mike Gilbert wrote:
>> The existing systemd-initctl (/dev/initctl) interface works quite
>> nicely, so I will probably end up extracting it from systemd when you
>> drop it, or just
On 04/12/2016 01:52 PM, Jóhann B. Guðmundsson wrote:
> Anyone know that centos is not running the latest version(s) of systemd
> required for the upstream bug tracker so one has to ask what
> notification spam is this
> "Can one of the admins verify this patch?"
Regarding that spam, I already
On Wed, Apr 13, 2016 at 07:20:12PM +, Zizka, Jan (Nokia - CZ/Prague) wrote:
> > From: systemd-devel [mailto:systemd-devel-boun...@lists.freedesktop.org] On
> > Behalf Of EXT Han Pingtian
> > Sent: Wednesday, April 06, 2016 4:33 AM
> > On Fri, Apr 01, 2016 at 09:13:54PM +0200, Lennart
2016-04-14 20:02 GMT+03:00 Zbigniew Jędrzejewski-Szmek :
> It's there. It works. See bootctl(1).
>
> Zbyszek
Thanks! Sorry for noise.
--
Vasiliy Tolstov,
e-mail: v.tols...@selfip.ru
___
systemd-devel mailing list
25 matches
Mail list logo