[Solved] Installed linux version on mac os.. help me remo...

[TenLeftFingers]

I did this as root and I want to totally get rid of anything I installed. I did a cat of the .run file but there are parts that don't display in the terminal. Can anyone tell me where the files are installed so I can clear them out?

[Cody]

Hi and welcome... sorry that you've had no reply as yet. I cannot help though... I'm a Windows man.

[Diziet Sma]

I'm probably not much help either.. I've never done a root-installation.. but hopefully one of the major Linux geeks will discover this thread soon.

(And welcome aboard, TLF! )

[Cody]

... but hopefully one of the major Linux geeks will discover this thread soon.

Aye... but is it the Penguin that we need, or a Mac expert?

[Diziet Sma]

A penguin.. for two reasons..

!. It was Linux files that got installed, so somebody who knows where those files would go is needed.
2. There is very little difference in the file-system structure of Mac and Linux machines.. both are Unix based.

If somebody doesn't step up to help soon, I'll try to replicate the problem on the old MacBook I have, and see where everything ends up.. I should be able to guide TLF through cleaning it out after that.

[Diziet Sma]

Ok..

I did a cat of the .run file but there are parts that don't display in the terminal.

The only parts that don't cat for you are the binary code and data files.. odds are good you were able to read the entire install script, not that that's necessarily the easiest thing to decipher.. (I looked at it)

Here's what I found when I duplicated TLF's problem..

Firstly, I enabled Revealer, so as to be able to easily browse all the sections of the hard-drive that OSX usually blocks access to (not really necessary, but I like to be able to go look at things for myself), and then set fseventer to record all file-system activity while I performed the root installation.

Good news, TLF!

If you simply delete the root-level /opt folder (which doesn't exist in a normal OSX installation, or at least not in 10.7.5) you will have gotten rid of everything. The only thing installed into the /opt folder is an Oolite folder, if you have some reason to leave /opt where it is. Deleting either folder will get rid of every trace of Oolite from your system.

The only other thing Oolite does when it installs is create some temporary files during the unpacking process, all of which should be removed the next time you rebooted anyway.

[Norby]

where the files are installed so I can clear them out?

My tip:

Code: Select all

locate oolite

My list is 4000 lines long, for example:

Code: Select all

/usr/games/oolite
/usr/lib/GNUstep/Applications/oolite.app
/usr/share/doc/oolite
/usr/share/app-install/desktop/oolite.desktop
/usr/share/app-install/icons/oolite-logo1.xpm
/usr/share/applications/oolite.desktop
/usr/share/doc/oolite
/usr/share/doc/oolite-data
/usr/share/doc/oolite-data-sounds
/usr/share/doc/oolite-doc
/usr/share/doc-base/oolite-advice-for-new-commander
/usr/share/doc-base/oolite-reference-sheet
/usr/share/icons/oolite-icon.png
/usr/share/lintian/overrides/oolite-data
/usr/share/man/man6/oolite.6.gz
/usr/share/menu/oolite
/usr/share/pixmaps/oolite-logo1.xpm
/var/lib/doc-base/documents/oolite*
/var/lib/doc-base/omf/oolite*
/var/lib/dpkg/info/oolite*

[Diziet Sma]

Ahh. but you did that on a Linux machine, Norby.. the locate database doesn't exist on a Macintosh.

None of the files you listed get created when the Linux installer gets installed system-wide on a Mac, by mistake. (The installer exits before those files get created, due to xdg not existing on a Mac.) I've just checked, using my MacBook as a guinea-pig. The only Oolite files created all reside in /opt/Oolite.

[Norby]

You are right, I have not mac, just I understand your previous post as an ask for files on Linux. Now I think the .run file use the /opt under Linux also and my files created when I installed oolite from a .deb package.

[TenLeftFingers]

Diziet Sma, thank you so much - that did the trick! I was really worried that a linux style 'shotgun blast' install might have happened and left files all over the place. I really appreciate the time you took to do all of that. As much as I enjoy the game, this forum is even more encouraging to keep playing

Cody, Norby & Diziet Sma, thanks for replying to my distress call It's a pleasure to meet you all.

[Diziet Sma]

You're very welcome, mate.. I'm glad I was able to help..

Now you can enjoy the game without worrying..

[Rxke]

Cody, Norby & Diziet Sma, thanks for replying to my distress call

Spoken like a true Ooliteer! This guy's already hooked, heehee!

(Aren't these board great, I don't play any more, but still visit them just for the positive vibe....)

[Getafix]

Welcome aboard TenLeftFingers.

Having consumed some weird looking purplish schnitzel in one of the con-stores,
I passed these last few days in a 1m x 1m room of the docked Cobra,
trying to clean it out of my system.
To cut the long story short... missed your distress call.

Please, also check for the probable existence of the following:
1. files generated during installation
/usr/local/bin/oolite
/usr/local/bin/oolite-update

2. folders generated during first run (self-extracting package distribution only)
~/.Oolite/
~/GNUstep/
Note 1: Before deleting the ~/GNUstep/ folder check with a Mac person that you don't actually need it for some other application.
Note 2: Both these folders are created by a wrapper shell script before the linux binary execution. Therefore, they can also be created on a Mac just before the linux binary execution fails.

EDIT: The /usr/local/bin/ folder exists by default on Mac, doesn't it?!?

[Diziet Sma]

Please, also check for the probable existence of the following:
1. files generated during installation
/usr/local/bin/oolite
/usr/local/bin/oolite-update

2. folders generated during first run (self-extracting package distribution only)
~/.Oolite/
~/GNUstep/
Note 1: Before deleting the ~/GNUstep/ folder check with a Mac person that you don't actually need it for some other application.
Note 2: Both these folders are created by a wrapper shell script before the linux binary execution. Therefore, they can also be created on a Mac just before the linux binary execution fails.

On my test-install, with all file-system activity being logged by a tracer program, these files/folders were not created.. the installer script apparently fails before that point, I'm guessing due to xdg not being on a Mac.. since that was when the installer script failed for me. It unpacked to /tmp, copied files into /opt/Oolite, then bombed out. Neither the wrapper script nor any other ~/ files get created, let alone executed.

EDIT: The /usr/local/bin/ folder exists by default on Mac, doesn't it?!?

No.. in fact, /usr/local doesn't exist on a Mac by default..

[Getafix]

Case gracefully closed then!