[Shaktai]

I did a restart on my Power Mac 800 (Quicksilver) and now the startup screen hangs at "Starting Ubero Client" and goes no where.

I tried restarting from OS-9 so that I could remove the startup file (holding down the option key on restart), but it doesn't find OS-9 to startup from (uurrgghh!!!)

I can't startup from a CD, because I can't get the CD drawer open to put one in.

How do I break out of this mess? Is there a way to quit the startup of the Ubero client during startup OR get the CD open to startup from CD or get the darn computer to startup fro OS-9 OR any other reasonable solution to get beyond the d**** startup screen in OS-X.

Interestingly, even though I can't do anything else, the Ubero client is actually running in the background processing units. I just need to get beyond the blue startup screen and the message that the Ubero client is starting up.

Help Please!!

[reader50]

I've read threads that outline numerous ways to open the CD drawer on a QS without manual eject hole. Unfortunately, I do not have a QS and did not write all the tricks down.

The one that comes to mind, is to boot into open firmware, then type "eject cd" at the prompt. That should open the drawer. If I recall correctly, you next type "boot-mac" for the boot process to continue, but a reset should work also.

ps - there are much easier ways (keys held down during startup) to get that drawer open.

[reader50]

http://forums.macnn.com/cgi-bin/ulti...2&t=005025

That's not the all-answers post that I recall, but it gives enough. Hold down the mouse button during the startup chime. Alternatively, try the Eject button, or the F12 button, after you reach the freeze point.

[Michael A. Peters]

Not to be an @ss, but this is one (of many) reasons why stuff shouldn't be started as root that doesn't need to be.
One bug and the entire OS can be affected.

Holding the mouse button works for ejecting floppy diskettes on the older models- so it may work for the CD on the newer flopyless models, too.

[Shaktai]

Thanks for the tips. I am back online with my main computer. Actually, I stumbled across a different workaround, when I discovered that I could access my power mac from my iBook. apparently network services were adequately loaded. I was then able to go into the startup files and modifiy the startup script. I couldn't save the changes, but it let me save under Ubero.txt. then when I restarted, the two conflicting scripts apparently canceled each other out. .

I will remember the tips on ejecting the CD tray though. I knew there was something, but Apple's basic manuals that come with the computers are worthless for that kind of help any more.

Now if I had been thinking clearly, I would have asked help on my iBook that would have told me that. (duhh!!!)

Thanks all.


[ 03-17-2002: Message edited by: Shaktai ]

[vesalius]

I had the same problem with Ubero at startup, but I was able to boot from CD and remove the ubero folder from /Library/Startupitems/. I do not beleive I will use this method to start ubero anymore. I agree with Michael. Root should not be running Ubero. The potential harm just outweighs the benefits, if any benefits exist.

I do not understand why the beta app just can't add a line to the user's crontab file. Something like:

"@reboot cd /Applications/Ubero/; ./ubero &"

Where ./ubero is the script curently being run from the ubero startup items folder. I have run Mikkyo's scripts this way before trying the MDC app out of curiousity. The only problem I have run into is that the script seems to die 12 to 24 hours after it is started and does not restart itself. Any one have any advice?

[ 03-17-2002: Message edited by: vesalius ]

[Arkham_c]

Well, the way I am doing startup items is the way recommended by Apple. It's the same method used by Timbuktu, Brickhouse, DAVE, and others. I can run the daemons as "nobody" rather than root if you prefer, but that doesn't address the true problem here, which is that the startup procedure isn't as robust as it should be.

Also, bear in mind we're talking about beta software, so you guys are beta testers. I am one guy with one computer and very few hours of free time. This app could be a great recruiting tool for Team MacNN, but we all need to contribute some time (and maybe some frustration) to get it to the point where people can use it easily and safely.

[Shaktai]

Originally posted by Arkham_c:
<STRONG>Well, the way I am doing startup items is the way recommended by Apple. It's the same method used by Timbuktu, Brickhouse, DAVE, and others. I can run the daemons as "nobody" rather than root if you prefer, but that doesn't address the true problem here, which is that the startup procedure isn't as robust as it should be.

Also, bear in mind we're talking about beta software, so you guys are beta testers. I am one guy with one computer and very few hours of free time. This app could be a great recruiting tool for Team MacNN, but we all need to contribute some time (and maybe some frustration) to get it to the point where people can use it easily and safely.</STRONG>

I for one am not complaining, and think that you are doing a great job. I was also well aware of that I was using a beta, and am not surprised at having some problems. It is part of the process. Keep up the good work.

[vesalius]

Originally posted by Arkham_c:
<STRONG>Well, the way I am doing startup items is the way recommended by Apple. It's the same method used by Timbuktu, Brickhouse, DAVE, and others. I can run the daemons as "nobody" rather than root if you prefer, but that doesn't address the true problem here, which is that the startup procedure isn't as robust as it should be.

Also, bear in mind we're talking about beta software, so you guys are beta testers. I am one guy with one computer and very few hours of free time. This app could be a great recruiting tool for Team MacNN, but we all need to contribute some time (and maybe some frustration) to get it to the point where people can use it easily and safely.</STRONG>

Well Look, I apologize if I seemed to overly critical without recognizing your effort. You are doing a service to everyone by working on this app, so more power to you. I am aware that this is a beta app, which will have bugs.

I also realize that many apps use this process to startup, but what I am questioning is whether any of the clients started by MDC fall into the same catagory as any of the apps you mentioned. Timbuktu, Dave, and Brickhouse are all good examples of processes that provide potential services to everyone who uses the computer. Running them as root is more sensible, but I do not beleive that ubero falls into that same catagory. I think ultimately that apple should address this issue. The processes in startup items items should be backgrounded after a predetermined amount of time so that they can not cause the problem illustrated by MDC beta 11.

Is there anyway to run the daemons as the user who is installing the apps? Running a third party script as root subverts all of the new security meusures built into OS X because while I am fairly certain that you have the best intentions, many others may not. Or even worse it opens a potential security hole for a malicious cracker to exploit. I realize the risk is small since they would need access to the source of MDC in order to add a few malicious lines to the scripts installed by the software, but it is possible.

[Arkham_c]

I am doing what I can to run the processes as "nobody" rather than root in the next release. I will still require the root password for installs and starting/stopping (nobody can't live on its own), but it should be safer for those who are concerned.

As a result though, the next beta may have some bugs in it that did not exist before. You guys seem to want this though, so I am adding it.

I'll make Scott test the next release before I put it out for you guys.