Re: 'ddgr' cli for duckduckgo snafu?

[Michael Howard]

On 23/02/2021 08:13, Darac Marjal wrote:

On 22/02/2021 22:56, Bob Bernstein wrote:

On Mon, 22 Feb 2021, Nicholas Geovanis wrote:


I had the same experience. Gave up on duckduckgo but one time it came
thru
in a pinch.

Why give up on the search engine merely because a rogue util has gone
goofy?

I went looking for duckduckgo search syntax and found what I need,
which is not all that much.

https://help.duckduckgo.com/duckduckgo-help-pages/results/syntax/

WHAT I REALLY WANT TO KNOW is why every doctor's office in the country
wants me to show up fifteen minutes early. Why not just push all the
appts back fifteen minutes? Gets me there at the same time No good?
Hmm...those bastards are up to something.

How do you know that's not already the case? What's the difference
between "Your appointment is at 1430, please arrive 15 minutes early"
and "Your appointment is at 1415, there will be a fifteen minute waiting
period before the doctor sees you"? Nothing measurable.

You need to be there 15 minutes early so you get a good dose of whatever 
is hanging about!


WHAT I REALLY WANT TO KNOW is why anybody is making appointments at 
every doctor's office in the country?


--
Michael Howard.

Re: 'ddgr' cli for duckduckgo snafu?

[Darac Marjal]

On 22/02/2021 22:56, Bob Bernstein wrote:
> On Mon, 22 Feb 2021, Nicholas Geovanis wrote:
>
>> I had the same experience. Gave up on duckduckgo but one time it came
>> thru
>> in a pinch.
>
> Why give up on the search engine merely because a rogue util has gone
> goofy?
>
> I went looking for duckduckgo search syntax and found what I need,
> which is not all that much.
>
> https://help.duckduckgo.com/duckduckgo-help-pages/results/syntax/
>
> WHAT I REALLY WANT TO KNOW is why every doctor's office in the country
> wants me to show up fifteen minutes early. Why not just push all the
> appts back fifteen minutes? Gets me there at the same time No good?
> Hmm...those bastards are up to something.
How do you know that's not already the case? What's the difference
between "Your appointment is at 1430, please arrive 15 minutes early"
and "Your appointment is at 1415, there will be a fifteen minute waiting
period before the doctor sees you"? Nothing measurable.



OpenPGP_signature
Description: OpenPGP digital signature

Re: 'ddgr' cli for duckduckgo snafu?

[Michael Lange]

Hi,

On Mon, 22 Feb 2021 13:21:30 -0500 (EST)
Bob Bernstein  wrote:

> I have v. 1.6 via apt-get on an uptodate buster amd64 system.
> 
> Every attempt to run a search yields "No results," even if I 
> specify 'Boston Red Sox'.
> 
> Recommendations? Calm soothing thoughts?
> 
> Thank you.

just download version 1.9 from

https://packages.debian.org/bullseye/all/ddgr/download

and install it with

# dpkg -i  ddgr_1.9-2_all.deb

Here this seems to fix the issue.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

You humans have that emotional need to express gratitude.  "You're
welcome," I believe, is the correct response.
-- Spock, "Bread and Circuses", stardate 4041.2

Re: 'ddgr' cli for duckduckgo snafu?

[Nicholas Geovanis]

On Mon, Feb 22, 2021, 2:15 PM Bob Bernstein  wrote:

> On Mon, 22 Feb 2021, Nicholas Geovanis wrote:
>
> > I had the same experience. Gave up on duckduckgo but one time it came
> thru
> > in a pinch.
>
> Why give up on the search engine merely because a rogue util has
> gone goofy?


Because I had better alternatives that were more reliable, easier to use,
and IMO a little more aligned with unix-y linux-y "tradition".

Re: 'ddgr' cli for duckduckgo snafu?

[Bob Bernstein]

On Mon, 22 Feb 2021, Nicholas Geovanis wrote:

I had the same experience. Gave up on duckduckgo 
but one time it came thru

in a pinch.


Why give up on the search engine merely because a 
rogue util has gone goofy?


I went looking for duckduckgo search syntax and 
found what I need, which is not all that much.


https://help.duckduckgo.com/duckduckgo-help-pages/results/syntax/

WHAT I REALLY WANT TO KNOW is why every doctor's 
office in the country wants me to show up fifteen 
minutes early. Why not just push all the appts back 
fifteen minutes? Gets me there at the same time No 
good? Hmm...those bastards are up to something.


--
RSB

Re: 'ddgr' cli for duckduckgo snafu?

[Bob Bernstein]

On Mon, 22 Feb 2021, Nicholas Geovanis wrote:


I had the same experience. Gave up on duckduckgo but one time it came thru
in a pinch.


Why give up on the search engine merely because a rogue util has 
gone goofy?


I went looking for duckduckgo search syntax and found what I 
need, which is not all that much.


https://help.duckduckgo.com/duckduckgo-help-pages/results/syntax/

WHAT I REALLY WANT TO KNOW is why every doctor's office in the 
country wants me to show up fifteen minutes early. Why not just 
push all the appts back fifteen minutes? Gets me there at the 
same time No good? Hmm...those bastards are up to something.


--
RSB

Re: 'ddgr' cli for duckduckgo snafu?

[Darac Marjal]

On 22/02/2021 18:21, Bob Bernstein wrote:
> I have v. 1.6 via apt-get on an uptodate buster amd64 system.
>
> Every attempt to run a search yields "No results," even if I specify
> 'Boston Red Sox'.
>
> Recommendations? Calm soothing thoughts?

This sounds like https://github.com/jarun/ddgr/issues/119

The reporter there was using version 1.7 and was advised to upgrade to
version 1.9. I imagine the same problem manifests in version 1.6.


>
> Thank you.
>



OpenPGP_signature
Description: OpenPGP digital signature

Re: 'ddgr' cli for duckduckgo snafu?

[Nicholas Geovanis]

On Mon, Feb 22, 2021, 12:29 PM Bob Bernstein 
wrote:

> I have v. 1.6 via apt-get on an uptodate buster amd64 system.
>
> Every attempt to run a search yields "No results," even if I
> specify 'Boston Red Sox'.
>
> Recommendations? Calm soothing thoughts?
>

Is this soothing enough?
I had the same experience. Gave up on duckduckgo but one time it came thru
in a pinch.

Thank you.
>
> --
> RSB
>
>

'ddgr' cli for duckduckgo snafu?

[Bob Bernstein]

I have v. 1.6 via apt-get on an uptodate buster amd64 system.

Every attempt to run a search yields "No results," even if I 
specify 'Boston Red Sox'.


Recommendations? Calm soothing thoughts?

Thank you.

--
RSB

Re: thunderbird / icedove directory snafu ?

[Andrea Borgia]

Il 22/07/19 08:24, Andrea Borgia ha scritto:

Basically, the keep the TB version currently in testing happy, I need 
.icedove to be a symlink to .thunderbird even if I have completed the 
transition long ago.


Filed a bug, even if I found a solution:
933274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933274

thunderbird / icedove directory snafu ?

[Andrea Borgia]

Hi.

I am aware TB in Debian went through a rebranding to Icedove and back to 
the original name because... well, reasons.


The new userprofile directory is supposed to be .thunderbird and the 
system checks whether .icedove still exists and it's not a symlink: in 
this case it will abort and display an error.


Then I zap .icedove and start TB again. All is well. I shut it down and 
repeat: again the same error and program quits. It re-created .icedove!


Basically, the keep the TB version currently in testing happy, I need 
.icedove to be a symlink to .thunderbird even if I have completed the 
transition long ago.


Does it make sense?
Is it a (possibly known) bug?

Thanks,
Andrea.

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Patrick Bartek]

On Sun, 11 Aug 2013, Bob Proulx wrote:

> Patrick Bartek wrote:
> > > > have resulted in Gnome being install, too.  More or less.  So I
> > > > just did as root in /root a 'dpkg --download,' and then an
> > > > '--unpack' thinking that would uncompress the .deb file in /root
> > > > from which I would get the single svg file I needed, and then
> > > > just
> 
> The command you were looking for was 'dpkg-deb -x foo.deb foo-dir'.

Wish I had know about that a couple days ago.  Would have saved a lot
of time and reading and rereading.

> 
> > > > delete everything else.  Simple. Right?  Wrong. Now, I'm stuck
> > > > with about 4.5 megs of Gnome data, icons,
> > 
> > [snip]
> 
> > If I don't hear anything bad to the contrary in the next day or so,
> > I'm just going to use "--purge" to remove the package after creating
> > a copy of the file I need in a safe directory, then copy the copy
> > back after the purging.  Hopefully, it will work.
> 
> That is the correct thing to do.  The dpkg package manager knows the
> state of the installation.  Simply tell it to purge the package.
> Simple!  No need to look any further.
> 
>   dpkg --purge foo

Thanks for the info and the recommendations.

B


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130811191907.2b3a1...@debian7.boseck208.net

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Bob Proulx]

Patrick Bartek wrote:
> > > have resulted in Gnome being install, too.  More or less.  So I
> > > just did as root in /root a 'dpkg --download,' and then an
> > > '--unpack' thinking that would uncompress the .deb file in /root
> > > from which I would get the single svg file I needed, and then just

The command you were looking for was 'dpkg-deb -x foo.deb foo-dir'.

> > > delete everything else.  Simple. Right?  Wrong. Now, I'm stuck with
> > > about 4.5 megs of Gnome data, icons,
> 
> Fortunately --unpack just "installed" files to their appropriate
> directories, but didn't "trigger" or configure anything.  Not all that
> up on dpkg. Have always used apt-get.

After a dpkg --unpack the package will be listed like this:

  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version  Architecture Description
  +++-=---===
  iU  foo  2.5-1  amd64  Foo description

That says installed but unpacked.  A long dpkg --status would show:

  Status: install ok unpacked

> If I don't hear anything bad to the contrary in the next day or so, I'm
> just going to use "--purge" to remove the package after creating
> a copy of the file I need in a safe directory, then copy the copy back
> after the purging.  Hopefully, it will work.

That is the correct thing to do.  The dpkg package manager knows the
state of the installation.  Simply tell it to purge the package.
Simple!  No need to look any further.

  dpkg --purge foo

Bob


signature.asc
Description: Digital signature

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Patrick Bartek]

On Sun, 11 Aug 2013, Kailash wrote:

> On Sunday 11 August 2013 10:39 AM, Dom wrote:
> > On 11/08/13 03:43, Patrick Bartek wrote:
> >> On Sun, 11 Aug 2013, Chris Bannister wrote:
> >>
> >>> On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:
> >>>> Changing subject as suggested by Chris, and reposting original
> >>>> question.
> >>>> -
> >>>>
> >>>
> >>> Still an unhelpful question, esp when one knows the true meaning
> >>> of SNAFU
> >>>
> >>>> have resulted in Gnome being install, too.  More or less.  So I
> >>>> just did as root in /root a 'dpkg --download,' and then an
> >>>> '--unpack' thinking that would uncompress the .deb file in /root
> >>>> from which I would get the single svg file I needed, and then
> >>>> just delete everything else.  Simple. Right?  Wrong. Now, I'm
> >>>> stuck with about 4.5 megs of Gnome data, icons,
> >>>
> >>> AFAIU, a .deb file is just an 'ar' archive.
> >>>
> >>> As to how to recover after an unintentional unpack, ... dunno.
> >>> Hopefully someone on this list knows now that the subject explains
> >>> your predicament.
> >>
> >> Fortunately --unpack just "installed" files to their appropriate
> >> directories, but didn't "trigger" or configure anything.  Not all
> >> that up on dpkg. Have always used apt-get.
> >>
> >> If I don't hear anything bad to the contrary in the next day or
> >> so, I'm just going to use "--purge" to remove the package after
> >> creating a copy of the file I need in a safe directory, then copy
> >> the copy back after the purging.  Hopefully, it will work.
> >
> > Good luck with that, it sounds like it will work.
> >
> > Alternatively you can get a list of the files contained in the .deb
> > file using "dpkg -c debfile". With a little bit of wrangling that
> > will give you a list of files and directories to delete - although
> > you should only delete directories if they are empty.
> >
> Hi,
> 
> As per the man pages: http://linuxreviews.org/man/dpkg/
> 
> dpkg -s 
> 
> will give you the status of a package. As per the man file, it should 
> show the status as "unpacked".

Did this first thing after the "unpack."  Status is "installed"
however.  Don't know why.

> 
> dpkg --purge
> 
> should work as expected. To make sure that it does work as expected
> you can add add the --no-act option which will ensure that no changes
> are written.

Sometimes things don't work as expected, but "purge" seems the best
option to "clean" my system of the unneeded files/directories.

Yes, I was going to use "--no-act" (or similar) with verbose output to
check for problems before doing it for real.

> 
> caveat: Be sure to give --no-act before the action-parameter, or you 
> might end up with undesirable results. (e.g. dpkg --purge foo
> --no-act will first purge package foo and then try to purge package
> --no-act, even though you probably expected it to actually do nothing)

Thanks.  That point is made in the dpkg man file.  After the initial
unpack snafu, I read the man more thoroughly.

Thanks for your advice.

B


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130811093621.40d7d...@debian7.boseck208.net

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Patrick Bartek]

On Sun, 11 Aug 2013, Dom wrote:

> On 11/08/13 03:43, Patrick Bartek wrote:
> > On Sun, 11 Aug 2013, Chris Bannister wrote:
> >
> >> On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:
> >>> Changing subject as suggested by Chris, and reposting original
> >>> question.
> >>> -
> >>
> >> Still an unhelpful question, esp when one knows the true meaning of
> >> SNAFU
> >>
> >>> have resulted in Gnome being install, too.  More or less.  So I
> >>> just did as root in /root a 'dpkg --download,' and then an
> >>> '--unpack' thinking that would uncompress the .deb file in /root
> >>> from which I would get the single svg file I needed, and then just
> >>> delete everything else.  Simple. Right?  Wrong. Now, I'm stuck
> >>> with about 4.5 megs of Gnome data, icons,
> >>
> >> AFAIU, a .deb file is just an 'ar' archive.
> >>
> >> As to how to recover after an unintentional unpack, ... dunno.
> >> Hopefully someone on this list knows now that the subject explains
> >> your predicament.
> >
> > Fortunately --unpack just "installed" files to their appropriate
> > directories, but didn't "trigger" or configure anything.  Not all
> > that up on dpkg. Have always used apt-get.
> >
> > If I don't hear anything bad to the contrary in the next day or so,
> > I'm just going to use "--purge" to remove the package after creating
> > a copy of the file I need in a safe directory, then copy the copy
> > back after the purging.  Hopefully, it will work.
> 
> Good luck with that, it sounds like it will work.
> 
> Alternatively you can get a list of the files contained in the .deb
> file using "dpkg -c debfile". With a little bit of wrangling that
> will give you a list of files and directories to delete - although
> you should only delete directories if they are empty.

