Re: quota memory HOG?

On Mon, 29 Jan 2001, Kurth Bemis wrote: > has anyone running debian 2.2r2 noticed anything funny with quota > support? I just installed 2.2r2 on a box and then compiled the 2.2.18 > kernel. after bootup my used RAM is up to ~85 megs! is this a "feature" > of quotas? does anyone have any ide

quota memory HOG?

has anyone running debian 2.2r2 noticed anything funny with quota support? I just installed 2.2r2 on a box and then compiled the 2.2.18 kernel. after bootup my used RAM is up to ~85 megs! is this a "feature" of quotas? does anyone have any ideas whats eating all my RAM? ~kurth **

Re: uppercase?

On Mon, 29 Jan 2001, Kurth Bemis wrote: > thanks to Microsoft and their wisdom i now have ~200 files that used to be > all lowercase...now their all caps. their web sites so now everything is > broken. does anyone know or a util or a script that will let me make all > the filenames lowercase?

uppercase?

thanks to Microsoft and their wisdom i now have ~200 files that used to be all lowercase...now their all caps. their web sites so now everything is broken. does anyone know or a util or a script that will let me make all the filenames lowercase? ~kurth *

Pointless debate about "correctness" (was: Procmail front-end?)

On Mon, 29 Jan 2001, Kevin D. Clark wrote: > I realize this is nit-picking, but... Subject line changed accordingly. ;-) > I have to disagree with the Camel book here. A program is correct when it > is correct, and no sooner. The point was, how do you define "correct"? Just because somet

Re: Procmail front-end?

[EMAIL PROTECTED] writes: > Hey, as the Camel says, "a Perl script is 'correct' if it gets the job done > before your boss fires you". I've always loved that bit; it captures quite a > bit about the reasons behind software in just a few words. If the script > worked on what you needed to con

Re: Procmail front-end?

On Mon, 29 Jan 2001, Kevin D. Clark wrote: > Actually, somebody who was braver than me ran it on a body of ~1.2 > million lines of production C++ code ... and only found 2 bugs ... > After that, I didn't worry about it too much anymore. (-: Hey, as the Camel says, "a Perl script is 'correct' i

Re: Procmail front-end?

[EMAIL PROTECTED] writes: > It almost sounded as if you didn't trust it or > something! ;-) Actually, somebody who was braver than me ran it on a body of ~1.2 million lines of production C++ code with thousands of references to sprintf() and only found 2 bugs (both of which were made to be im

Re: Procmail front-end?

