Justus Winter, le Thu 29 Aug 2013 12:35:32 +0200, a écrit :
> > Does procfs really need this information?
>
> Kinda. main.c (main) reads:
> > opt_kernel_pid = 2;
>
> Ugh.
Ugh.
That could probably be provided by the startup server?
> > As for glibc, I know it needs
> > it at least for reboot()
Quoting Samuel Thibault (2013-08-29 12:28:34)
> Justus Winter, le Thu 29 Aug 2013 12:22:30 +0200, a écrit :
> > Quoting Samuel Thibault (2013-08-28 23:30:27)
> > > Applied this one, thanks.
> >
> > This one as in the private header file?
>
> Yes.
>
> > I've come across an issue with the header b
Justus Winter, le Thu 29 Aug 2013 12:22:30 +0200, a écrit :
> Quoting Samuel Thibault (2013-08-28 23:30:27)
> > Applied this one, thanks.
>
> This one as in the private header file?
Yes.
> I've come across an issue with the header being private. This means
> that neither procfs (being maintained
Quoting Samuel Thibault (2013-08-28 23:30:27)
> Applied this one, thanks.
This one as in the private header file?
I've come across an issue with the header being private. This means
that neither procfs (being maintained and compileable out-of-tree) nor
the glibc can use the symbolic names.
Justu
Applied this one, thanks.
Samuel
* include/pids.h: New file.
* init/init.c (frob_kernel_process): Use symbolic name for kernel process.
* exec/exec.c (S_exec_init): Use symbolic name for startup process.
* libdiskfs/boot-start.c (diskfs_S_fsys_init): Likewise.
* libdiskfs/init-startup.c (_diskfs_init_completed): Likewise.
* pfinet
