lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 9 Nov 2009 19:07:17 +0100
From:	Daniel Mack <>
To:	David Newall <>
Cc:	Alan Cox <>,
	Clemens Ladisch <>,
	Greg Kroah-Hartman <>,
	Andrew Morton <>,
	Geert Uytterhoeven <>,
Subject: Re: [PATCH] vt: make the default cursor shape configurable

On Tue, Nov 10, 2009 at 04:28:03AM +1030, David Newall wrote:
> Daniel Mack wrote:
> > I had that previously and the response was that there is no reason to
> > define that setting per-boot process, as it is rather unlikely that you
> > want to change it from one boot to the next. Hence, it should be set at
> > compile time.
> >   
> It should be set as a boot parameter, since this is fixed at system
> installation and then left untouched.

I'd be fine with either way. As long as it disables the blinking cursor.

> It seems like adding cruft to the kernel that is just as effectively
> available at run-time. Where does it end? Do we eventually add bash to
> the kernel?

Well, all I need is a way to disable the cursor at boot time, as we
don't want it to be in our boot screen on a embedded system. It is not
only ruin the aesthetics but also gives the wrong assumption that the
system awaits input. There is no userspace at this point, so that's no

My first approach was adding a __setup variable to select that, but it
wasn't beloved by the people spit out. So I made it
compile-time definable, and Clemens extended that to a more powerful
interface of settings.

I don't really have a strong opinion on which way to go, all I need is a
cursor-free system startup :) And I would of course prefer that patch to
be in mainline.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists