Comments on: man and groff out, mandoc in https://www.dragonflydigest.com/2019/05/28/man-and-groff-out-mandoc-in/ A running description of activity related to DragonFly BSD. Fri, 07 Jun 2019 20:36:10 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Justin Sherrill https://www.dragonflydigest.com/2019/05/28/man-and-groff-out-mandoc-in/comment-page-1/#comment-488093 Fri, 07 Jun 2019 20:36:10 +0000 https://www.dragonflydigest.com/?p=22988#comment-488093 In reply to Anonymous.

No, it doesn’t quite fit… but if you are using a BSD, the chance of spare bootable equipment laying around is pretty good.

]]> By: Anonymous https://www.dragonflydigest.com/2019/05/28/man-and-groff-out-mandoc-in/comment-page-1/#comment-488089 Thu, 06 Jun 2019 00:44:30 +0000 https://www.dragonflydigest.com/?p=22988#comment-488089 But PXE requires multiple computers being around. It doesn’t quite cover the scenario.

]]> By: Justin Sherrill https://www.dragonflydigest.com/2019/05/28/man-and-groff-out-mandoc-in/comment-page-1/#comment-488086 Wed, 05 Jun 2019 03:27:52 +0000 https://www.dragonflydigest.com/?p=22988#comment-488086 You can do that now by PXEbooting. The installer image can even be used as a server for it; it’s quite nice.

]]> By: Anonymous https://www.dragonflydigest.com/2019/05/28/man-and-groff-out-mandoc-in/comment-page-1/#comment-488078 Thu, 30 May 2019 22:35:34 +0000 https://www.dragonflydigest.com/?p=22988#comment-488078 IMO, an even more useful thing would be a dfly, that boots from USB or SD flash medium, that can be removed after startup. The system would reside in RAM with no need for harddisks (which could still be used for persistent storage, if present). What I don’t understand though, is the standard of installation. Usually, you would boot a system and not switch it off until the next version is out, no?

]]> By: Justin Sherrill https://www.dragonflydigest.com/2019/05/28/man-and-groff-out-mandoc-in/comment-page-1/#comment-488077 Thu, 30 May 2019 20:24:53 +0000 https://www.dragonflydigest.com/?p=22988#comment-488077 ultimate dreamer: you could, in theory, do that now with the right settings… WORLDCC, I think? I am not sure but the various steps around clang would work the same for another compiler.

Whether it could build world and kernel, who knows. An interesting experiment!

]]> By: ultimate dreamer https://www.dragonflydigest.com/2019/05/28/man-and-groff-out-mandoc-in/comment-page-1/#comment-488076 Thu, 30 May 2019 16:44:24 +0000 https://www.dragonflydigest.com/?p=22988#comment-488076 my absolute dream is a trimmed down dfly that fits a cd (still a thing for me) and maybe the entire thing even statically linked? against (pcc, really? speaking from memories or what?) tcc. -> repo.or.cz/w/tinycc.git and github.com/TinyCC/tinycc

]]> By: Justin Sherrill https://www.dragonflydigest.com/2019/05/28/man-and-groff-out-mandoc-in/comment-page-1/#comment-488073 Wed, 29 May 2019 16:26:12 +0000 https://www.dragonflydigest.com/?p=22988#comment-488073 That leaves pcc as a compiler option, though I don’t know how realistic, or necessary, that would be to try.

]]> By: Anon https://www.dragonflydigest.com/2019/05/28/man-and-groff-out-mandoc-in/comment-page-1/#comment-488072 Wed, 29 May 2019 13:44:44 +0000 https://www.dragonflydigest.com/?p=22988#comment-488072 GCC and the gold linker are both written in C++. So are LLVM and Clang, so even replacing the GCC build environment with them won’t completely remove C++ from base.

]]>