On Mon, 29 Jan 2001, Kevin D. Clark wrote: >> Geez, put enough disclaimers on that? > > I probably should mention that, now that I'm older and wiser, I probably > wouldn't have implemented that hack in that way anymore. Hey, don't get me wrong, I'm not commenting on the quality of the code (

Re: Procmail front-end?

[EMAIL PROTECTED] writes: > On Mon, 29 Jan 2001, Kevin D. Clark wrote: > >> Anyways, here's my contribution to this type of zaniness. > > Geez, put enough disclaimers on that? I probably should mention that, now that I'm older and wiser, I probably wouldn't have implemented that hack in that

Re: Procmail front-end?

Mark Komarinski said: > When people ask me about writing for Access vs. MySQL, my best comparison > is that MS products are focus on how things look on the screen versus > how they act. MySQL (and most other UNIX tools) are focus on how things > work and act. A UI is left as an exercise to the r

Re: Procmail front-end?

Paul Lussier said: > In a message dated: Mon, 29 Jan 2001 10:19:55 EST > Jeffry Smith said: > > >One thing I'm still waiting for in any e-mail system that includes filtering > >is a tie-in to procmail. Why write your own filtering module instead of a > >front end to procmail (hm. Tie exmh to

Re: Procmail front-end?

On Mon, 29 Jan 2001, Kevin D. Clark wrote: > Anyways, here's my contribution to this type of zaniness. Geez, put enough disclaimers on that? "Do not taunt Happy-Fun Ball." ;-) -- Ben Scott <[EMAIL PROTECTED]> Net Technologies, Inc. Voice: (800)905-3049 x18 Fax:

RE: It's the amazing...

On Mon, 29 Jan 2001, Tony Lambiris wrote: > I feel sorry for the businesses who rely alot on reselling their DSL. We're less worried about the reseller business than we are our customers' (and our own) Internet connections. We are basically a service company; while the income from selling DSL

Re: Procmail front-end?

[EMAIL PROTECTED] writes: > Yeah, but WHY? Obviously Greg had too much time on his hands... Because it was there. Anyways, here's my contribution to this type of zaniness. --kevin PS I wrote this because I *didn't* have enough time on my hands. #!/usr/bin/perl # Author: Kevin D. Clark

Re: Procmail front-end?

When people ask me about writing for Access vs. MySQL, my best comparison is that MS products are focus on how things look on the screen versus how they act. MySQL (and most other UNIX tools) are focus on how things work and act. A UI is left as an exercise to the reader, or is at least the seco

It's the amazing...

Benjamin Scott <[EMAIL PROTECTED]> said: >>> Vitts says they're back in business this week. It was widely reported this morning - and I heard a blurb on the news on WZID(FM) - that apparently they were able to secure some last-minute funding from an unnamed source that will permit them to stay

Re: Procmail front-end?

In a message dated: Mon, 29 Jan 2001 10:19:55 EST Jeffry Smith said: >One thing I'm still waiting for in any e-mail system that includes filtering >is a tie-in to procmail. Why write your own filtering module instead of a >front end to procmail (hm. Tie exmh to dotfile-procmail, since both ar

RE: Procmail front-end?

A good example of Ben's point might be M$ Access. It offers a pretty series of boxes you can connect w/ lines to choose items out of column A to match with column B while avoiding column C, etc etc. When you're all done it creates an ugly SQL statement behind the scenes to do the work. Although

Re: Procmail front-end?

[EMAIL PROTECTED] writes: > Maybe I'm just a cynical bastard (okay, no "maybe" about it), but every time > I've seen such a front-end for anything, I see two groups of people: Those who > do not want to learn the underlying tool and just want the GUI, and those who > know that you cannot progr

RE: It's the amazing...

I feel sorry for the businesses who rely alot on reselling their DSL. I know I was considering to purchase DSL from them (before they announced they were closing up shop), but now I'm having second thoughts about the whole situation. I'm sure I'm not the only one. [+] Tony Lambiris [[EMAIL PROTEC

Re: Procmail front-end?

On Mon, 29 Jan 2001, Kevin D. Clark wrote: > > [EMAIL PROTECTED] writes: > > > There are countless other uses for both sed > > > #!/bin/sed -f > # dc.sed - an arbitrary precision RPN calculator > # Created by Greg Ubben <[EMAIL PROTECTED]> early 1995, late 1996 Yeah, but WHY? Obviously Gr

Re: Procmail front-end?

On Mon, 29 Jan 2001, Jeffry Smith wrote: > Some basic tools that would enable them to make simple choices, AND SHOW > THEM THE COMMAND LINE EQUIVILENT (i.e. learn by example) would be > extremely useful. Maybe I'm just a cynical bastard (okay, no "maybe" about it), but every time I've seen such

It's the amazing...

Step right up, step right up, for the greatest spectacle this side of the Mississippi river. The amazing -- Astounding! -- Incredible! -- disappearing -- reappearing -- DSL company! Vitts says they're back in business this week. http://www.vitts.com/ Anyone want to start a pool on

Re: Procmail front-end?

Benjamin Scott said: > On Sun, 28 Jan 2001, Joshua S. Freeman wrote: > > I thought it would be cool if there was a GUI frontend for sed and for > > awk.. if for no other reason to gain a better understanding of just what > > these two tools are for and how they are used... > > I recommend the d

Procmail front-end?

Kenneth E. Lussier writes: > Does anyone know of a GUI frontend for procmail? ... Try smearing jam on the keyboard, that should make it gooey. But, all seriousness aside, while we're at it, how about a GUI frontend for Windows?

RE: apt-get probs after perl upgrade

Hi, If it's only a configuration problem you can try: dpkg-reconfigure Warren -Original Message- From: Adam Wendt [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 28, 2001 10:03 PM To: Derek Doucette Cc: Gnhlug Subject: Re: apt-get probs after perl upgrade you should use the .debs f

Re: Is h/w to blame?

Bruce McCulley wrote: >> FWIW, I've seen different o/s architectures respond differently to >> h/w faults, so not crashing under Linux would not prove the h/w is >> clean. Incidentally, that raises an interesting question for discussion, >> is it better for the o/s to be fault-tolerant and run t

RE: Procmail front-end?

IMHO, a GUI for sed or awk would actually HINDER learning these tools (GUIs are usually designed to let you use something without actually understanding it). The best way to learn them is to have an actual purpose for them, so that you can put it into context. In my first few years playing with l

Re: Procmail front-end?

[EMAIL PROTECTED] writes: > There are countless other uses for both sed #!/bin/sed -f # dc.sed - an arbitrary precision RPN calculator # Created by Greg Ubben <[EMAIL PROTECTED]> early 1995, late 1996 # # Dedicated to MAC's memory of the IBM 1620 ("CADET") computer. # @(#)GSU dc.sed 1.0 27

Re: Procmail front-end?

In a message dated: Sun, 28 Jan 2001 12:41:37 EST "Joshua S. Freeman" said: >while we're on the subject, i was walking in the arnold arboretum this >morning.. thinking about the linux professional institute >certification.. i downloaded rute last night (a cert. manual..) from >rute.sourceforge.ne

Re: Is h/w to blame? (was: Re: MS is down again?)

On Mon, 29 Jan 2001, Bruce McCulley wrote: > That's the kind of thing that makes me wonder if the real culprit is h/w. With NT, who can tell? The system's been running fine since we hooked it up the LAN, so there is nothing to trouble-shoot. > I started wondering about that when I attended a

Re: Procmail front-end?

On Sun, 28 Jan 2001, Joshua S. Freeman wrote: > I thought it would be cool if there was a GUI frontend for sed and for > awk.. if for no other reason to gain a better understanding of just what > these two tools are for and how they are used... I recommend the dead-tree front-end entitled "sed

Is h/w to blame? (was: Re: MS is down again?)

> Benjamin Scott said: > > > On Fri, 26 Jan 2001, Jeffry Smith wrote: > > > Hey, they never said there were any apps running! > > > > FWIW, we once setup an NT 4.0 SP6 server at a customer site, but due to a > > SNAFU on their part, couldn't hook it up to the LAN for a couple weeks. All > > i

Re: Calendar...

Our thanks to you Bob for such a speedy (fix) recovery upon your return and a Big thank you for just maintaining the calendar for us. Jerry >My apologies to all. The calendar thought every year was 2000. This has >been fixed. > >Bob Knowles >=== >If Bill Gates had