[LUGSB] text editors for 4+ GB files

Vinay Pai vinay at cs.sunysb.edu
Sat Nov 20 16:43:31 EST 2004


I think you're better off either writing a program, or using tools like 
grep, awk, sed and so on.  Unless I've musunderstood your intent 
completely, some simple back-of-the envelope calculations show that you're 
going to be spending an awful lot of time.  Assume every line is 80 
characters long, a screen is 50 lines and you can scan a whole screenful 
in a second, you're talking 4e9/(80*50)=1000000 seconds, or 278 hours. 
Not to mention the fact that you're likely to miss what you're looking for 
when you're doing this mindnumbingly boring job for days on end.

On Sat, 20 Nov 2004, Lucas Carey wrote:

> I guess, more accurately, I want a text reader. I have a small output 
> file in which all results have been verified, and a larger run which is 
> a superset of the smaller one. I want to be able to scan through the 
> large output file and check them against the smaller one, by eye. Diff 
> won't work due to differences in ordreing of results with similar 
> scores. I know I could use split to break up the file, but I really 
> shouldn't have to, seeing as how the file does fit entirely in ram. When 
> I open it up in vim the RSIZE jumps to ~140MB and just sits there 
> alternating between wait & run states, using 80-90% cpu. I would also 
> like to be able to look at the results. Its a list of genes w/thier 
> similarity scores & alignments, and I'd liked to be able to look through 
> it for interesting genes. -Lucas
>
>> What exactly are you trying to do with the file? Are you sure you really
>> want a text editor?
>
> _______________________________________________
> lugsb mailing list
> lugsb at fsl.cs.sunysb.edu
> http://www.fsl.cs.sunysb.edu/mailman/listinfo/lugsb
>
>From cwright at cs.sunysb.edu Sun Nov 21 13:34:31 2004
Received: from localhost.localdomain
	(IDENT:RHwClJF3g2V5nrVOg1Te9Lwx2b/hP5As at localhost.localdomain [127.0.0.1])
	iALIYVWW014498
	for <lugsb at fsl.cs.sunysb.edu>; Sun, 21 Nov 2004 13:34:31 -0500
From: "Charles P. Wright" <cwright at cs.sunysb.edu>
To: lugsb at fsl.cs.sunysb.edu
In-Reply-To: <1100609152.10668.2.camel at localhost.localdomain>
References: <1100609152.10668.2.camel at localhost.localdomain>
Content-Type: text/plain
Date: Sun, 21 Nov 2004 13:33:47 -0500
Message-Id: <1101062027.844.2.camel at localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.2 (2.0.2-3) 
Content-Transfer-Encoding: 7bit
Subject: [LUGSB] Re: CUPS Printing
X-BeenThere: lugsb at fsl.cs.sunysb.edu
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Linux Users Group at Stony Brook <lugsb at fsl.cs.sunysb.edu>
List-Id: Linux Users Group at Stony Brook <lugsb.fsl.cs.sunysb.edu>
List-Unsubscribe: <http://www.fsl.cs.sunysb.edu/mailman/listinfo/lugsb>,
	<mailto:lugsb-request at fsl.cs.sunysb.edu?subject=unsubscribe>
List-Archive: <http://lists.fsl.cs.sunysb.edu/pipermail/lugsb>
List-Post: <mailto:lugsb at fsl.cs.sunysb.edu>
List-Help: <mailto:lugsb-request at fsl.cs.sunysb.edu?subject=help>
List-Subscribe: <http://www.fsl.cs.sunysb.edu/mailman/listinfo/lugsb>,
	<mailto:lugsb-request at fsl.cs.sunysb.edu?subject=subscribe>
X-List-Received-Date: Sun, 21 Nov 2004 18:34:31 -0000

I finally figured this out thanks to this useful SUSE help page.

http://portal.suse.com/sdb/en/2003/06/jsmeix_print-cups-filters.html

Basically, the solution that I needed was to create a generic Postscript
printer and then hack the generated ppd file in /etc/cups/ppd by
replacing the cupsFilter line with this:

*cupsFilter:    "application/vnd.cups-postscript
0 /usr/local/Brother/lpd/filterMFC6800"

The /usr/local/Brother/lpd/filterMFC6800 line corresponds directly to
the if= line that I had in /etc/printcap.

Chip

On Tue, 2004-11-16 at 07:45 -0500, Charles P. Wright wrote:
> I have a Brother MFC-6800 printer.  Brother provides drivers for the
> printer for lpr (it is essentially an if= line in /etc/printcap).
> 
> I just installed Fedora Core 3.  Does anyone know how to tell CUPS to
> run the job through the Brother filter?
> 
> Thanks,
> Chip



More information about the lugsb mailing list