2008/8/8 mike <[EMAIL PROTECTED]>:
> mike wrote:
> Then I decided to try them on one of the flat
> screen monitors. On or off they reported the same. Even if I took the
> power cable off of the monitor (it was really really off) it was still
> reporting the same info.
Probably there is some powe
2008/5/15 L. V. Gandhi <[EMAIL PROTECTED]>:
> Where am I wrong
With the knowledge of the content of your files it is easier to
answer. Running the script in trace mode is the best thing to do.
Anyway, I see that there are two problems here (which may or may not
be related to your problem):
> fo
2008/4/25 Martin Fuzzey <[EMAIL PROTECTED]>:
> I could get ethernet assigned to eth0 by editing (rather than
> deleting) the persisten-net.rules file but I'm trying to create a disk
> image whichj can be installed on multiple machines (and could thus
> include appropriate module blacklists but
On 16/04/2008, martin f krafft <[EMAIL PROTECTED]> wrote:
> > > I don't understand what's happening, but maybe some packet has
> > > been filtered from the dump. Do you have a firewall? Does it
> > > reject any packet?
> >
> > Well, a packet filter runs on 213.203.238.82, but it allows SSH
>
On 10/04/2008, Bob Cox <[EMAIL PROTECTED]> wrote:
> On Thu, Apr 10, 2008 at 17:02:14 -0400, Brian McKee ([EMAIL PROTECTED]) wrote:
> >
> > I don't understand why 'host fred' doesn't return 127.0.0.1
I think host performs a DNS lookup, so maybe it bypasses the file
hosts altogether. ping, as Bob
On 09/04/2008, martin f krafft <[EMAIL PROTECTED]> wrote:
> every once in a while, I am stuck in a crap wifi network and often
> cannot even establish SSH connections. What happens is that the
> socket connection is established, but the client then just waits for
> a server reply during the DH
On 04/04/2008, Damon L. Chesser <[EMAIL PROTECTED]> wrote:
> Two systems: amd64 and i386. Both ran Sid. printer is networked with
> 192.168.200.150. Added printer via localhost:631 as a network (LPD) printer
> url is lpd://192.168.200.150/lpt1.
>
> The printer comes to life, the data light bli
On 29/03/2008, Eike Lantzsch <[EMAIL PROTECTED]> wrote:
> I suspected the firewall on the workstation and casually CTRL-ALT-F2'ed into
> a
> console. I logged on as the same user. Lo-and-behold: It works fine on the
> same machine in a text console. I went back to KDE and tried an xterm instead
On 24/03/2008, Jörg Becker <[EMAIL PROTECTED]> wrote:
> No, I don't find any error or warning message about my sdc2, but from
> device-mapper, in the kernel logs.
> Mar 19 16:19:41 gandalf kernel: Filesystem "dm-0": Disabling barriers, not
> supported by the underlying device
This sounds as a
On 19/03/2008, Jörg Becker <[EMAIL PROTECTED]> wrote:
> I also tried noauto in fstab an manually mount after boot. But with the same
> result: device is busy.
Does any error or warning message appear in kernel logs? Either at
startup, or when you try to mount the device?
Happy Easter
Bernardo
I think I've found out why the TCP hangs: someone messes with TCP
sequence numbers and get them wrong.
I studied some advanced features of TCP, and discovered the existence
of "selective acknowledgment" (SACK), which is a very nice feature, by
the way. By comparing packets at the two ends of the
On 17/03/2008, Jörg Becker <[EMAIL PROTECTED]> wrote:
> I cannot mount an usb hd when it was connected while switching on my machine.
> The message is the famous "already mounted or busy". I found many things in
> google, but nothing matches my problem.
>
> symptoms:
> - device is detected on
On 17/03/2008, Ken Irving <[EMAIL PROTECTED]> wrote:
> MTU is my standard WAG for this kind of thing, having had problems in
> the distant past.
I don't understand how MTU could be the culprit, as my problem seems
to be that a packet is not resent, and not that a packet doesn't
arrive. Anyway,
I have intermittent problems in transferring files between two
machines via scp. Symptomps are: when transferring a large file from
the server to the client, scp transfers a few Kbytes and then says
"stalled".
After a while I was having this problem, I tried to investigate it,
and captured the TCP
14 matches
Mail list logo
