/etc/issue vs /etc/issue.net in shell.c
Sebastian Huber
sebastian.huber at embedded-brains.de
Mon Nov 24 07:12:36 UTC 2014
On 22/11/14 04:36, Joel Sherrill wrote:
> On November 21, 2014 5:50:08 PM CST, Chris Johns<chrisj at rtems.org> wrote:
>> >On 22/11/2014 1:53 am, Joel Sherrill wrote:
>>> >>
>>> >>On 11/21/2014 1:38 AM, Sebastian Huber wrote:
>>>> >>>On 20/11/14 22:08, Joel Sherrill wrote:
>>>>> >>>>Hi
>>>>> >>>>
>>>>> >>>>We have different code to process these two files on login.
>>>>> >>>>Can someone point me to a standard source which says
>>>>> >>>>what is supposed to be handled in each one?
>>>>> >>>>
>>>>> >>>>Should we really have both paths?
>>>>> >>>>
>>>> >>>One is for telnet:
>>>> >>>
>>>> >>>http://linux.die.net/man/5/issue.net
>>>> >>>
>>>> >>>One for the normal login:
>>>> >>>
>>>> >>>http://linux.die.net/man/5/issue
>>>> >>>
>>> >>I got that from the code. What standard/RFC/etc. requires that
>>> >>they be divergent?
>>> >>
>> >
>> >None I can see. It seems a convention specific to each platform.
>> >FreeBSD
>> >has other files.
>> >
>> >If you want a common file you could use a symlink.
> The code supports different "codes" in each. I don't see why they are that way.
>
Ok, know I understand what you mean with different codes. I thought you
mean one code location that uses /etc/issue and one code location that
uses /etc/issue.net.
I would not make it more complicated that necessary and use the same
format for both files.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the devel
mailing list