Joshua Isom wrote:
> But google and other search engines treats words([A-Za-z0-9])
> starting with - as meaning exclude results with this, even when
> obvious it's about unix commands. It can be rather annoying
> when searching for help.
This comment suggests a new translation of GNU: Google's
On Sat, 02 Mar 2013 23:45:30 +0100, Julian H. Stacey wrote:
> Hi,
> Reference:
> > From: Jos Chrispijn
> > Date: Sat, 02 Mar 2013 18:44:22 +0100
> > Message-id: <51323a76.2040...@webrz.net>
>
> Jos Chrispijn wrote:
>
On 3/2/2013 8:27 PM, Gary Kline wrote:
On Sat, Mar 02, 2013 at 07:43:50PM -0600, Joshua Isom wrote:
On 3/2/2013 2:43 PM, David Tilbrook wrote:
The problem (and its solution) have been
raised for at least 39 years.
But google and other search engines treats words([A-Za-z0-9])
starting with - a
On Sat, 2 Mar 2013 18:27:15 -0800, Gary Kline wrote:
> On Sat, Mar 02, 2013 at 07:43:50PM -0600, Joshua Isom wrote:
> > On 3/2/2013 2:43 PM, David Tilbrook wrote:
> > >The problem (and its solution) have been
> > >raised for at least 39 years.
> >
> > But google and other search engines treats wor
On Sat, Mar 02, 2013 at 07:43:50PM -0600, Joshua Isom wrote:
> On 3/2/2013 2:43 PM, David Tilbrook wrote:
> >The problem (and its solution) have been
> >raised for at least 39 years.
>
> But google and other search engines treats words([A-Za-z0-9])
> starting with - as meaning exclude results with
On 3/2/2013 2:43 PM, David Tilbrook wrote:
The problem (and its solution) have been
raised for at least 39 years.
But google and other search engines treats words([A-Za-z0-9]) starting
with - as meaning exclude results with this, even when obvious it's
about unix commands. It can be rather a
On Sat, 2 Mar 2013, David Tilbrook wrote:
Wjy are we syill having this conversation?
The problem (and its solution) have been
raised for at least 39 years.
To specify a file, directory, device, whatever,
whose leaf name begins with a `-', name it using
a leading `./' as in:
whatever ./-
Hi,
Reference:
> From: Jos Chrispijn
> Date: Sat, 02 Mar 2013 18:44:22 +0100
> Message-id: <51323a76.2040...@webrz.net>
Jos Chrispijn wrote:
>
> Teske, Devin:
> > rm -R -- -S
> >
> > The "--" tells it "here's
Wjy are we syill having this conversation?
The problem (and its solution) have been
raised for at least 39 years.
To specify a file, directory, device, whatever,
whose leaf name begins with a `-', name it using
a leading `./' as in:
whatever ./-S
That will work for all programs, even those
Teske, Devin:
rm -R -- -S
The "--" tells it "here's the end of the options, here come the
file/directories"
Almost:
rm -R -- -S;
did it, thanks very much for you help!
BR,
Jos Chrispijn
___
freebsd-questions@free
Teske, Devin:
rm -R -- -S
The "--" tells it "here's the end of the options, here come the
file/directories"
Almost : rm -R -- -S; did it, thanks very much!
BR,
Jos Chrispijn.
___
freebsd-questions@free
Ralf Mardorf:
rm -R "-S\;" rm -R ?S?
rm: illegal option -- S
usage: rm [-f | -i] [-dIPRrvW] file ...
unlink file
regards,
Jos Chrispijn
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listin
On Sat, 2013-03-02 at 16:50 +0100, Jos Chrispijn wrote:
> I made a folder called -S;
>
> how can I remove that again?
>
> did a rm -R '-S;' but that doesn't work (...).
rm -R "-S\;"
rm -R ?S?
___
freebsd
rm -R -- -S
The "--" tells it "here's the end of the options, here come the
file/directories"
--
Devin
From: owner-freebsd-questi...@freebsd.org [owner-freebsd-questi...@freebsd.org]
on behalf of Jos Chrispijn [ker...@webrz.n
I made a folder called -S;
how can I remove that again?
did a rm -R '-S;' but that doesn't work (...).
thanks for your advise,
Jos Chrispijn
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
>
>
>
> Feeding pkgdb/pkg_which a port creates a directory for that port
> in /var/db/pkg.
>
> It then returned a question mark, which kind of sucked, silence being
> golden in unix, but I had an entry for openmpi appear in /var/db/pkg
>
> Is this really just meaningless grasping at straws?
On Thu, 2007-10-18 at 20:11 +0100, RW wrote:
> On Thu, 18 Oct 2007 12:51:33 -0600
> James <[EMAIL PROTECTED]> wrote:
>
> > > It depends what state the ports were in at the time of the
> > > accident. If you haven't run a leaf-cutting program recently you
> > > may have old dependencies and tools
On Thu, 18 Oct 2007 12:51:33 -0600
James <[EMAIL PROTECTED]> wrote:
> > It depends what state the ports were in at the time of the
> > accident. If you haven't run a leaf-cutting program recently you
> > may have old dependencies and tools that have become leaves - they
> > may take years to show-
> It depends what state the ports were in at the time of the accident. If
> you haven't run a leaf-cutting program recently you may have old
> dependencies and tools that have become leaves - they may take years
> to show-up.
>
> ___
> freebsd-questions@
> > > > On Thu, 11 Oct 2007 14:26:19 -0600
> > > >
> > > > James <[EMAIL PROTECTED]> wrote:
> > > > > Call it a moment of sheer stupidity, call it a misremembering,
> > > > > call it whatever you want (and I imagine I'll hear a fe
gt; wrote:
> > > > Call it a moment of sheer stupidity, call it a misremembering,
> > > > call it whatever you want (and I imagine I'll hear a few
> > > > different ones), but I just did an rm -r /var/lib/pkg.
> > > >
> > > > Before I
membering,
> > > call it whatever you want (and I imagine I'll hear a few
> > > different ones), but I just did an rm -r /var/lib/pkg.
> > >
> > > Before I type anything to damage things further, does anyone have
> > > any suggestions as to how to reco
On Friday 12 October 2007 22:19:41 RW wrote:
> On Thu, 11 Oct 2007 14:26:19 -0600
>
> James <[EMAIL PROTECTED]> wrote:
> > Call it a moment of sheer stupidity, call it a misremembering, call it
> > whatever you want (and I imagine I'll hear a few different ones),
On Thu, 11 Oct 2007 14:26:19 -0600
James <[EMAIL PROTECTED]> wrote:
> Call it a moment of sheer stupidity, call it a misremembering, call it
> whatever you want (and I imagine I'll hear a few different ones), but
> I just did an rm -r /var/lib/pkg.
>
> Before I type
On Friday 12 October 2007 00:39:27 James wrote:
> On Thu, 2007-10-11 at 18:14 -0400, Robert Huff wrote:
> > James writes:
> > > What has happened, though, is I've never ran rm in
> > > /usr/ports/distfiles. I'm going to think for a little bit about
> > > a script that can move through /usr/port
On Oct 12, 2007, at 11:57 AM, James wrote:
This isn't quite as simple as I'd hoped it'd be to fix. Here's my
findings thus far (I haven't started writing my script yet, but I will
later today):
1. /usr/ports/distfiles contains everything I need
2. distfiles contains several versions of some p
On Fri, Oct 12, 2007 at 10:57:59AM -0600, James wrote:
>
> This isn't quite as simple as I'd hoped it'd be to fix. Here's my
> findings thus far (I haven't started writing my script yet, but I will
> later today):
>
> 1. /usr/ports/distfiles contains everything I need
> 2. distfiles contains seve
On Friday 12 October 2007 18:57:59 James wrote:
> This isn't quite as simple as I'd hoped it'd be to fix. Here's my
> findings thus far (I haven't started writing my script yet, but I will
> later today):
>
> 1. /usr/ports/distfiles contains everything I need
> 2. distfiles contains several version
This isn't quite as simple as I'd hoped it'd be to fix. Here's my
findings thus far (I haven't started writing my script yet, but I will
later today):
1. /usr/ports/distfiles contains everything I need
2. distfiles contains several versions of some packages, but that's
pretty trivial to resolve.
On Oct 11, 2007, at 5:39 PM, James wrote:
On Thu, 2007-10-11 at 18:14 -0400, Robert Huff wrote:
James writes:
What has happened, though, is I've never ran rm in
/usr/ports/distfiles. I'm going to think for a little bit about
a script that can move through /usr/ports/distfiles and reinst
On Thu, 2007-10-11 at 18:14 -0400, Robert Huff wrote:
> James writes:
>
> > What has happened, though, is I've never ran rm in
> > /usr/ports/distfiles. I'm going to think for a little bit about
> > a script that can move through /usr/ports/distfiles and reinstall
> > everything that exists
On Thursday 11 October 2007 23:29:05 James wrote:
> What has happened, though, is I've never ran rm in /usr/ports/distfiles.
> I'm going to think for a little bit about a script that can move
> through /usr/ports/distfiles and reinstall everything that exists there.
Well, if you figure out what p
James writes:
> What has happened, though, is I've never ran rm in
> /usr/ports/distfiles. I'm going to think for a little bit about
> a script that can move through /usr/ports/distfiles and reinstall
> everything that exists there.
Having been in almost the identical situation for
bering, call it
> > > > whatever you want (and I imagine I'll hear a few different ones), but I
> > > > just did an rm -r /var/lib/pkg.
> > > >
> > > > Before I type anything to damage things further, does anyone have any
> > > > sugg
James wrote:
Yes, you're right. On all counts, I'm afraid.
But, yes, ultimately. And the more I'm reading man pages, the more I'm
thinking that the only solution here will be to reinstall everything. I
was wondering if portmaster or something similar might be able to solve
this, but it looks
w different ones), but I
> > > just did an rm -r /var/lib/pkg.
> > >
> > > Before I type anything to damage things further, does anyone have any
> > > suggestions as to how to recover from this? I have other FreeBSD boxes
> > > available to me, none
On Thu, 2007-10-11 at 15:53 -0500, Kevin Kinsey wrote:
> James wrote:
> > Call it a moment of sheer stupidity, call it a misremembering, call it
> > whatever you want (and I imagine I'll hear a few different ones), but I
> > just did an rm -r /var/lib/pkg.
> >
James wrote:
Call it a moment of sheer stupidity, call it a misremembering, call it
whatever you want (and I imagine I'll hear a few different ones), but I
just did an rm -r /var/lib/pkg.
Before I type anything to damage things further, does anyone have any
suggestions as to how to recover
Call it a moment of sheer stupidity, call it a misremembering, call it
whatever you want (and I imagine I'll hear a few different ones), but I
just did an rm -r /var/lib/pkg.
Before I type anything to damage things further, does anyone have any
suggestions as to how to recover from this? I
"unrm" and "lazarus".
From: Ian Lord <[EMAIL PROTECTED]>
To: freebsd-questions@freebsd.org
Subject: Re: urgent: I just rm-r a directory
Date: Mon, 07 Aug 2006 08:44:48 -0400
Thanks to all how had replyed to me :)
I'm from a dos/windows world so I was hoping for
t;
To: freebsd-questions@freebsd.org
Subject: Re: urgent: I just rm-r a directory
Date: Mon, 07 Aug 2006 08:44:48 -0400
Thanks to all how had replyed to me :)
I'm from a dos/windows world so I was hoping for an "undelete utility" On
fat partitions data is not deleted, it's just fl
ore our tapes offsite
to recover :)
Thanks to all
At 20:34 2006-08-06, jan gestre wrote:
On 8/7/06, Ian Lord <[EMAIL PROTECTED]> wrote:
I did a rm-r by mistake on a directory... any way to recover ?
Help please :(
_
if you don't have back ups of the directory concerned, i
On 8/7/06, Ian Lord <[EMAIL PROTECTED]> wrote:
I did a rm-r by mistake on a directory... any way to recover ?
Help please :(
_
if you don't have back ups of the directory concerned, i'm sorry to inform
you that you won't be able to recover it. a word of advise, at leas
Ian Lord <[EMAIL PROTECTED]> wrote:
> I did a rm-r by mistake on a directory... any way to recover ?
As has already been said, it's extremely difficult to recover an
rmed directory.
If you don't have backups, and the data is _very_ importation, immediately
shut down the
On Sunday 06 August 2006 18:02, Ian Lord wrote:
> I did a rm-r by mistake on a directory... any way to recover ?
>
> Help please :(
Restore from your backups :)
Seriously, if you don't have backups, your chances of recovery are near 0.
Nicolas.
--
FreeBSD 7.0-CURRENT #11: Sun J
I did a rm-r by mistake on a directory... any way to recover ?
Help please :(
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Greetings,
I have a Dell PowerEdge 2650 with one 2.8G Xeon CPU and 2G RAM running
5.1-RELEASE. This machine is a dedicated NFS server. Everything on the
system is "default": no custom kernel, no custom filesystem options, no
tweaking.
Earlier today I ran "rm -R" on a
47 matches
Mail list logo
