path

2021-09-08 Thread Michael via PLUG-discuss
What directory is in the path that is also accessible by the user? -- :-)~MIKE~(-: --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubscribe, or to change your mail settings: https://lists.phxlinux.org/mailman

KDE - PATH

2013-06-12 Thread der.hans
moin moin, I've tried a couple of things and am probably just missing something obvious, but ... How do I adjust the search path used by the command pop up? It's missing an important directory for me. Same question for GNOME and Unity actually :). ciao, der.hans -- # http://www.Lu

$PATH question

2014-02-26 Thread Dazed_75
I thought $PATH contained the series of paths searched to find an executable file by the name specified on the command line. Specifically if my $ENV contains a $PATH which reads: /home/larry/bin: that an executable file like foo.sh found in /home/larry/bin/ could be run by simply typing foo.sh

Re: path

2021-09-08 Thread Snyder, Alexander J via PLUG-discuss
Type: echo "$PATH" to view the folders in your user path. Root will have a different PATH. You can add to it by typing: export PATH="$PATH:/your/new/directory" To append to the end. Put that at the bottom of your "~/.bashrc" file. Thanks, Alexander. Sent f

Re: path

2021-09-08 Thread Michael via PLUG-discuss
Thanks! I'm trying to install arch (your suggestion) onto a persistent USB drive and then to use that to install it to my main computer. On Wed, Sep 8, 2021 at 1:40 PM Snyder, Alexander J < alexan...@snyderfamily.co> wrote: > Type: echo "$PATH" > > to view the f

Re: path

2021-09-08 Thread Snyder, Alexander J via PLUG-discuss
tent USB > drive > and then to use that to install it to my main computer. > > On Wed, Sep 8, 2021 at 1:40 PM Snyder, Alexander J < > alexan...@snyderfamily.co> wrote: > >> Type: echo "$PATH" >> >> to view the folders in your user path. Root w

Re: path

2021-09-08 Thread Ryan Petris via PLUG-discuss
uggestion) onto a persistent USB > drive > and then to use that to install it to my main computer. > > On Wed, Sep 8, 2021 at 1:40 PM Snyder, Alexander J > wrote: >> Type: echo "$PATH" >> >> to view the folders in your user path. Root will have a d

Re: path

2021-09-08 Thread Michael via PLUG-discuss
then download Rufus: >>>>> >>>>> Arch ISO (mirror): >>>>> >>>>> https://mirrors.edge.kernel.org/archlinux/iso/2021.09.01/archlinux-2021.09.01-x86_64.iso >>>>> >>>>> Rufus (*only available for Mac/Windows*): &

Re: path

2021-09-08 Thread Michael via PLUG-discuss
gt; >>>>>> Okay, from your existing desktop (Windows) download the ISO image, >>>>>> and then download Rufus: >>>>>> >>>>>> Arch ISO (mirror): >>>>>> >>>>>> https://mirrors.edge.kernel.or

Re: path

2021-09-10 Thread Michael via PLUG-discuss
t;>>> >>>>> >>>>> On Wed, Sep 8, 2021 at 11:36 AM Michael wrote: >>>>> >>>>>> rufus won't work... I have run linux since 98 >>>>>> >>>>>> On Wed, Sep 8, 2021 at 2:22 PM Snyder, Alexander

Re: KDE - PATH

2013-06-12 Thread Lisa Kachold
Hans, On Wed, Jun 12, 2013 at 1:05 PM, der.hans wrote: > moin moin, > > I've tried a couple of things and am probably just missing something > obvious, but ... > > How do I adjust the search path used by the command pop up? It's missing > an important director

Re: KDE - PATH

2013-06-12 Thread Nathan England
On Wednesday, June 12, 2013 01:05:49 PM der.hans wrote: > moin moin, > > I've tried a couple of things and am probably just missing something > obvious, but ... > > How do I adjust the search path used by the command pop up? It's missing > an important directory

Re: KDE - PATH

2013-06-12 Thread Brian Cluff
On 06/12/2013 01:15 PM, Nathan England wrote: It could also be that you have akonadi turned off or not searching your files and folders? Typically with SSD's you woud turn akonadi off, but sadly that disables a lot of functionality in KDE. If you do have nepomuk (akonadi is for connectors to va

