public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Rob Hudson" <captinlogic@gmail.com>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: mirroring (was: slackware)
Date: Sun, 29 Jun 2014 12:03:36 -0500	[thread overview]
Message-ID: <4F37EB5263A0410A832EB44007925F76@train> (raw)
In-Reply-To: <53B03D77.10207@math.wisc.edu>

Okay, looks simple enough. Thanks for the tips.
----- Original Message ----- 
From: "John G. Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." 
<speakup@linux-speakup.org>
Sent: Sunday, June 29, 2014 11:23 AM
Subject: mirroring (was: slackware)


>I used apt-cacherng. I'm not saying that's the best tool. I do recall that 
>it took me about one afternoon to set up.  So this is not a true mirror. 
>But it automatically downloads packages to it's own cache whenever you ask 
>for them. Next time, you don't have to download them again. But what you do 
>is point the machine itself to it's own cache and have it  update all 
>packages each night. Therefore, the cache on the mirror machine is always 
>up to date. When you do an install, you install from the mirror. On a 
>debian install, you select 1 when the list of mirrors come up and this 
>allows you to enter the URL for your cache. It decreased the time it takes 
>me to install debian from 2 to 4 hours to about 20 minutes.
>
> I have a gig network in my house but I found that didn't make that much 
> difference. I had a 100mb ethernet card in my cache machine and I replaced 
> it with a 1000mb card. But it didn't seem to make any difference. So I am 
> guessing the download time is no longer the bottleneck. Unpacking the 
> packages and writing  them to disk is now the limiting factor.
>
>
> On 6/29/2014 11:02 AM, Rob Hudson wrote:
>> I have a few machines like that sitting around, and have been considering 
>> setting up my own local debian mirror for situations when I don't have an 
>> outside connection. Is it just a matter of using wget on something like 
>> us.debian.org? Or is there a master archive that can be downloaded?
>> ----- Original Message ----- From: "John G. Heim" <jheim@math.wisc.edu>
>> To: "Speakup is a screen review system for Linux." 
>> <speakup@linux-speakup.org>
>> Sent: Sunday, June 29, 2014 10:12 AM
>> Subject: Re: slackware on a fast machine
>>
>>
>>> I suspect that when speakup wasn't working with a particular keyboard it 
>>> wasn't the keboard itself. Probably speakup wasn't loaded. There could 
>>> be timing issues between USB and PS2 keyboards but I don't think that 
>>> speakup itself cares about the kind of keyboard you use.
>>>
>>> How short on hardware are you? When I had to deal with a slow internet 
>>> connection, I set up my own debian mirror. I have no idea how hard that 
>>> is to do in slackware. But for a mirror that you are going to use 
>>> yourself, all you need is an old P4 or even a 486. I think the debian 
>>> mirror takes about 16Gb of space. I don't know how things are where you 
>>> live but around here, machines like that are free for the taking. People 
>>> give them away to avoid paying the recycling fee.
>>>
>>> I'll bet if you ask around at your local maker space or on the local 
>>> lug, you'll get offers for a dozen machines that could serve as a 
>>> mirror.
>>>
>>> On 6/29/2014 6:48 AM, Jude DaShiell wrote:
>>>> I just remembered something and why this is I can't figure.  The
>>>> speakup_ltlk module in speakup.s in slackware and possibly also in the
>>>> Linux kernel unless it was patched requires a ps/2 keyboard to be used 
>>>> to
>>>> boot up the computer.  I remember on an earlier slackware installation
>>>> switching out keyboards to a usb keyboard and I couldn't get speech
>>>> working when trying to boot into slackware until I switched that USB
>>>> keyboard out for a ps/2 again.  In that move, all the ps/2 keyboards I
>>>> have also got donated.  Slackware does respond to a three-fingered 
>>>> salute
>>>> on the usb keyboard I have and does respond to typing on that keyboard
>>>> otherwise but that's as far as I can go here.  This is using an amd k8
>>>> athelon machine too.  If I remember properly, this also happened on an
>>>> intel machine I was using.  Now I'm wondering if this happens to any 
>>>> other
>>>> slackware speakup users using usb keyboards.  It could be my particular
>>>> brand keyboard is the problem or it could be this effects more than one
>>>> brand and model of usb keyboard I don't know.  Aside from that, I can't
>>>> get any audible indication as to when the boot: prompt comes up on the
>>>> screen so I don't know if I ever keyed in the boot parameters at the 
>>>> right
>>>> time during the past few days either.  When I get slackware any more, I
>>>> use bittorrent and let that run overnight and burn DVD's in the 
>>>> afternoon
>>>> of the next day since the distributor of slackware boxed sets will not
>>>> package those shrink wrapped sets well enough to prevent breakage of 
>>>> cases
>>>> and sometimes disks inside those cases and this is happening for people
>>>> who have a slackware subscription.
>>>>
>>>> I'll put archlinux on this 80GB disk and hope Slackware improves a few
>>>> things eventually.  The faq files on slackware.com are outdated in that
>>>> they don't refelect slackware's move from multiple floppy disk
>>>> distribution to cd's and DVD's distributions.  It is unfortunate the
>>>> linux-slackware email list on yahoogroups.com had to be closed down 
>>>> since
>>>> it was being misused by people who didn't even know what Linux is let
>>>> alone the slackware distribution is but list moderators apparently
>>>> couldn't manage those problems.  I could restart that mailing list and 
>>>> may
>>>> be able to moderate it, I don't know if a lynx user on linux can do the
>>>> necessary web work on yahoogroups to moderate lists yet.  I have time
>>>> since retiring from Southern Maryland and the Navy but that could 
>>>> change
>>>> in a while too.
>>>>
>>>>
>>>>
>>>> jude <jdashiel@shellworld.net>
>>>>
>>>> _______________________________________________
>>>> Speakup mailing list
>>>> Speakup@linux-speakup.org
>>>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@linux-speakup.org
>>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 


  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 slackware on a fast machine Jude DaShiell
 ` John G. Heim
   ` Rob Hudson
     ` mirroring (was: slackware) John G. Heim
       ` Rob Hudson [this message]
         ` Gregory Nowak
           ` mirroring John G. Heim

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=4F37EB5263A0410A832EB44007925F76@train \
    --to=captinlogic@gmail.com \
    --cc=speakup@linux-speakup.org \
    /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).