public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Nick Gawronski" <nick@nickgawronski.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: next etch net-install cd
Date: Fri, 13 Apr 2007 21:20:51 -0500	[thread overview]
Message-ID: <000f01c77e3b$88f8de90$250110ac@CHIHUAHUAD1> (raw)
In-Reply-To: <20070412210804.GA3433@gmx.net>

Hi, I agree, if you really want to upgrade you can always download and 
compile from source.  I think the etch net install CD should stay as close 
as to the release as possible.
----- Original Message ----- 
From: "Alex Snow" <alex_snow@gmx.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, April 12, 2007 4:08 PM
Subject: Re: next etch net-install cd


> Yeah but if the stock etch netinst cd contains a 2.6.18 kernel the
> speakup modified one should also.
> On Thu, Apr 12, 2007 at 04:50:36PM
> -0400, Jude DaShiell wrote:
>> Should not include kernel 2.6.18 since that kernel has been obsolete for
>> quite some time now.  If you download and run the debsecan package you'll
>> be able to read a current report as to what's obsolete on your system
>> along with other informative security-connected information about your
>> system.
>>
>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> -- 
> LILO, you've got me on my knees!
> -- David Black, dblack@pilot.njin.net, with apologies to Derek and the
> Dominos, and Werner Almsberger
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



      reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jude DaShiell
 ` Alex Snow
   ` Nick Gawronski [this message]

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='000f01c77e3b$88f8de90$250110ac@CHIHUAHUAD1' \
    --to=nick@nickgawronski.com \
    --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).