Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.
Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We're all here because we have a shared love for Linux and open source software.
Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the "Support Pop" button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we'll work to push the Linux desktop forward with COSMIC.
Links
Guides
Hardware
Recommended
Follow the Code of Conduct
All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct
Be helpful
Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like "RTM" or links to LMGTFY. Linking to direct sources that answer the asker's question is fine, but it's advised to provide some explanation as to how you got to that source.
Critique should be constructive
We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic "It's bad" or other simple negative comments don't help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.
This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.
Don't post malicious "advice"
It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.
Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn't serious, but a new user might not.
No personal attacks
Posts making a personal attack on any user will not be tolerated.
No hate speech
Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.
The Pop Shell extension includes tiling but not the keyboard shortcuts, gestures, or anything involving workspaces.
Your options to get the full experience would be to manually configure all of those things. It would be far easier to start with Pop_os and add the packages from Kali that you want than to go the other way.
That is what I feared / thought. I was thinking about doing it the Pop!_OS to Kali direction but there are challenges there too.
Kali does a lot of very unique configurations for compatibility like still having Python 2 for backwards compatibility with the huge number of exploit scripts that were written in Python 2.
I love the idea of having the Pop!_OS and the tiling but not sure that I want to spend the time and endure the pain of making it all work. I tried playing with i3 and liked that too but there were some issues that became show stoppers.
Thanks for the reply!
I ran into a bunch of show stoppers when I first tried Linux in the late 90s. Just configuring the right settings to your monitor was a bit daunting to a newbie - and if you did it wrong you could literally fry your monitor!
Little by little I kept learning how to do things in Linux instead of in Windows. One day I uninstalled Windows altogether (no more dual boot) and decided that I was going to avoid using Windows at all costs so that I could truly learn to live in Linux full time.
That was 15 years ago, and I've been quite happy since. Windows has never been my personal OS since (I still had to work with it for my jobs, naturally).
Kali isn't meant to be a daily driver. I think you'll have a better time learning how to add those tools to a general purpose Linux distro. Doing that will teach you some of the basics on how to configure your OS to your liking while having lots of little things already configured for usability.
Kali can be run within a virtual machine too if you want to avoid some of that setup work in getting the tools installed to a different distro.
You have to install all of the cosmic extensions and the Pop session. However, extensions are sensitive to the version of GNOME you're using so you need the master_jammy branch of each extension for GNOME 42.
Thanks! This sounds promising but there is not much there in the way of ... hey ... here is what you do with this stuff.
/usr ... do I just copy the contents into the /usr directory?
/debian .... do not know what to do with this
Any pointers would be greatly appreciated.
Thanks!
These repos have makefiles so it's make && sudo make install after using git to clone the repo URLs. You can reference build dependencies in debian/control. You can call dpkg-buildpackage -b to build a debian package if you'd rather that then installing with make directly.