I did that.  Quite a long list.  Too long (and too much trouble) to
manually delete the files and/or directories.  Even thought of
building a script that used the list to automate it.  But one little
mistake and my system could be trashed.  Safer to just use --purge.

Thanks for your advice.

B


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130811091600.1574e...@debian7.boseck208.net

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Kailash]

On Sunday 11 August 2013 10:39 AM, Dom wrote:

On 11/08/13 03:43, Patrick Bartek wrote:

On Sun, 11 Aug 2013, Chris Bannister wrote:


On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:

Changing subject as suggested by Chris, and reposting original
question.
-



Still an unhelpful question, esp when one knows the true meaning of
SNAFU


have resulted in Gnome being install, too.  More or less.  So I
just did as root in /root a 'dpkg --download,' and then an
'--unpack' thinking that would uncompress the .deb file in /root
from which I would get the single svg file I needed, and then just
delete everything else.  Simple. Right?  Wrong. Now, I'm stuck with
about 4.5 megs of Gnome data, icons,


AFAIU, a .deb file is just an 'ar' archive.

As to how to recover after an unintentional unpack, ... dunno.
Hopefully someone on this list knows now that the subject explains
your predicament.


Fortunately --unpack just "installed" files to their appropriate
directories, but didn't "trigger" or configure anything.  Not all that
up on dpkg. Have always used apt-get.

If I don't hear anything bad to the contrary in the next day or so, I'm
just going to use "--purge" to remove the package after creating
a copy of the file I need in a safe directory, then copy the copy back
after the purging.  Hopefully, it will work.


Good luck with that, it sounds like it will work.

Alternatively you can get a list of the files contained in the .deb file
using "dpkg -c debfile". With a little bit of wrangling that will give
you a list of files and directories to delete - although you should only
delete directories if they are empty.


Hi,

As per the man pages: http://linuxreviews.org/man/dpkg/

dpkg -s 

will give you the status of a package. As per the man file, it should 
show the status as "unpacked".


dpkg --purge

should work as expected. To make sure that it does work as expected you 
can add add the --no-act option which will ensure that no changes are 
written.


caveat: Be sure to give --no-act before the action-parameter, or you 
might end up with undesirable results. (e.g. dpkg --purge foo --no-act 
will first purge package foo and then try to purge package --no-act, 
even though you probably expected it to actually do nothing)


Sincerely,
Kailash


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/5207863f.4060...@gmail.com

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Dom]

On 11/08/13 03:43, Patrick Bartek wrote:

On Sun, 11 Aug 2013, Chris Bannister wrote:


On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:

Changing subject as suggested by Chris, and reposting original
question.
-


Still an unhelpful question, esp when one knows the true meaning of
SNAFU


have resulted in Gnome being install, too.  More or less.  So I
just did as root in /root a 'dpkg --download,' and then an
'--unpack' thinking that would uncompress the .deb file in /root
from which I would get the single svg file I needed, and then just
delete everything else.  Simple. Right?  Wrong. Now, I'm stuck with
about 4.5 megs of Gnome data, icons,


AFAIU, a .deb file is just an 'ar' archive.

As to how to recover after an unintentional unpack, ... dunno.
Hopefully someone on this list knows now that the subject explains
your predicament.


Fortunately --unpack just "installed" files to their appropriate
directories, but didn't "trigger" or configure anything.  Not all that
up on dpkg. Have always used apt-get.

If I don't hear anything bad to the contrary in the next day or so, I'm
just going to use "--purge" to remove the package after creating
a copy of the file I need in a safe directory, then copy the copy back
after the purging.  Hopefully, it will work.


Good luck with that, it sounds like it will work.

Alternatively you can get a list of the files contained in the .deb file 
using "dpkg -c debfile". With a little bit of wrangling that will give 
you a list of files and directories to delete - although you should only 
delete directories if they are empty.


--
Dom


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/52071ca5.9070...@rpdom.net

Re: How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Patrick Bartek]

On Sun, 11 Aug 2013, Chris Bannister wrote:

> On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:
> > Changing subject as suggested by Chris, and reposting original
> > question.
> > -
> 
> Still an unhelpful question, esp when one knows the true meaning of
> SNAFU
> 
> > have resulted in Gnome being install, too.  More or less.  So I
> > just did as root in /root a 'dpkg --download,' and then an
> > '--unpack' thinking that would uncompress the .deb file in /root
> > from which I would get the single svg file I needed, and then just
> > delete everything else.  Simple. Right?  Wrong. Now, I'm stuck with
> > about 4.5 megs of Gnome data, icons,
> 
> AFAIU, a .deb file is just an 'ar' archive.
> 
> As to how to recover after an unintentional unpack, ... dunno.
> Hopefully someone on this list knows now that the subject explains
> your predicament.

Fortunately --unpack just "installed" files to their appropriate
directories, but didn't "trigger" or configure anything.  Not all that
up on dpkg. Have always used apt-get.

If I don't hear anything bad to the contrary in the next day or so, I'm
just going to use "--purge" to remove the package after creating
a copy of the file I need in a safe directory, then copy the copy back
after the purging.  Hopefully, it will work.

B


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130810194301.6ce2c...@debian7.boseck208.net

How to recover after unintentional 'dpkg --unpack' ? (was ... Re: Dpkg SNAFU was Re: Oops!)

[Chris Bannister]

On Sat, Aug 10, 2013 at 06:13:20PM +0100, Lisi Reisz wrote:
> Changing subject as suggested by Chris, and reposting original question.
> -

Still an unhelpful question, esp when one knows the true meaning of
SNAFU

> have resulted in Gnome being install, too.  More or less.  So I just did
> as root in /root a 'dpkg --download,' and then an '--unpack' thinking
> that would uncompress the .deb file in /root from which I would get the
> single svg file I needed, and then just delete everything else.  Simple.
> Right?  Wrong. Now, I'm stuck with about 4.5 megs of Gnome data, icons,

AFAIU, a .deb file is just an 'ar' archive.

As to how to recover after an unintentional unpack, ... dunno. Hopefully
someone on this list knows now that the subject explains your
predicament.

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130811012017.GB30256@tal

Dpkg SNAFU was Re: Oops!

[Lisi Reisz]

On Saturday 10 August 2013 18:08:53 Patrick Bartek wrote:
> On Sat, 10 Aug 2013, Chris Bannister wrote:
> > On Fri, Aug 09, 2013 at 06:56:56PM -0700, Patrick Bartek wrote:
> >
> > 
> >
> > Could you please provide a meaningful subject relating to your post.
>
> This is the second try replying to your post.  The first one failed to
> send. Don't know why.
>
> I did.  The original subject was "Oops! Dpkg SNAFU," but when I posted
> it only "Oops!" showed up.  Don't know why.

Changing subject as suggested by Chris, and reposting original question.
-

Finally got around to installing Pulseaudio-Equalizer on my 64-bit
Wheezy, which by the way is NOT in the Wheezy repos or backports.
However, was able to find a tar.gz file of it from the developer's site,
IIRC. It's been months since I downloaded it.  I've been busy. ;-)

