Bypass Aqua Dec 06, '00 01:30:58AM • Contributed by: Anonymous
If you login with the username >console with no password you will bypass the Aqua interface and be presented with a text login screen. I came across this hint at daemonnews.org. I hadn't seen it here and so I thought I would share the info.
[Editor's note: Simply typing logout will return you to the GUI login screen.]
There are many people who use a software router to share one DSL connection among multiple networked computers. The most popular programs are IPNetRouter and SoftRouter. Under OS X, neither one of these will function, since OS X is handling the networking chores.
However, BSD UNIX contains a built-in network address translation (NAT) function, which can do the job that either package used to do.
Configuring it under the beta is non trivial, but it's not that complicated, and there are some pre-written scripts to help with the task.
There's a great thread here on the MacNN forums that discusses all the relevant steps, and includes some links to additional information.
You should be comfortable with your terminal and file-editing skills before attempting to configure NAT -- it's much more like UNIX work than typical Macintosh work!
I noticed something sorta funny, when you open up the applications list, by mashing cmd + opt +esc, the menu bar disappears when the list becomes active. Does anyone have any clues to why this happens?
Also , The whole concept of the preferences being xml files is pretty cool. Does anybody know of any sites that have more stuff you can add, such as the translucent terminal window. OS X PB seems like there is a bunch of stuff that is disabled and only takes a little bit of hacking to enable it.
[Editor's note: Search elsewhere here for the command line hacks, as there are a bunch of them!]
Want your Mac to power down every night at 11:00pm? User 'Gee4orce' posted the following tidbit to the MacNN OSX forums to accomplish just that feat. Here's how it's done:
Open a terminal session
shutdown -h 2300
This will shutdown the computer at 11pm (2300 on a 24-hour clock). Replace the '2300' in the example with the (24-hour) time of your choosing. If you want to prevent the shutdown, you need to kill the process using either ProcessViewer or the 'kill' command.
First, here's what happened: my terminal.app blew up. I hadn't encountered the hint here that gives the easy fix (ie: grab /bin/tcsh from the Installer CD and chuck it in /bin - it seems that, somehow, things in /bin can get corrupted, which is very wierd, but that't another story!) so I reinstalled OS X. That worked fine and my terminal.app was fixed.
Lo and behold, though, I now had a USB option available in my Modem Port choice in PPP Connect Preferences. I am 100% sure that it was not there beofre I reinstalled, because I was stuck using my old Motorola serial 28.8 modem (eeewww - slow!) under OS X but I could use my Swann MacSurfer V.90 under OS 9. So, I selected the USB option, and was able to use my V.90 modem under MacOS X. Great!!!
Some people (such as myself) have the need to run OS X services (such as Apache, ftp, ssh, telnet) on alternate ports. In my case, my router has a mini-http server, so I can't use port 80 for Apache, and my ISP blocks all ports below 1000 to prevent servers.
How do you work around this in OS X? For Apache, it's fairly simple. From a terminal session, edit (note: edits referred to in this article should be done as the root user; 'su' before editing!) the file /Library/Web Server/Configuration/apache.conf, and find the line that reads "Port 80." Replace 80 with the port you would like to use -- keep in mind that visitors to your site will have to enter:
(where portnum is the number you chose)in order to see your pages.
[Editor's note: See the comments for a suggestion or two...]
Not sure what happened -- OS X hung, then after two hours of trying various things and then leaving it alone, the system displayed a kernel panic message and rebooted, after I pressed "r" as prompted. I finally had to clear the p-ram for the thing to even boot into OS 9. I followed Apple's instructions in the TILs and booted into single user mode after using the System Disk utility BUT ... fsck won't fix the error it finds: "Problem: Invalid LEOF, 28239, 1024"!!! And yes I've made sure to try -f -y -b16, etc.
It will boot into OS X if I let it (quite unstable and I don't like forceably rebooting Un*x boxen); and when the OS X disk utility is used to verify my OS X volume, it reports the exact same error. I even tried running Disk Doctor after booting into OS 9 but it can't fix the error either ... sigh =(
Am I out of luck, do I have to reinstall? Anyone have any suggestions or run into the same problem? Anyone know what to do in the future to avoid this type of problem?
Although it hasn't received much coverage, the services menu appears to be one of the niftier features of OS X. To get a brief example of how it works, open the Mail application, pick any message, reply to it, and select all the text. Make sure Terminal is also running, although you don't need to have a session open.
Under the Mail menu, select Services, then Terminal, and finally Word Count. All your text will be replaced by a series of three numbers - 7 57 362, in the test I ran. This translates to 7 lines, 57 words, and 362 characters.
For a second demo, start a new email message, and pick Time under the Terminal services menu. The current date and time will be pasted in your email.
Although these are neat demos, the real power appears to lie in the fact that we will (hopefully!) be able to add our own services in the final release. To see what this could look like, look at the Terminal Services menu under Terminal in the (you guessed it!) Terminal application.
Since the terminal application has incredible power, the ability to add a service which will then be available to any application seems like a very useful thing!
I added a test service, but I haven't been able to make it show up in the services menu in other apps yet, but I'll post something if I do.
[Editor's note: Please see the comments for the proposed solution]
I'm using OS X Public Beta as my primary web development environment - that is I develop the html/code using my OS X box. Now, my web servers and my desktops are behind a firewall and DNS hosting has been outsourced to AT&T, so resolving my webservers' URLs "within" my network isn't possible without modifications being made to a desktop's hosts file. Under Windows and Mac OS 9 its easy -- just make the changes to the file. But the hosts file I found in "/etc" under OS X says it "isn't used" and modifications don't take hold.
Does anyone have a suggestion or know the right way to go about doing this?