What do the symbols displayed by ls -F mean?What does * next to the file name mean in the output of ls?What does the * with a file name signify?what does the @ mean in ls -l?what does the @ mean in ls -l?ls command: what does the first line mean?What is the @ after directory listing mean?How to set what field names are displayed in listings?What does * next to the file name mean in the output of ls?What do the fields in ls -al output mean?What does 'l' in file metadata meanWhat does the @ symbol mean on filenamesWhat does a red-colored filename mean?How to find what the fields in ls -l mean

Doubts in understanding some concepts of potential energy

School performs periodic password audits. Is my password compromised?

What is this diamond of every day?

Finitely many repeated replacements

After `ssh` without `-X` to a machine, is it possible to change `$DISPLAY` to make it work like `ssh -X`?

Under what conditions can the right to remain silent be revoked in the USA?

How does Ehrenfest's theorem apply to the quantum harmonic oscillator?

How to resolve: Reviewer #1 says remove section X vs. Reviewer #2 says expand section X

Would an aboleth's Phantasmal Force lair action be affected by Counterspell, Dispel Magic, and/or Slow?

In the late 1940’s to early 1950’s what technology was available that could melt ice?

This Alpine town?

How to design an organic heat-shield?

(Codewars) Linked Lists - Remove Duplicates

Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?

Was it really inappropriate to write a pull request for the company I interviewed with?

Why do phishing e-mails use faked e-mail addresses instead of the real one?

Does Christianity allow for believing on someone else's behalf?

Does a difference of tense count as a difference of meaning in a minimal pair?

Signed and unsigned numbers

How to write a chaotic neutral protagonist and prevent my readers from thinking they are evil?

Why restrict private health insurance?

Are small insurances worth it?

Should I take out a loan for a friend to invest on my behalf?

Which classes are needed to have access to every spell in the PHB?



What do the symbols displayed by ls -F mean?


What does * next to the file name mean in the output of ls?What does the * with a file name signify?what does the @ mean in ls -l?what does the @ mean in ls -l?ls command: what does the first line mean?What is the @ after directory listing mean?How to set what field names are displayed in listings?What does * next to the file name mean in the output of ls?What do the fields in ls -al output mean?What does 'l' in file metadata meanWhat does the @ symbol mean on filenamesWhat does a red-colored filename mean?How to find what the fields in ls -l mean













58















I noticed that if I run ls -F on a directory, some of the entries have a * or a @ after them.



spuder@ubuntu:~$ ls -F /sbin
acpi_available* getpcaps* lvmconf* ntfscp* start-stop-daemon*
agetty* getty* lvmdiskscan@ ntfslabel* status@
alsa* halt@ lvmdump* ntfsresize* stop@
alsactl* hdparm* lvmsadc@

spuder@ubuntu:~$ ls -F ~
daq-0.6.1/ examples.desktop noname-cache.lib snort-2.9.1/ Templates/
Desktop/ jpgraph-1.27.1/ noname.sch snortfiles/ Ubuntu One/
Documents/


According to the ls man pages



spuder@ubuntu:~$ man ls
...
-F, --classify
append indicator (one of */=>@|) to entries
...


I'm guessing that @ means symbolic link,



What do these other indicators mean ( */=>@| ) ?










