home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!news.service.uci.edu!ucivax!news.claremont.edu!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: re: Re: HELP!!! Security problem for gurus. [Directories]
- Date: 30 Dec 1992 11:19:05 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 25
- Distribution: world
- Message-ID: <1hs0j9INNnqs@gap.caltech.edu>
- References: <9212290242.AA00964@uu3.psi.com>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- In article <9212290242.AA00964@uu3.psi.com>, leichter@lrw.com (Jerry Leichter) writes:
- >BTW, it's not impossible that SOME invalid directory entries will could cause
- >(probably non-fatal) bugchecks.
-
- Hmmm. After the way DEC screwed up the V5.4 release*, I don't really believe
- in "non-fatal" bugchecks any more.
-
- I *THINK* it was 5.4. Maybe it was 5.2. The old-timers know what I'm talking
- about: The time some DEC developer didn't change the SYSGEN parameter
- BUGCHECKFATAL back to FALSE before shipping (for those not familiar with this
- sysgen parameter, if it's set to TRUE, then *ALL* bugchecks are fatal. It's
- intended [as best I can tell] [almost {maybe}] exclusively for DEC developers
- to use while they're testing a new version of the operating system. When
- something goes wrong, they get a nice system dump, which allows them to debug
- the O/S. On a production system, you don't normally want a continuable
- bugcheck to give you a system dump. The sudden >>> prompt on the console might
- confuse somebody :-).
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-