Question of setting environment variables - Slackware

This is a discussion on Question of setting environment variables - Slackware ; I've used Linux before but it has been awhile and I have forgotten a few things. If I recall correctly, there use to be a file in my home directory called .bashrc or maybe .bash_profile in which one could set ...

+ Reply to Thread
Page 1 of 9 1 2 3 ... LastLast
Results 1 to 20 of 174

Thread: Question of setting environment variables

  1. Question of setting environment variables

    I've used Linux before but it has been awhile and I have forgotten a few
    things. If I recall correctly, there use to be a file in my home directory
    called .bashrc or maybe .bash_profile in which one could set environment
    variables. I don't see this file and would like to add some environment
    variables.

  2. Re: Question of setting environment variables

    Chris Saunders wrote:
    > I've used Linux before but it has been awhile and I have forgotten a few
    > things. If I recall correctly, there use to be a file in my home directory
    > called .bashrc or maybe .bash_profile in which one could set environment
    > variables. I don't see this file and would like to add some environment
    > variables.


    Just create it. I have ~/.profile, also, which contains only this:

    if [ -f ~/.bashrc ] ; then . ~/.bashrc ; fi

    Both files have these permissions:

    -rw-r--r--

    You will probably want to export the variables:

    export FOO_OOF=foofoo

    If you want them to apply to the entire system, use /etc/profile.

    Sid

    --
    My newsfilter kills all threads and subthreads
    originating with a post from googlegroups.
    See: http://tinyurl.com/4v394u

  3. Re: Question of setting environment variables

    Chris Saunders writes:

    > I've used Linux before but it has been awhile and I have forgotten a few
    > things. If I recall correctly, there use to be a file in my home directory
    > called .bashrc or maybe .bash_profile in which one could set environment
    > variables. I don't see this file and would like to add some environment
    > variables.


    http://www.slackbook.org/html/book.html#SHELL-BASH

    Its good stuff!

    atb

    Glyn
    --
    RTFM http://www.tldp.org/index.html
    GAFC http://slackbook.org/ The Official Source :-)
    STFW http://groups.google.com/groups?hl=e...inux.slackware
    JFGI http://jfgi.us/

  4. Re: Question of setting environment variables

    Chris Saunders writes:

    > I've used Linux before but it has been awhile and I have forgotten a few
    > things. If I recall correctly, there use to be a file in my home directory
    > called .bashrc or maybe .bash_profile in which one could set environment
    > variables. I don't see this file and would like to add some environment
    > variables.


    Sorry - that wasn't the best link to give you!

    Try this one :-

    http://www.tldp.org/LDP/Bash-Beginne...ect_03_01.html

    atb

    Glyn
    --
    RTFM http://www.tldp.org/index.html
    GAFC http://slackbook.org/ The Official Source :-)
    STFW http://groups.google.com/groups?hl=e...inux.slackware
    JFGI http://jfgi.us/

  5. Re: Question of setting environment variables

    Sidney Lambe wrote:
    >
    > Just create it. I have ~/.profile, also, which contains only this:
    >
    > if [ -f ~/.bashrc ] ; then . ~/.bashrc ; fi
    >


    "man bash" also has a surprising amount of information.

    - Kurt

  6. Re: Question of setting environment variables

    On Wed, 24 Sep 2008 21:07:21 -0500, ~kurt wrote:



    > "man bash" also has a surprising amount of information.




    Heh. Is there a longer man-page known to man?


    --
    "Ubuntu" -- an African word, meaning "Slackware is too hard for me".
    The Usenet Improvement Project: http://improve-usenet.org


  7. Re: Question of setting environment variables

    Dan C writes:

    > On Wed, 24 Sep 2008 21:07:21 -0500, ~kurt wrote:
    >
    >
    >
    >> "man bash" also has a surprising amount of information.

    >
    >

    >
    > Heh. Is there a longer man-page known to man?



    Nice one!


    $man bash | less -N gives 4902 here

    $man fvwm | less -N gives 8899

    any advance on fvwm?

    atb


    Glyn
    --
    RTFM http://www.tldp.org/index.html
    GAFC http://slackbook.org/ The Official Source :-)
    STFW http://groups.google.com/groups?hl=e...inux.slackware
    JFGI http://jfgi.us/

  8. Re: Question of setting environment variables

    Glyn Millington wrote:
    >$man bash | less -N gives 4902 here
    >$man fvwm | less -N gives 8899


    $ man gcc | wc -l
    11542

    But I think this is the record:

    $ man perltoc | wc -l
    12602

    -Beej


  9. Re: Question of setting environment variables

    ~kurt wrote:
    >
    > "man bash" also has a surprising amount of information.


    Don't do that if you have only ten minuts of spare time.


    --
    No sig available.

  10. Re: Question of setting environment variables

    Glyn Millington wrote:

    > $man fvwm | less -N gives 8899
    >
    > any advance on fvwm?


    Mmmmm. thinking...
    Oh, I've got it.
    fvwm --> f*ck*ng very wide manpage ?

    --
    No sig available.

  11. Re: Question of setting environment variables

    On Thu, 25 Sep 2008 06:42:34 +0100, Glyn Millington wrote:

    > $man fvwm | less -N gives 8899


    That would be about 99 lines on using fvwm and about 8800 lines on its
    config file syntax?

  12. Re: Question of setting environment variables

    Mark Madsen writes:

    > On Thu, 25 Sep 2008 06:42:34 +0100, Glyn Millington wrote:
    >
    >> $man fvwm | less -N gives 8899

    >
    > That would be about 99 lines on using fvwm and about 8800 lines on its
    > config file syntax?


    Pretty much! But there is more .........

    * fvwm
    * fvwm
    * FvwmAnimate
    * FvwmAuto
    * FvwmBacker
    * FvwmBanner
    * FvwmButtons
    * FvwmCommand
    * FvwmConsole
    * FvwmConsoleC.pl
    * FvwmCpp
    * FvwmDebug
    * FvwmDragWell
    * FvwmEvent
    * FvwmForm
    * FvwmGtk
    * FvwmGtkDebug
    * FvwmIconBox
    * FvwmIconMan
    * FvwmIdent
    * FvwmM4
    * FvwmPager
    * FvwmPerl
    * FvwmProxy
    * FvwmRearrange
    * FvwmSave
    * FvwmSaveDesk
    * FvwmScript
    * FvwmScroll
    * FvwmTabs
    * FvwmTaskBar
    * FvwmTheme
    * FvwmWharf
    * FvwmWinList
    * FvwmWindowMenu
    * fvwm-bug
    * fvwm-config
    * fvwm-convert-2.2
    * fvwm-convert-2.4
    * fvwm-convert-2.6
    * fvwm-menu-desktop
    * fvwm-menu-directory
    * fvwm-menu-headlines
    * fvwm-menu-xlock
    * fvwm-perllib
    * fvwm-root

    :-)


    Glyn
    --
    RTFM http://www.tldp.org/index.html
    GAFC http://slackbook.org/ The Official Source :-)
    STFW http://groups.google.com/groups?hl=e...inux.slackware
    JFGI http://jfgi.us/

  13. Re: Question of setting environment variables

    Beej Jorgensen wrote:
    > $ man gcc | wc -l
    > 11542
    >
    > But I think this is the record:
    >
    > $ man perltoc | wc -l
    > 12602


    $ man wireshark-filter | wc -l
    197775

    OK, it's not included by default...

  14. Re: Question of setting environment variables

    On 2008-09-25, ~kurt wrote:
    > Sidney Lambe wrote:
    >>
    >> Just create it. I have ~/.profile, also, which contains only this:
    >>
    >> if [ -f ~/.bashrc ] ; then . ~/.bashrc ; fi

    >
    > "man bash" also has a surprising amount of information.


    If by "surprising" you mean "difficult to navigate", I agree.

    Look up the INVOCATION section of the manpage for bash. It has docs for
    what files are sourced on startup. You'll see that there might be good
    reason not to do what ''Sidney'' aka netkook Alan Connor suggests above.
    (In particular if you use interactive shells that might not be login
    shells you do not want to call .bashrc from .bash_profile or vice versa.
    Most people don't do this, but some do.)

    --keith


    --
    kkeller-usenet@wombat.san-francisco.ca.us
    (try just my userid to email me)
    AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
    see X- headers for PGP signature information


  15. Re: Question of setting environment variables

    fuzzix wrote:
    >$ man wireshark-filter | wc -l
    >197775


    Good Lord, man... that's impressive.

    -Beej


  16. Re: Question of setting environment variables

    Keith Keller wrote:
    >> "man bash" also has a surprising amount of information.

    >
    > If by "surprising" you mean "difficult to navigate", I agree.
    >
    > Look up the INVOCATION section of the manpage for bash.


    No, no, no, NO! If you've got something to do with GNU Software, look up
    the *info*-pages! 'info bash' is the way to go. There are no manpages
    about GNU Software except the ones someone put together unofficially.

    Rupa

  17. Re: Question of getting system/application information

    Responding to Rupa Zangpo:

    > Keith Keller wrote:
    >>> "man bash" also has a surprising amount of information.

    >>
    >> If by "surprising" you mean "difficult to navigate", I agree.
    >>
    >> Look up the INVOCATION section of the manpage for bash.

    >
    > No, no, no, NO! If you've got something to do with GNU Software, look up
    > the *info*-pages! 'info bash' is the way to go. There are no manpages
    > about GNU Software except the ones someone put together unofficially.
    >
    > Rupa



    Hey! Yeah! Another obscure method of storing and retrieving information!
    Just what the world needs!

    What, I have to wonder, is the problem with html? Its universal, simple,
    and all but one single wood burning computer somewhere up a mountain in
    Siberia actually has the capacity to read html from the moment they are
    booted.

    So why are we still stuck with "man this" and "info that" and "xyz the
    other" etc.? Why are these obscure, specialist, restrictive,
    incantational, and arguably obsolete ways of storing information still
    with us?

    Ah mean tah say! Plain text is as searchable as a man/info page!

    --
    *===( http://principiadiscordia.com/
    *===( http://www.badphorm.co.uk/
    *===( http://www.zenwalk.org/

  18. Re: Question of setting environment variables

    Rupa Zangpo wrote:

    > No, no, no, NO! If you've got something to do with GNU Software, look
    > up the *info*-pages! 'info bash' is the way to go. There are no
    > manpages about GNU Software except the ones someone put together
    > unofficially.


    That's the problem with GNU: they had to go and re-invent documentation
    too.

    --
    ----------------------------------------------------------------------
    Sylvain Robitaille syl@alcor.concordia.ca

    Network and Systems analyst Concordia University
    Instructional & Information Technology Montreal, Quebec, Canada
    ----------------------------------------------------------------------

  19. Re: Question of getting system/application information

    Mike wrote:

    > What, I have to wonder, is the problem with html?


    That's the problem with newbies: they want everything to be a web page
    ....

    > Its universal, simple, and all but one single wood burning computer
    > somewhere up a mountain in Siberia actually has the capacity to read
    > html from the moment they are booted.


    Perhaps, but even that one computer in Siberia is able to process
    and display a manpage relatively quickly, so "man" is still the most
    universal.

    Do you have an html reader that will search for a particular file,
    through a preset search-path, based on arguments you give it? See
    "man man" for details.

    > Ah mean tah say! Plain text is as searchable as a man/info page!


    Um ... a manpage *is* plain text, with some markup (sound familiar?)
    I would be very surprised if the same were not true of info pages,
    but I care too little about those to bother checking.

    In fact, check out the man2html manpage (that would be "man man2html", of
    course ;-). I think you you'll find you *can* have your manpages in html.

    --
    ----------------------------------------------------------------------
    Sylvain Robitaille syl@alcor.concordia.ca

    Network and Systems analyst Concordia University
    Instructional & Information Technology Montreal, Quebec, Canada
    ----------------------------------------------------------------------

  20. Re: Question of getting system/application information

    Mike wrote:
    > So why are we still stuck with "man this" and "info that" and "xyz the
    > other" etc.? Why are these obscure, specialist, restrictive,
    > incantational, and arguably obsolete ways of storing information still
    > with us?


    it's not a matter of being "stuck" with them. they have properties that
    have not been duplicated in html readers, such as the ability to search a
    series of predefined directories for the doc you want to read, much simpler
    markup, integration with emacs (for info at least), faster startup times
    than the average browser, command-line capable.

    in short, i'd much rather read documentation with man or info than with
    firefox. of course there's lynx and links, and w3m, and if someone would
    ever take the trouble to build the other advantages of man and info into
    them, and to convert all relevant documentation into html format, i
    probably wouldn't really mind switching to html doc, but why would one go
    through all that trouble just to duplicate functionality that already
    exists?

    but you know, info pages are generally generated from texinfo source files,
    which can just as easily be converted to html (and even pdf). in fact, gnu
    info pages are always available on the net in a variety of formats, among
    which html (in two variants, even). so if you prefer, you can read any info
    page as html. there are also several ways to convert man or t/nroff docs to
    html.


    --
    Joost Kremers joostkremers@yahoo.com
    Selbst in die Unterwelt dringt durch Spalten Licht
    EN:SiS(9)

+ Reply to Thread
Page 1 of 9 1 2 3 ... LastLast