-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On RaspApple II distro, the apple2 userid has no password (sudo fails) #3
Comments
David - No idea why, all of a sudden, messages directed to you are being sent to me. Ken Visit my sales venues at: ¡¸ Webstore: http://drkenb.blujay.com - Vintage Apple II Computers, Canon Portable Printers & other miscellaneous items Visit my informational websites at: ¡¸ http://www.Apple2Online.com - the ultimate online resource for the Apple II family of computers! ¡¸ http://CanonPortablePrinters.drkenb.com - the comprehensive online resource for Canon's portable inkjet printers! ¡¸ http://Photography.drkenb.com - Photographic library ¡¸ http://BeauMontFarmWeather.drkenb.com - CWOP Weather Station Date: Wed, 15 Oct 2014 12:15:56 -0700 In one particular circumstance, I happened to be in a terminal session with userid apple2. I attempted to use sudo but that fails since I could not enter a password when prompted by sudo (it would not take an empty password promtp; how does one use sudo when the userid has no password?) So, how did I get into a terminal session with userid apple2? From the initial terminal session at boot, login as pi. I then issued startx to bring up the desktop (this allowed my inserted USB devices to be recognized). Then I did a logout from the desktop session, back to the terminal session under pi. Type exit, and you get requested to login. I logged in as apple2. IT CAME UP AS A TERMINAL SESSION, not gsport. This is where the sudo attempt failed. However, running gsport from that apple2 logged in terminal session, provides a plus. If one then exits gsport with Alt-F4, it comes back to the terminal session (does not power off as indicated). This allows greater flexibility and the ability to run gsport again without power down. As indicated above, inserted USB devices (flash drive and memory stick) are not recognized unless the desktop comes up first. I was referencing some image files in the gsport config file, and they could not be found unless the desktop was started, then exited. Also, I tried KEGS and the configuration failed due to missing ROM files. I have to do some work here (or maybe the distro needs some work). ¡X |
Hi Ken- Thanks for all the feedback - I'll forward it on to Ivan and we will As for the messages, probably a github thing. Dave... On Wed, 15 Oct 2014 12:32:01 -0700
|
In one particular circumstance, I happened to be in a terminal session with userid apple2. I attempted to use sudo but that fails since I could not enter a password when prompted by sudo (it would not take an empty password promtp; how does one use sudo when the userid has no password?)
So, how did I get into a terminal session with userid apple2?
From the initial terminal session at boot, login as pi. I then issued startx to bring up the desktop (this allowed my inserted USB devices to be recognized). Then I did a logout from the desktop session, back to the terminal session under pi. Type exit, and you get requested to login.
I logged in as apple2. IT CAME UP AS A TERMINAL SESSION, not gsport.
This is where the sudo attempt failed.
However, running gsport from that apple2 logged in terminal session, provides a plus. If one then exits gsport with Alt-F4, it comes back to the terminal session (does not power off as indicated). This allows greater flexibility and the ability to run gsport again without power down.
As indicated above, inserted USB devices (flash drive and memory stick) are not recognized unless the desktop comes up first. I was referencing some image files in the gsport config file, and they could not be found unless the desktop was started, then exited.
Also, I tried KEGS and the configuration failed due to missing ROM files. I have to do some work here (or maybe the distro needs some work).
The text was updated successfully, but these errors were encountered: