[Cialug] Introduction

[Sean McClanahan]

Yep, I missed the # at the beginning of the line.  Won't happen again.
:-)

Sean


-----Original Message-----
From: cialug-bounces at cialug.org [mailto:cialug-bounces at cialug.org] On
Behalf Of Kendall Bailey
Sent: Friday, July 06, 2007 2:52 PM
To: Central Iowa Linux Users Group
Subject: Re: [Cialug] Introduction

I'm guessing you didn't run updatedb as root.  The "#" is typically
the prompt you see when logged in as root, so when you see a command
line like the one given in this case

# updatedb; locate firewalk | xargs file | grep executable

it's a hint to run it as root.  Also, the "sbin" directory is
typically in root's PATH already.  Executables and scripts installed
there usually have system administration purposes.  That doesn't mean
a non-privileged user can't run them at all, but there's things that
only root can do.

To add a path to your PATH environment variable, in bash, or ksh you can

$ PATH="${PATH}:/add/a/path/here"

With csh, or tcsh the syntax is different, see setenv.

good luck.

On 7/6/07, Sean McClanahan <sean.mcclanahan at westecnow.com> wrote:
> That's what I thought too - that installing the RPM would do the
trick,
> especially if it is an FC7 RPM, which it is.
>
> So I ran the command you suggested.  The first thing that happened was
> updatedb complaining that it cannot open a temporary file for
> /var/lib/mlocate/mlocate.db
>
> Then, on the next line, I got /usr/sbin/firewalk:   ELF 32-bit LSB
> executable, Intel 80386, version 1 (SYSV), dynamically linked (uses
> shared libs), for GNU/Linux 2.6.9, stripped
>
> How does one go about changing the path in FC?  When I type $PATH, I
can
> see what my path is; Firewalk is indeed an executable in /usr/sbin, I
> can see that when I look at the file system.
>
> Also, I am one who typically doesn't want to just be shown how to do
> something.  I want to learn along the way, and hopefully someday, be
> able to pass along that knowledge to someone else.  That's part of why
I
> wanted to find a local group to get involved with, so I can learn.  I
> know there are man pages out the wazoo out there, but I tend to learn
> more when doing the hands on aspect than just reading about it.  Heck,
> that's how I learned a lot of what I know already.  But I also believe
> in giving back the knowledge that I have gained.
>
> I guess what I'm saying in the above paragraph is that I'm not trying
to
> get on here and leech out information, then leave.  If I could make
sure
> that I understand Linux well enough to be comfortable with it, and I
can
> start to figure out stumbling blocks like I already can do with a
> Windows box, I see no reason to not install Linux for core services
here
> too - at least for things like file servers.  I know I can't make it
> into an AD DC or GC, but I bet Linux would work great for a file
server,
> among other things.
>
> Sean
>
>
> -----Original Message-----
> From: cialug-bounces at cialug.org [mailto:cialug-bounces at cialug.org] On
> Behalf Of Todd Walton
> Sent: Friday, July 06, 2007 12:45 PM
> To: Central Iowa Linux Users Group
> Subject: Re: [Cialug] Introduction
>
> On 7/6/07, Sean McClanahan <sean.mcclanahan at westecnow.com> wrote:
> > Hmmm...  an example of some difficulty that I've had is with the
> program
> > Firewalk.  I was exposed to it in a SANS class, and it seems to be
an
> > interesting program.  So, I downloaded the RPM and it looked like
the
> > program installed itself OK - but I cannot seem to get it to run.
>
> So, you've found how to run it?  The command is there?  What messages
> does it give you?
>
> I tried to look up Firewalk on the Internet, but nothing has any good
> information on it.  The freshmeat page is closed.  The home page is
> down.
>
> > I would say that it looks like there is no path to the executable
>
> Oh, I see.  Try this:
>
> # updatedb; locate firewalk | xargs file | grep executable
>
> That should update your 'locate' database, then find all files that
> have "firewalk" somewhere in the pathname, then determine the file
> type of each of those files.  Any file type listings that read
> something about "executable" will print out to your screen.  I suppose
> that's a start.  You'd want to make sure that the executable is in
> your $PATH.
>
> But without Internet references for the program, it's hard to say
> anything beyond that.  For example, maybe it's not "executable"
> according to 'file', but rather "script".
>
> I don't know.  One would think that installing it by RPM would make
> everything work just fine.
>
> -todd
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>
>
> www.westecnow.com
>
>  _________________________________________________
>
> NOTICE BY WESTEC INTERACTIVE
>
> This message, as well as any attached document, contains information
from Westec InterActive that is proprietary, confidential and/or
privileged. The information is intended only for the use of the
addressee named above. If you are not the intended recipient, you are
hereby notified that any disclosure, copying, distribution or the taking
of any action in reliance on the contents of this message or its
attachments is strictly prohibited, and may be unlawful. If you have
received this message in error, please delete all electronic copies of
this message and its attachments, if any, destroy any hard copies you
may have created, without disclosing the contents, and notify the sender
immediately. Unintended transmission does not constitute waiver of any
privilege.
>
> Unless expressly stated otherwise, nothing contained in this message
should be construed as a digital or electronic signature, nor is it
intended to reflect an intention to make an agreement by electronic
means.
>
>
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>
_______________________________________________
Cialug mailing list
Cialug at cialug.org
http://cialug.org/mailman/listinfo/cialug