Hunting Forum

Peter da Silva: No, try "rm -rf /" Dave Aronson: As your life flashes before your eyes, in the unit of time known as an ohnosecond....

   I spent a LOT of years as a software engineer. Started on Jes 3 systems and moved on to UNIX/AIX/SunOS/HP and then to Linux as they evolved.  As such, I always had root auth to my systems.   Shot myself in the foot many times over the years with an rm -fr * sequence!  Thank gawd we had an excellent backup strategy!    (yeah, of course I disabled the safe version of rm on my system - )

Thanks for the chuckle.

Posted By Steve on 08 Oct 2012 03:12 PM

Peter da Silva: No, try "rm -rf /" Dave Aronson: As your life flashes before your eyes, in the unit of time known as an ohnosecond....

   I spent a LOT of years as a software engineer. Started on Jes 3 systems and moved on to UNIX/AIX/SunOS/HP and then to Linux as they evolved.  As such, I always had root auth to my systems.   Shot myself in the foot many times over the years with an rm -fr * sequence!  Thank gawd we had an excellent backup strategy!    (yeah, of course I disabled the safe version of rm on my system - )

Thanks for the chuckle.

That's why you never, ever run as root unless you absolutely require root privs.....   I always set myself up as wheel (or system,
on some Unix variants) so I can do most things...and if I really must have root, I'll just su or su -.

That, btw, is one of the problems I have with typing here....I keep wanting to use ESC to go to command mode, then b0$hjkl
(etc.) for moving the cursor, and using TAB to indent by my tabskip (set to 3 normally).  :-)   That, or I try to use the abbrevs
I have in my ~/.vimrc .....and for a second, wonder why they're not working.  :-)

Later,
   --jim

Damn, ya'll may as well be talking in Arabic or Spic cause I'll be damned if I know anything that was posted in those last two posts!!!!!!!!!!!!!!!!!

   Sorry rt, we kinda are.   It's AIX/UNIX/Linux speak - it's a totally different operating system than WinBLOWS.     The    rm -r *   command says to immediately remove all files, sub-directories and their contents beginning with the current directory. Problem is; you'd BETTER make sure of the directory you're in! Once you hit enter, it's too late because as Murpys Law would dictate, it ALWAYS starts with the most important files and directories first.


We now return you to your regularly scheduled programming...

Posted By Steve on 09 Oct 2012 06:16 PM
   Sorry rt, we kinda are.   It's AIX/UNIX/Linux speak - it's a totally different operating system than WinBLOWS.     The    rm -r *   command says to immediately remove all files, sub-directories and their contents beginning with the current directory. Problem is; you'd BETTER make sure of the directory you're in! Once you hit enter, it's too late because as Murpys Law would dictate, it ALWAYS starts with the most important files and directories first.


We now return you to your regularly scheduled programming...

Not quite.....

First, WinBlows is one name, but my favorite is Windoze.   Windoze comes from Mickeysoft, aka M$.  As for rm -rf, its risk
goes even farther.  Let's say you're in the very top directory (root, or /).   You mean to remove some temporary files (*.tmp).
But you acciidentally tap the space bar and don't notice it, and you enter "rm -rf * .tmp".  The first indication that you've
completely fscked[1], is the following error message:

/bin/rm:  file busy     (meaning /bin/rm can't remove itself because it's in use ... removing the rest of the system).

Thus the term "ohnosecond"  used in a very old post from the Usenet newsgroup alt.sysadmin.recovery.

[1] fsck is file system check ... kind of like M$'s chkdsk, except far more dangerous if you don't know what you're doing,
     and is not pronounced as it's spelled ....... to know how it's pronounced, you need to change the second letter.  This
     is explained by DMR (Dennis M. Ritchie, one of the creators of Unix) in the following quote:

DMR:  So fsck was originally called something else.
Q: So what was it called?
DMR:  Well, the second letter was different.
      --Dennis M. Ritchie, Usenix, June 1998.

Later,
   --jim

