Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
Setup PATH for X Window (urxvt)On Tue, 1 May 2007 12:03:23 +0200 > Hello! Are you using GDM to log in? It does execute a login shell default. However, you can circumvent that by making .xsession invoke a login shell, i.e., by changing the first line #!/bin/sh --login Alternatively, you could start X by running 'startx' after logging Better, though, would be to install the software to /usr/local instead. -- Liam -- Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
Setup PATH for X Window (urxvt)
On Tue, 1 May 2007 11:51:07 +0100
Liam O'Toole wrote:
> Are you using GDM to log in? It does execute a login shell default.
Just to correct an appalling typo: the above should read "It does not
execute a login shell by default".
--
Liam
--
Setup PATH for X Window (urxvt)
On Tue, May 01, 2007 at 11:51:07AM +0100, Liam O'Toole wrote:
> On Tue, 1 May 2007 12:03:23 +0200
> csanyipal wrote:
>
> > Hello!
> >
> > I try to setup PATH permanently for X Window, that is for urxvt, in
> > which must to run brlcad.
> >
> > brlcad is here: /usr/brlcad/bin
> >
> > Now, if I run mged (editor for brlcad) I must to open urxvt, then
> > setup PATH for brlcad and then can run mged.
> >
> > I want to setup PATH permanently to can run brlcad without setting up
> > every time the PATH.
> >
> > I try to write these:
> > PATH=/usr/brlcad/bin:$PATH
> > export PATH
> >
> > in several places:
>
> > but env shows me that the PATH have not setup to brlcad:
> > PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
> >
> > How can I setup PATH for brlcad permanently?
> Better, though, would be to install the software to /usr/local instead.
Or put a symlink in /usr/local/bin to the files in /usr/brlcad/bin
Or a script in /usr/local/bin that calls /usr/brlcad/bin/...
Doug.
--
Setup PATH for X Window (urxvt)
On Tue, 1 May 2007 16:39:39 +0200
csanyipal wrote:
> On Tue, May 01, 2007 at 11:51:07AM +0100, Liam O'Toole wrote:
>
> > Are you using GDM to log in? It does execute a login shell default.
>
> Yes. I edit the /etc/gdm/Init/Default but still not change the PATH.
> I try to edit /etc/gdm/PostLogin/Default too, but with no success.
Then the solution which involves running .xsession in a login shell
should work.
>
> > Better, though, would be to install the software to /usr/local
> > instead.
>
> I agree with this. But the brlcad package can one to download in
> tar.bz2 package or from CVS repository. Which one can one use to
> build the debian package from it?
Usually stable releases are made available as a tarball. So I would try
that first.
--
Liam
--
Setup PATH for X Window (urxvt)
On Tue, May 01, 2007 at 04:39:39PM +0200, csanyipal wrote:
> On Tue, May 01, 2007 at 11:51:07AM +0100, Liam O'Toole wrote:
> > Better, though, would be to install the software to /usr/local instead.
>
> I agree with this. But the brlcad package can one to download in tar.bz2
> package or from CVS repository. Which one can one use to build the debian
> package from it?
Shouldn't pre-compiled tarballs go in /opt?
Doug.
--
Setup PATH for X Window (urxvt)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Douglas Allan Tutty wrote:
> On Tue, May 01, 2007 at 04:39:39PM +0200, csanyipal wrote:
>> On Tue, May 01, 2007 at 11:51:07AM +0100, Liam O'Toole wrote:
>
>>> Better, though, would be to install the software to /usr/local instead.
>> I agree with this. But the brlcad package can one to download in tar.bz2
>> package or from CVS repository. Which one can one use to build the debian
>> package from it?
>
> Shouldn't pre-compiled tarballs go in /opt?
Does it really make a difference? What matters is that it is in a
different place than /bin or /usr/bin so that the system won't clobber
it when it gets upgraded. Perhaps I am wrong. Personally, I have some
things in /opt and some others in /usr/local/bin.
Joe
- --
Registerd Linux user #443289 at http://counter.li.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGN58eiXBCVWpc5J4RAljwAJ0Qc4eUhYKKofLuCBnCTXdQHZQl2gCggqtt
LFhhrmDGGkZZhgFGlctwj/c=
=YMCt
-----END PGP SIGNATURE-----
--
Setup PATH for X Window (urxvt)
On Tue, May 01, 2007 at 10:12:14PM +0200, Joe Hart wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Douglas Allan Tutty wrote:
> > On Tue, May 01, 2007 at 04:39:39PM +0200, csanyipal wrote:
> >> On Tue, May 01, 2007 at 11:51:07AM +0100, Liam O'Toole wrote:
> >
> >>> Better, though, would be to install the software to /usr/local instead.
> >> I agree with this. But the brlcad package can one to download in tar.bz2
> >> package or from CVS repository. Which one can one use to build the debian
> >> package from it?
> >
> > Shouldn't pre-compiled tarballs go in /opt?
>
> Does it really make a difference? What matters is that it is in a
> different place than /bin or /usr/bin so that the system won't clobber
> it when it gets upgraded. Perhaps I am wrong. Personally, I have some
> things in /opt and some others in /usr/local/bin.
I suppose it makes a difference depending on how update tarballs get
handled. If you just get a new tarball, how do you ensure that all the
old stuff is removed? With everything under /opt then you just remove
the directory.
If you're compiling, then a make uninstall (or whatever) handles this.
Doug.
--
Setup PATH for X Window (urxvt)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Douglas Allan Tutty wrote:
> On Tue, May 01, 2007 at 10:12:14PM +0200, Joe Hart wrote:
[snip]
>>> Shouldn't pre-compiled tarballs go in /opt?
>>
>> Does it really make a difference? What matters is that it is in a
>> different place than /bin or /usr/bin so that the system won't clobber
>> it when it gets upgraded. Perhaps I am wrong. Personally, I have some
>> things in /opt and some others in /usr/local/bin.
>
> I suppose it makes a difference depending on how update tarballs get
> handled. If you just get a new tarball, how do you ensure that all the
> old stuff is removed? With everything under /opt then you just remove
> the directory.
>
> If you're compiling, then a make uninstall (or whatever) handles this.
Some people put them in /home/username so that only they have permission
to use them, and others put them in /opt and yet others in /usr/bin.
IMO, it doesn't really matter as long as one knows what is where, but
you are definitely right in saying that if they are in one place it
would be easier to keep track of them.
Joe
- --
Registerd Linux user #443289 at http://counter.li.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGOOWViXBCVWpc5J4RAipUAJ4nzijPjBXWoH5ba4XoanW3ggmyGwCgwtY+
Ne8z9sGBVCYlJ9j4YFkZpnE=
=LEks
-----END PGP SIGNATURE-----
--