Re: Need linux for alpha
On Wed, Jun 24, 1998 at 03:33:47PM -0400, Will Lowe wrote: > My lab has an old Alpha 3000 sitting around (at least that's what the case > says) that's not being used for anything, and for various reasons we're > in search of a new OS to run on it. > > Can Alpha linux run here? Is there a decent release of it? I'm under the > impression that our alpha port isn't quite ready.. unless something drastic happened very recently, Linux will NOT run on any of the DEC 3000 series. for more info, check out http://www.azstarnet.com/~axplinux/FAQ-4.html besides, depending on the model you have, that machine is really old (circa 1993 and 1994) so you won't get any benefits (such as performance) other than the novelty of running Linux on Alpha. --andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dump again
On Thu, May 28, 1998 at 04:50:05PM -0400, Behan Webster wrote: > > That's actually what I tried first. I get the same results with -i. > > > dragon:~/tmp# restore -i -v -f ~/prev/dragon.hda2.19980523.0 > Verify tape and initialize maps > Tape block size is 32 > Dump date: Sat May 23 03:44:19 1998 > Dumped from: the epoch > Level 0 dump of /home on dragon:/dev/hda2 > Label: none > Extract directories from tape > Initialize symbol table. > restore > add bcwhite/longtmp/testfuncs.cpp > bad name to addentry ./bcwhite/longtmp > abort? [yn] n > warning: ./bcwhite/longtmp: No such file or directory > bad name to addentry ./bcwhite/longtmp/testfuncs.cpp > abort? [yn] n > restore > extract > Extract requested files > You have not read any tapes yet. > Unless you know which volume your file(s) are on you should start > with the last volume and work towards the first. > Specify next volume #: 1 > You have read volumes: 1 > Specify next volume #: 1 > You have read volumes: 1 > Specify next volume #: dragon:~/tmp# > try this: restore -if /dev/ restore > cd bcwhite/longtmp restore > add testfuncs.cpp restore > extract at the "Specify next volume" prompt, enter 1 or 0 (i don't recall which one works). this will restore that file (and the directory tree it's in) into the current working directory of where you originally executed restore. --andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [OFF-TOPIC] Pentium II performance?
"Marcelo E. Magallon" wrote: -> -> On 16 Feb 1998, Ben Pfaff wrote: -> -> > Can you point me to the source code for the benchmark? I can run it -> > on my PII/233 for comparison if you want. -> -> and Alex Yukhimets: -> -> > Same here, only with PII/300. -> -> You can find the source code here: -> ->http://www.efis.ucr.ac.cr/~mmagallo/flops_p.c -> -> This is extracted from the flops program written by Al Burto -> ([EMAIL PROTECTED]). This is just module 1, using 7 sums, 6 mults, 1 div. -> I think I got this from http://www.hensa.ac.uk/parallel/ or netlib. -> -> Compiling with gcc -O2 gives a bit more than 39 on the PII. Using egcc -> (1.0.1-0.3) with -mpentiumpro gives almost 40.9 -> -> Many thanks in advance. -> -> Marcelo -> a better (and much more thorough) benchmark can be found at: http://gwyn.tux.org/~mayer/linux/bmark.html the benchmark displays integer, floating point, and some of the memory system performance. there is a link to a lot of results from various contributors on that page as well. --andy -- Andy Kahn* Digital Equipment Corporation * Phone 603-884-2557 [EMAIL PROTECTED] * Unix File Systems Development * Fax 603-881-2257 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Year 2000 & Debian
"Darin Johnson" wrote: -> -> > Before 100 people jump to correct me, yes, time_t overflows after -> > Tuesday, January 19, 03:14:07 2038. Fixing this requires that time_t by -> > typedefed as a 64-bit quantity and then programs using it must be -> > recompiled. One would hope that the world can find something better -> > than POSIX, C, and Unix by 2038. -> -> Ok, the worst thing about the year 2000 problem, is that so few people -> understand it, yet think they do! People panic about things that -> probably won't break (Linux and utilities), yet ignore things that -> are more likely to break (user applications and data). -> -> 1) There is no quick fix! Yes, for the 2038 problem, you can just -> change time_t. But that only changes those applications that have -> been recompiled. The Y2K problem has almost always been about stuff -> that hasn't been recompiled and needs scrutiny before recompiling. -> The 2038 problem may be simpler in that the scrutiny can be done more -> automatically, but it's still a bigger job than just redefining -> time_t. -> -> 2) The sort of thinking that something else will be in common use -> before the problem comes around is exactly what has caused the problem -> in the first place. 2038 is 40 years in the future, but we have Y2K -> problems now for systems and programs that are 20 or 30 years old. -> People underestimate the longevity of code; the "if it ain't broke, -> don't fix it" philosophy is standard procedure (especially on -> mainframes, which is where Y2K will rear its ugly head, not on unix or -> wintel machines). -> -> 3) Setting a computer's date to 12/31/1999 and running it a few days -> does not test anything useful. The defects that this test will find -> are relatively trivial. For this to be more useful, it needs to be -> the same environment as you use in production (ie, you don't want to -> test the OS and utilities, you want to test your customer billing -> system, your automatic ordering system, your file archival system, -> your interest calculations, etc). Y2K problems are *complex*, they -> are usually not isolated to a few lines of code, and may not manifest -> themselves in a testing situation (ie, you may need to be on a network -> talking to a remote database server before a certain bug rears its -> head, etc). The real fix is to scrutinize all code. -> -> 4) Y2K problems have *already* happened, and we haven't hit 1/1/2000 yet. -> -> 5) I'm really glad no one has said "Y2K compliant" yet. There are a -> lot of poeple that use that term the same way they use "ISO 9000 -> compliant", as if there were a Y2K bugs clearning house, standards -> body, or certification program... -> -> 6) If you want to know if your system is going to have Y2K problems, -> then examine your own data and applications. UNIX in general will -> have few problems, and probably no major problems; however -> applications running on top of UNIX *will* have these problems. Same -> with Windows. Find out what's critical on your system and examine -> those components; if you do customer billing, then research the -> product that you use. If you have transactions (ie, databases) with -> other computers, then examine them as well. If you use commercial -> products, try to get upgrades to them; if you have data for those -> products, upgrade your data as well (it makes no sense to get new -> binaries, then forget that you have dates stored as character fields). -> -> 7) Finally - make backups, keep written records of all transactions, -> train your employees how to cope if the systems go down, and so forth. -> Ie, prepare for the worst. (I can't believe how inept some companies -> are; I was at a computer store whose point of sale system went down, -> and it took them ages to figure out what to do manually, and resulted -> in 4 people staffing each register). -> -> blah blah blah blah... y2k this, y2k that. all that stuff just described above talks about the y2k problem according to the *applications* used. the >> original question << was whether or not the operating system (in this case, Debian Linux) has a problem with it. the OS doesn't. fixing applications is another story. --andy -- Andy Kahn ([EMAIL PROTECTED])Phone: 603-884-2557 (DTN: 264-2557) Digital Equipment CorporationFax : 603-881-2257 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Netscape font question
Hi all, i recently installed Debian and even more recently put Netscape on my system as well. when launching Netscape, it complains: Warning: Cannot convert string "-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct Warning: Cannot convert string "-*-courier-medium-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct Warning: Cannot convert string "-*-helvetica-medium-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct Warning: Cannot convert string "-*-helvetica-medium-r-*-*-*-100-*-*-*-*-iso8859-*" to type FontStruct Warning: Cannot convert string "-*-helvetica-bold-r-*-*-*-100-*-*-*-*-iso8859-*" to type FontStruct Warning: Cannot convert string "-*-helvetica-medium-o-*-*-*-100-*-*-*-*-iso8859-*" to type FontStruct can anyone tell me where these fonts are located? thanks, --andy -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Linux in Wired
-> At 12:35 AM 8/28/97 -0400, Tan Wee Yeh wrote: -> >Maybe its becuase all my presentations to date are quite -> >technical and there is no need for flashy stuff. -> -> I would think that XFig, gnuplot and LaTeX could produce all the -> "flashiness" that one would need. -> -> Later, -> Marc -> i definitely disagree. gnuplot is nice in that it can be integrated as part of automated scripts (e.g., as part of a script that processes data files, formats them, then feeds them to gnuplot), and it does have loads of features. however, i recently took the same data that i was pumping into gnuplot and plopped it into MS Excel, then made terrificly beautiful graphs (multi-column, bar, 3d, etc) with un- believable ease, and then sent them into a PowerPoint presentation. as much as i dislike Win95/NT/MS, this Excel->PowerPoint process was unbelievable and beats the heck out of grinding through gnuplot's numerous options. --andy -- Andy Kahn ([EMAIL PROTECTED])Phone: 603-884-2557 (DTN: 264-2557) Digital Equipment CorporationFax : 603-881-2257 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Virtual Console is garbaged
-> -> hi, logout and login again -> Paul -> -> On Thu, 14 Aug 1997, Shaleh wrote: -> -> > I ran grep and it ended up reading a binary file. Now my console is -> > gibberish -- control chars, escape sequences, and non-printable chars. -> > I tried kill -HUP on getty, I tried kill on getty -- no dice. Any -> > ideas? -> > -> logging out and logging back in doesn't necessarily reset the terminal correctly. a better solution would be stay logged in, and then do ctrl-v, ctrl-o, and hit return. --andy -- Andy Kahn ([EMAIL PROTECTED])Phone: 603-884-2557 (DTN: 264-2557) Digital Equipment CorporationFax : 603-881-2257 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: [backup method] - what about TOB?
-> What you're doing looks pretty cool. I was looking in to backing up -> my /home (which isn't too big) onto a Zip disk. I was checking out -> TOB (tape oriented backup), but there are a couple of things that bug -> me about it. -> -> 1) It tars directly to a device - not to a filesystem. This means one -> backup (full, differential, or incremental) per disk, yes? I haven't -> looked too hard yet - hacking the script to tar to a filesystem can't -> be that hard, though. ... i've never seen TOB, but regarding tar'ing directly to a device: you can do multiple tar's to device (e.g., tape device). to do this, let's say you already tar'd once. to do it again, but append it to the first one, you need to forward past the first one. so if you were at the beginning of your tape, you need mt -f /dev/ntape fsf 1 where /dev/ntape represents the >> non-rewinding << device entry for your tape drive. afterwards, you can tar again. --andy -- Andy Kahn ([EMAIL PROTECTED])Phone: 603-884-2557 (DTN: 264-2557) Digital Equipment CorporationFax : 603-881-2257 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Using procmail to filter and MH to read.
"Peter S Galbraith" wrote: -> -> Looking for advice here... -> -> Suppose I use procmail as my delivery agent (instead of deliver) -> and MH (actually mh-e in Emacs) to read mail. -> -> What do people do to separate out (filter) the Debian mailing? -> Do you use a new sendmail ruleset? Or some /etc/procmail or -> ~/.procmailrc file? -> -> Does the filtering drop the mail directly into a folder, or better yet -> produce another mail drop that can be included using MH's inc'ed, e.g. -> -> inc -file /var/spool/mail/galbraith-Debian -> -> That would be neat... I could use standard xbiff-like programs -> (like xbuffy) to monitor the mail, and inc the spool file directly into -> a distinct mail folder. -> -- -> Peter Galbraith, research scientist <[EMAIL PROTECTED]> -> Maurice-Lamontagne Institute, Department of Fisheries and Oceans Canada -> P.O. Box 1000, Mont-Joli Qc, G5H 3Z4 Canada 418-775-0852 - FAX 418-775-0546 -> -> -> -- i don't use MH, but i've used procmail before. you can simply set a rule in ~/.procmailrc to (re)direct mail to a file. for example: :0 f * ^To: debian-user@lists.debian.org debian in this case, the "debian" file resides in MAILDIR, which must be specified in the beginning of .procmailrc (e.g., MAILDIR=$HOME/Mail) the resulting mail file is in no particular format, other than the format initially delivered to your system. considering that i'm fairly new to the Debian set (after being a Redhat user for a while), i'm sure there are other (possibly better ways) to do this, but this has worked for me in the past. hope this helps, --andy -- Andy Kahn ([EMAIL PROTECTED])Phone: 603-884-2557 (DTN: 264-2557) Digital Equipment CorporationFax : 603-881-2257 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
