Thanks Jerry, I don't understand why anyone would object to these people selling a compiled, easy-install version of an OS program. I'll be trying to figure out how to do it the hard way, but only because I want to know how. It's frustrating to have gone from semi-wonk with OS9 to newbie with OSX. And since I got no joy from something as simple as looking for instructions with the "man 5 crontab" entry that Lee shared a few notes back, I'm sure the road to joy is not going to be straight and smooth.
BTW: [whine]The "recent items" is not the same functionality as I was accustomed to. My ideal list was carefully constructed from years of blind stumbling with key components added after the consumption of considerable beer. So it contained not only logic and frequency observations but a bit of whimsy which no friggin machine can duplicate![/whine] I have added a folder to the task bar with the original contents and that works ... with an extra click. Funny how attached we can get attached to the ways these machines allow us to do things. That extra click - multiplied by hundreds of times - might be worth sixty seconds of my life, but it irritates me to have to give it up. Bill > From: Jerry Yeager <jerry at browseryshop.com> > Reply-To: macgroup at erdos.math.louisville.edu > Date: Mon, 3 May 2004 22:22:52 -0400 > To: macgroup at erdos.math.louisville.edu > Subject: Re: MacGroup: Processor temp and cron job - can't finds > > Ask and you shall receive (smile)... > > At the moment GRASS can come in two ways, a homegrown version and the > buy-it kind. > > The free homegrown version can be found at > http://grass.itc.it/grass5/binary/mac_os_x/ but does require some > do-it-yourself messing with under the hood *NIX configurations. The > instructions are all there though. > > The buy-it-kind comes from OpenOSX > http://openosx.com/grass/index.html a group that skirts the GNU > licensing of open source software by making GUIs for *nix based > software and selling them, you can draw you own conclusions whether > this is shady as some claim or if it is a fair business practice (I am > only writing this to tell you of the debate that still continues, as I > said you can draw your own conclusion, ---- myself I see nothing wrong > with selling the compiled GUI program, but I do not think they should > sell the source code which you have to compile yourself). > > Jerry > > > p.s. Look under the Apple menu, you will see an menu item called > 'Recent Items' which acts just like the familiar 'Programs' folder you > are talking about below. You can configure it to keep large number of > things just like you were used to in OS-8 and OS-9. Consistency remains > constant. > > p.p.s. No more bad puns or straight lines for a week or two days which > ever comes first, I promise. > > > On May 03, 2004, at 5:59 PM, Bill Holt wrote: > >> Lee, >> >> I really appreciate you going into the level of detail you did to guide me >> through the process of tweaking the self-repair routines, but I have to admit >> that my eyes glazed over more than once. Ye gads ... I am a Mac person, and >> I have been since the spring of 1984. Granted, there is one OSX specific >> thing that I want to do, soon, which will no doubt force me to use toothpicks >> to prop the lids ... make use of the Unix window so I can make use of the >> GRASS program, but it's going to take me a while longer just to get past the >> irritation of all of the changes that seem to have been made in OSX just for >> the sake of change. >> >> I wonder why, in the creation of OSX, Apple did such a poor job of >> maintaining consistency of interface. There was less of a change between 6 >> and 7, and between 1 and 2. Was it really of value to me to have to learn >> twenty new ways of doing things that I'd been happily and easily doing for a >> lot of years? Going to the Apple menu to select a program from an alias >> holding folder I put there, cleverly called "Programs", was much easier than >> the task bar. And no matter where you put it, the task bar is always popping >> up when its only function is to get in the way. >> >> Now that's not to say that I don't, overall, like OSX. I do. I love how >> solid it is. In about a month of pushing it through what's probably a >> strange combination of concurrently running programs, I've never seen a >> system crash. My OS9 system was acceptably stable, but I'd guess I did see a >> crash a week ... usually inspiring me to turn to Redmond and cuss. Does it >> look pretty? Sure. El neato buttons that seem alive when they are the >> default choice. Slick. But it seems to me that a lot of the changes were >> just enforced cultural changes ... which irritate me almost as much as the >> ATM machines that now insist the I inform them that I speak English before >> doing business. >> >> Ironically, SoftWindows 95 - which was partly broken since about OS 8 - seems >> completely functional running in the OS9.2 emulation under OSX. Also, my >> oldest CAD program, circa '87, does better now than it has in years. Go >> figure. >> >> And I sincerely thank you for this opportunity to exercise the ritual of >> worthless tirade. I feel a little better now. Remind me at the next >> meeting, and I'll buy you a root beer. :) >> >> Bill >> >>> From: Lee Larson <leelarson at mac.com> >>> Reply-To: macgroup at erdos.math.louisville.edu >>> Date: Tue, 27 Apr 2004 18:06:59 -0400 >>> To: macgroup at erdos.math.louisville.edu >>> Subject: Re: MacGroup: Processor temp and cron job - can't finds >>> >>> On Apr 27, 2004, at 2:07 PM, Bill Holt asked: >>> >>>> Second "can't find" - there is a way, I know, to have the OSX system do >>>> it's self-repair thing on a schedule of my choosing instead of it's wee >>>> hours of the morning preference. I know I've read about it here ... but >>>> can't find it because that exchange is in my archive. Can't even find it >>>> on the apple site ... probably because I don't have enough of a clue to ask >>>> the question intelligently. >>>> >>> There's probably a nice GUI program somewhere to let you change the >>> times, but I've never looked for one. It's actually not very >>> complicated, if you're willing to use a text editor. >>> >>> If you look at the file /etc/crontab, you'll see near the end >>> >>> # Run daily/weekly/monthly jobs. >>> 15 3 * * * root periodic daily >>> 30 4 * * 6 root periodic weekly >>> 30 5 1 * * root periodic monthly >>> >>> These three lines tell when the periodic maintenance scripts are >>> executed. The columns stand for >>> >>> minute hour monthday month weekday owner command >>> >>> From this, we see that the run times are >>> >>> daily 3:15 AM >>> weekly 4:30 AM on Saturday (Monday is 1) >>> monthly 5:30 AM on the first of the month >>> >>> With a text editor, you can change them to run whenever you want. >>> >>> To learn more about this than you'll ever need to know, open up a >>> terminal window and read the documentation by typing >>> >>> man 5 crontab >>> >>> >>> >>> >>> >>> >>> | The next meeting of the Louisville Computer Society will >>> | be April 27. The LCS Web page is <http://www.kymac.org>. >>> | List posting address: <mailto:macgroup at erdos.math.louisville.edu> >>> | List Web page: <http://erdos.math.louisville.edu/macgroup> >>> >> >> >> >> | The next meeting of the Louisville Computer Society will >> | be May 25. The LCS Web page is <http://www.kymac.org>. >> | List posting address: <mailto:macgroup at erdos.math.louisville.edu> >> | List Web page: <http://erdos.math.louisville.edu/macgroup> >> > > > > | The next meeting of the Louisville Computer Society will > | be May 25. The LCS Web page is <http://www.kymac.org>. > | List posting address: <mailto:macgroup at erdos.math.louisville.edu> > | List Web page: <http://erdos.math.louisville.edu/macgroup> > | The next meeting of the Louisville Computer Society will | be May 25. The LCS Web page is <http://www.kymac.org>. | List posting address: <mailto:macgroup at erdos.math.louisville.edu> | List Web page: <http://erdos.math.louisville.edu/macgroup>
