Results 1 ... 239 for 'from:discord

2025-02-11

(gregorynyssa) Thus we keep headers and "libraries" somewhere in the personal folder (/home/gregorynyssa for instance) of that user. Moreover there is no need to standardize the names "lib" or "include" or whatever. It should be possible to name the sub-folders anything.

2025-02-11

2025-02-11	discord_bridge	(gregorynyssa) Thus we keep headers and "libraries" somewhere in the personal folder (/home/gregorynyssa for instance) of that user. Moreover there is no need to standardize the names "lib" or "include" or whatever. It should be possible to name the sub-folders anything.
2025-02-11	discord_bridge	(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034787 << Compilation is considered the private activity of a particular user, not a systemic activity.
2025-02-11	discord_bridge	(gregorynyssa) Examples of correct invocations of a given program.
2025-02-11	discord_bridge	(gregorynyssa) Moreover, the man-pages of BSD give examples whereas those of Linux usually do not.
2025-02-11	discord_bridge	(gregorynyssa) For every assertion made in a man-page two things must be clear: (1) by whose authority/authorship? (2) since when?
2025-02-11	discord_bridge	(gregorynyssa) Unlike Linux (but more similar to BSD), every man-page (especially under Sections 1 and 8) must contain the version-number of the program, the date of release, and the name of the author.
2025-02-11	discord_bridge	(gregorynyssa) * built
2025-02-11	discord_bridge	(gregorynyssa) Also, Sections 2–7 of man(1) under my Linux distribution are edited, bundled, and curated as a single file, whereas Sections 1 and 8 are bulit into particular executables as described above.
2025-02-11	discord_bridge	(gregorynyssa) Aside from providing more information, the advantage of the man(1) system lies in the TUI controls (like the less(1) program by GNU) and searching features.
2025-02-11	discord_bridge	(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034786 << The --help option is a shorter summary, while the man-page is a longer explanation, even constituting a specification. Both are important.
2025-02-11	discord_bridge	(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034783 << Yep, both ELF and COFF were designed as file-bundles containing constituent files.
2025-02-11	discord_bridge	(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034788 << We have thought very much along the same lines.
2025-02-11	discord_bridge	(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-11#1034789 << Thanks a lot.
2025-02-10	discord_bridge	(gregorynyssa) hapax: https://dpaste.org/tfeMo
2025-02-10	discord_bridge	(gregorynyssa) If the man-page is present then it is extracted and displayed.
2025-02-10	discord_bridge	resent then it is extracted and displayed.
2025-02-10	discord_bridge	(gregorynyssa) When man(1) is used to search for a man-page belonging to Section 1 or Section 8, it simply locates the file of that name in /bin (and in /sbin, but I would merge the two folders), treating it as a file-bundle (that is, as a tarball) and peering inside to see whether there is a man-page. If the man-page is p
2025-02-10	discord_bridge	(gregorynyssa) Another idea which I had was to eliminate sparsive packages not by creating one folder per package (as done by GoboLinux and also explicated in your article) but rather by compiling supportive files such as man-pages directly into the executables.
2025-02-10	discord_bridge	(gregorynyssa) There is no /lib, nor /usr/lib, nor /usr/include. These are all artifacts of self-hosting.
2025-02-10	discord_bridge	(gregorynyssa) The term "oblative" basically means "sideloading." The distribution assumes the existence of a second machine which will cross-compile programs for the present machine.
2025-02-10	discord_bridge	(gregorynyssa) Self-hosting will still be possible, but compilation is viewed as the private activity of a particular user of that system, not as a systemic operation.
2025-02-10	discord_bridge	(gregorynyssa) The Linux distribution which I have been constructing is an "oblative" distribution. What that means is, it is designed without the goal or presumption of self-hosting.
2025-02-10	discord_bridge	(gregorynyssa) Many FOSS projects embody this broken paradigm. For instance, MariaDB does not provide a manual because its aim is to be compatible with MySQL. The users of MariaDB are therefore expected to go to MySQL for documentation.
2025-02-10	discord_bridge	(gregorynyssa) Linux was built with the assumption that the team would not need to provide documentation, because Linux would be POSIX-compliant and when people have questions they should just go to POSIX for help.
2025-02-10	discord_bridge	(gregorynyssa) Linux was built with the following philosophy: you should not write programs for Linux; you should write programs for GCC, and the fact that those programs run on the Linux kernel should be treated as an implementation-detail.
2025-02-10	discord_bridge	(gregorynyssa) However, the project was based on some flawed and underhanded presumptions from the very start.
2025-02-10	discord_bridge	(gregorynyssa) I believe that the Linux kernel has some value owing to the sheer number of man-hours of revision and refinement which have been expent (the JVM is in a similar situation, though others here may disagree).
2025-02-10	discord_bridge	(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-10#1034748 << The way that LaTeX subsumed TeX, with the proponents of the former using the terms LaTeX and TeX interchangeably in order to bury the advocacy of the latter, was deeply depraved.
2025-02-10	discord_bridge	(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-10#1034745 << It has been very useful to me. (=
2025-02-10	discord_bridge	(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-02-10#1034742 << A friend of mine had pointed out that the sys-calls of the MS-DOS platform were basically a parallel of POSIX but better conceived.
2025-02-09	discord_bridge	(gregorynyssa) hapax: I was wondering if you had interest in the creation of a new Linux distribution, like what "signpost" had worked on previously.
2025-02-09	discord_bridge	(gregorynyssa) hapax: As I understand it, "asciilifeform" has not been very actively lately. However, based on your blog-articles I can see that you had a rather productive year of experimentation of research.
2025-02-09	discord_bridge	(gregorynyssa) Thanks a lot.
2025-02-09	discord_bridge	(awtho) @gregorynyssa it's up again
2025-01-30	discord_bridge	(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-01-29#1034729 << Another sad draw-back in my mind.
2025-01-30	discord_bridge	(gregorynyssa) That is, the author of the software still presumes a sparsive installation-model, though in most cases there would probably be no naming clash if you placed all files in a single folder.
2025-01-30	discord_bridge	(gregorynyssa) http://logs.nosuchlabs.com/log/pest/2025-01-29#1034726 << The path-related options of ./configure are decent, but one possible detraction is that the package still expects the replacements of /usr/bin, /usr/share, and so forth to be separate folders.
2025-01-29	discord_bridge	(gregorynyssa) It may be tedious to specify every parametric path for every invocation, but I would contend that it is the shell's reponsibility to relieve that burden (having shell-functions, shell-scripts, and the "alias" feature already goes a long way, but of course the shell might do even better).
2025-01-29	discord_bridge	(gregorynyssa) Even under Plan 9 this rule should not be relaxed. Rather, the use of parametric paths and per-process namespaces would complement each other.
2025-01-29	discord_bridge	(gregorynyssa) An executable should be viewed as a transformer between two states of the filesystem. All paths which the executable deals with should be chosen at invocation because they represent the parameters of the transformation.