From: "propaine" <propaine@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: why I didn't choose GRML
Date: Wed, 28 Jun 2006 15:25:03 -0400 [thread overview]
Message-ID: <002e01c69ae8$8ee3ecf0$6505a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <20060628182929.GC2302@asmodean>
Thanks very much!
----- Original Message -----
From: "Raul A. Gallegos" <raul@asmodean.net>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, June 28, 2006 2:29 PM
Subject: why I didn't choose GRML
> * propaine <propaine@verizon.net> [060628 10:14]:
> > Since I'm considering whether to upgrade Fedora or switch to something
else,
> > can you tell me why you decided that GRML is not for you? Thanks!
>
>
> I'd be happy to. But first let me say that I like GRML linux very much
> and am not interested in starting any sort of distro war here.
>
> I don't just use Linux as an end user. I run my own mail server, web
> server, ssh server, etc, you get the picture. Right now it seems that
> because GRML is based on Debian unstable there are sometimes problems.
> Packages are constantly updated which is the nature of the beast and
> from time to time a package might break your system. Because I run a
> production server I cannot run an unstable os. I've used Debian before
> and liked it very much and even considerred going back to it. However
> one of the main concerns here was time. I know how to install Fedora
> very quickly and needed to get up and running as quick as possible. Here
> is where GRML originally came into the picture. I love how you can
> simply pop the cd in and have a running Linux system right away. On
> three machies I tried it on both using software and hardware speakup
> synthesizers they worked from the get go. So, it's not GRML's fault
> really. It's just for my particular needs I need something which is not
> unstable in the way of packages.
>
> When I ran grml2hd it gave me fits and I had to manually tweak the
> script to make it possible for me to install. I forget the line number
> but it had to do with the code which checks the hard drive space
> available. There was a /1024 line which was throwing it off. So, I took
> that line out and hard coded in the space value so the script would
> continue.
>
> On top of that dovecot had to be tweaked quite a bit to get pop logins
> working right and really, the list goes on.
>
> This is not to say that GRML is bad and in fact I really love their mutt
> configureation style. I've actually used some of those settings for my
> muttrc now. I also like the fact that it boots so quickly although I
> realize that GRML is not the only one so take that for what it's worth.
>
> Hope this helps.
>
>
> --
> Raul A. Gallegos ... IliwSsmc
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.9.5/377 - Release Date: 6/27/2006
>
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
installed Fedora Core 5 but have questions Raul A. Gallegos
` Willem van der Walt
` Raul A. Gallegos
` Dawes, Stephen
` Raul A. Gallegos
` propaine
` why I didn't choose GRML Raul A. Gallegos
` propaine [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='002e01c69ae8$8ee3ecf0$6505a8c0@ALBERTLC7SN0ZA' \
--to=propaine@verizon.net \
--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).