Timeline for How can I reliably get the operating system's name?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 27, 2015 at 13:37 | comment | added | Peter Mortensen | This also works on a Raspberry Pi (and with the exact same output on the Raspberry Pi I tried it on). | |
| Sep 27, 2013 at 9:21 | comment | added | Nils | Here is a good one with many further links and related law-stuff. | |
| Sep 24, 2013 at 19:42 | comment | added | terdon♦ | @drewbenn the man page says what I quoted in my first comment, there is nothing there about its needing to contain the system info. It just often does. | |
| Sep 24, 2013 at 19:36 | comment | added | Nils | Recommended by security guidelines and auditors. There was once a case at law where a hacker came away without punishment, because there was WELCOME in /etc/issue | |
| Sep 24, 2013 at 19:06 | comment | added | Nils | It is recommended to fill that file with. legal stuff like who is allowed to login. | |
| Sep 24, 2013 at 18:52 | comment | added | Mat | /etc/issue is completely unreliable. (I've see systems in version X.Y with an /etc/issue banner saying they were Y.Z following bad patch management. It can contain absolutely anything.) | |
| Sep 24, 2013 at 18:49 | comment | added | terdon♦ | Ah, that's a good suggestion, +1. It might not always work though The file /etc/issue is a text file which contains a message or system identification to be printed before the login prompt. It seems to be up to the sysadmin to write whatever he/she desires. | |
| Sep 24, 2013 at 18:46 | history | answered | user4443 | CC BY-SA 3.0 |