On Fri, Apr 12, 2019 at 01:40:56PM +0200, Enrico Weigelt, metux IT consult
wrote:
>On 12.04.19 09:30, Adamski, Krzysztof (Nokia - PL/Wroclaw) wrote:
>
>> Well, that depends. If the program doing those writes expects /dev/console
>> to be a tty device, then it cannot be any file.
>
>According to
On 12.04.19 09:30, Adamski, Krzysztof (Nokia - PL/Wroclaw) wrote:
> Well, that depends. If the program doing those writes expects /dev/console
> to be a tty device, then it cannot be any file.
According to Vincent's mail, the actual problem is just systemd.
Changing the kernel just for making
On 11.04.19 17:28, Vincent Whitchurch wrote:
>> hmm, wo (which programs) do you need, that really need them ?> > I think it
>> was systemd's debug-shell which complained about the ioctls.
Okay, why not fixing this broken userland ?
systemd is written by somebody who doesn't even know the
On Fri, Apr 12, 2019 at 09:17:28AM +0200, Enrico Weigelt, metux IT consult
wrote:
>On 11.04.19 15:05, Adamski, Krzysztof (Nokia - PL/Wroclaw) wrote:
>
>> There are (embedded) cases where the kernel ring buffer is stored for> log
>> inspection and all the logs that are *not* wanted there (like>
On 11.04.19 15:05, Adamski, Krzysztof (Nokia - PL/Wroclaw) wrote:
> There are (embedded) cases where the kernel ring buffer is stored for> log
> inspection and all the logs that are *not* wanted there (like>
interactive debug logs, some progress bar, etc) are send specifically
to> /dev/console
On Fri, Apr 05, 2019 at 02:32:41PM +0200, Enrico Weigelt, metux IT consult
wrote:
> On 05.04.19 11:00, Vincent Whitchurch wrote:
> > On Fri, Apr 05, 2019 at 10:39:43AM +0200, Enrico Weigelt, metux IT consult
> > wrote:
> >> On 03.04.19 16:11, Vincent Whitchurch wrote:
> >>
> >>> Especially on
On Fri, Apr 05, 2019 at 02:32:41PM +0200, Enrico Weigelt, metux IT consult
wrote:
>On 05.04.19 11:00, Vincent Whitchurch wrote:
>> On Fri, Apr 05, 2019 at 10:39:43AM +0200, Enrico Weigelt, metux IT consult
>> wrote:
>>> On 03.04.19 16:11, Vincent Whitchurch wrote:
>>>
Especially on embedded
On 05.04.19 11:00, Vincent Whitchurch wrote:
> On Fri, Apr 05, 2019 at 10:39:43AM +0200, Enrico Weigelt, metux IT consult
> wrote:
>> On 03.04.19 16:11, Vincent Whitchurch wrote:
>>
>>> Especially on embedded systems, it would be convenient to have a simple
>>> way to disable the console (both
On Fri, Apr 05, 2019 at 10:39:43AM +0200, Enrico Weigelt, metux IT consult
wrote:
> On 03.04.19 16:11, Vincent Whitchurch wrote:
>
> > Especially on embedded systems, it would be convenient to have a simple
> > way to disable the console (both for kernel and userspace) on a system
> > which
On 03.04.19 16:11, Vincent Whitchurch wrote:
> Especially on embedded systems, it would be convenient to have a simple
> way to disable the console (both for kernel and userspace) on a system
> which normally uses it, to free up the UART for other things.
Just symlinking to /dev/null does not
On Wed, Apr 03, 2019 at 03:12:13PM +0200, Greg KH wrote:
> On Wed, Apr 03, 2019 at 01:33:27PM +0200, Vincent Whitchurch wrote:
> > If no console driver is enabled (or if a non-present driver is selected
> > with something like console=null in an attempt to disable the console),
> > opening
On Wed, Apr 03, 2019 at 01:33:27PM +0200, Vincent Whitchurch wrote:
> If no console driver is enabled (or if a non-present driver is selected
> with something like console=null in an attempt to disable the console),
> opening /dev/console errors out, and init scripts and other userspace
> code
If no console driver is enabled (or if a non-present driver is selected
with something like console=null in an attempt to disable the console),
opening /dev/console errors out, and init scripts and other userspace
code that relies on the existence of a console will fail. Symlinking
/dev/null to
13 matches
Mail list logo
