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
On Sat, May 12, 2012 at 03:04:31PM +0300, Anton Zinoviev wrote:
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
On Sat, May 12, 2012 at 07:01:20AM -0700, Steve Langasek wrote:
No, you absolutely do *not* need this. The policy rule isn't on purge,
remove all config files if the admin hasn't edited them, it's on purge,
remove *all configuration files*.
All configuration files owned by the package.
On Sat, May 12, 2012 at 08:04:15PM +0300, Anton Zinoviev wrote:
On Sat, May 12, 2012 at 07:01:20AM -0700, Steve Langasek wrote:
No, you absolutely do *not* need this. The policy rule isn't on purge,
remove all config files if the admin hasn't edited them, it's on purge,
remove *all
Hi,
Anton Zinoviev wrote (12 May 2012 12:04:31 GMT) :
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
]] 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
propose is to generate the files in a directory
/boot/console-setup. After all the whole need of such directory arises
due to the specifics of the boot process.
Personally, I think I prefer /boot to /etc.
Some additional info: most of the time the package requires only
read-only access
/etc since the very first version of
Debian.
The second solution I propose is to generate the files in a directory
/boot/console-setup. After all the whole need of such directory arises
due to the specifics of the boot process.
Maybe I'm missing something obvious, but /boot seems
On Thu, May 10, 2012 at 07:43:46PM +0300, Anton Zinoviev wrote:
[Please preserve the CC to 672...@bugs.debian.org because I am not
subscribed to debian-devel.]
First the problem in few words. The package console-setup needs an
access to a directory similar to /var very early during the
On 2012-05-10 19:45 +0200, Roger Leigh wrote:
On Thu, May 10, 2012 at 07:43:46PM +0300, Anton Zinoviev wrote:
[Please preserve the CC to 672...@bugs.debian.org because I am not
subscribed to debian-devel.]
First the problem in few words. The package console-setup needs an
access to a
On Thu, May 10, 2012 at 07:45:21PM +0200, Sven Joachim wrote:
Maybe I'm missing something obvious, but /boot seems to be a very bad
choice for the location, simply because it is not available any earlier
than /var.
Ah, you are right.
So it seems only /etc is an option. Thanks.
Anton
On Thu, May 10, 2012 at 10:13:39PM +0300, Anton Zinoviev wrote:
On Thu, May 10, 2012 at 07:45:21PM +0200, Sven Joachim wrote:
Maybe I'm missing something obvious, but /boot seems to be a very bad
choice for the location, simply because it is not available any earlier
than /var.
Ah,
On Thu, May 10, 2012 at 09:40:23PM +0100, Ben Hutchings wrote:
Generally the console has to work even before root is mounted, so
that the user can enter a decryption password if necessary.
Unfortunately, as far as I know currently this doesn't work in
Debian. Proper wishlist bug reports
On ven., 2012-05-11 at 00:16 +0300, Anton Zinoviev wrote:
On Thu, May 10, 2012 at 09:40:23PM +0100, Ben Hutchings wrote:
Generally the console has to work even before root is mounted, so
that the user can enter a decryption password if necessary.
Unfortunately, as far as I know
it - it's the
creation of a a .cache subdirectory that I object to.
The second solution I propose is to generate the files in a directory
/boot/console-setup. After all the whole need of such directory arises
due to the specifics of the boot process.
Personally, I think I prefer /boot
15 matches
Mail list logo
