On Sun, Jun 04, 2017 at 05:57:01PM -0500, Scott Cheloha wrote: > Hi, > > There is no command-line sample at the end of step 3 in release(8): > > After the build is completed, update /etc, /var, and /dev, > using sysmerge(8) and MAKEDEV(8). > > While needs vary by site, providing a sample for the typical case > is useful here because MAKEDEV operates in the current working > directory while sysmerge(8) "just works" from any directory. > > That MAKEDEV(8) operates on the current working directory is not > stated in its manpage. My guess is that this is not obvious > to a person who is new to building releases. You could add this > detail to the description in the MAKEDEV(8) page itself, but even > then the command example would still be useful in release(8) as an > applied example. > > Unless it's a very important rite of passage to fill /usr/src with > device nodes by accident the first time one updates a machine from > source (laugh it up :D), why not emphasize through example that > MAKEDEV(8) makes device nodes in the current working directory? > > Am I missing something here?
No not at all. Committed with 'cd /dev && ./MAKEDEV all' instead of the three separate commands. A clarification for MAKEDEV(8) is currently being discussed. Thanks! > > -- > Scott Cheloha > > Index: share/man/man8/release.8 > =================================================================== > RCS file: /cvs/src/share/man/man8/release.8,v > retrieving revision 1.88 > diff -u -p -r1.88 release.8 > --- share/man/man8/release.8 18 Apr 2017 16:21:06 -0000 1.88 > +++ share/man/man8/release.8 4 Jun 2017 22:15:02 -0000 > @@ -153,7 +153,12 @@ and > using > .Xr sysmerge 8 > and > -.Xr MAKEDEV 8 . > +.Xr MAKEDEV 8 : > +.Bd -literal -offset indent > +# sysmerge > +# cd /dev > +# ./MAKEDEV all > +.Ed > .Pp > At this point, the base system is up to date and running the code > that will be made into a release. >
