Sure.
________________________________ From: Sysvinit-devel <sysvinit-devel-bounces+gborowiak=advaoptical....@nongnu.org> on behalf of Jesse Smith <jsm...@resonatingmedia.com> Sent: 22 September 2018 23:49:45 To: sysvinit-devel@nongnu.org Subject: Re: [sysvinit-devel] console= fix Grzegorz I have put together a small fix for init which uses the init.autocon=1 kernel parameter you suggested. If I send you a tarball with the init source code, could you test it and confirm it works in your environment? Jesse > Hi, thank you for your answer. > > > I managed the situation by reverting to version 2.88 and temporarily > disabling automatic upgrades of sysvinit. > > > While all your ideas 1, 2, 3 are viable, I have fourth idea: add kernel > parameter, for example, init.autocon=1, which will enable automatic console > creation. This would have two advantages over idea 2: > > - shorter cmdline > > - no necessity of repeating (DRY principle) > > For example, instead of cmdline: > > > console=tty0 console=ttyS0,15200 console=ttyS1,9600 init.console=tty0 > init.console=ttyS0,15200 init.console=ttyS1,9600 > > > it would be: > > > console=tty0 console=ttyS0,15200 console=ttyS1,9600 init.autocon=1 > > and if this cmdline is going to be generated (for example, by sophiscated > bootloader or by installer) or changed manually, it would be far easier to > maintain console names and baudrates if these do not need to be repeated > twice. > > Sincerely, > Grzegorz Borowiak > >
