On 18 May 2016 at 17:42, Anton Zinoviev wrote:
> On Wed, May 18, 2016 at 01:33:06PM -0300, Felipe Sateler wrote:
>>
>> Ok. I see that the rules file appears to invoke the scripts in /etc
>> directly. Is this intended
>
> Yes. The keyboard is configured by /lib/console-setup/keyboard-setup.sh
> an
On Wed, May 18, 2016 at 01:33:06PM -0300, Felipe Sateler wrote:
>
> Ok. I see that the rules file appears to invoke the scripts in /etc
> directly. Is this intended
Yes. The keyboard is configured by /lib/console-setup/keyboard-setup.sh
and the font by the scripts in /etc.
Notice that /lib/con
On 18 May 2016 at 07:59, Anton Zinoviev wrote:
> On Wed, May 11, 2016 at 01:27:52PM -0300, Felipe Sateler wrote:
>>
>> Sure. Also, feel free to point me to what you have, and I can comment
>> on that as well.
>
> I've pushed the changes I made in git. The new version of
> keyboard-setup.service is
On Wed, May 11, 2016 at 01:27:52PM -0300, Felipe Sateler wrote:
>
> Sure. Also, feel free to point me to what you have, and I can comment
> on that as well.
I've pushed the changes I made in git. The new version of
keyboard-setup.service is more or less unchanged:
[Unit]
Description=Set the co
On 11 May 2016 at 11:18, Anton Zinoviev wrote:
> On Wed, Mar 16, 2016 at 03:22:42PM -0300, Felipe Sateler wrote:
>>
>> > On Sun, Mar 06, 2016 at 02:51:34PM -0300, Felipe Sateler wrote:
>> >>
>> >> I meant the logic to determine if setupcon or the cached scripts
>> >> should be run. If in the futur
On Wed, Mar 16, 2016 at 03:22:42PM -0300, Felipe Sateler wrote:
>
> > On Sun, Mar 06, 2016 at 02:51:34PM -0300, Felipe Sateler wrote:
> >>
> >> I meant the logic to determine if setupcon or the cached scripts
> >> should be run. If in the future that part is changed (eg, the names
> >> are chang
On 24 April 2016 at 16:32, Anton Zinoviev wrote:
> On Fri, Apr 01, 2016 at 08:55:31PM -0300, Felipe Sateler wrote:
>>
>> I have uploaded a new version. I have not yet, however, secured commit
>> rights to d-i git repository. If you want to pull the changes before I
>> get the access, you can pull
On Fri, Apr 01, 2016 at 08:55:31PM -0300, Felipe Sateler wrote:
>
> I have uploaded a new version. I have not yet, however, secured commit
> rights to d-i git repository. If you want to pull the changes before I
> get the access, you can pull the signed tag from my fork:
I noticed that you put the
On 24 April 2016 at 04:33, Christian PERRIER wrote:
>
> Quoting Felipe Sateler (fsate...@debian.org):
> > I have uploaded a new version. I have not yet, however, secured commit
> > rights to d-i git repository. If you want to pull the changes before I
> > get the access, you can pull the signed ta
Quoting Felipe Sateler (fsate...@debian.org):
> I have uploaded a new version. I have not yet, however, secured commit
> rights to d-i git repository. If you want to pull the changes before I
> get the access, you can pull the signed tag from my fork:
>
> git pull https://anonscm.debian.org/git/us
On 19 March 2016 at 06:55, Anton Zinoviev wrote:
> On Wed, Mar 16, 2016 at 03:22:42PM -0300, Felipe Sateler wrote:
>>
>> Yet another one would be to have setupcon itself detect the existence
>> of the cached scripts.
>
> The only reason there are cached scripts is that people are complaining
> tha
On Sun, Mar 20, 2016 at 11:46:30AM +0300, Adam Wilson wrote:
>
> Is console-setup the thing which initialises the console fonts and
Yes.
> resolution?
No.
> Is its slowness the reason why, on boot, it takes a few
> seconds for the text-mode screen to transition to a virtual terminal,
No.
> W
On Sat, 19 Mar 2016 12:55:41 +0300
Anton Zinoviev wrote:
> On Wed, Mar 16, 2016 at 03:22:42PM -0300, Felipe Sateler wrote:
> >
> > Yet another one would be to have setupcon itself detect the
> > existence of the cached scripts.
>
> The only reason there are cached scripts is that people are
>
On 6 March 2016 at 19:29, Anton Zinoviev wrote:
> Thank you for the useful explanations in your message!
Glad they are useful :)
>
> On Sun, Mar 06, 2016 at 02:51:34PM -0300, Felipe Sateler wrote:
>>
>> I meant the logic to determine if setupcon or the cached scripts should be
>> run. If in the
On Wed, Mar 16, 2016 at 03:22:42PM -0300, Felipe Sateler wrote:
>
> Yet another one would be to have setupcon itself detect the existence
> of the cached scripts.
The only reason there are cached scripts is that people are complaining
that console-setup is slow at boot. The cached scripts conta
Thank you for the useful explanations in your message!
On Sun, Mar 06, 2016 at 02:51:34PM -0300, Felipe Sateler wrote:
>
> I meant the logic to determine if setupcon or the cached scripts should be
> run. If in the future that part is changed (eg, the names are changed, or
> more scripts are gene
On 5 Mar 2016 17:01, "Anton Zinoviev" wrote:
>
> On Fri, Mar 04, 2016 at 03:08:39PM -0300, Felipe Sateler wrote:
> >
> > > Unfortunately, I will not be able to maintain this file or to update
it
> > > in accordance with future changes in systemd. So I suppose that
unless
> > > you or somebody els
On Fri, Mar 04, 2016 at 03:08:39PM -0300, Felipe Sateler wrote:
>
> > Unfortunately, I will not be able to maintain this file or to update it
> > in accordance with future changes in systemd. So I suppose that unless
> > you or somebody else volunteers to maintain it, it will be better to
> > cont
On Fri, Mar 04, 2016 at 11:23:54AM -0300, Felipe Sateler wrote:
>
> There is still keyboard-configuration.sh in runlevel S. So this
> problem is still present.
Yes. The problem however is much smaller because this script does not
require $remote_fs.
> I suggest including a service file like t
Control: reopen -1
Control: found -1 1.138
On 3 March 2016 at 08:24, Debian Bug Tracking System
wrote:
> Source: console-setup
> Source-Version: 1.138
>
> We believe that the bug you reported is fixed in the latest version of
> console-setup, which is due to be installed in the Debian FTP archive
On 4 March 2016 at 14:40, Anton Zinoviev wrote:
> On Fri, Mar 04, 2016 at 11:23:54AM -0300, Felipe Sateler wrote:
>>
>> There is still keyboard-configuration.sh in runlevel S. So this
>> problem is still present.
>
> Yes. The problem however is much smaller because this script does not
> require
21 matches
Mail list logo
