On 04/23/2012 08:33 AM, Mark Hounschell wrote:
On 04/22/2012 06:54 AM, Lennart Poettering wrote:
On Fri, 13.04.12 13:37, Mark Hounschell (ma...@compro.net) wrote:
On 04/12/2012 08:25 AM, Mark Hounschell wrote:
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark Ho
On 04/22/2012 06:54 AM, Lennart Poettering wrote:
On Fri, 13.04.12 13:37, Mark Hounschell (ma...@compro.net) wrote:
On 04/12/2012 08:25 AM, Mark Hounschell wrote:
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark Hounschell wrote:
Same thing. About 20 seconds
On Fri, 13.04.12 13:37, Mark Hounschell (ma...@compro.net) wrote:
>
> On 04/12/2012 08:25 AM, Mark Hounschell wrote:
> >On 04/11/2012 05:12 PM, Kay Sievers wrote:
> >>On Wed, Apr 11, 2012 at 22:44, Mark Hounschell wrote:
> >>
> >>>Same thing. About 20 seconds after reaching the target, the device
On 04/13/2012 01:37 PM, Mark Hounschell wrote:
On 04/12/2012 08:25 AM, Mark Hounschell wrote:
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark Hounschell wrote:
Same thing. About 20 seconds after reaching the target, the device
entries
show up.
Does that block
On 04/12/2012 08:25 AM, Mark Hounschell wrote:
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark Hounschell wrote:
Same thing. About 20 seconds after reaching the target, the device
entries
show up.
Does that block or return immediately?
rmmod;
modprobe; time ude
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark Hounschell wrote:
Same thing. About 20 seconds after reaching the target, the device entries
show up.
Does that block or return immediately?
rmmod;
modprobe; time udevadm settle
Your driver creates the stuf
On Wed, Apr 11, 2012 at 22:44, Mark Hounschell wrote:
> Same thing. About 20 seconds after reaching the target, the device entries
> show up.
Does that block or return immediately?
rmmod ;
modprobe ; time udevadm settle
Your driver creates the stuff async?
Kay
_
On 04/11/2012 04:17 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:07, Mark Hounschell wrote:
On 04/11/2012 04:02 PM, Kay Sievers wrote:
Try:
systemctl enable udev-settle.service
I should enter this command then reboot?
Yeah, there is a chance, that the uevents will block this servi
On Wed, Apr 11, 2012 at 22:07, Mark Hounschell wrote:
> On 04/11/2012 04:02 PM, Kay Sievers wrote:
>> Try:
>> systemctl enable udev-settle.service
>>
>
> I should enter this command then reboot?
Yeah, there is a chance, that the uevents will block this service then.
Or just make your applicati
On 04/11/2012 04:02 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 21:41, Mark Hounschell wrote:
On 04/10/2012 09:10 AM, Kay Sievers wrote:
On Tue, Apr 10, 2012 at 14:36, Mark Hounschellwrote:
I am having another issue with an out of kernel "GPL" device driver not
being available "on ti
On Wed, Apr 11, 2012 at 21:41, Mark Hounschell wrote:
> On 04/10/2012 09:10 AM, Kay Sievers wrote:
>>
>> On Tue, Apr 10, 2012 at 14:36, Mark Hounschell wrote:
>>
>>> I am having another issue with an out of kernel "GPL" device driver not
>>> being available "on time" so to say. When the kernel di
On 04/10/2012 09:10 AM, Kay Sievers wrote:
On Tue, Apr 10, 2012 at 14:36, Mark Hounschell wrote:
I am having another issue with an out of kernel "GPL" device driver not
being available "on time" so to say. When the kernel discovers this pci card
it loads it's kernel module and sets up the card
On 04/10/2012 05:07 PM, Lennart Poettering wrote:
On Mon, 09.04.12 09:59, Mark Hounschell (ma...@compro.net) wrote:
On 04/05/2012 05:23 PM, Colin Guthrie wrote:
'Twas brillig, and Mark Hounschell at 05/04/12 18:26 did gyre and gimble:
I'm not a systemd developer but I am trying to use it in
On Mon, 09.04.12 09:59, Mark Hounschell (ma...@compro.net) wrote:
>
> On 04/05/2012 05:23 PM, Colin Guthrie wrote:
> >'Twas brillig, and Mark Hounschell at 05/04/12 18:26 did gyre and gimble:
> >>I'm not a systemd developer but I am trying to use it in place of
> >>sysvinit to create a dedicated
On 04/10/2012 10:52 AM, Kay Sievers wrote:
On Tue, Apr 10, 2012 at 16:26, Mark Hounschell wrote:
On 04/10/2012 09:10 AM, Kay Sievers wrote:
We do not support any kernel device driver which does not create the
device nodes on its own from inside the kernel. Such drivers cause
problems and wil
'Twas brillig, and Colin Guthrie at 10/04/12 13:57 did gyre and gimble:
> 'Twas brillig, and Mark Hounschell at 10/04/12 13:36 did gyre and gimble:
>> On 04/09/2012 08:06 PM, Colin Guthrie wrote:
>>
Yep, that works. Can the NAutoVTs be set differently on a per target
basis?
>>>
>>> Not as
On Tue, Apr 10, 2012 at 16:26, Mark Hounschell wrote:
> On 04/10/2012 09:10 AM, Kay Sievers wrote:
>> We do not support any kernel device driver which does not create the
>> device nodes on its own from inside the kernel. Such drivers cause
>> problems and will fail for various non-interesting re
On 04/10/2012 09:10 AM, Kay Sievers wrote:
On Tue, Apr 10, 2012 at 14:36, Mark Hounschell wrote:
I am having another issue with an out of kernel "GPL" device driver not
being available "on time" so to say. When the kernel discovers this pci card
it loads it's kernel module and sets up the card
On Tue, Apr 10, 2012 at 14:36, Mark Hounschell wrote:
> I am having another issue with an out of kernel "GPL" device driver not
> being available "on time" so to say. When the kernel discovers this pci card
> it loads it's kernel module and sets up the card for use. This takes around
> 15 seconds
'Twas brillig, and Mark Hounschell at 10/04/12 13:36 did gyre and gimble:
> On 04/09/2012 08:06 PM, Colin Guthrie wrote:
>
>>> Yep, that works. Can the NAutoVTs be set differently on a per target
>>> basis?
>>
>> Not as far as I know, but you should be able to do something similar via
>> a conflic
On 04/09/2012 08:06 PM, Colin Guthrie wrote:
Yep, that works. Can the NAutoVTs be set differently on a per target basis?
Not as far as I know, but you should be able to do something similar via
a conflicts directive.
e.g. if you have NAutoVTs=6 by default you can just put:
Conflicts=autovt@tt
'Twas brillig, and Mark Hounschell at 09/04/12 17:40 did gyre and gimble:
> On 04/09/2012 10:30 AM, Colin Guthrie wrote:
>>> So I just created a test target that I expected/hoped would just start a
>>> single mingetty on tty1. It did do that but I also got agettys on ttys
>>> 2-6.
>>
>> Are you sur
On 04/09/2012 10:30 AM, Colin Guthrie wrote:
'Twas brillig, and Mark Hounschell at 09/04/12 14:59 did gyre and gimble:
On 04/05/2012 05:23 PM, Colin Guthrie wrote:
'Twas brillig, and Mark Hounschell at 05/04/12 18:26 did gyre and gimble:
I'm not a systemd developer but I am trying to use it in
'Twas brillig, and Mark Hounschell at 09/04/12 14:59 did gyre and gimble:
> On 04/05/2012 05:23 PM, Colin Guthrie wrote:
>> 'Twas brillig, and Mark Hounschell at 05/04/12 18:26 did gyre and gimble:
>>> I'm not a systemd developer but I am trying to use it in place of
>>> sysvinit to create a dedica
On 04/05/2012 05:23 PM, Colin Guthrie wrote:
'Twas brillig, and Mark Hounschell at 05/04/12 18:26 did gyre and gimble:
I'm not a systemd developer but I am trying to use it in place of
sysvinit to create a dedicated "run-level" for our application. Is this
list an appropriate place to inquire ab
'Twas brillig, and Mark Hounschell at 05/04/12 18:26 did gyre and gimble:
> I'm not a systemd developer but I am trying to use it in place of
> sysvinit to create a dedicated "run-level" for our application. Is this
> list an appropriate place to inquire about problems I have?
Yup, ask questions h
I'm not a systemd developer but I am trying to use it in place of
sysvinit to create a dedicated "run-level" for our application. Is this
list an appropriate place to inquire about problems I have?
Thanks in advance
Mark
___
systemd-devel mailing list
27 matches
Mail list logo