In any case, here's the "problem:"  the equalizer needs
multimedia-volume-control.svg.  A search turned up it was part of
the gnome-control-center-data package.  Not having Gnome on this
system, just a window manager--Openbox--installing the package would
have resulted in Gnome being install, too.  More or less.  So I just did
as root in /root a 'dpkg --download,' and then an '--unpack' thinking
that would uncompress the .deb file in /root from which I would get the
single svg file I needed, and then just delete everything else.  Simple.
Right?  Wrong. Now, I'm stuck with about 4.5 megs of Gnome data, icons,
and config files scattered all over the system that I want to get rid
of before they cause any problems, if any.

My plan is to copy the file I need to someplace safe, then 'dpkg
--purge' the original package to clean the system of it, and copy the
file back to where it needs to be.  Sound okay?  Any expected gotchas?
Any better alternatives?

Thanks.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201308101813.20627.lisi.re...@gmail.com

Re: upgrade snafu

[Frank McCormick]

On 01/03/13 05:30 PM, Bob Proulx wrote:

Frank McCormick wrote:

localepurge: checking for existence of
/var/cache/localepurge/localelist... localepurge:
checking system for new locale ...
Segmentation fault E: Problem executing scripts DPkg::Post-Invoke
'if [ -x /usr/sbin/localepurge ] && [ $(ps w -p $PPID | egrep -c
'(remove|purge)') != 1 ]; then /usr/sbin/localepurge; else exit 0;
fi' E: Sub-process returned an error code debian:
/home/frank#
 Any ideas or should I just wait until it sorts itself out ?


A segmentation fault in a program you are writing is probably a bug in
your program.  A segmentation fault in a program that everyone runs
okay but you is probably not a software bug.  Instead it must be
hardware.





I would start by checking the disk drive for errors.  Run a SMART
drive selftest.


  I run Smartdrive on this machine all the time - the disk is clean.




I would carefully (beware and avoid the ESD zap) unsocket the ram and
resocket it.  I would carefully unplug and reattach every SATA cable.
Hopefully that will sort things out.  If not run memtest.  If no
answer there I would bisect the problem by splitting the ram or
swapping cpus with another.  I usually debug these things by swapping
components until I can isolate the problem to something specific.


  I have suspected this for a while - I get intermittent lockups where 
only a hard poweroff allows me to regain control. However they are few 
and far between.  Because the MB is so old (circa 2005) I am leaning 
towards replacing it and the ram..rather than spending upwards of $60 on it.



Thanks for the advice.
--
Cheers
Frank


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/51321f40.4010...@videotron.ca

Re: upgrade snafu

[Bob Proulx]

Frank McCormick wrote:
> localepurge: checking for existence of
> /var/cache/localepurge/localelist... localepurge:
> checking system for new locale ...
> Segmentation fault E: Problem executing scripts DPkg::Post-Invoke
> 'if [ -x /usr/sbin/localepurge ] && [ $(ps w -p $PPID | egrep -c
> '(remove|purge)') != 1 ]; then /usr/sbin/localepurge; else exit 0;
> fi' E: Sub-process returned an error code debian:
> /home/frank#
> Any ideas or should I just wait until it sorts itself out ?

A segmentation fault in a program you are writing is probably a bug in
your program.  A segmentation fault in a program that everyone runs
okay but you is probably not a software bug.  Instead it must be
hardware.

I suspect bad ram or a flakey socket connection.  Bad ram is a likely
suspect but it could be a problem SATA cable or other.  Think hardware
problem.  But probably just a component.  I have had both ram problems
and disk cable problems produce these types of issues.

I would start by checking the disk drive for errors.  Run a SMART
drive selftest.  These exact commands are not important but just to
show you the general idea.

  smartctl -l error /dev/sda
  smartctl -t short /dev/sda &&
sleep 120 &&
  smartctl -l selftest /dev/sda

I would carefully (beware and avoid the ESD zap) unsocket the ram and
resocket it.  I would carefully unplug and reattach every SATA cable.
Hopefully that will sort things out.  If not run memtest.  If no
answer there I would bisect the problem by splitting the ram or
swapping cpus with another.  I usually debug these things by swapping
components until I can isolate the problem to something specific. 

Alternatively it is possible that some attacker is wedging into your
system and the files are compromised.  I doubt that is the problem but
I feel compelled to cover the base by mentioning it.

Good luck!
Bob


signature.asc
Description: Digital signature

upgrade snafu

[Frank McCormick]

Did a quick apt-get update this afternoon:
Haven't seem this in a while:

localepurge: checking for existence of 
/var/cache/localepurge/localelist... localepurge:

checking system for new locale ...
Segmentation fault E: Problem executing scripts DPkg::Post-Invoke 'if [ 
-x /usr/sbin/localepurge ] && [ $(ps w -p $PPID | egrep -c 
'(remove|purge)') != 1 ]; then /usr/sbin/localepurge; else exit 0; fi' 
E: Sub-process returned an error code debian:

/home/frank#


Any ideas or should I just wait until it sorts itself out ?


--
Cheers
Frank


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/51310833.5010...@videotron.ca

Re: ikiwiki + Apache 1.3 =?=> NFG/SNAFU

[Eric d'Alibut]

On Sun, Jul 26, 2009 at 6:12 AM, Jochen Schulz wrote:

> Is there any specific reason why you don't upgrade to Apache2?

As noted, task-aversion.

SOLUTION FOUND:

# apt-get install apache2

:-)

> Atrocities committed in Rwanda pervade my mind when I am discussing
> mundanities with acquaintances.
> [Agree]   [Disagree]
>                 

Agree

-- 
No no no, my fish's name is Eric, Eric the fish. He's an halibut. I am
not a looney! Why should I be tarred with the epithet looney merely
because I have a pet halibut?


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: ikiwiki + Apache 1.3 =?=> NFG/SNAFU

[Eric d'Alibut]

On Sun, Jul 26, 2009 at 6:12 AM, Jochen Schulz wrote:

> http://httpd.apache.org/docs/1.3/misc/FAQ-F.html#premature-script-headers

Thanks for the link.

> Is there any specific reason why you don't upgrade to Apache2?

I am task-aversive. 


Best,

-- 
No no no, my fish's name is Eric, Eric the fish. He's an halibut. I am
not a looney! Why should I be tarred with the epithet looney merely
because I have a pet halibut?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: ikiwiki + Apache 1.3 =?= > NFG/SNAFU

[Jochen Schulz]

Eric d'Alibut:
> On Sat, Jul 25, 2009 at 6:11 AM, Jochen Schulz wrote:
> 
>> Do you have any concrete problems or are you asking in advance?
> 
> I should have posted the  I was having, which concerns
> running ikiwiki.cgi. I am getting "Premature end of script headers"
> when this script is called, for example, when I try to use the 'Edit'
> link on my wiki pages.

This appears to be a quite common error message. Solutions I can find
ad-hoc include fixing script permissions or using UNIX newlines in your
script. But you have probably googled already as well. :) See also:

http://httpd.apache.org/docs/1.3/misc/FAQ-F.html#premature-script-headers

> So I seem to have a generic "Premature end of script headers" cgi
> error since upgrading from Etch to Lenny. (I waited as long as I
> could!)

Is there any specific reason why you don't upgrade to Apache2?

J.
-- 
Atrocities committed in Rwanda pervade my mind when I am discussing
mundanities with acquaintances.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