Re: KDE - PATH

2013-06-12 Thread Nathan England
On Wednesday, June 12, 2013 02:43:12 PM Brian Cluff wrote: > If you do have nepomuk (akonadi is for connectors to various PIM) turned > off because it ate your system alive in the past, and you are using KDE > 4.10, go ahead and turn it back on. With KDE 4.10 it has been totally > rewritten and

Re: KDE - PATH

2013-06-12 Thread Patrick Callahan
If you want it to find random files scattered on your hard drive, have it use Nepomuk and then configure Nepomuk's search path. If you want it to find executable binaries (no metadata), maybe the PATH variable will help you, but... you can also put shortcuts (.desktop files) in any of the

Re: KDE - PATH

2013-06-14 Thread Ryan Rix
On Wed 12 June 2013 13:05:49 der.hans wrote: > moin moin, > > I've tried a couple of things and am probably just missing something > obvious, but ... > > How do I adjust the search path used by the command pop up? It's missing > an important directory for me. &

Re: KDE - PATH

2013-06-14 Thread Nathan England
n, > > > > I've tried a couple of things and am probably just missing something > > obvious, but ... > > > > How do I adjust the search path used by the command pop up? It's missing > > an important directory for me. > > > > Same question fo

Re: KDE - PATH

2013-06-15 Thread der.hans
Am 14. Jun, 2013 schwätzte Ryan Rix so: On Wed 12 June 2013 13:05:49 der.hans wrote: How do I adjust the search path used by the command pop up? It's missing an important directory for me. {0}% cat ~/.kde/env/path.sh export PATH=$PATH:$HOME/bin/ export KDEDIRS=/usr:/usr/local DING,

Re: KDE - PATH

2013-06-15 Thread der.hans
Am 12. Jun, 2013 schwätzte Nathan England so: moin moin Nathan, On Wednesday, June 12, 2013 01:05:49 PM der.hans wrote: moin moin, I've tried a couple of things and am probably just missing something obvious, but ... How do I adjust the search path used by the command pop up? It'

Re: $PATH question

2014-02-26 Thread Carl Parrish
Did you export? On Feb 26, 2014 8:18 PM, "Dazed_75" wrote: > I thought $PATH contained the series of paths searched to find an > executable file by the name specified on the command line. Specifically if > my $ENV contains a $PATH which reads: > > /home/larry/bin: &g

Re: $PATH question

2014-02-26 Thread Dazed_75
I don't remember as I did it long ago. but when I type echo $PATH, what I get is: /home/larry/bin:/opt/OpenPrinting-Gutenprint/sbin:/opt/OpenPrinting-Gutenprint/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games does that mean I did? or

Re: $PATH question

2014-02-26 Thread James Mcphee
If you don't add export PATH=/home/larry/bin:${PATH} to your .bash_profile (or .profile, or .bashrc depending on your shell and how you execute it), you'd need to do it each time. Adding the export into your profile or rc files will make sure that's run at shell execution. Con

Re: $PATH question

2014-02-26 Thread Paul Mooring
exporting your path just makes it available for other shells. If you can run `echo $PATH` and you see '/home/larry/bin' as part of your PATH, it's definitely in you path for that particular seesion, you might make sure that the permissions are correct `ls -lah /home/larry/bin` shou

Re: $PATH question

2014-02-26 Thread Michael Havens
ohh so that's whu when I added something to my path it didn't work! :-)~MIKE~(-: On Wed, Feb 26, 2014 at 10:29 PM, Paul Mooring wrote: > exporting your path just makes it available for other shells. If you can > run `echo $PATH` and you see '/home/larry/bin&

Re: $PATH question

2014-02-26 Thread Nathan England
I would guess the file is not executable. chmod +x ~/bin/foo.sh On Wednesday, February 26, 2014 09:18:31 PM Dazed_75 wrote: > I thought $PATH contained the series of paths searched to find an > executable file by the name specified on the command line. Specifically if > my $ENV c

Re: $PATH question

2014-02-26 Thread Dazed_75
The shell file IS marked executable. I do not have a ~/.bash_profile, ~/.bash_login I DO have a ~/.profile but it appears not to have run at login because if I do run it manually in a command shell, suddenly the path to my ~/bin does work and the foo.sh works properly. Still puzzled. On Wed

Re: $PATH question

2014-02-27 Thread kitepilot
Pls show the output of: which foo.sh or type foo.sh ET Dazed_75 writes: I thought $PATH contained the series of paths searched to find an executable file by the name specified on the command line. Specifically if my $ENV contains a $PATH which reads: /home/larry/bin: that an

Re: $PATH question

2014-02-27 Thread Dazed_75
comes down to why is .profile not being run on login (I already said I do not have the two files which might prevent it). This is Ubuntu 12.04 BTW. On Thu, Feb 27, 2014 at 6:50 AM, wrote: > Pls show the output of: > which foo.sh > or > type foo.sh > ET > > > Dazed_75 writ

Re: $PATH question

2014-02-27 Thread sean
What's the actual output of `which killsol.sh` when it's not working? It should say "which: no killsol.sh in ($PATH)". This will probably not have /home/larry/bin. man bash, see: INVOCATION to figure out where (and which) files need to be. Upstream bash does not include

Re: $PATH question

2014-02-27 Thread Nathan England
50 AM, <mailto:kitepi...@kitepilot.com>> wrote: Pls show the output of: which foo.sh or type foo.sh ET Dazed_75 writes: I thought $PATH contained the series of paths searched to find an executable file by the name specified on the command line.

Re: $PATH question

2014-02-27 Thread Dazed_75
t). > This is Ubuntu 12.04 BTW. > > > > On Thu, Feb 27, 2014 at 6:50 AM, wrote: > >> Pls show the output of: >> which foo.sh >> or >> type foo.sh >> ET >> >> >> Dazed_75 writes: >> >>> I thought $PATH contained the se

Re: $PATH question

2014-02-27 Thread sean
No, we want the output of : which killsol.sh "which" tells you where "killsol.sh" is in your path. And by "doesn't work" I mean when it is apparently not found in your path. I want to see what "which" says when your shell does not run "killso

Re: $PATH question

2014-02-27 Thread James Mcphee
dash uses /etc/profile, ~/.profile, and $ENV (if available). grep your username from /etc/passwd to find your shell. On Thu, Feb 27, 2014 at 12:04 PM, sean wrote: > No, we want the output of : > > which killsol.sh > > "which" tells you where "killsol.sh" i

Re: $PATH question

2014-02-27 Thread kitepilot
you where "killsol.sh" is in your path. And by "doesn't work" I mean when it is apparently not found in your path. I want to see what "which" says when your shell does not run "killsol.sh" by itself. On Thu, Feb 27, 2014 at 11:59 AM, Dazed_75 wrote: >

Re: $PATH question

2014-02-27 Thread Dazed_75
>> No, we want the output of : >>> which killsol.sh >>> "which" tells you where "killsol.sh" is in your path. >>> And by "doesn't work" I mean when it is apparently not found in your >>> path. I want to see what "w

Re: $PATH question

2014-02-27 Thread sean
$0 >> ET >> >> James Mcphee writes: >> >>> dash uses /etc/profile, ~/.profile, and $ENV (if available). grep your >>> username from /etc/passwd to find your shell. >>> >>> On Thu, Feb 27, 2014 at 12:04 PM, sean >>> wrote: >>> >

Re: $PATH question

2014-02-27 Thread James Mcphee
>>> ET >>> >>> James Mcphee writes: >>> >>>> dash uses /etc/profile, ~/.profile, and $ENV (if available). grep your >>>> username from /etc/passwd to find your shell. >>>> >>>> On Thu, Feb 27, 2014 at 12:04 PM, sean

Re: $PATH question

2014-02-27 Thread Dazed_75
gt;>> Or: >>> echo $0 >>> ET >>> >>> James Mcphee writes: >>> >>>> dash uses /etc/profile, ~/.profile, and $ENV (if available). grep your >>>> username from /etc/passwd to find your shell. >>>> >>>> On

Re: $PATH question

2014-02-27 Thread sean
There is a utility called WHICH and you can use it by typing WHICH KILLSOL.SH and it will give you some output. That is what I want! I don't care about killsol's output. Just type "which killsol.sh"! Does your bashrc set your path? Does your bashrc source any files in /etc? On

Re: $PATH question

2014-02-27 Thread KevinO
On 02/27/2014 03:55 PM, Dazed_75 wrote: > Sean, as stated before, I do have a bashrc and it is being adhered to by > the system. There IS NO OUTPUT from killsol.sh. It is designed to kill a > process if it exists and do so silently whether the process exists or not. Larry, Sean is asking for the

Re: $PATH question

2014-02-27 Thread Dazed_75
You guys need to read the thread which already shows the output of which and type. Let's just drop the whole subject as all we are getting is repeats of the same questions. On Thu, Feb 27, 2014 at 4:00 PM, KevinO wrote: > On 02/27/2014 03:55 PM, Dazed_75 wrote: > > Sean, as stated before, I do

Re: $PATH question

2014-02-27 Thread sean
You only posted the output of which after sourcing .profile. Your non-login, interactive bash sessions are sourcing .bashrc. Export your path in there. On Feb 27, 2014 5:29 PM, "Dazed_75" wrote: > You guys need to read the thread which already shows the output of which > and t

Re: $PATH question

2014-02-28 Thread Paul Mooring
I think people are trying to overcomplicate this issue asking about commands like `file` and `type`. There's only 2 things that matter for it to try and execute without an absolute or relative path: 1. Is it in a directory in my PATH? 2. Does is have the executable bit on? If you wa

OT Re: KDE - PATH

2013-06-15 Thread Ryan Rix
; light? > > On Friday, June 14, 2013 02:13:34 PM Ryan Rix wrote: > > On Wed 12 June 2013 13:05:49 der.hans wrote: > > > moin moin, > > > > > > I've tried a couple of things and am probably just missing something > > > obvious, but ... >

Re: OT Re: KDE - PATH

2013-06-15 Thread Brian Cluff
14, 2013 02:13:34 PM Ryan Rix wrote: On Wed 12 June 2013 13:05:49 der.hans wrote: moin moin, I've tried a couple of things and am probably just missing something obvious, but ... How do I adjust the search path used by the command pop up? It's missing an important directory for me. Sam

Re: OT Re: KDE - PATH

2013-06-15 Thread Lisa Kachold
gt;>>> On Wed 12 June 2013 13:05:49 der.hans wrote: >>>> >>>>> moin moin, >>>>> >>>>> I've tried a couple of things and am probably just missing something >>>>> obvious, but ... >>

Re: OT Re: KDE - PATH

2013-06-16 Thread Nathan England
This is seriously rediculous! Why did a question about KDE become Off Topic? Was this an accident? Was this intentional? Was it just to test the new OT: fliters? --- PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org To subscribe, unsubs

Re: OT Re: KDE - PATH

2013-06-16 Thread Ryan Rix
We're only allowed to talk about the kernel itself here now... On Sun 16 June 2013 18:21:16 Nathan England wrote: > This is seriously rediculous! Why did a question about KDE become Off Topic? > Was this an accident? Was this intentional? > > Was it just to test the new OT: fliters? > > > -

Re: OT Re: KDE - PATH

2013-06-16 Thread Michael Havens
how about if it is related to open source technology it is on topic? :-)~MIKE~(-: On Sun, Jun 16, 2013 at 8:05 PM, Ryan Rix wrote: > We're only allowed to talk about the kernel itself here now... > > On Sun 16 June 2013 18:21:16 Nathan England wrote: > > This is seriously rediculous! Why did a

Re: OT Re: KDE - PATH

2013-06-16 Thread Nathan England
On Sunday, June 16, 2013 08:05:53 PM Ryan Rix wrote: > We're only allowed to talk about the kernel itself here now... > > On Sun 16 June 2013 18:21:16 Nathan England wrote: > > This is seriously rediculous! Why did a question about KDE become Off > > Topic? Was this an accident? Was this intention

Re: OT Re: KDE - PATH

2013-06-16 Thread Matt Graham
don't have a ~/.kde/env/ dir here. I've been using KDE since KDE 1 in 1999. On my Gentoo install, at least, the search path for the minicli is apparently taken from $PATH, which is set in ~/.bashrc for me, but note that YMMV on all that. -- Matt G / Dances With Crows The Crow202 Bl

Re: OT: Re: KDE - PATH

2013-06-16 Thread der.hans
Am 16. Jun, 2013 schwätzte Nathan England so: moin moin, This is seriously rediculous! Why did a question about KDE become Off Topic? Was this an accident? Was this intentional? Ryan set OT for his response to your question about CotS. That was a good move by him as that part of the thread ha

Re: OT: Re: KDE - PATH

2013-06-16 Thread Nathan England
On Sunday, June 16, 2013 09:14:01 PM der.hans wrote: > > > This is seriously rediculous! Why did a question about KDE become Off > > Topic? Was this an accident? Was this intentional? > > > Now my dilemma, do I fix that tag syntax to be TO: since the thread > wandered off to off-topic or leave t

Re: OT Re: KDE - PATH

2013-06-17 Thread Ryan Rix
On Sun 16 June 2013 20:40:51 Matt Graham wrote: > ...I'm not sure why the OT thing happened, but I don't have a ~/.kde/env/ > dir here. I've been using KDE since KDE 1 in 1999. On my Gentoo install, > at least, the search path for the minicli is apparently taken from

Re: OT: Re: KDE - PATH

2013-06-17 Thread Lisa Kachold
Hans, On Sun, Jun 16, 2013 at 9:14 PM, der.hans wrote: > Am 16. Jun, 2013 schwätzte Nathan England so: > > moin moin, > > This is seriously rediculous! Why did a question about KDE become Off >> Topic? >> Was this an accident? Was this intentional? >> > > Ryan set OT for his response to your qu

How to set up PATH ??

2020-10-04 Thread joe--- via PLUG-discuss
My backup computer system has this version: Linux Mint 19.1 Tessa How can I edit .profile so it will find all of my shell script utilities in /home/joe/path ?? I tried adding the 4 "set PATH" lines shown below, but it does not work: # ~/.profile: executed by the command interpreter

Re: How to set up PATH ??

2020-10-04 Thread Matt Graham via PLUG-discuss
On 2020-10-04 12:31, joe--- via PLUG-discuss wrote: Linux Mint 19.1 Tessa How can I edit .profile so it will find all of my shell script utilities in /home/joe/path ?? I tried adding the 4 "set PATH" lines shown below, but it does not work: # ~/.profile: executed by the command i

CentOS 6.x and CentOS 7 upgrade path and testing PHP on current and future versions.

2014-05-06 Thread keith smith
Hi, I want to test some PHP code on future versions of PHP / MySql / MariaDB. I'm running CentOS 6.5 that installs php 5.3.3-27 which is at it's end of life.  It is my understanding RHEL 6.x will always be using PHP 5.3.  Is that correct?  RHEL will be supported until Nov of 2020.  That is a

Re: CentOS 6.x and CentOS 7 upgrade path and testing PHP on current and future versions.

2014-05-07 Thread George Toft
Hi Keith, I have solid word from Red Hat that each minor rev to their major releases are 100% binary compatible, and yes, they lock the version numbers for the entire release. If you look at the RH version numbers, you'll see something like this: 5.3.3-27.el6_5 Everything after the dash

Re: CentOS 6.x and CentOS 7 upgrade path and testing PHP on current and future versions.

2014-05-07 Thread keith smith
If each major version of RHEL is supported for 10 years, and if RHEL 7 is in beta then I think one can look at that and plan for the worse case scenario of being on 7 for more than 5 years.  I'm planning based on a 5 year life cycle for my next project.  I would like not to have to do anything m

Re: CentOS 6.x and CentOS 7 upgrade path and testing PHP on current and future versions.

2014-05-07 Thread James Dugger
I use CentOS 6.5 with php 5.4 and 5.5 through webtatic repo. Below is the link http://webtatic.com/packages/php55/ On Wed, May 7, 2014 at 7:46 AM, George Toft wrote: > Hi Keith, > > I have solid word from Red Hat that each minor rev to their major releases > are 100% binary compatible, and y

Re: CentOS 6.x and CentOS 7 upgrade path and testing PHP on current and future versions.

2014-05-07 Thread keith smith
That's pretty cool!!  Thanks!!   Keith Smith On Wednesday, May 7, 2014 5:24 PM, James Dugger wrote: I use CentOS 6.5 with php 5.4 and 5.5 through webtatic repo.  Below is the link http://webtatic.com/packages/php55/ On Wed, May 7, 2014 at 7:46 AM, George Toft wr