public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: help with compilation?
Date: Sat, 7 Jan 2006 11:54:08 -0800	[thread overview]
Message-ID: <002701c613c4$1f962850$2cc69245@dataplus4puarg> (raw)
In-Reply-To: <000b01c613c3$d6f18220$2cc69245@dataplus4puarg>

btw, I don't use grex.org, I had looked at there services, and had thought 
about it, but my friend told me they weren't worth signing up with. I am 
going through someone else on this list who is allowing me a shell account 
until I get my linux system set up.
Tyler Littlefield.
Check out our website:
http://tysplace.the-leetest.net
check out my blog:
livejournal.com/~tylerrl
[my programs don't have bugs, just randomly added features]
[failure is not an option, it comes bundled with windows!]
----- Original Message ----- 
From: "tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, January 07, 2006 11:52 AM
Subject: Re: help with compilation?


>I have a frostmud account that is letting me use mud, but they don't allow 
>for anything else.
> That is where I am hosting my mud from.
>
> Tyler Littlefield.
> Check out our website:
> http://tysplace.the-leetest.net
> check out my blog:
> livejournal.com/~tylerrl
> [my programs don't have bugs, just randomly added features]
> [failure is not an option, it comes bundled with windows!]
> ----- Original Message ----- 
> From: "Lorenzo Taylor" <lorenzo@taylor.homelinux.net>
> To: "Speakup is a screen review system for Linux." 
> <speakup@braille.uwo.ca>
> Sent: Saturday, January 07, 2006 10:38 AM
> Subject: Re: help with compilation?
>
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I think the problem may be with your shell account.  If I understand 
>> grex.org's
>> policies correctly,
>>
>> a) They only allow 1MB of storage space in your home directory.
>> B) They don't allow background processes of any kind including server
>> applications.
>>
>> I think most likely you are running into the first of these problems. 
>> The
>> combined space used by the tarball and it's untarred directory is most 
>> likely
>> larger than 1Mb.
>>
>> HTH,
>> Lorenzo
>> - -- 
>> Be careful of reading health books, you might die of a misprint.
>> -- Mark Twain
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.2 (GNU/Linux)
>>
>> iD8DBQFDwAqUG9IpekrhBfIRAkY4AJ9DaKt3+nl3/Elg7UfEEusWV8wjxwCgx1DQ
>> QqZWvoo//8kSdjqAYYT7Jpw=
>> =x+/Y
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 



      reply	other threads:[~ UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 tyler
 ` Jim Grimsby
   ` tyler
     ` Gregory Nowak
       ` tyler
       ` Sina Bahram
         ` tyler
           ` Sina Bahram
       ` Butch Bussen
         ` tyler
   ` tyler
 ` Lorenzo Taylor
   ` tyler
     ` tyler [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='002701c613c4$1f962850$2cc69245@dataplus4puarg' \
    --to=compgeek13@gmail.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).