PS:  if you use fsck, and don't know what you're doing, its pronunciation describes what it can (and probably will) do
to your filesystem (similar to a hard drive partition on an M$ system, at least, at the overall concept level).

NOW we return you to your regularly scheduled programming (well, not programming, as such, but...)......

Check out the two images (attached).  This is a spot I found in a different management area (Jackson South) that, if I'm reading
the map right, looks promising.  Two creeks intersect between  two areas that go from ground level to about 45 to 50 feet in
a small area on all sides (it makes a + type intersection).  I've picked out a spot (see the zoomed-in image) in one of
the corners that, again, if I'm reading this right, which I THINK will be a great (potential) spot; at the very least, I'm thinking
it's a good spot to check before the deer season starts on 22Nov (through 25Nov for this early bit).

Does anyone think I'm A) right to think it's a good place to check, or B) completely wrong ?    Btw, this editor SAYS that the
two image files are attached.  If not, I've uploaded them at http://www.jstrack.org/imagery/     (the ones attached may also
not be full-sized, either, but then, neither are the two jpegs on my JStrack site...the REAL full-sized images are png files I
converted from the tiff images, but the jpegs on my site are probably bigger, based on file size, than the ones here).

Thanks,
   ---jim

Where is the question about hunting land features on a topo map?  Either I'm more  iliterate on this thing than I thought.  Or, I totally missed the question with all the tec talk.

Posted By bigrig on 20 Oct 2012 12:21 PM
Where is the question about hunting land features on a topo map?  Either I'm more  iliterate on this thing than I thought.  Or, I totally missed the question with all the tec talk.

The question was what does "submerged wooded marsh or swamp" mean?  But now, having been out there last Tuesday and
Wednesday, I know what it means:  it means it's dry land with a creek running through it, and a *LOT* of deer tracks and a
BIG pile of droppings on the road.    As for the tracks, they were all over the road (red clay) and the sides of the road (beach
sand), and there were tiny tracks (clearly from multiple fawns), medium-sized tracks (does or small bucks) and a set of HUGE
tracks, some of which were also very deep (one, in particular, was about 2 inches deep in sand).  I checked out three other
areas (one based on looking over the three maps---the Eglin Range map you get when you buy your permit, a topo map, and
Google Earth (terrain map).  The other two spots were ones I just passed while driving by them and checked them out just
because.....  One of those last two was too close to the road (minimum 200 yards) at its most distant point, so it was out.
The other spontaneous one had a closed gate (temporarily off-limits), but I checked out the area before the gate, and it
had three piles of large deer droppings.  The other area I'd intended to check (which is also where I got my little Honda
Civic Si stuck in sand on Tuesday---it was tightly packed down and driving on it was easy...until it wasn't) had tracks
EVERYWHERE, again, all sizes from very small to huge and very deep.  And at the entrance, there were acorns all over the
place on the ground.  That one opened up to a big, open field.

So basically, in this part of the Eglin AFB public land, every area I checked had abundant deer sign.  Oh, and for those who
aren't familiar with the beach sand in this area, NO tracks are going to last very long at all in that sand; the same is true
for the clay that makes up the two main roads I CAN drive on, where I saw lots of tracks at the first spot (the "swamp").
When the four-day early general gun season opens on 21Nov (it's the Early Archery season now), I'll be ready with
three different spots to hunt.  The plan is to rotate to the next spot after shooting anything at the current spot.  Between
that, and (during the longer general gun and late archery/muzzleloader seasons) hunting primarily on weekdays (when
most potential hunters are more likely to be at work), I'm hoping that the deer will feel less pressure on the weekdays.
That plan has, so far, been met with positive responses, so I think it'll help.  If not, oh well...no loss either way.  I'll
need the weekends to rest, either way.

Later,
   --jim

PS:  On Eglin, the daily limit for deer is two.  The season limit is NO LIMIT.  And for hogs, the only limit is take as many as
you possibly can, but only during the specific seasons when taking hogs is permitted.