public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: linux still dying;potential errors
Date: Fri, 18 May 2007 23:06:23 -0700	[thread overview]
Message-ID: <20070519060623.GA10482@localhost.localdomain> (raw)
In-Reply-To: <000c01c799cf$cfeacca0$6401a8c0@laptop>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok, it seems like we've got some confusion when it comes to netmasks with
standard dhcp query addresses. The log snipit he posted said nothing
at all about the netmask, and no, 255.255.255.255 isn't the netmask
he's using, (never mind the fact it isn't a netmask to begin with, at
least not for a class c address).

Greg



On Fri, May 18, 2007 at 11:40:21PM -0500, Shawn Keen wrote:
> it didn't show that  to be so in that log. it showed
> 255.255.255.255
> 

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGTpPf7s9z/XlyUyARAofQAJ9S0+0PicK2mAdz8d3NxCF3dosXAgCgmHLG
uVbk9JYzDp6AppQODe3s/XM=
=9Z2D
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Littlefield, Tyler
 ` Richard Villa
   ` Gregory Nowak
 ` Cody
   ` Gregory Nowak
     ` Cody
     ` Littlefield, Tyler
   ` Littlefield, Tyler
     ` Shawn Keen
       ` Gregory Nowak [this message]
       ` Richard Villa
 ` Ralph W. Reid
   ` Littlefield, Tyler
     ` Cody
       ` Littlefield, Tyler
     ` Ralph W. Reid

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070519060623.GA10482@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).