src/libexec/getty, branch release/13.1.0 FreeBSD source tree pkgbase: Put more binaries/lib in runtime 2022-01-05T17:23:51+00:00 Emmanuel Vadot manu@FreeBSD.org 2021-12-14T14:31:30+00:00 b2d245a0b010b8ca254297e00a5a30a632bac9fe Move some needed binaries/libs from FreeBSD-utilities to FreeBSD_runtime. This is everything needed to boot to multiuser with FreeBSD-rc installed. MFC after: 2 weeks Sponsored by: Beckhoff Automation GmbH & Co. KG Differential Revision: https://reviews.freebsd.org/D33435 (cherry picked from commit 93c43690960274dd3bb67b1ee0f1dd3ca4d13def) 
Move some needed binaries/libs from FreeBSD-utilities to FreeBSD_runtime.
This is everything needed to boot to multiuser with FreeBSD-rc installed.

MFC after:	2 weeks
Sponsored by:	Beckhoff Automation GmbH & Co. KG
Differential Revision:	https://reviews.freebsd.org/D33435

(cherry picked from commit 93c43690960274dd3bb67b1ee0f1dd3ca4d13def)
Do a sweep and remove most WARNS=6 settings 2020-10-01T01:10:51+00:00 Kyle Evans kevans@FreeBSD.org 2020-10-01T01:10:51+00:00 7cc42f6d25ef2e19059d088fa7d4853fe9afefb5 Repeating the default WARNS here makes it slightly more difficult to experiment with default WARNS changes, e.g. if we did something absolutely bananas and introduced a WARNS=7 and wanted to try lifting the default to that. Drop most of them; there is one in the blake2 kernel module, but I suspect it should be dropped -- the default WARNS in the rest of the build doesn't currently apply to kernel modules, and I haven't put too much thought into whether it makes sense to make it so. 
Repeating the default WARNS here makes it slightly more difficult to
experiment with default WARNS changes, e.g. if we did something absolutely
bananas and introduced a WARNS=7 and wanted to try lifting the default to
that.

Drop most of them; there is one in the blake2 kernel module, but I suspect
it should be dropped -- the default WARNS in the rest of the build doesn't
currently apply to kernel modules, and I haven't put too much thought into
whether it makes sense to make it so.
getty appears to date from 3rd edition research unix. That's the oldest man page 2020-07-22T00:44:47+00:00 Warner Losh imp@FreeBSD.org 2020-07-22T00:44:47+00:00 49d941eee087076eb2b3b901247386119b1f1dd3 on TUHS and its 'unix 1972' restoration effort has assembler sources that look like simpler version of what's in the 5th edition. 
on TUHS and its 'unix 1972' restoration effort has assembler sources that look
like simpler version of what's in the 5th edition.
Add cross references betwen ttys(5) and related drivers 2020-07-11T20:56:57+00:00 Allan Jude allanjude@FreeBSD.org 2020-07-11T20:56:57+00:00 463b8ebdcb319bf3784b24462ad917f584145031 nmdm(4), ucom(4), and uart(4) PR: 247638 Submitted by: Pau Amma <pauamma@gundo.com> Reported by: 0mp MFC after: 4 weeks Sponsored by: Klara Inc. Event: July 2020 Bugathon 
nmdm(4), ucom(4), and uart(4)

PR:		247638
Submitted by:	Pau Amma <pauamma@gundo.com>
Reported by:	0mp
MFC after:	4 weeks
Sponsored by:	Klara Inc.
Event:		July 2020 Bugathon
Simplify code with strlcpy/strlcat. 2019-12-01T08:04:22+00:00 Xin LI delphij@FreeBSD.org 2019-12-01T08:04:22+00:00 76b71718fe86d974e463624409c9f3ea040f7e2e MFC after: 2 weeks 
MFC after:	2 weeks
Fix potential buffer overflow and undefined behavior. 2019-01-26T20:43:28+00:00 Stefan Eßer se@FreeBSD.org 2019-01-26T20:43:28+00:00 71bc4af6edda147f6272a5c525c213d36ce7d9ec The buffer allocated in read_chat() could be 1 element too short, if the chatstr parameter passed in is 1 or 3 charachters long (e.g. "a" or "a b"). The allocation of the pointer array does not account for the terminating NULL pointer in that case. Overlapping source and destination strings are undefined in strcpy(). Instead of moving a string to the left by one character just increment the char pointer before it is assigned to the results array. MFC after: 2 weeks 
The buffer allocated in read_chat() could be 1 element too short, if the
chatstr parameter passed in is 1 or 3 charachters long (e.g. "a" or "a b").
The allocation of the pointer array does not account for the terminating
NULL pointer in that case.

Overlapping source and destination strings are undefined in strcpy().
Instead of moving a string to the left by one character just increment the
char pointer before it is assigned to the results array.

MFC after:	2 weeks
Move gettytab to libexec/getty/ 2018-09-05T15:25:23+00:00 Brad Davis brd@FreeBSD.org 2018-09-05T15:25:23+00:00 ce9e223ebd9c3fc9225b1d45d598fe2988f64dde Approved by: re (gjb), will (mentor) Differential Revision: https://reviews.freebsd.org/D16953 
Approved by:	re (gjb), will (mentor)
Differential Revision:	https://reviews.freebsd.org/D16953
Remove pointless comment. 2018-08-03T10:59:05+00:00 Edward Tomasz Napierala trasz@FreeBSD.org 2018-08-03T10:59:05+00:00 b32ae5fe795d684389f353edd8b7a4df827e3b5d MFC after: 2 weeks Sponsored by: DARPA, AFRL 
MFC after:	2 weeks
Sponsored by:	DARPA, AFRL
.Xr pam_securetty(8) from ttys(5), to hint the users as to what actually 2018-08-03T10:58:13+00:00 Edward Tomasz Napierala trasz@FreeBSD.org 2018-08-03T10:58:13+00:00 b6784423605b1d5ce6d1dfab57084f192acd47e4 enforces the 'secure' tty flag. MFC after: 2 weeks Sponsored by: DARPA, AFRL 
enforces the 'secure' tty flag.

MFC after:	2 weeks
Sponsored by:	DARPA, AFRL
.Xr pstat(8), so that people have a chance to learn how to get a list 2018-03-02T14:16:19+00:00 Edward Tomasz Napierala trasz@FreeBSD.org 2018-03-02T14:16:19+00:00 7a467312ef9f4c8f354d5747b2312b1fbe4a18dd of terminal devices using "pstat -t". MFC after: 2 weeks Sponsored by: The FreeBSD Foundation 
of terminal devices using "pstat -t".

MFC after:	2 weeks
Sponsored by:	The FreeBSD Foundation