search for: _exclusively_

Displaying 5 results from an estimated 5 matches for "_exclusively_".

2004 Aug 06
0
Re: Stallman @ NYU
...p breath now ...) GNU/BSD/ASL/PD/QPL/MPL/SCL/NCL/DCL/IBMPL/JOSL/NOSL/SCL/NGPL/PL/MCVWL/Linux and then we get into the argument of who's name goes in what order and which ones we leave out for brevity. Where it does get termed GNU/Linux, as with Debian, an immediate pressure arises to make it _exclusively_ GNU/Linux and prevent the distribution of non-FSF-approved open source material. It is better to identify the FSF and GPL (not the same thing) where they apply, on a package by package basis. -- Gary Lawrence Murphy <garym@linux.ca>: office voice/fax: 01 519 4222723 T(C)Inc Business Innov...
2004 Aug 06
5
Stallman @ NYU
I did manage to dv-tape this from the front row, and thus got pretty fair audio, but a slightly awkward camera angle. NYU Media Lab had a tripod set up at the back, and were apparently intending to webcast the results via real. They were a little taken aback when I mentioned Richard's aversion to propietary formats, and thanked me profusely for pointing it out, and saving them grief.
2015 Jan 13
1
PATH directive
...ing absolute > paths, i.e. regular file system semantics. > I understand that the paths used in the PATH directive are supposed to be treated as absolute paths (as per your own explanations since the PATH directive was introduced). What I don't understand is the reason to be treated _exclusively_ as absolute paths. To be clear, I am not claiming that it should be treated differently; but only that I am not sure that there is no place (or use-case) for some kind of relative path for the PATH directive. Users/members with more experience with network booting mixed firmware's architect...
2015 Jan 13
0
PATH directive
On Fri, 02 Jan, at 02:23:48AM, Ady wrote: > > Hmm, I thought it was decided to consider the colon (":") character as > deprecated, and instead we should be using a space character as > separator for the PATH directive (or multiple lines). Well, at least as > for the current MASTER HEAD, Syslinux 6.03. Are you referring to commit 1945579 ("PATH: use a linked
2015 Jan 02
2
PATH directive
> On Sat, 20 Dec, at 12:48:18AM, Ady wrote: > > > > So, my first (still incomplete and still inaccurate) attempt to write > > some rules about the PATH directive, and ask about remaining doubts!... > > > > > > The search (for c32 files) is supposed to respect the following rules: > > > > 1_ The search for c32 files is performed according to