On Mon, 07 Apr 2014 00:47:18 -0400 (EDT), Chris Bannister wrote:
>
> TBH, I didn't see any evidence of a broken thread. Mutt shows a broken
> thread with an asterisk in the arrow symbol.
>
> A poster shouldn't have to jump through hoops to make the archives look
> good, IMHO.
>
> IOW, how the ar
On Sun, Apr 06, 2014 at 10:06:04AM -0400, Stephen Powell wrote:
> On Sat, 05 Apr 2014 20:55:12 -0400 (EDT), Tom Furie wrote:
> >
> > Thread wasn't broken here. The References: header in Robert's mail
> > indicates that it was indeed a reply (to his original post on this
> > thread).
>
> Perhaps I
On Sat, 05 Apr 2014 20:55:12 -0400 (EDT), Tom Furie wrote:
>
> Thread wasn't broken here. The References: header in Robert's mail
> indicates that it was indeed a reply (to his original post on this
> thread).
Perhaps I need to explain what I mean by "broken thread".
The original post was in Marc
On Sat, Apr 05, 2014 at 08:05:09PM -0400, Stephen Powell wrote:
> First of all, you've broken the thread. The thread was broken once
> already by the March / April forced break at the end of the month.
> You can't help that. But this time, you've broken it yourself by
> starting a new thread.
T
On Sat, 05 Apr 2014 13:26:44 -0400 (EDT), Robert Holtzman wrote:
>
> For a while it looked like a bad cable as I was able to connect on a
> different one from the same router. The connection lasted long enough to
> d/l an update. Then I closed the connection. Today none of the cables
> from the ro
On Sun, Mar 30, 2014 at 10:31:54PM -0700, Robert Holtzman wrote:
> I seem to remember this happening after an update but I'm not positive.
> It did work before. My wireless connection continues to work.
>
> Looked at the usual suspects, /etc/ network/interfaces, /etc/resolv.conf,
> etc but everyt
On 20140402_2236-0700, Robert Holtzman wrote:
> On Sun, Mar 30, 2014 at 10:31:54PM -0700, Robert Holtzman wrote:
> > I seem to remember this happening after an update but I'm not positive.
> > It did work before. My wireless connection continues to work.
> >
> > Looked at the usual suspects, /etc/
On Wed 02 Apr 2014 at 20:52:55 -0400, Stephen Powell wrote:
> Well, you are right about wheezy. At least on the i386 architecture,
> the file does get regenerated at the next boot if you erase it. I
> just tried it on a wheezy system I have. But as for jessie, I don't
> think that the "bug" you
On Sun, Mar 30, 2014 at 10:31:54PM -0700, Robert Holtzman wrote:
> I seem to remember this happening after an update but I'm not positive.
> It did work before. My wireless connection continues to work.
>
> Looked at the usual suspects, /etc/ network/interfaces, /etc/resolv.conf,
> etc but everyt
On Wed, 02 Apr 2014 13:33:58 -0400 (EDT), Brian wrote:
>
> On Tue 01 Apr 2014 at 21:24:24 -0400, Stephen Powell wrote:
>>
>> On Tue, 01 Apr 2014 05:08:12 -0400 (EDT), Brian wrote:
>>>
>>> Deleting the file is quicker and less hassle. It is rewritten at the
>>> next boot.
>>
>> That used to be t
On Tue 01 Apr 2014 at 21:24:24 -0400, Stephen Powell wrote:
> On Tue, 01 Apr 2014 05:08:12 -0400 (EDT), Brian wrote:
> >
> > Deleting the file is quicker and less hassle. It is rewritten at the
> > next boot.
>
> That used to be true, but it isn't anymore. The file no longer gets
> re-created d
On Tue, 01 Apr 2014 05:08:12 -0400 (EDT), Brian wrote:
>
> On Mon 31 Mar 2014 at 20:47:56 -0400, Stephen Powell wrote:
>>
>> Did you do anything that might have changed a MAC address? Like changing
>> PC card Ethernet adapters, for example? Or replacing a motherboard that
>> has a built-in Ethe
Am 01.04.2014 um 11:58 schrieb Chris Bannister :
> On Tue, Apr 01, 2014 at 09:52:12AM +0200, Helmut Wollmersdorfer wrote:
>>
>>
>> root@dev:/home/helmutw# apt-cache search lshw
>> lshw-gtk - graphical information about hardware configuration
>> lshw - information about hardware configuration
>
On Tue, Apr 01, 2014 at 09:52:12AM +0200, Helmut Wollmersdorfer wrote:
>
> Am 01.04.2014 um 04:00 schrieb Charles Kroeger :
>
> > On Mon, 31 Mar 2014 10:30:03 +0200
> > François Patte wrote:
> >
> >> # lshw -class network
> >
> > root@mundo:/home/charles# lshw -class network
> > bash: lshw: c
On Mon, Mar 31, 2014 at 7:31 AM, Robert Holtzman wrote:
> I seem to remember this happening after an update but I'm not positive.
> It did work before. My wireless connection continues to work.
>
> Looked at the usual suspects, /etc/ network/interfaces, /etc/resolv.conf,
> etc but everything looke
On Mon 31 Mar 2014 at 20:47:56 -0400, Stephen Powell wrote:
>> Did you do anything that might have changed a MAC address? Like
>> changing PC card Ethernet adapters, for example? Or replacing a
>> motherboard that has a built-in Ethernet adapter? The correspondence
>> between MAC addresses a
On Mon 31 Mar 2014 at 20:47:56 -0400, Stephen Powell wrote:
> Did you do anything that might have changed a MAC address? Like changing
> PC card Ethernet adapters, for example? Or replacing a motherboard that
> has a built-in Ethernet adapter? The correspondence between
> MAC addresses and inte
Am 01.04.2014 um 04:00 schrieb Charles Kroeger :
> On Mon, 31 Mar 2014 10:30:03 +0200
> François Patte wrote:
>
>> # lshw -class network
>
> root@mundo:/home/charles# lshw -class network
> bash: lshw: command not found
root@dev:/home/helmutw# apt-cache search lshw
lshw-gtk - graphical inform
On Mon, 31 Mar 2014 10:30:03 +0200
François Patte wrote:
> # lshw -class network
root@mundo:/home/charles# lshw -class network
bash: lshw: command not found
--
CK
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@li
On Mon, 31 Mar 2014 01:31:54 -0400 (EDT), Robert Holtzman wrote:
>
> I seem to remember this happening after an update but I'm not positive.
> It did work before. My wireless connection continues to work.
>
> Looked at the usual suspects, /etc/network/interfaces, /etc/resolv.conf,
> etc., but e
On Du, 30 mar 14, 22:31:54, Robert Holtzman wrote:
> I seem to remember this happening after an update but I'm not positive.
> It did work before. My wireless connection continues to work.
>
> Looked at the usual suspects, /etc/ network/interfaces, /etc/resolv.conf,
> etc but everything looked th
Le 31/03/2014 07:31, Robert Holtzman a écrit :
> I seem to remember this happening after an update but I'm not positive.
> It did work before. My wireless connection continues to work.
>
> Looked at the usual suspects, /etc/ network/interfaces, /etc/resolv.conf,
> etc but everything looked the sa
On 03/31/2014 01:31 AM, Robert Holtzman wrote:
I seem to remember this happening after an update but I'm not positive.
It did work before. My wireless connection continues to work.
Robert, it might be that the upgrade knocked you into using eth1. Try
opening a new ethernet connection using eth
23 matches
Mail list logo
