Re: Laptop wireless problem - further progress

On Saturday 02 July 2016 06:23:34 Francesco Ariis wrote: > On Sat, Jul 02, 2016 at 01:46:37AM +0100, Lisi Reisz wrote: > > [...] > > Please you are already a prolific poster, try at least to reply > to your own threads with the proper `In-Reply-To` header or we'll > get one new thread for every mes

Re: Laptop wireless problem - further progress

On Sat, Jul 02, 2016 at 01:46:37AM +0100, Lisi Reisz wrote: > [...] Please you are already a prolific poster, try at least to reply to your own threads with the proper `In-Reply-To` header or we'll get one new thread for every message you post.

Re: Laptop wireless problem

Further to the two from me which haven't got through yet (threading is going to be really mucked up) having appeared to connect through /e/n/i/, and got only an IPv6 address so that I appeared to be unable to make any actual connections anywhere, I obviously did get through because, from my rout

Re: catastrophe - but how? Aptitude goes mad

On Sat, 02 Jul 2016, Lisi Reisz wrote: > On Friday 01 July 2016 19:07:11 Henrique de Moraes Holschuh wrote: > > On Fri, 01 Jul 2016, Lisi Reisz wrote: > > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > > > Try this when you open a root session (in a typical console, and >

Laptop wireless problem - further progress

The following lines in /e/n/i worked and wireless is now running (I am connected over it with ssh), so the hardware is fine - though it is the onboard card that is working, and the USB card is still not!! sarah@debian-wheezy:~$ cat /etc/network/interfaces # This file describes the network interf

Laptop wireless problem - further to this

When booting up the messages reported failure to load something to do with the wireless cards. It went by too fast and too small for me to read it properly. And I have tried one modification of the /e/n/i file, but if the drivers haven't loaded, it won't do any good. Original message. The bui

Silkylux mosógél megapack hihetetlen áron, 4 x 4L színes vagy fehér különböző variációkban. Válaszd ki a háztartásodnak megfelelőt, és még ajándék 0,5 L öblítőt és szappant is kapsz hozzá.

Mai ajánlat: Fedezd fel! 4x4L Silkylux mosógél pack Ajándék 0,5L öblítő + 0,5L szappan Eredeti ár: 13 170 Ft Kedvezményes ár: 3

Laptop wireless problem

The built in wireless on teh Dell Inspiron 9300 suddenly stopped working. Having poked around a bit with wicd and network-manager (not simultaneously), I am checkinh whether the problem is sudden hardware failure. I plugged in a USB network card. Here is what I get: sarah@debian-wheezy:~$ ls

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 19:07:11 Henrique de Moraes Holschuh wrote: > On Fri, 01 Jul 2016, Lisi Reisz wrote: > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > > Try this when you open a root session (in a typical console, and > > > certainly in a typical graphical terminal):

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 18:12:51 +, Curt wrote: > On 2016-07-01, Brian wrote: > >> > >> That's not what I meant. I meant ask *him* *here* in this public thread > >> why ... > >> etc. > > > > He is a subscriber to -user. By definition he *has been* asked here in > > this public thread. > >

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Brian wrote: >> >> That's not what I meant. I meant ask *him* *here* in this public thread why >> ... >> etc. > > He is a subscriber to -user. By definition he *has been* asked here in > this public thread. Well, there you go then, man. Maybe he's formulating a thorough reply a

Re: catastrophe - but how? Aptitude goes mad

On Fri, 01 Jul 2016, Lisi Reisz wrote: > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > Try this when you open a root session (in a typical console, and > > certainly in a typical graphical terminal): > > > > stty sane > > No output in either. "stty sane" shouldn't

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 18:18:42 Brian wrote: > On Fri 01 Jul 2016 at 17:59:34 +0100, Lisi Reisz wrote: > > On Friday 01 July 2016 17:52:08 Curt wrote: > > > On 2016-07-01, Lisi Reisz wrote: > > > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > > >> Try this when you open a

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 17:59:34 +0100, Lisi Reisz wrote: > On Friday 01 July 2016 17:52:08 Curt wrote: > > On 2016-07-01, Lisi Reisz wrote: > > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > >> Try this when you open a root session (in a typical console, and > > >> certai

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Lisi Reisz wrote: > On Friday 01 July 2016 17:52:08 Curt wrote: >> On 2016-07-01, Lisi Reisz wrote: >> > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: >> >> Try this when you open a root session (in a typical console, and >> >> certainly in a typical graphical

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 16:57:02 +, Curt wrote: > On 2016-07-01, Lisi Reisz wrote: > > On Friday 01 July 2016 17:39:57 Curt wrote: > >> > > Because then the answer might be private too, and this is a public thread. > > I > > would obviously be interested in the answer, and many others might

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Lisi Reisz wrote: > On Friday 01 July 2016 17:39:57 Curt wrote: >> > Because then the answer might be private too, and this is a public thread. I > would obviously be interested in the answer, and many others might be too. > Not to mention that it would be useful for the archiv

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 17:52:08 Curt wrote: > On 2016-07-01, Lisi Reisz wrote: > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > >> Try this when you open a root session (in a typical console, and > >> certainly in a typical graphical terminal): > >> > >> stty sane >

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Lisi Reisz wrote: > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: >> Try this when you open a root session (in a typical console, and >> certainly in a typical graphical terminal): >> >> stty sane > > No output in either. > What were you expecting? > >

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 17:39:57 Curt wrote: > On 2016-07-01, Brian wrote: > >> >> > Must be progress. GNU grep 2.12 here. > >> > > >> > Bug #678652. > >> > >> He didn't write that. > > > > No, you wrote it and I accidentally snipped a line when replying. But > > now we know why the manual for grep

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Brian wrote: >> >> >> >> > Must be progress. GNU grep 2.12 here. >> > >> > Bug #678652. >> >> He didn't write that. > > No, you wrote it and I accidentally snipped a line when replying. But > now we know why the manual for grep 2.20-4.1 says something different > for -r/-R from th

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > Try this when you open a root session (in a typical console, and > certainly in a typical graphical terminal): > > stty sane No output in either. Lisi

Re: systemd I/O error :-(

On Friday 01 July 2016 16:12:39 Michael Biebl wrote: > Am 30.06.2016 um 17:25 schrieb Lisi Reisz: > > [24772.681833] systemd-logind[21814]: Failed to enable subscription: > > Launch helper exited with unknown return code 1 > > [24772.681890] systemd-logind[21814]: Failed to fully start up daemon: >

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 15:19:20 +, Curt wrote: > On 2016-07-01, Brian wrote: > > On Fri 01 Jul 2016 at 13:56:22 +0200, to...@tuxteam.de wrote: > > > >> On Fri, Jul 01, 2016 at 11:42:58AM +, Curt wrote: > >> > On 2016-07-01, wrote: > >> > >> [...] > >> > >> > > GNU grep 2.20, Debian pac

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 16:06:30 Ralph Katz wrote: > On 07/01/2016 10:25 AM, Lisi Reisz wrote: > ... > > > Aptitude has served me well, reliably and faithfully for 14 years. I was > > not rushing to blame it in this case. > > > > But until I do find out what went wrong, I shall be a little nervous

Re: systemd I/O error :-(

Am 30.06.2016 um 17:25 schrieb Lisi Reisz: > [24772.681833] systemd-logind[21814]: Failed to enable subscription: > Launch helper exited with unknown return code 1 > [24772.681890] systemd-logind[21814]: Failed to fully start up daemon: > Input/output errror Could you post the output of systemctl

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, Brian wrote: > On Fri 01 Jul 2016 at 13:56:22 +0200, to...@tuxteam.de wrote: > >> On Fri, Jul 01, 2016 at 11:42:58AM +, Curt wrote: >> > On 2016-07-01, wrote: >> >> [...] >> >> > > GNU grep 2.20, Debian package grep 2.20-4.1 -- progress or regression? >> >> [...] >> >> > M

Re: catastrophe - but how? Aptitude goes mad

On 07/01/2016 10:25 AM, Lisi Reisz wrote: ... > Aptitude has served me well, reliably and faithfully for 14 years. I was not > rushing to blame it in this case. > > But until I do find out what went wrong, I shall be a little nervous of > aptitude. :-( ... Sorry to read of your upgrade trouble

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 08:36:02 (-0400), Gene Heskett wrote: > On Friday 01 July 2016 05:43:44 Jörg-Volker Peetz wrote: > > Gene Heskett wrote on 07/01/16 01:35: > > > On Thursday 30 June 2016 19:25:37 Lisi Reisz wrote: > > > > > > > > > No, thats just grep being grep, it says that of ANY binary fi

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 13:19:46 Brian wrote: > On Fri 01 Jul 2016 at 00:37:32 +0100, Lisi Reisz wrote: > > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > > On Fri, 01 Jul 2016, Lisi Reisz wrote: > > > > assumed, it wasn't asked to remove anything. It was asked to add one >

Re: ppp0 and "SIOCADDRT: Operation not supported by device"

Azzz Sent from my iPhoneapp.pp0-0--

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 05:43:44 Jörg-Volker Peetz wrote: > Gene Heskett wrote on 07/01/16 01:35: > > On Thursday 30 June 2016 19:25:37 Lisi Reisz wrote: > > > > > No, thats just grep being grep, it says that of ANY binary file it > > tries to read as text. I have spent days pouring over the manp

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 03:44:01 to...@tuxteam.de wrote: > On Fri, Jul 01, 2016 at 09:42:09AM +0200, to...@tuxteam.de wrote: > > [...] > > > And I have paid tribute to the (in the man/info pages) unnamed > > authors (but one can find out [1]) who gave me such a little jewel. > > Eh, sorry. Forgot >

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 00:37:32 +0100, Lisi Reisz wrote: > On Friday 01 July 2016 00:14:34 Henrique de Moraes Holschuh wrote: > > On Fri, 01 Jul 2016, Lisi Reisz wrote: > > > assumed, it wasn't asked to remove anything. It was asked to add one > > > thing which in now way depended on anything remo

Re: catastrophe - but how? Aptitude goes mad

On Fri 01 Jul 2016 at 13:56:22 +0200, to...@tuxteam.de wrote: > On Fri, Jul 01, 2016 at 11:42:58AM +, Curt wrote: > > On 2016-07-01, wrote: > > [...] > > > > GNU grep 2.20, Debian package grep 2.20-4.1 -- progress or regression? > > [...] > > > Must be progress. GNU grep 2.12 here. Bug

Re: catastrophe - but how? Aptitude goes mad

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jul 01, 2016 at 11:42:58AM +, Curt wrote: > On 2016-07-01, wrote: [...] > > GNU grep 2.20, Debian package grep 2.20-4.1 -- progress or regression? [...] > Must be progress. GNU grep 2.12 here. Phew :-) thanks - -- t -BEGIN PGP S

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, wrote: > >> I looked it up in the man page too. It said: >> >> -R, -r, --recursive >> Read all files under each directory, recursively; this >> is equivalent to the -d recurse option. > > Hm. My man page seems more complete (it's the one in Debian coming with > GNU grep 2.2

Re: catastrophe - but how? Aptitude goes mad

H, Dario Strbenac wrote: > Have you considered upgrading your customer's computer to Windows 10 > instead ? It's free to do until the end of the month! Beware, Microsoft had to pay 10,000 USD in damages after Windows 10 installed itself on a customer's computer. Have a nice day :) Thomas

Re: catastrophe - but how? Aptitude goes mad

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jul 01, 2016 at 09:36:16AM +, Curt wrote: > On 2016-07-01, wrote: > > > > I freely admit I didn't know, but now I do: > > > > -R follows (recursively) symbolic links > > -r follows a symbolic link only if it is the top-level argument >

Re: catastrophe - but how? Aptitude goes mad

Gene Heskett wrote on 07/01/16 01:35: > On Thursday 30 June 2016 19:25:37 Lisi Reisz wrote: > > No, thats just grep being grep, it says that of ANY binary file it tries > to read as text. I have spent days pouring over the manpages for grep, > looking for a option to feed it to make grep quit

Re: catastrophe - but how? Aptitude goes mad

On Friday 01 July 2016 07:00:08 Dario Strbenac wrote: > Have you considered upgrading your customer's computer to Windows 10 > instead ? It's free to do until the end of the month! :-)) ROTFLOL! It hasn't ever seen Windows, this lucky computer. So I can't upgrade!! Lisi

Re: catastrophe - but how? Aptitude goes mad

On 2016-07-01, wrote: > > I freely admit I didn't know, but now I do: > > -R follows (recursively) symbolic links > -r follows a symbolic link only if it is the top-level argument I looked it up in the man page too. It said: -R, -r, --recursive Read all files under each directory, recur

Re: catastrophe - but how? Aptitude goes mad

Have you considered upgrading your customer's computer to Windows 10 instead ? It's free to do until the end of the month!

Re: catastrophe - but how? Aptitude goes mad

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jul 01, 2016 at 09:42:09AM +0200, to...@tuxteam.de wrote: [...] > And I have paid tribute to the (in the man/info pages) unnamed authors > (but one can find out [1]) who gave me such a little jewel. Eh, sorry. Forgot [1]

Re: catastrophe - but how? Aptitude goes mad

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jun 30, 2016 at 06:57:06PM -0400, Gene Heskett wrote: > On Thursday 30 June 2016 16:12:46 Henrique de Moraes Holschuh wrote: > > > grep -r Assume-Yes /etc > > 100% missing here, but lemme see what happens when I use the recursive -R > since