Re: ikiwiki + Apache 1.3 =?=> NFG/SNAFU

[Eric d'Alibut]

On Sat, Jul 25, 2009 at 6:11 AM, Jochen Schulz wrote:

> Do you have any concrete problems or are you asking in advance?

I should have posted the  I was having, which concerns
running ikiwiki.cgi. I am getting "Premature end of script headers"
when this script is called, for example, when I try to use the 'Edit'
link on my wiki pages.

But in looking at apache's error log I see other instances of this
same error message connected to running, for example, other cgi
scripts in other users' public_html dirs..

So I seem to have a generic "Premature end of script headers" cgi
error since upgrading from Etch to Lenny. (I waited as long as I
could!)


Best regards,

-- 
No no no, my fish's name is Eric, Eric the fish. He's an halibut. I am
not a looney! Why should I be tarred with the epithet looney merely
because I have a pet halibut?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: ikiwiki + Apache 1.3 =?=> NFG/SNAFU

[Frank Lin PIAT]

On Sat, 2009-07-25 at 03:00 -0400, Eric d'Alibut wrote:
> I notice the ikiwiki docs provide httpd server config hints only for
> Apache 2 and lighttpd. Should I take this as an implicit hint that my
> attempt to run ikiwiki (that *is* hard to type!) on the older Apache
> vintage are foolhardy, extremely ill-advised, a recipe for disaster,
> paving the road to perdition?
> 
> ii  ikiwiki 3.14159a wiki compiler
> ii  apache  1.3.34-4.1+etch1  versatile,
> high-performance HTTP server

ughhh #...@?

You seems to be running the latest version of ikiwiki (from unstable),
with an apache version from etch #...@?

One sensible reason why ikiwiki 3.14159 doesn't mention apache v1, is
because apache v1 is deprecated upstream, and it is removed in Debian
Testing and Unstable

Franklin


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: ikiwiki + Apache 1.3 =?= > NFG/SNAFU

[Jochen Schulz]

Eric d'Alibut:
>
> I notice the ikiwiki docs provide httpd server config hints only for
> Apache 2 and lighttpd. Should I take this as an implicit hint that my
> attempt to run ikiwiki (that *is* hard to type!) on the older Apache
> vintage are foolhardy, extremely ill-advised, a recipe for disaster,
> paving the road to perdition?

I don't think so. It's just that Apache2 is more or less the "default"
webserver and lighty is a common alternative. Apache1 is just very old.
AFAICS, it's not even in lenny anymore.

Do you have any concrete problems or are you asking in advance? I don't
know ikiwiki very well, but I suspect some people here do.

J.
-- 
I have never been happier than I am now; a fact which depresses me
immensely.
[Agree]   [Disagree]
 


signature.asc
Description: Digital signature

ikiwiki + Apache 1.3 =?=> NFG/SNAFU

[Eric d'Alibut]

I notice the ikiwiki docs provide httpd server config hints only for
Apache 2 and lighttpd. Should I take this as an implicit hint that my
attempt to run ikiwiki (that *is* hard to type!) on the older Apache
vintage are foolhardy, extremely ill-advised, a recipe for disaster,
paving the road to perdition?

ii  ikiwiki 3.14159a wiki compiler
ii  apache  1.3.34-4.1+etch1  versatile,
high-performance HTTP server


-- 
No no no, my fish's name is Eric, Eric the fish. He's an halibut. I am
not a looney! Why should I be tarred with the epithet looney merely
because I have a pet halibut?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: progress, but... - re. fixing LVM/md snafu

[kj]

Miles Fidelman wrote:

Hello again Folks,

So.. I'm getting closer to fixing this messed up machine.

Where things stand:

I have root defined as an LVM2 LV, that should use /dev/md2 as it's PV.
/dev/md2 in turn is a RAID1 array built from /dev/sda3 /dev/sdb3 and 
/dev/sdc3


Instead, LVM is reporting: "Found duplicate PV 
2ppSS2q0kO3t0tuf8t6S19qY3ypWBOxF: using /dev/sdb3 not /dev/sda3"
and the /dev/md2 is reporting itself as inactive (cat /proc/mdstat) 
and active,degraded (mdadm --detail)
I get this all the time with servers connected to SAN (mulitpath).   You 
need to look at the filter line in /etc/lvm/lvm.conf


The default (on my Lenny box) is to accept all devices:

filter = [ "a/.*/" ]

You need to either replace that and accept md devices only or exclude 
your sda/b/c explicitly


In your case this won't help you fix things, but it will make sure LVM 
doesn't grab the wrong device.




1. stop changes to /dev/sdb3 (actually, to / - which complicates things)
2. rebuild the RAID1 array, making sure to use /dev/sdb3 as the 
starting point for current data
I'm guessing if you fail and remove sda3 and sdc3, it won't try to 
rebuild anything, and you should be able to boot cleanly with a degraded 
raid.  Then add each drive and rebuild.  I've never done this though.


3. restart in such a way that LVM finds /dev/md2 as the right PVM 
instead of one of its components


This is where the LVM filter comes in.

--kj


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: progress, but... - re. fixing LVM/md snafu

[Goswin von Brederlow]

Miles Fidelman  writes:

> Hello again Folks,
>
> So.. I'm getting closer to fixing this messed up machine.
>
> Where things stand:
>
> I have root defined as an LVM2 LV, that should use /dev/md2 as it's PV.
> /dev/md2 in turn is a RAID1 array built from /dev/sda3 /dev/sdb3 and
> /dev/sdc3
>
> Instead, LVM is reporting: "Found duplicate PV
> 2ppSS2q0kO3t0tuf8t6S19qY3ypWBOxF: using /dev/sdb3 not /dev/sda3"
> and the /dev/md2 is reporting itself as inactive (cat /proc/mdstat)
> and active,degraded (mdadm --detail)

So you didn't tell lvm.conf to ignore raid component devices or the
detection fails. Worst case exclude sd?3 manualy.

After that a reboot should fix it.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

progress, but... - re. fixing LVM/md snafu

[Miles Fidelman]

Hello again Folks,

So.. I'm getting closer to fixing this messed up machine.

Where things stand:

I have root defined as an LVM2 LV, that should use /dev/md2 as it's PV.
/dev/md2 in turn is a RAID1 array built from /dev/sda3 /dev/sdb3 and 
/dev/sdc3


Instead, LVM is reporting: "Found duplicate PV 
2ppSS2q0kO3t0tuf8t6S19qY3ypWBOxF: using /dev/sdb3 not /dev/sda3"
and the /dev/md2 is reporting itself as inactive (cat /proc/mdstat) and 
active,degraded (mdadm --detail)


---
I'm guessing that, during boot:

- the raid array failed to start
- LVM found both copies of the PV, and picked one (/dev/sdb3)
- everything then came up and my server is humming away

but: the md array can't rebuild because the most current device in it is 
already in use


so...  I'm looking for the right sequence of events, with the minimum 
downtime to:


1. stop changes to /dev/sdb3 (actually, to / - which complicates things)
2. rebuild the RAID1 array, making sure to use /dev/sdb3 as the starting 
point for current data
3. restart in such a way that LVM finds /dev/md2 as the right PVM 
instead of one of its components


Each of these is just tricky enough that I'm sure there are lots of 
gotchas to watch out for.


So.. any suggestions?

Thanks very much,

Miles Fidelman





--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Re: mtab SNAFU

[Haines Brown]

> > Interesting. I see the logic by looking at /dev/disk/by-id, and it
> > looks simple. But I am a bit nervous about experimenting. Can you
> > refer me to a HOWTO, or do I have to play around to see if I can get
> > it to work? It seems this use of by-id is actually part of udev.
> 
> It's quite simple:
> - check the content of /dev/disk/by-id
> - plug your thumb-drive
> - check the new entries in  /dev/disk/by-id
> - add this kind of line to your fstab:
>   /dev/disk/by-id/  auto rw,noatime,user 0 0 

Aha! Simple as that. Thanks.

Haines


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mtab SNAFU

[Dominique Dumont]

Haines Brown <[EMAIL PROTECTED]> writes:

> Thanks for your reply. Yes, I sometimes run into trouble by having too
> many different USB drives to mount. I got the impression that
> configuring udev was the answer, but I was intimidated by the coding
> necessary to do it.

disk/by-id is now provided by udev config (may be by debian). So you
should not have any udev coding to do.

>> On my side, to be sure that a usb-device is always mounted on the same
>> point, I use an entry from /dev/disk/by-id/ instead of relying on
>> /dev/sdd1.  
>
> Interesting. I see the logic by looking at /dev/disk/by-id, and it
> looks simple. But I am a bit nervous about experimenting. Can you
> refer me to a HOWTO, or do I have to play around to see if I can get
> it to work? It seems this use of by-id is actually part of udev.

It's quite simple:
- check the content of /dev/disk/by-id
- plug your thumb-drive
- check the new entries in  /dev/disk/by-id
- add this kind of line to your fstab:
  /dev/disk/by-id/  auto rw,noatime,user 0 0 

HTH

-- 
Dominique Dumont 
"Delivering successful solutions requires giving people what they
need, not what they want." Kurt Bittner


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mtab SNAFU

[Haines Brown]

Dominique,

Thanks for your reply. Yes, I sometimes run into trouble by having too
many different USB drives to mount. I got the impression that
configuring udev was the answer, but I was intimidated by the coding
necessary to do it.

> On my side, to be sure that a usb-device is always mounted on the same
> point, I use an entry from /dev/disk/by-id/ instead of relying on
> /dev/sdd1.  

Interesting. I see the logic by looking at /dev/disk/by-id, and it
looks simple. But I am a bit nervous about experimenting. Can you
refer me to a HOWTO, or do I have to play around to see if I can get
it to work? It seems this use of by-id is actually part of udev.

Haines


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mtab SNAFU

[Dominique Dumont]

Haines Brown <[EMAIL PROTECTED]> writes:

> I'm running a stock etch kernel. For whatever it's worth, the line in
> /etc/fstab for usb-key is:
>
>   /dev/sdd1  /media/usb-key   vfat   rw,user,noauto0 0

This setup is fine if you have only one usb-drive.

On my side, to be sure that a usb-device is always mounted on the same
point, I use an entry from /dev/disk/by-id/ instead of relying on /dev/sdd1.

On the other hand, if I do not want to control exactly where to mount
the device, I let KDE handle it.

HTH

-- 
Dominique Dumont 
"Delivering successful solutions requires giving people what they
need, not what they want." Kurt Bittner


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mtab SNAFU

[Haines Brown]

"David Fox" <[EMAIL PROTECTED]> writes:

> On 25 Nov 2007 10:59:25 -0500, Haines Brown <[EMAIL PROTECTED]> wrote:
> 
> > desperation I deleted the multiple instances from /etc/mtab. I
> > should have consulted first, but didn't want to be pain.
...
> Yes, that's correct. Filesystems are mounted per /etc/fstab and if 
> that is in good order, there shouldn't be a problem.

Well, rebooting was ultimately the answer, although for unrelated
reasons, being able to boot and then to communicate was a complicated
process that took a couple hours to straighten out. But all's well
now. Thanks.

Someone suggestdd doing:

  # cat /proc/mounts > /etc/mtab

which I presume is wrong because it involves modifying mtab, which I
infer from your comment should not be done. 

-- 
 
   Haines Brown, KB1GRM

 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: mtab SNAFU

[David Fox]

On 25 Nov 2007 10:59:25 -0500, Haines Brown <[EMAIL PROTECTED]> wrote:

> desperation I deleted the multiple instances from /etc/mtab. I should
> have consulted first, but didn't want to be pain.

That might have been the first problem. /etc/mtab is a
dynamically-created file - it is a file of all the mount points at any
given time. /etc/fstab should contain the mount points for everything
you need or want mounted on startup.

> This got me into trouble, for deleting the lines for /media/usb-key
> actually caused all lines to disapper. I tried to restore /etc/mtab

My /etc/mtab is less than 1 K so I don't see how this could fail. But
then agan, you shouldn't be restoring /etc/mtab since it is a dynamic
file.


> /dev/sdd1 on /media/usb-key type vfat
>   (rw,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0022,dmask=0022,
>   codepage=cp437,iocharset=iso8859-1)

It's not that unusual, it's basically your /etc/fstab mount info with
a few extra options thrown in.

> My intuition tells me that if I were to reboot, the /etc/mtab file will be
> reconstituted normally and my multiple mounted usb-key problem will be

Yes, that's correct. Filesystems are mounted per /etc/fstab and if
that is in good order, there shouldn't be a problem.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

mtab SNAFU

[Haines Brown]

I had a problem of multiple mountings of /media/usb-key, and I was
struggling without success to umount them. (tried -f option for
umount, tried to find mount PID to delete it, tried fuser), and in
desperation I deleted the multiple instances from /etc/mtab. I should
have consulted first, but didn't want to be pain.

This got me into trouble, for deleting the lines for /media/usb-key
actually caused all lines to disapper. I tried to restore /etc/mtab
from a backlup, but the copy failed because no space left on device,
which is contrary to fact. I ended up with an empty /etc/mtab and then
no no mtab at all. In fact, /etc/ is half used and I've deleted files
from the USB-key so that it is only half used. I can't run df because
it can't find mtab.)  

I'm running a stock etch kernel. For whatever it's worth, the line in
/etc/fstab for usb-key is:

  /dev/sdd1  /media/usb-key   vfat   rw,user,noauto0 0

At the moment the mount command appears nomrally for directories on my
hard disk, but ends with this unusual statement for the /media/usb-key:  

/dev/sdd1 on /media/usb-key type vfat
  (rw,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0022,dmask=0022,
  codepage=cp437,iocharset=iso8859-1)   

My intuition tells me that if I were to reboot, the /etc/mtab file will be
reconstituted normally and my multiple mounted usb-key problem will be
over, but I'm afraid I'll simply be unable to access my hd, and so
need resassurance. Is it safe to reboot?

Multiple instances of mounting is a common problem, but in all the
discussion, I've yet to see a definitive answer.

-- 
 
   Haines Brown, KB1GRM

 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

snort install script snafu

[paul]

Hi. I'm setting up a Woody box, getting the following errors on
configuration of the snort package. The debian bug tracker doesn't show
this issue, but lists enough other bugs that I'm wondering whether to
bother.

Any advice appreciated.

Setting up snort (1.8.4beta1-3) ...
Bareword found where operator expected at -e line 4, near 
"s,^(DEBIAN_SNORT_OPTIONS=).*$,$1" -i eth0, eth1"
String found where operator expected at -e line 5, near 
"s,^(DEBIAN_SNORT_STATS_RCPT=).*$,$1""
  (Might be a runaway multi-line "" string starting on line 4)
(Missing semicolon on previous line?)
Bareword found where operator expected at -e line 5, near 
"s,^(DEBIAN_SNORT_STATS_RCPT=).*$,$1"root"
Unquoted string "root" may clash with future reserved word at -e line 5.
String found where operator expected at -e line 6, near 
"s,^(DEBIAN_SNORT_STATS_TRESHOLD=).*$,$1""
  (Might be a runaway multi-line "" string starting on line 5)
(Missing semicolon on previous line?)
Number found where operator expected at -e line 6, near 
"s,^(DEBIAN_SNORT_STATS_TRESHOLD=).*$,$1"1"
String found where operator expected at -e line 6, at end of line
(Missing semicolon on previous line?)
syntax error at -e line 4, near 
"s,^(DEBIAN_SNORT_OPTIONS=).*$,$1" -i eth0, eth1"
Can't find string terminator '"' anywhere before EOF at -e line 6.
dpkg: error processing snort (--configure):
 subprocess post-installation script returned error exit status 255
- 
Paul Mackinney
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: WindowMaker 'applications' menu SNAFU ...

[Rodney D. Myers]

On Sun, 27 Jul 2003 10:07:55 +1000
Adam Bogacki <[EMAIL PROTECTED]> wrote:

> Sorry for the WWII jargon but I've installed some themes into
> 
> ~/GNUstep/Library/WindowMaker/Themes
> 
> but the 'applications' menu does not show any. In fact it has not been
> working at all in this WM installation, but has not troubled me until
> now.
> 
> Any ideas out there ?
> 
> Adam Bogacki,
> [EMAIL PROTECTED]

Look for a program called "genmenu". It'll generate a windowmaker
applications menus'.

-- 
Rodney D. Myers <[EMAIL PROTECTED]> Registered Linux User #96112
ICQ#: AIM#:   YAHOO:
18002350  mailman452  mailman42_5

They that can give up essential liberty to obtain a 
little temporary safety deserve neither liberty nor safety.
Ben Franklin - 1759


pgp0.pgp
Description: PGP signature

WindowMaker 'applications' menu SNAFU ...

[Adam Bogacki]

Sorry for the WWII jargon but I've installed some themes into

~/GNUstep/Library/WindowMaker/Themes

but the 'applications' menu does not show any. In fact it has not been
working at all in this WM installation, but has not troubled me until now.
Any ideas out there ?

Adam Bogacki,
[EMAIL PROTECTED]


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: htdig snafu after woody upgrade

[nate]

will trillich said:

>   /usr/bin/rundig: cd: /var/spool/htdig: No such file or directory
>   DB2 problem...: /var/spool/htdig/db.docdb: No such file or
>   directory
>
> (at one point i thought i was beginning to get the hang of
> figuring these things out. alas...)
>
> what salve is there for this wound?
>

be sure theres a /var/spool/htdig directory ? and be sure it's accessable
by whatever user htdig uses(unless it runs as root..been a couple years since
I used it)

nate




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

htdig snafu after woody upgrade

[will trillich]

here's what i get from cron.daily these days--

/etc/cron.daily/htdig:
DB2 problem...: /var/spool/htdig/db.docdb.work: No such file or
directory
htdig: Unable to open/create document database
'/var/spool/htdig/db.docdb.work'

htmerge: Unable to create temporary word file
'/var/spool/htdig/db.wordlist.work.new'

/usr/bin/rundig: cd: /var/spool/htdig: No such file or directory
DB2 problem...: /var/spool/htdig/db.docdb: No such file or
directory

(at one point i thought i was beginning to get the hang of
figuring these things out. alas...)

what salve is there for this wound?

-- 
I use Debian/GNU Linux version 3.0;
Linux server 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown
 
DEBIAN NEWBIE TIP #107 from Mark Janssen <[EMAIL PROTECTED]>
:
Is it possible to RESTRICT SSH LOGINS TO CERTAIN COMMANDS? Sure.
Use the autorized_keys file on the server side. Place an entry
in there like to following:
command="some_command" X Y Z 
where the X Y Z  is the public key file for
that user.  If they login now they can only do command
some_command.

Also see http://newbieDoc.sourceForge.net/ ...


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Way OT: openSSH 2.9.9p2, perl and cron SNAFU

[Dimitri Maziuk]

Hi all,
this is way OT, but maybe someone can come up with an
explanation. Here's a snippet of perl I'm trying to run 
as a cron job:

open( IN, "$cmd |" );  # read output of $cmd via pipe
while( $line =  ) {
push @lines, $line; # store it in array
}
close( IN );
foreach $line (@lines) { print $line; } # print the array

When $cmd is, say "sar -u 1" (this is on Solaris), it works.
When $cmd = "rsh  sar -u 1", it works.
When $cmd = "ssh  sar -u 1", it works from command line.
If I run it as cron job, @lines is empty.

It works if $cmd = "ssh  echo FUBAR". 

So far I tried specifying full paths to executables, backticking
$cmd instead of piping it, adding stuff to %ENV (this shouldn't
be relevant anyway as rsh works with the same environment)... 
No go.

Any clues?

TIA
Dima
-- 
"Mirrors and copulation are abominable because they increase the number of 
entities."-- corollary to Occam's Razor

/usr/sbin/pptpdconfig.pl snafu?

[will trillich]

installing "pptpd" went like a charm--but i can't get the config
script to run:

# apt-get install pptpd
Reading Package Lists... Done
Building Dependency Tree... Done
The following extra packages will be installed:
  ppp 
The following NEW packages will be installed:
  ppp pptpd 
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 236kB/289kB of archives. After unpacking 600kB will be used.
Do you want to continue? [Y/n] 
Get:1 http://ftp.digex.net stable/main ppp 2.3.11-1.4 [236kB]
Fetched 236kB in 3s (75.4kB/s)
Configuring packages ...  
Selecting previously deselected package ppp.
(Reading database ... 34906 files and directories currently installed.)
Unpacking ppp (from .../ppp_2.3.11-1.4_i386.deb) ...
Selecting previously deselected package pptpd.
Unpacking pptpd (from .../pptpd_1.0.0-4_i386.deb) ...
Setting up ppp (2.3.11-1.4) ...

Setting up pptpd (1.0.0-4) ...
Starting PPTP Daemon: pptpd.

presumably all known dependencies are now met, but--

# perl /usr/sbin/pptpdconfig.pl
Can't exec "/usr/sbin/pptpdconfig.pl": Permission denied at 
/usr/lib/perl5/5.005/IPC/Open3.pm line 188.
open2: exec of /usr/sbin/pptpdconfig.pl failed at 
/usr/lib/perl5/Debian/DebConf/ConfModule.pm line 86
Use of uninitialized value at 
/usr/lib/perl5/Debian/DebConf/ConfModule.pm line 478.

-- 
DEBIAN NEWBIE TIP #21 from Will Trillich <[EMAIL PROTECTED]> 
:
Looking to configure your Debian NETWORK SETTINGS? Look at the
file /etc/network/interfaces (try "man interfaces" for more
info). Then "ifup -a" to reload your settings, and "ifconfig" to
display them. (Also check out "apt-get install ipmasq"!)

Also see http://newbieDoc.sourceForge.net/ ...

Potato -> Woody; apt-get snafu..

[Gregory Guthrie]

I started (over) with a clean system, installed 2.2 from CDroms, added a 
few packages (Apache, ntop, wuftp, gnome,..).


I got several unresolved dependencies reported by dselect, but what to do?

I wanted a few unsupported packages, so I added a ../woody/ line to 
/etc/apt/source/list, and did apt-get update, and dist-upgrade.


Oops; it took about 10 passes to get all the files (220M); many many 400 
not founds, 404 file errors, lost connections, etc. Anyway, a day later all 
was there, and it started updating. At the end it reported a bunch of 
missing dependencies and thus install failures. I ran the cycle again, and 
it downloaded another 20M, and in install gave another bunch of problems. 
Well, after about 5 cycles, it seems to be in such a mess (it now reports 
perl may not be installed properly), that it seems like I need to start all 
over.


What went wrong here?
[I had a similar experience upgrading the sibling machine, but after a few 
cycles it resolved itself.]


I think I didn't do anything wrong, since all I did was to select a few 
dselect packages, and let apt do the work (make a mess..!).


1) Any ideas on how to avoid such snafu's!

2) any ideas for a recovery; or just give up.

3) how stable is woody, on a scale of 0-100%?

4) Can I get only one package from Woody, without upgrading the whole 
distribution?


Thanks,
Gregory Guthrie

Dr. Gregory Guthrie
[EMAIL PROTECTED] (641)472-1125Fax: -1103
   Computer Science Department
   School of Computing and Information Science
   Maharishi University of Management
  (Maharishi International University 1971-1995)
http://www.mum.edu/cs_dept

Re: Snafu

[David Wright]

Quoting Ray Woodcock ([EMAIL PROTECTED]):
> I'm somewhere in the process of installing slink.  There was an
> interruption during installation, I rebooted, etc.  I guess I could wipe
> out the disk and start over, but I'd kind of like to understand where I
> am and why.

The $64000 question is whereabouts were you at the interruption.
When you started the installation, you booted off the rescue disk.
Had you finished this program entirely? If not, then boot from this
disk again and follow the menus carefully.

Certain things will need repeating (configure kbd, activate swap)
and certain things won't (you don't need to initialise partitions
that you initialised previously) which is why there are all these
alternat(iv)e commands.

> The system boots and reboots OK.  I've been playing around with bash
> commands.  Not all of the ones I read about on Web pages seem to be
> working.  Now I want to run dbootstrap to configure my base system.

So it seems likely that you completed that program and got as far as
"Reboot the system" ? And you set a root password? And did you set
up the first user account? If so, login as user, type
/bin/su -
to make yourself root and now you can type
dselect

Does what you see now look familiar? If not, then it's likely that
dselect has never been run. The safest thing to do here is to press
return when it displays the package selection list and let it
install whatever it had in its default list. (This may or may not
have been modified if you got as far as answering the question
"What sort of machine are you intending to run".)

Once dselect has installed it's first load of packages (after
which, for slink, the output from
dpkg -l | wc
should start with a number around 150) you can run dselect again
and pick and choose what packages you want.

> But
> when I type dbootstrap at the $ prompt, I get "command not found."  I go
> to the root (or whatever you call /) and type "find dbootstrap," but
> that just gives me "no such file or directory."

A linux root directory shouldn't have any non-directories in it,
apart from a link to the kernel.

> Anybody know where I am and where I should be going?  Or is it time to
> use a blunt instrument on this installation?

This is not normally necessary. But it would have helped to know when
you were interrupted.

Cheers,

-- 
Email:  [EMAIL PROTECTED]   Tel: +44 1908 653 739  Fax: +44 1908 655 151
Snail:  David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA
Disclaimer:   These addresses are only for reaching me, and do not signify
official stationery. Views expressed here are either my own or plagiarised.

Re: Snafu

[John Miskinis]

Hello,


The system boots and reboots OK.  I've been playing around with bash
commands.  Not all of the ones I read about on Web pages seem to be
working.  Now I want to run dbootstrap to configure my base system.  But
when I type dbootstrap at the $ prompt, I get "command not found."  I go
to the root (or whatever you call /) and type "find dbootstrap," but
that just gives me "no such file or directory."

Anybody know where I am and where I should be going?  Or is it time to
use a blunt instrument on this installation?


I've been running debian for months, and never heard of the
dbootstrap program.  Perhaps others can elaborate, as it may
be a transient (and temporary) file only used during the install.
I checked MY system, with the command listed below, and it does
not exist anywhere on my system.

find / -name "dbootstrap" -print

As far as commands in general, depending on what command you are
trying to execute, it may or may not exist in the "base system"
provided by a linux distribution.  In the case of Debian, it is
a simple matter to install the correct package that supplies the
command.  If you post some of the commands you are trying, more
information can be provided.

If you are executing "standard" commands, and they are failing, I
would suggest a re-install, which in my opinion is what I would do
anyway.  Again, I'm not familiar with the details of the interruption
of the install you mentioned.

In any case, I would reccomend posting more detail about your
situation.  There are many friendly people on this list with open
ears.

John


__
Get Your Private, Free Email at http://www.hotmail.com

Snafu

[Ray Woodcock]

I'm 
somewhere in the process of installing slink.  There was an interruption 
during installation, I rebooted, etc.  I guess I could wipe out the disk 
and start over, but I'd kind of like to understand where I am and 
why.
 
The 
system boots and reboots OK.  I've been playing around with bash 
commands.  Not all of the ones I read about on Web pages seem to be 
working.  Now I want to run dbootstrap to configure my 
base system.  But when I type dbootstrap at the $ prompt, I get "command 
not found."  I go to the root (or whatever you call /) and type "find 
dbootstrap," but that just gives me "no such file or 
directory."
 
Anybody know where I am and where I should be 
going?  Or is it time to use a blunt instrument on this 
installation?

list mail snafu-ed

[Bruce Perens]

Some list mail and other debian mail will have its delivery delayed.
The mail delivery agent was accidentaly replaced on our main system and
now I have an smail queue of this morning's messages. Smail proved it was
not as fast as qmail. I'll get that queue delivered later today, meanwhile
I have switched qmail back on.

Bruce
-- 
Can you get your operating system fixed when you need it?
Linux - the supportable operating system. http://www.debian.org/support.html
Bruce Perens K6BP   [EMAIL PROTECTED]   510-215-3502


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

SNAFU system

[Chad D. Zimmerman]

I had an interesting problem develop .. would almost say overnight, but I
don't think so.

I hadn't used my system for 3 days and the other night we had the worst
thunderstorm (and the first of them) this summer.  I did a shutdown -h now
before the storm took out power.

It was down a day and last night I fired it back up.  I noticed it
couldn't find some modules in the kernel, like vfat and some other file
system types.

When I login, I get addition chars when I type.  The 5 and 6 keys put out
something like this h6 and g5 the - gives me '- the G key is 5g and I
think the H is something like 6h.

Also the esc key would complete what ever I was typing ... now it doesn't
and it just beeps at me.

This happens in both console and xwindows, so I am at a loss what could
have caused all this to happen.

Any ideas?  Would like to have my system back to working order :}

Chad


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Chad D. Zimmerman   [EMAIL PROTECTED]
Southwest Technology Development Institute
New Mexico State University
---
HP: http://dabcc-www.nmsu.edu/~chad/
DBP: http://dabcc-www.nmsu.edu/~chad/Debian/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .