Junior Spellweaver
- Joined
- Mar 28, 2014
- Messages
- 186
- Reaction score
- 22
The more I have been thinking about it, the more I want to 'future proof' this release too (especially since/if this winds up being my last release/update)!
So, the segmentation fault errors that Ubuntu 12.04.3 is causing in Win10 and/or VMware 16 environments does have me (overall) concerned about this..! So, moving forward I am going to look into a version that will not seg fault under a Win10/VMware16 - but is also already EOL...
My thoughts behind this are, if I just update to "the latest and greatest" or to *anything* that's currently still "supported" (in ANY way [including ESM]) - they could change something, at any point, that would cause it and or this package to no longer work! So, my thoughts/hopes are that a fully EOL version of Ubuntu server, that doesn't already currently incur a segmentation fault on Win10/VMware16, may be the most solid choice to go with for said "future proofing"... Because if/since it's already EOL, they will NOT be changing anything about it moving forward... So, at least in theory, that would mean that version combined with this package could (again in theory) work "forever"... And that's what I want, I would like for this release package to still be able to function 100 or even 1000 years from now (even if they have to go back to Win7 or Win10 too)..!
So, all that being said I have already begun my research on which version of Ubuntu I should "require" and use in/for/with this package release..! So far most of my homework has been reading and studying this page ~You must be registered to see linksWhich, if I'm reading it correctly, they actually EOL'd 12.04.3 in 2014..! As where even the "base" 12.04 (12.04.0) received support until EOL in 2017..! Also, it looks as though 12.04.5 is actually still "supported" (in "ESM") as well..!
So, my current thoughts are switching the "requirement" to be for Ubuntu 12.04 x64 - instead of 12.04.3..! I am currently testing some of the things that I can test to assure I can switch this over from 12.04.3 to base 12.04 (12.04.0)... However, I CANNOT test to see if 12.04.0 gets a seg fault when installing on Win10/VMware16 since I do not have either...
So, if someone could please let me know if Ubuntu 12.04 (12.04.0) gets the segmentation fault on Win10/VMware16 (like 12.04.3 does) ~ I would GREATLY appreciate it..!
You must be registered to see links
You must be registered to see links
Linux support is only persuaded by the support of it is industry and warranty of service. It has nothing to do with comparability across versions and editions. You can still install the packages offline if you are not using a distro officiated downloader like apt-get. Just use the linux OS with the supported comparability and kernel package. I like always the shortcut. Instead of changing the OS version over and over. Just provide the required packages to install on the provided OS by you. That way your support of your release can have a lifetime run. Windows 10 is unnecessary as well. If you notice the whole lot of Operating systems now are taking the path of closed platforms like consoles. Sooner or later, Jailbreak over operating systems will become a thing like on Android platform.
The more I have been thinking about it, the more I want to 'future proof' this release too (especially since/if this winds up being my last release/update)!
So, the segmentation fault errors that Ubuntu 12.04.3 is causing in Win10 and/or VMware 16 environments does have me (overall) concerned about this..! So, moving forward I am going to look into a version that will not seg fault under a Win10/VMware16 - but is also already EOL...
My thoughts behind this are, if I just update to "the latest and greatest" or to *anything* that's currently still "supported" (in ANY way [including ESM]) - they could change something, at any point, that would cause it and or this package to no longer work! So, my thoughts/hopes are that a fully EOL version of Ubuntu server, that doesn't already currently incur a segmentation fault on Win10/VMware16, may be the most solid choice to go with for said "future proofing"... Because if/since it's already EOL, they will NOT be changing anything about it moving forward... So, at least in theory, that would mean that version combined with this package could (again in theory) work "forever"... And that's what I want, I would like for this release package to still be able to function 100 or even 1000 years from now (even if they have to go back to Win7 or Win10 too)..!
So, all that being said I have already begun my research on which version of Ubuntu I should "require" and use in/for/with this package release..! So far most of my homework has been reading and studying this page ~You must be registered to see linksWhich, if I'm reading it correctly, they actually EOL'd 12.04.3 in 2014..! As where even the "base" 12.04 (12.04.0) received support until EOL in 2017..! Also, it looks as though 12.04.5 is actually still "supported" (in "ESM") as well..!
So, my current thoughts are switching the "requirement" to be for Ubuntu 12.04 x64 - instead of 12.04.3..! I am currently testing some of the things that I can test to assure I can switch this over from 12.04.3 to base 12.04 (12.04.0)... However, I CANNOT test to see if 12.04.0 gets a seg fault when installing on Win10/VMware16 since I do not have either...
So, if someone could please let me know if Ubuntu 12.04 (12.04.0) gets the segmentation fault on Win10/VMware16 (like 12.04.3 does) ~ I would GREATLY appreciate it..!
You must be registered to see links
You must be registered to see links
donno why 343 posted that openly when he privately contacted me to do the same thing, it's been confirmed to work on VMware player on win 10 as well
Well, sorry, was getting impatient as I was literally sitting here needing to know the results before I can continue my work
Let me preface by saying: I think I "get" what you're saying, I think...
But I've been between a rock and a hard spot with the "requirements" of this package all along because it's not even meant for Windows anything in the first place; well the client is of course, but the server is NOT... The server is MEANT to be installed on ACTUAL linux, not a VM... BUT I also know, or maybe just assume? That most people downloading this will not have a spare machine (let alone an actual server machine) to run it on, and are most likely downloading it to "play around" (AKA "mess around")... Maybe even made a server that their family/friends will play on; but will likely never run a server that will see numbers in the thousands..!
All that being said, the ONLY reason this package "requires" a specific OS: Ubuntu 12.04.3 x64 - is because of the offline install it does of IA32-LIBS..! I do want the "base package" to have absolutely ZERO external dependencies - ergo, can be installed with absolutely no interwebs connection whatsoever:
That being said I often say "requires" specifically in quotes because obviously anyone with enough experience will know how to make it work with ANY OS of their choice... While the default installer I've made does "require" what it requires, there are plenty of ways around this - some I've even built in (for those who care to look)! So, could you take this and manually install it on Ubuntu 20.x, sure... Could you take it and install it on CentOS, or RH, or FC, - I'm almost sure of it... If you want to, and (actually) know what you're doing...
I'm thinking that will not be most people that download this...
At one point I thought about going down the path of making it a "real" .DEB; but then I urged myself against that because I figured why limit it to DEBIAN based distros!? For the same reason I wouldn't have considered making it an .RPM either...!
But for the most basic of use (and users) I have to "require" what I have to "require" in order to facilitate an installation which is 100% "self sufficient"! That, as long as you have the "required" OS (ISO) and this package (ISOs) and a PC, you can and will succeed at getting it installed. Even if the interwebs blew up tomorrow and ceased to exist, or if you were on an island with a laptop and a solar generator ROFL... Or whatever scenario you could dream up (that's never even going to happen in the first place)... But, point being = it has NO/ZERO external dependencies:
So, back to point - I think LOL; sure, Ubuntu x64 12.04.3 would continue to "do the job" if actually installing it on a physical machine (like a server)! Which is what this SHOULD be, but I also DO have to "cater" (to some degree) to those which I know will not "do things 'right'" whether by choice, or limitation...
So I do suppose for the actual longevity moving forward; I can supply Ubuntu 12.04 LTS x64, this package, and at some point I may find myself having to add an ISO for Win7 / Win10 for the client, and for those who actually WANT (again, for whatever reason, choice or hardware/financial limitation) to also run the Server in a VM with a Win host...
So, IDK if that all even made any sense, but I know what I'm thinking LOL I guess to TL;DR would be; yes, there's NO reason for "compatibility" between Win and Linux (and VMs)... BUT; I also know/figure that is how MOST people that DL this are actually gonna use it! So while I cannot assure 100% compatibility - I will still do my best to make sure my package/release is as versatile as humanly possible..!
Using the 18'th of March files listed in the 1st post.