Yeah it’s not in the repos but I need it for the college course that I’m doing, sigh. So I got it to work in LEAP somehow (though probably with system damage?) last year.
Though when I try to install it in Tumbleweed It modifies /etc/profile among other things, leaving it full of syntax errors and changing the indenting and other changes. I’m going to leave it for a while as I don’t go back to school until term 2.
I’ll try to send an error report to cisco packettracer, I’m sure they’ll fix it pronto (lol).
Well, you could make a backup of /etc/profile and restore that after installing it.
If there are necessary changes, you could probably add them manually to /etc/profile.local or a file in /etc/profile.d/…
Hmmm maybe that’s an option (if only I new more about shell scripts). Surely someone in the world must have already done this? I’ll try to find them.
Just compare the modified copy with the original one, e.g. using diff, to see what exact changes it made.
Feel free to post it for help.
I always use $ zypper dup --no-allow-vendor-change, are you suggesting that it should be only zypper dup? I do have a few other repos…
tim@t420 ~ sudo zypper lr -u
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | URI
--+------------------+------------------+---------+-----------+---------+-----------------------------------------------------------------------------------
1 | fonts | fonts | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/M17N:/fonts/openSUSE_Tumbleweed/
2 | namtracfonts | namtracfonts | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/home:/namtrac:/subpixel/openSUSE_Factory
3 | packman | packman | Yes | (r ) Yes | Yes | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/
4 | repo-debug | repo-debug | Yes | (r ) Yes | Yes | http://download.opensuse.org/tumbleweed/repo/debug
5 | repo-non-oss | repo-non-oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/tumbleweed/repo/non-oss
6 | repo-oss | repo-oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/tumbleweed/repo/oss
7 | repo-src-non-oss | repo-src-non-oss | No | ---- | ---- | http://download.opensuse.org/tumbleweed/repo/src-non-oss
8 | repo-src-oss | repo-src-oss | No | ---- | ---- | http://download.opensuse.org/tumbleweed/repo/src-oss
9 | repo-update | repo-update | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/tumbleweed/
What about other changes to other files that it might be doing that I have no idea about?
The Cisco PacketTracer install appears to provide its own version of quite a few programs and libraries that are in a standard openSUSE KDE installation. I am guessing that the developers have tried it with one Gnome distro and assumed it was “suitable for Linux”.
My suggestion is to use VirtualBox and install a lightweight nonKDE desktop (e.g. Xfce, Openbox, IceWM) Leap-42.3 instance. Then you could run PacketTracer in that. hared data directories will make it easy to access PT output from the host Tumbleweed-KDE desktop.
–no-allow-vendor-change is the default for “zypper dup” on Tumbleweed since a while.
So you don’t need to explicitly specify it.
Well, you already did install it, no? Otherwise that thread wouldn’t exist.
So it already did possible other changes anyway.
One possibility to see them would probably be YaST->System->Snapper, if you use btrfs.
There you can inspect all changes to system files between two snapshots.
If PacketTracer’s install is a shell script, you could of course inspect (or post) that script to see what changes it makes.
That’s not necessarily a problem though, depending on how/where they are installed.
My suggestion is to use VirtualBox and install a lightweight nonKDE desktop (e.g. Xfce, Openbox, IceWM) Leap-42.3 instance. Then you could run PacketTracer in that. hared data directories will make it easy to access PT output from the host Tumbleweed-KDE desktop.
Definitely a good idea, that would prevent any changes to the real system…
Ok I’ll consider doing the virtualbox thing though I consider it a real pain just to use an application.
What really concerns me is the other potential damage done by PacketTracer! I was lead to believe that one of the benefits of the file system is that I would be able to re-install without losing my user data. Is this true and if so how?
Just do an update from the installer Or if you want a clean install be sure NOT to format home. This assumes you keep home on a separate partition.
I’m not sure what you mean here.
Sure you can re-install without losing your user data. That’s especially easy if /home is on a separate partition, as it is by default.
OTOH, with btrfs (and snapshots), which also is default on openSUSE since a while now, you can just revert the system to a previous snapshot, or inspect differences between two snapshots as I mentioned.
IOW, you can easily revert all changes that the PacketTracer installer did, or even see what exactly it changed.
Just to make sure, create a snapshot manually before running the installer. (in YaST->Misc->Snapper e.g. or directly with snapper)
See also https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.snapper.html
thnx works for me