ftp.nice.ch/peanuts/GeneralData/Usenet/news/1989/CSN-89.tar.gz#/comp-sys-next/1989/Jan-Apr/Application-launch-time

This is Application-launch-time in view mode; [Up]


Date: Sun 29-Jan-1989 22:16:58 From: Unknown Subject: Re: Application launch time A similar question is why does it take so long for the NeXT to boot? I timed it... it takes exactly 5 minutes and 10 seconds and I doubt much of that was fsck time although I could be wrong... One reason it takes so long to boot might be that the object oriented window stuff takes that long to be created, thus it isn't kernel boot time at all but rather the amount of time taken to build the window interface. Thus the time it takes to launch applications might be due to the time it takes to build objects and set up the window interface for that particular application. Just a guess...... >From: carter@sloth.gatech.edu (Carter Bullard)
Date: Sun 30-Jan-1989 18:04:22 From: Unknown Subject: Re: Application launch time In article <7554@potomac.ads.com> jtn@potomac.ads.com (John T. Nelson) writes: > > >A similar question is why does it take so long for the NeXT to boot? I >timed it... it takes exactly 5 minutes and 10 seconds and I doubt much >of that was fsck time although I could be wrong... > Unfortunately, it is mostly fsck. If you press the command key and the back quote key at the same time, you'll get a mach window asking if you really want to reboot. type y and, if it gives you a NeXT> prompt, type bsd (for boot off of the sd drive). you'll see whats going on when you boot. Carter Bullard School of Information & Computer Science, Georgia Tech, Atlanta GA 30332 >From: gil%daffy@gatech.edu (Gil Neiger)
Date: Sun 31-Jan-1989 06:48:09 From: Unknown Subject: Re: Application launch time In article <7554@potomac.ads.com> jtn@potomac.ads.com (John T. Nelson) writes: >One reason it takes so long to boot might be that the object oriented >window stuff takes that long to be created, thus it isn't kernel boot >time at all but rather the amount of time taken to build the window >interface. >Thus the time it takes to launch applications might be due to the time >it takes to build objects and set up the window interface for that >particular application. I'm pretty sure that you are incorrect here. If you do a verbose boot, you will see thatecking the disks takes an enormous chunk of that 5 minutes. Also, in the release notes, it says to logout and log-in as 'exit' every once in awhile. This, I beleive, relaunches the Window server as a kludge for garbage collection Chris >From: johnl@ima.ima.isc.com (John R. Levine)
Date: Sun 30-Jan-1989 19:59:03 From: Unknown Subject: Re: Application launch time In article <7554@potomac.ads.com> jtn@potomac.ads.com (John T. Nelson) writes: >A similar question is why does it take so long for the NeXT to boot? I >timed it... it takes exactly 5 minutes and 10 seconds and I doubt much >of that was fsck time although I could be wrong... It's mostly fsck time. If you get into the ROM monitor, you can give the "p" command and turn on verbose booting, so it says the same stuff while booting that any other Unix system does. (The spinning disk is cute, but not very informative.) It seems usually to assume that the disk might be dirty, and so does a full fsck. If I shut down with /etc/halt, it usually but not invariably will skip the long fsck and boots a lot faster. >From: jbn@glacier.STANFORD.EDU (John B. Nagle)

These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.