Check Linux Version
Elpidio Heart
Linux versions are different distributions of the Linux operating system that are based on the Linux kernel. Some of the most popular Linux versions are Ubuntu, Debian, Fedora, and Mint. Each version has its own features, software repositories, and update cycles. Linux versions can be used for desktops, servers, smartphones, and other devices.
If you have any further issues, questions, or would like some assistance checking on this or anything else, please reach out to us from your my.hivelocity.net account and provide your server credentials within the encrypted field for the best possible security and support.
If you are unable to reach your my.hivelocity.net account or if you are on the go, please reach out from your valid my.hivelocity.net account email to us here at: sup...@hivelocity.net. We are also available to you through our phone and live chat system 24/7/365.
I'm running LAMP on Proxmox VE. I saw a new version of Turnkey came out today and thought, "Huh, what version do I currently have?" I understand it's supposed to update automatically, but I was curious how to check.
I logged into the shell, but can't find a list of Turnkey specific commands anywhere, and "help" just gives me Linux commands. How do I check the version? And, so I can stop asking such mind-numbing questions, is there a place I can go to wisen myself to the ways of Linux and Turnkey commands?
As for TurnKey-specific commands I think 'man tklbam' pretty much covers it. And there is turnkey-sysinfo that is displayed when you ssh in. Eveything else pretty much requires a recent book on Linux.
I don't mean to say that you should've googled your questions, more that google will provide heaps of information about Linux. Personally i find google to be the most valuable resource for Linux info.
Although if you want more specific info in regards to TKL then the Ubuntu forums and docs are very useful (TKL v11.x is based on Ubuntu 10.04). There is obviously some limited TKL specific docs here in the 'docs' section as well as heaps of gems here in the forums (but you have to dig). The Ubuntu Server Guide (google it) is chock full of useful genericly relevant info (although quite a bit of it is not relevant to TKL as a lot of the config is already done in TKL - but it is still useful if you want to understand some of the stuff under the hood). Info regarding Debian is often relevant too (Ubuntu is in turn loosely based on Debian). And there is plenty of other generic Linux info that you will find is common to all Linux distros.
If you want to find out how to use a specific command then most packages have manual info available straight from the commandline using the man command (like Dan suggested you do with tklbam). These days there are tons of newb friendly 'intro' type sites and lots of info on Wikipedia. Although a good book like Dan suggested is probably not a bad idea if you want to get a coherant overview.
The sad truth is: I did Google first, but quickly found I wasn't even sure what I was searching for. The terminology I was using seemed to be leading me in all the wrong directions. I know enough about Linux to get along on the very surface, but getting deeper requires at least enough knowledge to know where to start digging.
Anyway, thanks for the resources and directions. I will definitely look into the Ubuntu docs. I'm not sure where Ubuntu ends and Turnkey begins, but I suspect I'll figure that out later down the road. As far as books go, any recommendations? I'd be happy to buy one, but I trust your recommendations over my "Huh, that's a nice cover" sensibility.
As for a Linux book, unfortunately I can't recommend anything. I've never read one. Everything I know about Linux has been learned first hand or via google (and/or Ubuntu docs and/or Ubuntu forums and/or TKL forums and/or trying to help other people around here on the TKL forums).
I started 3 years ago with no Linux experience at all, I have signifcant experience as a Win Admin though (the worst kind of Linux newb so I've been told!) I dived in the deep end by ditching Win at home and going for a Linux (Ubuntu 8.04, then 9.04, then 10.04) desktop plus a Proxmox server with lots of TKL VMs. Nothing like having to try to be productive to hone your skills! :) It took at lot of patience and it was quite a steep learning curve but it's paid off. I still wouldn't consider myself a "Linux expert" but I know a few things... And I am definitely a convert. I still use Windows, but only because I have to. And I understand that it still has it's place, but I don't really get why more people don't use it - for example Education and/or Government. Anyway I won't harp on...
As for where Ubuntu ends and TKL starts, that's a bit of a tricky one. Under the hood, TKL is Ubuntu (v11.x is based on 10.04). But it is a highly customised system with a lot of software pre-installed. It also has some TKL only features such as TKLBAM. Beyond TKLBAM though it still essentially remains mostly Ubuntu.
Don't be scared to ask questions here. Obviously do a bit of a hunt around first, but if you're having trouble finding the answers then you can guarantee others have had (or will have) the same or similar issues. I am always happy to share what knowledge I have, especially if you're trying to help yourself (which you obviously are). The other side of it is, if you do find an answer to something that you think is worth sharing, then by all means post it here and/or edit the TKL docs.
Yeah, I do not have a book recommendation either since I started using Linux about 14 years ago and just kept poking around. If you like webmin as a gentler introduction, there are some webmin-specific book
here:
I think that approach could help you understand more about all of the components, how they fit together, and their features. From there, you can really learn a lot more from the web sites of the components you are using most heavily.
There are two ways that I can think of. The first is to grep the JAMFSoftwareServer.log. The version is written on every startup. The other is to check the version.xml inside the deployed application. It should be in $JSS_INSTALL/tomcat/webapps/ROOT/WEB-INF/xml. It holds all of the version of different binaries in a normal xml format.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
I am looking to see how to check the current TLS version on a linux box. We are needing to do some upgrades for payment requirements and need to check this out. In my research I found that there is no cmd that will spit out this info. Any help is greatly appreciated.
I have an ArchLinux Docker container and would like to detect on the ArchLinux version.
I have tried all the common Linux commands for version detection, but have not found any successful variants.
@jasonwryan
If I use a docker container, then the operating system running in the container uses the kernel of the guest OS.
At this point, I can't tell if I'm using an outdated ArchLinux that may even have known security issues.
What is wrong with my thinking?
Then update your system. Once you run the update, you are all set for any known security issues (and generally for many that are not even yet publicly well known ... security patches frequently make it to the arch repos before any popular media reports on a given vulnerability). In other words, don't try to check a version to see if you could be vulnerable, just update and eliminate any such possibility.
1) That's releases of the isos. 2) You don't even install what is on the iso, you install the most up-to-date packages at the time of your installation regardless of which iso you use.
What is my motivation? We offer Versio.io, a solution that enables enterprise customers to verify product lifecycle and security governance compliance.
And here we were missing Arch Linux in the knowledgebase. But with your comments, we now know how to map it in the knowledgebase. Thank you!
First off, they are all correct. Arch is a "rolling release" there is no "version". However, I do know that, during boot, you may get a message that looks like an "Arch Version" (Currently "252.4-2-arch" as of the time of my typing this). That is actually the Systemd version and you can get that by typing "systemctl --version" in the command line. That, along with "uname -r" to get the current running kernel could, perhaps, be thought of as your current build state of Arch.
Since not all packages are updated every day, and depending on your setup, there is no rule for saying it's now outdated, or it's up-to-date,
but you can put in a very rough calculation, maybe you get better numbers from others here:
1 day: system probably up-to-date
30 days: system probably outdated
90 days: system outdated.
That tells you virtually nothing as one could install a new package without updating anything else. A less-problematic approach would be to check the age of the sync databases - though it is possible that a user could sync the databases without updating. Though that is completely unsupported / ill-advised, and no reasonable archer ever would:
At a Windows 10 command prompt, run ver. Is the next-to-last numeric group version 18917 or higher? If so, it is possible you have WSL 2 but not yet verified. Go on to step A or B.
If you do not see Windows version 18917 or higher, you have version 1.
This illustrates the result when the OS is Build 16299: