Re: stuff in ~/bin won't run

I know this is old stuff, but... On Tue,13.Jan.09, 11:10:49, JoeHill wrote: > > I'm used to ~/bin being automatically picked up in my path, so therefore I am > absolutely clueless as to how to add it. Also, considering the potential > consequences to my system, I would rather not do it the wrong

Re: stuff in ~/bin won't run

Dotan Cohen wrote: > Thanks, Mike. Actually, rather than be busy for hours, I do wish that > there were some document that explains what gets run where, clearly. I > have yet to find one. Put these lines in your .bashrc and .bash_profile and you'll see what gets run when # bashrc echo "R

Re: stuff in ~/bin won't run

On Sun, Jan 18, 2009 at 08:07:11PM -0500, JoeHill wrote: > I used to have an option for 'automatically start X when computer boots', > which > I would disable. What is the 'Debian Way' for this? ;) Unless you want it for other users, simplest is probably to remove gdm and install xinit (if not al

Re: stuff in ~/bin won't run

Mike Castle wrote: > On Wed, Jan 14, 2009 at 8:33 AM, JoeHill wrote: > > The funny thing is, I already have this in my .bash_profile: > > > > # set PATH so it includes user's private bin if it exists > > if [ -d ~/bin ] ; then > >PATH=~/bin:"${PATH}" > > fi > > I don't think .bash_profil

Re: stuff in ~/bin won't run

Mike Castle wrote: > On Wed, Jan 14, 2009 at 8:33 AM, JoeHill wrote: > > The funny thing is, I already have this in my .bash_profile: > > > > # set PATH so it includes user's private bin if it exists > > if [ -d ~/bin ] ; then > >PATH=~/bin:"${PATH}" > > fi > > I don't think .bash_profil

Re: stuff in ~/bin won't run

JoeHill wrote: > Could you not just give your versions of the apps you want to run > different names? Would that not be safer? What I've done in the past is to > add _mine to end of the names, ie. 'todisc_mine'. > This approach will be a PITA if you use tab completion. Inputting _ is more painfu

Re: stuff in ~/bin won't run

Tzafrir Cohen writes: >On Wed, Jan 14, 2009 at 04:16:57PM -0800, Mike Castle wrote: >> >> I don't think .bash_profile gets sourced when you log in via an >> XDM/GDM type session. (After all, when would it, since you don't >> really have a login shell.) >Possible fix: > echo 'if [ $SHELL = /bin

Re: stuff in ~/bin won't run

2009/1/15 Mike Castle : > On Wed, Jan 14, 2009 at 8:33 AM, JoeHill wrote: >> The funny thing is, I already have this in my .bash_profile: >> >> # set PATH so it includes user's private bin if it exists >> if [ -d ~/bin ] ; then >>PATH=~/bin:"${PATH}" >> fi > > I don't think .bash_profile gets

Re: stuff in ~/bin won't run

On Wed, Jan 14, 2009 at 04:16:57PM -0800, Mike Castle wrote: > On Wed, Jan 14, 2009 at 8:33 AM, JoeHill wrote: > > The funny thing is, I already have this in my .bash_profile: > > > > # set PATH so it includes user's private bin if it exists > > if [ -d ~/bin ] ; then > >PATH=~/bin:"${PATH}"

Re: stuff in ~/bin won't run

On Wed, Jan 14, 2009 at 8:33 AM, JoeHill wrote: > The funny thing is, I already have this in my .bash_profile: > > # set PATH so it includes user's private bin if it exists > if [ -d ~/bin ] ; then >PATH=~/bin:"${PATH}" > fi I don't think .bash_profile gets sourced when you log in via an XDM

Re: stuff in ~/bin won't run

Dotan Cohen wrote: > 2009/1/13 JoeHill : > > > > I'm used to ~/bin being automatically picked up in my path, so therefore I > > am absolutely clueless as to how to add it. Also, considering the potential > > consequences to my system, I would rather not do it the wrong way ;) > > > > This was wha

Re: stuff in ~/bin won't run

2009/1/13 JoeHill : > Could you not just give your versions of the apps you want to run different > names? Would that not be safer? What I've done in the past is to add _mine to > end of the names, ie. 'todisc_mine'. > Depends on what you are doing. Here is a good example of appending locale infor

Re: stuff in ~/bin won't run

On 2009-01-13 20:28 +0100, Daryl Styrk wrote: > "This is unsafe because you are trusting that your own version of the > more command works properly. But it is also risky for a more important > reason: system security. If your PATH is set up in this way, you leave > open a "hole" that is well known

Re: stuff in ~/bin won't run

Dotan Cohen wrote: > 2009/1/13 Steve Kemp : > > On Tue Jan 13, 2009 at 21:08:02 +0200, Dotan Cohen wrote: > > > >> Why is that dangerous? Because if your account is compromised then > >> critical system programs (ls, cd, and the like) can be easily replaced > >> with compromised versions. Putti

Re: stuff in ~/bin won't run

Daryl Styrk writes: > I have no idea what the policy is for quoting excerpts from a book so 've > chosen to leave it out. In the US the "policy" is the bit of copyright law called "Fair Use". It says you can quote excerpts without permission without infringing copyright. -- John Hasler -- To

Re: stuff in ~/bin won't run

Dotan Cohen wrote: > 2009/1/13 Daryl Styrk : >> Mike Castle wrote: >>> On Tue, Jan 13, 2009 at 8:15 AM, Dotan Cohen wrote: Put the new bin BEFORE the old path. >>> Huh? Why? >> According to "Learning the BASH Shell" by Cameron Newham and Bill >> Rosenblatt it is dangerous to have personal b

Re: stuff in ~/bin won't run

2009/1/13 Steve Kemp : > On Tue Jan 13, 2009 at 21:08:02 +0200, Dotan Cohen wrote: > >> Why is that dangerous? Because if your account is compromised then >> critical system programs (ls, cd, and the like) can be easily replaced >> with compromised versions. Putting your own bin at the end of the p

Re: stuff in ~/bin won't run

On Tue Jan 13, 2009 at 21:08:02 +0200, Dotan Cohen wrote: > Why is that dangerous? Because if your account is compromised then > critical system programs (ls, cd, and the like) can be easily replaced > with compromised versions. Putting your own bin at the end of the path > is meant to thwart this

Re: stuff in ~/bin won't run

2009/1/13 Daryl Styrk : > Mike Castle wrote: >> On Tue, Jan 13, 2009 at 8:15 AM, Dotan Cohen wrote: >>> Put the new bin BEFORE the old path. >> >> Huh? Why? > > According to "Learning the BASH Shell" by Cameron Newham and Bill > Rosenblatt it is dangerous to have personal bin directory listed be

Re: stuff in ~/bin won't run

Mike Castle wrote: > On Tue, Jan 13, 2009 at 8:15 AM, Dotan Cohen wrote: >> Put the new bin BEFORE the old path. > > Huh? Why? > > According to "Learning the BASH Shell" by Cameron Newham and Bill Rosenblatt it is dangerous to have personal bin directory listed before the public bin directo

Re: stuff in ~/bin won't run

On Tue, Jan 13, 2009 at 8:15 AM, Dotan Cohen wrote: > Put the new bin BEFORE the old path. Huh? Why? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: stuff in ~/bin won't run

Sorry, that should have been: PATH=$HOME/bin:$PATH export PATH in your ~/.bash_profile file. Put the new bin BEFORE the old path. -- Dotan Cohen http://what-is-what.com http://gibberish.co.il א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת ا-ب-ت-ث-ج-ح-خ-د-ذ-ر-ز-س-ش-ص-ض-ط-ظ-ع-غ-ف-ق-ك-ل-م

Re: stuff in ~/bin won't run

2009/1/13 JoeHill : > > I'm used to ~/bin being automatically picked up in my path, so therefore I am > absolutely clueless as to how to add it. Also, considering the potential > consequences to my system, I would rather not do it the wrong way ;) > > This was what came up on a search, is this corr