on Mon, Apr 16, 2001 at 09:17:45PM -0400, D-Man ([EMAIL PROTECTED]) wrote:
> On Mon, Apr 16, 2001 at 05:29:42PM -0700, Phil Murphy wrote:
> |
> | Unless I convert my 486-sx to Debian, I'll never see those great
> | uptimes I see posted. :) I may do that just because I can. 486-sx,
> | 24 megs, s
D-Man wrote:
>
> On Mon, Apr 16, 2001 at 05:29:42PM -0700, Phil Murphy wrote:
> |
> | Unless I convert my 486-sx to Debian, I'll never see those great
> | uptimes I see posted. :) I may do that just because I can. 486-sx,
> | 24 megs, should run properly I would assume.
>
> 24MB RAM!! It shoul
On Mon, 16 Apr 2001, D-Man wrote:
>
> Any ideas on where I can find some RAM for it? It only has 2 slots,
> so I need to get some relatively large SIMMS.
You might have some luck with ComputerGeeks.com, they have some
decent prices on RAM and other used hardware. I've bought from
them quite a fe
On Mon, Apr 16, 2001 at 05:29:42PM -0700, Phil Murphy wrote:
|
| Unless I convert my 486-sx to Debian, I'll never see those great
| uptimes I see posted. :) I may do that just because I can. 486-sx,
| 24 megs, should run properly I would assume.
24MB RAM!! It should run great, I think. I have
รบ anseo (aka Farside)
- Original Message -
From: Rob Mahurin <[EMAIL PROTECTED]>
To: Glyn Millington <[EMAIL PROTECTED]>
Cc: Karsten M. Self ; ;
<[EMAIL PROTECTED]>
Sent: Friday, April 13, 2001 11:01 AM
Subject: Re: what i've learned, and explanation.
> X_Operating
On Fri, Apr 13, 2001 at 03:33:13PM -0400, D-Man wrote:
> Ditto. The list has enough volume as it is without adding an extra
> mail every day. Sending it to new subscribers (or on-demand) sounds
> like a good idea. I would also recommend making it fairly easy to
> find on the signup/archive web p
On Fri, 13 Apr 2001, [EMAIL PROTECTED] wrote:
> To that end, the rest of this document has the following structure:
>
> 1. How to Find (and Understand) Documentation
> 1.1 Figuring Out the Name of a Command
> apropos
> [tab][tab]
> ... ?
On Fri, Apr 13, 2001 at 02:01:24PM -0400, Rob Mahurin wrote:
| On Fri, Apr 13, 2001 at 09:05:43AM +0100, Glyn Millington wrote:
| > Seems to me that there is a problem for real newcomers with the docs -
| > for the very reasons that make them so useful to those who know their way
| > around a littl
i'm pro ! great teamwork people :)
-Original Message-
From: Carl Fink [mailto:[EMAIL PROTECTED]
Sent: vrijdag 13 april 2001 19:26
To: debian-user@lists.debian.org
Subject: Re: what i've learned, and explanation.
On Fri, Apr 13, 2001 at 09:05:43AM +0100, Glyn Millington wrote
On Fri, Apr 13, 2001 at 09:05:43AM +0100, Glyn Millington wrote:
> Seems to me that there is a problem for real newcomers with the docs -
> for the very reasons that make them so useful to those who know their way
> around a little. So much variety, so little time.
>
> What might help is a daily p
CF> And make the lists "only subscribers can post"?
IM> Please don't. IMHO mailists with 'only subscribers can post' policy is
IM> very unfriendly. At least it so for maillists which are aimed to
IM> provide support for users. Probably it can be OK for maillists like
IM> debian-devel but not for
Carl Fink wrote:
> On Fri, Apr 13, 2001 at 09:05:43AM +0100, Glyn Millington wrote:
>
> > What might help is a daily post to the list with a subject line
> > "NEW TO LIST? READ THIS!!"
>
> How about something automatically sent to anyone who subscribes to
> the list(s), ONCE, not every day? And m
CF> And make the lists "only subscribers can post"?
Please don't. IMHO mailists with 'only subscribers can post' policy is
very unfriendly. At least it so for maillists which are aimed to
provide support for users. Probably it can be OK for maillists like
debian-devel but not for debian-user. Man
On Fri, Apr 13, 2001 at 09:05:43AM +0100, Glyn Millington wrote:
> What might help is a daily post to the list with a subject line
> "NEW TO LIST? READ THIS!!"
How about something automatically sent to anyone who subscribes to
the list(s), ONCE, not every day? And make the lists "only
subscribe
[EMAIL PROTECTED] wrote:
...
> read for those who have little familiarlity with Linux. Personally, I
> don't think either of those resources were of any help to me until I was
> at least 3 months in, and I had a pretty solid background in general
> computing concepts, and the willingness to spend
will trillich <[EMAIL PROTECTED]> wrote:
>On Thu, Apr 12, 2001 at 01:16:50PM -0700, [EMAIL PROTECTED] wrote:
>> 4) Don't make any requests unless you can help to carry them out yourself.
>>(By that logic, I can't report bugs in Apache, since I can't fix them,
>>and I shouldn't request docum
On Thu, 12 Apr 2001, kmself@ix.netcom.com wrote:
> Second. This isn't win/lose. It's live/learn.
How true! So in that spirit, how did you set up that four-stroke kill
file ? ;-) Sounds really useful.
Seems to me that there is a problem for real newcomers with the docs -
for the very reasons
On Thursday 12 April 2001 06:20 pm, [EMAIL PROTECTED] wrote:
> Of course, we will have more and more people coming from the other
> paradigm, where there's absolutely no sense of community. Sometimes it
> may take an act of kindness on our part to get the ball rolling. Like
> I said, maybe I miss
on Thu, Apr 12, 2001 at 01:16:50PM -0700, [EMAIL PROTECTED] ([EMAIL PROTECTED])
wrote:
> Ok, ok, I give up. For what's it's worth, here's what I have learned from
> the day's events:
>
> 1) Don't respond to mail when you're already in a poor mood.
Excellent advice. I should have followed it my
On Thu, Apr 12, 2001 at 05:47:07PM -0500, will trillich wrote:
>
> Expect two to four months of "aaugh! Ever since the lobotomy i
> can't figure anything out" before you can start helping others
> here. (Your spouse will hate it nearly as much as you do.) Once
> you get past the "i feel lobotomize
On Thu, Apr 12, 2001 at 01:16:50PM -0700, [EMAIL PROTECTED] wrote:
> Ok, ok, I give up. For what's it's worth, here's what I have learned from
> the day's events:
> 2) In fact, don't respond to mail at all if you're going to be expressing
>your opinion, unless you've got some homies on the De
Having dealt with Lusers for far longer than I care to think about
I'm going to go ahead and give some opnions on the subject.
>Other important questions are:
>
>* Specifically, _what_ are people entitled to? Are they entitled
to
> demand that I spend my time catering to their needs? Are th
> A good, clear bug report is just as valuable as code, because it can
> point out where things are going wrong. A user who is completely
> new to an application can point out things which are overly obtuse,
> or gaps in the manual.
This is good-- but one thing I've run into as the rankest
On Thu, Apr 12, 2001 at 02:24:42PM -0700, [EMAIL PROTECTED] wrote:
...
> Anyway, like I said, I think it comes down to that basic question: What
> do you believe? Do you believe everyone is entitled to a free, stable OS
> regardless of their ability to contribute to it, or should Linux always be
>
[EMAIL PROTECTED] writes:
> Anyway, like I said, I think it comes down to that basic question:
> What do you believe? Do you believe everyone is entitled to a free,
> stable OS regardless of their ability to contribute to it, or should
> Linux always be something that is only usable if you have t
On Thu, Apr 12, 2001 at 05:09:06PM -0400, Alan Shutko wrote:
> There's a difference between making requests and acting "entitled" to
> help.
>
Well, it sort of depends on what you want Linux to be. If you want it to
become something that's easily accessible to all, because you feel that
everyone
[EMAIL PROTECTED] writes:
> 1) Don't respond to mail when you're already in a poor mood.
Always good advice. I wish I followed it more, but I do queue
outgoing messages in my mailer by default, so I normally have a bit of
cooling-off time.
> 2) In fact, don't respond to mail at all if you're go
27 matches
Mail list logo
