Bug#671589: bootlog does not work if the kernel boot command line is too long

2019-01-01 Thread Dmitry Bogatov
control: tags -1 +fixed-upstream [2018-12-29 14:44] Jesse Smith > > Jesse, can you please take a look? While I believe that 4Kb for kernel > > command line is enough, you might prefer to use getline(3). > > > > As I can see bootlogd.c already uses stdio.h, but is malloc-free. Use of > > getline

Bug#671589: bootlog does not work if the kernel boot command line is too long

2018-12-29 Thread Jesse Smith
> > Jesse, can you please take a look? While I believe that 4Kb for kernel > command line is enough, you might prefer to use getline(3). > > As I can see bootlogd.c already uses stdio.h, but is malloc-free. Use of > getline(3) would break this wonderful propery :( I have accepted the patch to m

Bug#671589: bootlog does not work if the kernel boot command line is too long

2018-12-29 Thread Dmitry Bogatov
control: tags -1 +confirmed +upstream Jesse, can you please take a look? While I believe that 4Kb for kernel command line is enough, you might prefer to use getline(3). As I can see bootlogd.c already uses stdio.h, but is malloc-free. Use of getline(3) would break this wonderful propery :( [20

Bug#671589: bootlog does not work if the kernel boot command line is too long

2012-05-04 Thread Marc MERLIN
Package: initscripts Version: 2.88dsf-13.1 Courtesy of Maciej Zenczykowski: sysvinit - kernel command lines can be longer than 256 characters. Fix a bug where a kernel commandline option of 'console=ttyS0,115200n8' was not being parsed correctly by bootlogd because it was 253 bytes into the str