On Sun, 8 Jan 2017 19:59:34 -0500
pereira wrote:
> Still, adding to the instructions how best to add the link to
> whatever to $PATH
http://www.troubleshooters.com/linux/prepostpath.htm
SteveT
Steve Litt
December 2016 featured book: Rapid Learning for the 21st
On Tue, Jan 10, 2017, pereira wrote:
> I learn a lot here... keep it going!
>
> > Like /usr
> > No, it is NOT a short name fuer /user
> > It is an abbreviation of UNIX system ressources.
> >
> > We have to live with it since 1970 :-)
That's a total urban legend, a folk etymology, and a
I learn a lot here... keep it going!
Like /usr
No, it is NOT a short name fuer /user
It is an abbreviation of UNIX system ressources.
We have to live with it since 1970 :-)
--
xubuntu-users mailing list
xubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at:
On Tue 2017-01-10 (21:48), Peter Flynn wrote:
(/opt)
> The idea has merit but the name is bad.
> What I said: call things what they are, not what imagination offers.
> Calling it /apps might have been a better idea, but it's too late now,
> just another ill-considered name that needs better
> On Tue, Jan 10, 2017 at 2:06 AM, Ulli Horlacher
> SysV UNIX
On 01/10/2017 12:17 PM, Benjamin P. August wrote:
> In some worlds it was /opt and others it was /usr/local that got used
> for extra packages.
> But Solaris (SysV based) used /opt, and once upon a time it was the #1
> proprietary
Of course it depends onthe developer/packager to an extent(whether or
not they follow standards). Thereare the occasional packages that
install under /opt yet also put stuff under /usr/lib, /usr/share, etc.
Fortunately that doesn't happen too often. On our Solaris boxen, we have
stuff in just
In some worlds it was /opt and others it was /usr/local that got used for
extra packages.
But Solaris (SysV based) used /opt, and once upon a time it was the #1
proprietary UNIX.
On Tue, Jan 10, 2017 at 2:06 AM, Ulli Horlacher <
frams...@rus.uni-stuttgart.de> wrote:
> On Mon 2017-01-09 (22:33),
On Mon 2017-01-09 (22:33), Peter Flynn wrote:
> I must have been off-planet when /opt got "standardised"...I still don't
> know where it came from.
SysV UNIX
> Possibly one of the most unnecessary changes ever to affect Linux.
It is a good idea. You can place an optional software package in
I saw it uses /etc/os-release, which is so well-named that there is no
doubt about what it's good for but I did not know existed. It's good to
know though
There are many good ideas which have never succeeded, alas.
Amen
That's the kind of thing that drives me up the wall. There should be
On Mon 2017-01-09 (17:03), pereira wrote:
> Another post mentioned that your way of doing it is not necessarily
Which way?
> You mention putting them in /opt: the problem is then that they
> disappear when you install a new version from scratch, so now I put
> them under
> /home (and, I'm
On 01/09/2017 10:03 PM, pereira wrote:
> On 01/09/2017 08:19 AM, Ulli Horlacher wrote:
[...]
>> Though I am German, I have NEVER written German programs. All my
>> programs are in English, because this is the world languange.
All my [few] programs are in English, but I have also written the
Ulli,
Another post mentioned that your way of doing it is not necessarily
the canonical (that is, preferred; not the Ubuntu people) .
I do not write programs just for Ubuntu. Seldomly I wrote Linux-only code.
Normally my programs are generic for all UNIX systems, even MacOS.
Therefore I do not
On Sun 2017-01-08 (19:59), pereira wrote:
> > Everbody working with the shell should know what $PATH is.
> > If you do not know what a shell is, then fstools is nothing for you.
> Actually, I did know just enough to get the $PATH added, but as you
> pointed out, not in what you consider the
an additional step is necessary
to get them to work without having to jump through hoops.
The only hoop is setting $PATH.
Everbody working with the shell should know what $PATH is.
If you do not know what a shell is, then fstools is nothing for you.
Actually, I did know just enough to get the
On Sun 2017-01-08 (14:12), pereira wrote:
> > You can download fstools or part of them manually from
> > http://fex.belwue.de/fstools/
>
> get -O- http://fex.belwue.de/sw/share/fstools-0.0.tar | tar xvf -
>
> This worked without problem, except that the executables ended up in a
> local
On 01/08/2017 12:06 PM, Ulli Horlacher wrote:
On Sun 2017-01-08 (11:22), pereira wrote:
Trying to learn some more, I tried sudo apt get install sw,
and sudo apt-get install swtools, but nothing useful happend.
/sw is a UNIX software distribution system developed at the University of
On 1/8/2017 10:05 AM, Len Philpot wrote:
TECO ... fondly?:-) :-)
It did teach me to watch my punctuation. IIRC it was a misused
comma or semicolon in an edit macro that put me in an infinite loop.
Besides its what was available in the department at the time -
was an Engr Tech at DEC at
You're right - sloppy wording on my part. More accurate would be
"for-terminal-use". For example, $PS1 and other terminal related stuff.
That is,things I want set typically for all terminal instances.
That's based on the bash manpage I read somewhere back on Solaris years
ago. It said that
Hi Uri,
Real Unix Men were once little children too, and passed through various
stages as they
developed their magical powers in dealing with xubuntu or more in
general unix.
Others, though, became Real Expert Men in other areas, never having had
the time
or the motivation to learn other OSs
On Sun 2017-01-08 (10:02), Len Philpot wrote:
> For bash, I usually put per-terminal-instance values in ~/.bashrc
No good idea, because *every* bash subshell will execute ~/.bashrc, not
only when you start a new terminal program!
You can see it, when you add the line
echo executing ~/.bashrc
TECO ... fondly?:-) :-)
I think I tried it once... kinda like EMACS. Just once. I do vi for
quick stuff all over the place, but even so I'll jump to (e.g.) Geanyfor
longer-term editing. However, use vi on Solaris for while and it'll make
you appreciate Vim greatly. :-)
*Len Philpot*
On 01/08/2017 09:24 AM, Ulli Horlacher wrote:
Environment variables like PATH must be placed in /etc/profile or
$HOME/.profile
$HOME/.bash_aliases is for - oh-wonder! - bash aliases!
Do not mix them!
You'll get a lot of varied opinions on this kind of topic, but
~/.profile is actually
On 1/8/2017 8:50 AM, Ulli Horlacher wrote:
On Sun 2017-01-08 (08:24), Richard Owlett wrote:
http://fex.belwue.de/fstools/del.html
I would suggest that any new to Linux browse
http://fex.belwue.de/fstools/index.html just to gain perspective
of what can be done at the command line.
Beware!
On Sun 2017-01-08 (10:00), pereira wrote:
> the web site downloads
> and installs all the 193 (IIRC) files in the fstool directory. That's easy.
>
> But, to make use of them you have to know some linux magic that is not
> described anywhere
Of course, one should know what $PATH is (for)!
This
FWIW, thh ones I tried (del and df3) work fine.
Pointing and clicking on an almost invisible command at the bottom of
the web site downloads
and installs all the 193 (IIRC) files in the fstool directory. That's easy.
But, to make use of them you have to know some linux magic that is not
On Sun 2017-01-08 (08:24), Richard Owlett wrote:
>> http://fex.belwue.de/fstools/del.html
> I would suggest that any new to Linux browse
> http://fex.belwue.de/fstools/index.html just to gain perspective
> of what can be done at the command line.
Beware!
This is only for Real Men [TM]
26 matches
Mail list logo