share|improve this question



















  • 2





    Have you thought of looking at the man page?

    – mdpc
    Jul 9 '13 at 17:20






  • 19





    He has. In fact, he posted an excerpt from the manpage. The full ls documentation, including information about the symbols displayed by ls -F, is in a Texinfo manual. (info ls).

    – user26112
    Jul 9 '13 at 17:33







  • 1





    On a side note, since Texinfo manuals generally feel strange and foreign, it's common to keep around functions like these: infos () info --vi-keys --subnodes -o - "$@" .

    – user26112
    Jul 9 '13 at 17:37







  • 1





    @EvanTeitelman This is great information, I will keep info foo --vi-keys in mind. Unfortunately the syntax you mentioned does not work for me (infos () info --vi-keys...

    – spuder
    Jul 9 '13 at 17:44







  • 1





    @spuder: It's a function; you have to call it. infos ls. The $@ part passes all of the function's arguments to info. You can put this function in your ~/.bashrc file for later use.

    – user26112
    Jul 9 '13 at 17:56
















58















I noticed that if I run ls -F on a directory, some of the entries have a * or a @ after them.



spuder@ubuntu:~$ ls -F /sbin
acpi_available* getpcaps* lvmconf* ntfscp* start-stop-daemon*
agetty* getty* lvmdiskscan@ ntfslabel* status@
alsa* halt@ lvmdump* ntfsresize* stop@
alsactl* hdparm* lvmsadc@

spuder@ubuntu:~$ ls -F ~
daq-0.6.1/ examples.desktop noname-cache.lib snort-2.9.1/ Templates/
Desktop/ jpgraph-1.27.1/ noname.sch snortfiles/ Ubuntu One/
Documents/


According to the ls man pages



spuder@ubuntu:~$ man ls
...
-F, --classify
append indicator (one of */=>@|) to entries
...


I'm guessing that @ means symbolic link,



What do these other indicators mean ( */=>@| ) ?










share|improve this question



















  • 2





    Have you thought of looking at the man page?

    – mdpc
    Jul 9 '13 at 17:20






  • 19





    He has. In fact, he posted an excerpt from the manpage. The full ls documentation, including information about the symbols displayed by ls -F, is in a Texinfo manual. (info ls).

    – user26112
    Jul 9 '13 at 17:33







  • 1





    On a side note, since Texinfo manuals generally feel strange and foreign, it's common to keep around functions like these: infos () info --vi-keys --subnodes -o - "$@" .

    – user26112
    Jul 9 '13 at 17:37







  • 1





    @EvanTeitelman This is great information, I will keep info foo --vi-keys in mind. Unfortunately the syntax you mentioned does not work for me (infos () info --vi-keys...

    – spuder
    Jul 9 '13 at 17:44







  • 1





    @spuder: It's a function; you have to call it. infos ls. The $@ part passes all of the function's arguments to info. You can put this function in your ~/.bashrc file for later use.

    – user26112
    Jul 9 '13 at 17:56














58












58








58


26






I noticed that if I run ls -F on a directory, some of the entries have a * or a @ after them.



spuder@ubuntu:~$ ls -F /sbin
acpi_available* getpcaps* lvmconf* ntfscp* start-stop-daemon*
agetty* getty* lvmdiskscan@ ntfslabel* status@
alsa* halt@ lvmdump* ntfsresize* stop@
alsactl* hdparm* lvmsadc@

spuder@ubuntu:~$ ls -F ~
daq-0.6.1/ examples.desktop noname-cache.lib snort-2.9.1/ Templates/
Desktop/ jpgraph-1.27.1/ noname.sch snortfiles/ Ubuntu One/
Documents/


According to the ls man pages



spuder@ubuntu:~$ man ls
...
-F, --classify
append indicator (one of */=>@|) to entries
...


I'm guessing that @ means symbolic link,



What do these other indicators mean ( */=>@| ) ?










share|improve this question
















I noticed that if I run ls -F on a directory, some of the entries have a * or a @ after them.



spuder@ubuntu:~$ ls -F /sbin
acpi_available* getpcaps* lvmconf* ntfscp* start-stop-daemon*
agetty* getty* lvmdiskscan@ ntfslabel* status@
alsa* halt@ lvmdump* ntfsresize* stop@
alsactl* hdparm* lvmsadc@

spuder@ubuntu:~$ ls -F ~
daq-0.6.1/ examples.desktop noname-cache.lib snort-2.9.1/ Templates/
Desktop/ jpgraph-1.27.1/ noname.sch snortfiles/ Ubuntu One/
Documents/


According to the ls man pages



spuder@ubuntu:~$ man ls
...
-F, --classify
append indicator (one of */=>@|) to entries
...


I'm guessing that @ means symbolic link,



What do these other indicators mean ( */=>@| ) ?







ls






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 9 '13 at 17:39







user26112

















asked Jul 9 '13 at 16:30









spuderspuder

6,6712571106




6,6712571106







  • 2





    Have you thought of looking at the man page?

    – mdpc
    Jul 9 '13 at 17:20






  • 19





    He has. In fact, he posted an excerpt from the manpage. The full ls documentation, including information about the symbols displayed by ls -F, is in a Texinfo manual. (info ls).

    – user26112
    Jul 9 '13 at 17:33







  • 1





    On a side note, since Texinfo manuals generally feel strange and foreign, it's common to keep around functions like these: infos () info --vi-keys --subnodes -o - "$@" .

    – user26112
    Jul 9 '13 at 17:37







  • 1





    @EvanTeitelman This is great information, I will keep info foo --vi-keys in mind. Unfortunately the syntax you mentioned does not work for me (infos () info --vi-keys...

    – spuder
    Jul 9 '13 at 17:44







  • 1





    @spuder: It's a function; you have to call it. infos ls. The $@ part passes all of the function's arguments to info. You can put this function in your ~/.bashrc file for later use.

    – user26112
    Jul 9 '13 at 17:56













  • 2





    Have you thought of looking at the man page?

    – mdpc
    Jul 9 '13 at 17:20






  • 19





    He has. In fact, he posted an excerpt from the manpage. The full ls documentation, including information about the symbols displayed by ls -F, is in a Texinfo manual. (info ls).

    – user26112
    Jul 9 '13 at 17:33







  • 1





    On a side note, since Texinfo manuals generally feel strange and foreign, it's common to keep around functions like these: infos () info --vi-keys --subnodes -o - "$@" .

    – user26112
    Jul 9 '13 at 17:37







  • 1





    @EvanTeitelman This is great information, I will keep info foo --vi-keys in mind. Unfortunately the syntax you mentioned does not work for me (infos () info --vi-keys...

    – spuder
    Jul 9 '13 at 17:44







  • 1





    @spuder: It's a function; you have to call it. infos ls. The $@ part passes all of the function's arguments to info. You can put this function in your ~/.bashrc file for later use.

    – user26112
    Jul 9 '13 at 17:56








2




2





Have you thought of looking at the man page?

– mdpc
Jul 9 '13 at 17:20





Have you thought of looking at the man page?

– mdpc
Jul 9 '13 at 17:20




19




19





He has. In fact, he posted an excerpt from the manpage. The full ls documentation, including information about the symbols displayed by ls -F, is in a Texinfo manual. (info ls).

– user26112
Jul 9 '13 at 17:33






He has. In fact, he posted an excerpt from the manpage. The full ls documentation, including information about the symbols displayed by ls -F, is in a Texinfo manual. (info ls).

– user26112
Jul 9 '13 at 17:33





1




1





On a side note, since Texinfo manuals generally feel strange and foreign, it's common to keep around functions like these: infos () info --vi-keys --subnodes -o - "$@" .

– user26112
Jul 9 '13 at 17:37






On a side note, since Texinfo manuals generally feel strange and foreign, it's common to keep around functions like these: infos () info --vi-keys --subnodes -o - "$@" .

– user26112
Jul 9 '13 at 17:37





1




1





@EvanTeitelman This is great information, I will keep info foo --vi-keys in mind. Unfortunately the syntax you mentioned does not work for me (infos () info --vi-keys...

– spuder
Jul 9 '13 at 17:44






@EvanTeitelman This is great information, I will keep info foo --vi-keys in mind. Unfortunately the syntax you mentioned does not work for me (infos () info --vi-keys...

– spuder
Jul 9 '13 at 17:44





1




1





@spuder: It's a function; you have to call it. infos ls. The $@ part passes all of the function's arguments to info. You can put this function in your ~/.bashrc file for later use.

– user26112
Jul 9 '13 at 17:56






@spuder: It's a function; you have to call it. infos ls. The $@ part passes all of the function's arguments to info. You can put this function in your ~/.bashrc file for later use.

– user26112
Jul 9 '13 at 17:56











2 Answers
2






active

oldest

votes


















59














ls -F appends symbols to filenames. These symbols show useful information about files.




  • @ means symbolic link (or that the file has extended attributes).


  • * means executable.


  • = means socket.


  • | means named pipe.


  • > means door.


  • / means directory.

If you want this behavior to be the default, add this to your shell configuration: alias ls='ls -F'.






share|improve this answer




















  • 9





    do not realias commands, it can break badly written scripts. I have aliased l to have -F and colour, and ll to also have -l

    – ctrl-alt-delor
    Jun 30 '16 at 11:03











  • On Android I get a completely two column output. I get the filename or directory name and BEFORE the name there is a minus if it is file, or a "d" if it is a directory, or a "ld" if it is a link. It is a disaster that Linuxes are so inconsistent!

    – Elmue
    Jun 1 '18 at 16:31



















0














Just to add how I found this info. As indicated at the bottom of man ls:




Full documentation at: https://www.gnu.org/software/coreutils/ls
or available locally via: info '(coreutils) ls invocation'




Following this, we see




‘-F’ ‘--classify’ ‘--indicator-style=classify’ Append a character to
each file name indicating the file type. Also, for regular files that
are executable, append ‘*’. The file type indicators are ‘/’ for
directories, ‘@’ for symbolic links, ‘|’ for FIFOs, ‘=’ for sockets,
‘>’ for doors, and nothing for regular files. Do not follow symbolic
links listed on the command line unless the --dereference-command-line
(-H), --dereference (-L), or --dereference-command-line-symlink-to-dir
options are specified.




on https://www.gnu.org/software/coreutils/manual/coreutils.html#ls-invocation






share|improve this answer






















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f82357%2fwhat-do-the-symbols-displayed-by-ls-f-mean%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    59














    ls -F appends symbols to filenames. These symbols show useful information about files.




    • @ means symbolic link (or that the file has extended attributes).


    • * means executable.


    • = means socket.


    • | means named pipe.


    • > means door.


    • / means directory.

    If you want this behavior to be the default, add this to your shell configuration: alias ls='ls -F'.






    share|improve this answer




















    • 9





      do not realias commands, it can break badly written scripts. I have aliased l to have -F and colour, and ll to also have -l

      – ctrl-alt-delor
      Jun 30 '16 at 11:03











    • On Android I get a completely two column output. I get the filename or directory name and BEFORE the name there is a minus if it is file, or a "d" if it is a directory, or a "ld" if it is a link. It is a disaster that Linuxes are so inconsistent!

      – Elmue
      Jun 1 '18 at 16:31
















    59














    ls -F appends symbols to filenames. These symbols show useful information about files.




    • @ means symbolic link (or that the file has extended attributes).


    • * means executable.


    • = means socket.


    • | means named pipe.


    • > means door.


    • / means directory.

    If you want this behavior to be the default, add this to your shell configuration: alias ls='ls -F'.






    share|improve this answer




















    • 9





      do not realias commands, it can break badly written scripts. I have aliased l to have -F and colour, and ll to also have -l

      – ctrl-alt-delor
      Jun 30 '16 at 11:03











    • On Android I get a completely two column output. I get the filename or directory name and BEFORE the name there is a minus if it is file, or a "d" if it is a directory, or a "ld" if it is a link. It is a disaster that Linuxes are so inconsistent!

      – Elmue
      Jun 1 '18 at 16:31














    59












    59








    59







    ls -F appends symbols to filenames. These symbols show useful information about files.




    • @ means symbolic link (or that the file has extended attributes).


    • * means executable.


    • = means socket.


    • | means named pipe.


    • > means door.


    • / means directory.

    If you want this behavior to be the default, add this to your shell configuration: alias ls='ls -F'.






    share|improve this answer















    ls -F appends symbols to filenames. These symbols show useful information about files.




    • @ means symbolic link (or that the file has extended attributes).


    • * means executable.


    • = means socket.


    • | means named pipe.


    • > means door.


    • / means directory.

    If you want this behavior to be the default, add this to your shell configuration: alias ls='ls -F'.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Apr 13 '17 at 12:37









    Community

    1




    1










    answered Jul 9 '13 at 16:34







    user26112














    • 9





      do not realias commands, it can break badly written scripts. I have aliased l to have -F and colour, and ll to also have -l

      – ctrl-alt-delor
      Jun 30 '16 at 11:03











    • On Android I get a completely two column output. I get the filename or directory name and BEFORE the name there is a minus if it is file, or a "d" if it is a directory, or a "ld" if it is a link. It is a disaster that Linuxes are so inconsistent!

      – Elmue
      Jun 1 '18 at 16:31













    • 9





      do not realias commands, it can break badly written scripts. I have aliased l to have -F and colour, and ll to also have -l

      – ctrl-alt-delor
      Jun 30 '16 at 11:03











    • On Android I get a completely two column output. I get the filename or directory name and BEFORE the name there is a minus if it is file, or a "d" if it is a directory, or a "ld" if it is a link. It is a disaster that Linuxes are so inconsistent!

      – Elmue
      Jun 1 '18 at 16:31








    9




    9





    do not realias commands, it can break badly written scripts. I have aliased l to have -F and colour, and ll to also have -l

    – ctrl-alt-delor
    Jun 30 '16 at 11:03





    do not realias commands, it can break badly written scripts. I have aliased l to have -F and colour, and ll to also have -l

    – ctrl-alt-delor
    Jun 30 '16 at 11:03













    On Android I get a completely two column output. I get the filename or directory name and BEFORE the name there is a minus if it is file, or a "d" if it is a directory, or a "ld" if it is a link. It is a disaster that Linuxes are so inconsistent!

    – Elmue
    Jun 1 '18 at 16:31






    On Android I get a completely two column output. I get the filename or directory name and BEFORE the name there is a minus if it is file, or a "d" if it is a directory, or a "ld" if it is a link. It is a disaster that Linuxes are so inconsistent!

    – Elmue
    Jun 1 '18 at 16:31














    0














    Just to add how I found this info. As indicated at the bottom of man ls:




    Full documentation at: https://www.gnu.org/software/coreutils/ls
    or available locally via: info '(coreutils) ls invocation'




    Following this, we see




    ‘-F’ ‘--classify’ ‘--indicator-style=classify’ Append a character to
    each file name indicating the file type. Also, for regular files that
    are executable, append ‘*’. The file type indicators are ‘/’ for
    directories, ‘@’ for symbolic links, ‘|’ for FIFOs, ‘=’ for sockets,
    ‘>’ for doors, and nothing for regular files. Do not follow symbolic
    links listed on the command line unless the --dereference-command-line
    (-H), --dereference (-L), or --dereference-command-line-symlink-to-dir
    options are specified.




    on https://www.gnu.org/software/coreutils/manual/coreutils.html#ls-invocation






    share|improve this answer



























      0














      Just to add how I found this info. As indicated at the bottom of man ls:




      Full documentation at: https://www.gnu.org/software/coreutils/ls
      or available locally via: info '(coreutils) ls invocation'




      Following this, we see




      ‘-F’ ‘--classify’ ‘--indicator-style=classify’ Append a character to
      each file name indicating the file type. Also, for regular files that
      are executable, append ‘*’. The file type indicators are ‘/’ for
      directories, ‘@’ for symbolic links, ‘|’ for FIFOs, ‘=’ for sockets,
      ‘>’ for doors, and nothing for regular files. Do not follow symbolic
      links listed on the command line unless the --dereference-command-line
      (-H), --dereference (-L), or --dereference-command-line-symlink-to-dir
      options are specified.




      on https://www.gnu.org/software/coreutils/manual/coreutils.html#ls-invocation






      share|improve this answer

























        0












        0








        0







        Just to add how I found this info. As indicated at the bottom of man ls:




        Full documentation at: https://www.gnu.org/software/coreutils/ls
        or available locally via: info '(coreutils) ls invocation'




        Following this, we see




        ‘-F’ ‘--classify’ ‘--indicator-style=classify’ Append a character to
        each file name indicating the file type. Also, for regular files that
        are executable, append ‘*’. The file type indicators are ‘/’ for
        directories, ‘@’ for symbolic links, ‘|’ for FIFOs, ‘=’ for sockets,
        ‘>’ for doors, and nothing for regular files. Do not follow symbolic
        links listed on the command line unless the --dereference-command-line
        (-H), --dereference (-L), or --dereference-command-line-symlink-to-dir
        options are specified.




        on https://www.gnu.org/software/coreutils/manual/coreutils.html#ls-invocation






        share|improve this answer













        Just to add how I found this info. As indicated at the bottom of man ls:




        Full documentation at: https://www.gnu.org/software/coreutils/ls
        or available locally via: info '(coreutils) ls invocation'




        Following this, we see




        ‘-F’ ‘--classify’ ‘--indicator-style=classify’ Append a character to
        each file name indicating the file type. Also, for regular files that
        are executable, append ‘*’. The file type indicators are ‘/’ for
        directories, ‘@’ for symbolic links, ‘|’ for FIFOs, ‘=’ for sockets,
        ‘>’ for doors, and nothing for regular files. Do not follow symbolic
        links listed on the command line unless the --dereference-command-line
        (-H), --dereference (-L), or --dereference-command-line-symlink-to-dir
        options are specified.




        on https://www.gnu.org/software/coreutils/manual/coreutils.html#ls-invocation







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 48 mins ago









        flow2kflow2k

        19712




        19712



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f82357%2fwhat-do-the-symbols-displayed-by-ls-f-mean%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            -ls

            Popular posts from this blog

            Word for a person who has no opinion about whether god existsWord for having a definite opinion while simultaneously withholding judgment?What's the opposite of “newcomer? Is ”veteran" OK?What do you call an “atheist” who might believe in an afterlife?What's a word for someone who wants to voice opinions but not have them challenged?Word for someone who dismisses contrary opinions as irrational?Somone who thinks they are overly special/out of the ordinaryIs there a word, phrase or idiom for “a person who is incapable of thinking about the future”?The belief that a god is human-likeA word for a non-famous person/thing you have heard a lot aboutAdjective for a person who enjoys taking care of their appearance

            2017 IndyCar Series Contents Series news Teams and drivers Schedule Season summary Footnotes References External links Navigation menu"INDYCAR: Initial 2018 bodywork concepts unveiled"the original"IndyCar confirms switch to Performance Friction brakes in 2017""AJ Foyt Racing will switch to Chevy"the original"Carlos Munoz, Conor Daly will drive for AJ Foyt Racing""Zach Veach's Indy 500 Debut Confirmed with Foyt""No mass exodus from Honda after Ganassi switch""Ex-F1 driver Sato joins Andretti Autosport for 2017 IndyCar season""IndyCar's Ryan Hunter-Reay, sponsor DHL paired through 2020""hhgregg and Andretti Autosport announce partnership for key races in 2016""INDYCAR: Rossi re-signs with Andretti"the original"McLaren Formula 1 - Fernando Alonso to race at Indy 500 with McLaren, Honda and Andretti Autosport""Shank will finally take part in Indy 500 with Harvey, Andretti | MotorSportsTalk""Andretti adds Jack Harvey to Indy 500 field""Ganassi switches to Honda power for 2017""INDYCAR: Chilton returns to Ganassi"the original"IndyCar silly season: Who's going where in 2017?""INDYCAR: Kanaan, NTT Data return to Ganassi"the original"Kimball to remain at Ganassi for 2017""Coyne confirms Bourdais for 2017 IndyCar season""Davison to sub for Bourdais in Indy 500"the original"Gutierrez confirmed for Detroit IndyCar debut""Gutierrez returns with Coyne for rest of 2017 season""Vautier to drive for Coyne at Texas"the original"INDYCAR: Coyne confirms Jones for 2017"the original"Pippa Mann returns to Coyne for Indy 500""Karam, Dreyer & Reinbold teaming up again for Indianapolis 500""Pigot to return to Ed Carpenter Racing""Hildebrand confirmed as full-time Ed Carpenter driver""Veach to replace injured Hildebrand at Barber"the originalNew Team Harding Racing Enters Chaves for 101st Indianapolis 500"Juncos Racing Announces Entry in 101st Running of the Indianapolis 500 :: Juncos Racing""Juncos confirms Pigot for Indy 500""Saavedra confirmed in Juncos' second 500 entry"the original"Lazier confirms Indy 500 run after son's USF2000 debut"the original"Claman DeMelo to race for RLLR at Sonoma"the original"Rahal signs Servia and ace engineer for 2017""IndyCar: Aleshin returns with Schmidt"the original"Aleshin replaced by Saavedra for Toronto""Jack Harvey will pilot SPM No. 7 car at Watkins Glen, Sonoma""Jay Howard confirmed in Tony Stewart's supported SPM Indy entry""INDYCAR: Newgarden to wave the flag at Penske"the original"Pagenaud opts for No. 1 in 2017"the original"Penske confirms Newgarden for 2017""Montoya to stay with Team Penske in 2017""Target leaving IndyCar after 27 seasons with Chip Ganassi""Cavin: IndyCar could see complete driver/team shakeup in 2017""End of the road for KV Racing?""KV Racing confirms closure, equipment sold to Juncos""Juncos confirms IndyCar Series entry"the original"Juncos readies IndyCar program, aims for '17 500"the original"Harding Racing to add Texas, Pocono to schedule"the original"Sato signs with Andretti Autosport for 2017""INDYCAR: Aleshin in Doubt at SPM"the original"Long Beach notebook: JR Hildebrand breaks hand""Hildebrand cleared to return at Phoenix"the original"Bourdais to undergo surgery on multiple fractures""Aleshin loses Schmidt Peterson IndyCar ride""Saavedra in at SPM for Pocono, Gateway"the original"Bourdais to make return at Gateway"the original"The IndyCar Grand Prix no longer is sponsored by Angie's List""2017 IndyCar Series rulebook""2017 Verizon IndyCar Series Official Rulebook"Official websiteeeeee

            What was this official D&D 3.5e Lovecraft-flavored rulebook?What was this set of RPG tools called?As a first-time DM should I let my players play complex character classes and roles?Nymph's Kiss and the RelationshipWhat was the name of this Cleric Prestige Class that shapes metal with its bare hands?Are the 3.5e Dragonlance books third party or official works?What's up with the domain Vile Darkness?What was this 80s book about RPGs?What was the name of this Werewolf band?What book had Rituals to “upgrade” animal companions to keep them viable at higher levels?What was this RPG that had rules for player-owned businesses?