Re: Directory /boot/console-setup
On Fri, May 11, 2012 at 09:07:57AM +0200, Tollef Fog Heen wrote:
> ]] Steve Langasek
>
> > My complaint is that this is excessively ugly. For persistent variable data
> > that needs to be available during early boot, even when this is binary data
> > that the user won't edit, /etc is the normal place to keep it - it's the
> > creation of a a .cache subdirectory that I object to.
>
> Very strongly agreed, if we could outright ban using dot directories
Ok, then it will be /etc/console-setup/cache (no dot).
On Thu, May 10, 2012 at 02:54:16PM -0700, Steve Langasek wrote:
> On Thu, May 10, 2012 at 07:43:46PM +0300, Anton Zinoviev wrote:
> > Currently it creates files in the directory /etc/console-setup. As
> > a result when the package is purged it is impossible to tell which
> > files in /etc/console-setup are automatically generated (so they
> > have to be removed) and which are put there by the admin (so we are
> > not permitted to remove them).
>
> I think your premise here is false. The /etc/console-setup directory is
> owned by the console-setup package; there are certain predictable filenames
The file names are not predictable unless one has acces to all previous
versions of the configuration files. But even if they were predictable
we would need MD5 or other hash to be sure the files have not be
modified somehow by the admin.
Yves-Alexis Perez wrote on debian-devel:
>
> What do you mean with “this doesn't work in Debian”? Some people do use
> encrypted root and they do have a working console asking for the
> passphrase.
As far as I know currently the console works with default settings,
meaning the keyboard is standard US-QWERTY layout.
Anton Zinoviev
Reply to: