On 08/30/2016 07:28 AM, Drew White wrote:
On Tuesday, 30 August 2016 16:26:40 UTC+10, Andrew David Wong wrote:
The minimum requirements haven't been officially announced yet. (Only
the requirements for Qubes Hardware Certification have been).
Well, it would be good to know now, BEFORE the time comes.
Because if this PC isn't good enough for it, then I'll leave Qubes behind.
I've got 24 thread CPUs with 32 GB RAM multiple SSDs, several Monitors..
Your Windows Tools have NOT been fixed yet either, not since Qubes 2.0.
The Qubes Manager has not been fixed, forcing me to make my own for Qubes
3.0/3.1/3.2
I'd love to know what the requirements are now so that I know what is going on
and whether it will require me spending thousands of dollars on a new
workstation or not.
I'd also love to know if the bugs in Qubes are ever going to be fixed, since
they have been there since version 2, and I have been reporting them over and
over again, and nothing has ever happenned about them (to my knowledge).
So I'm just trying to work out if Qubes is actually going to be fully security
related or not, whether I'll be able to run it on my X5650 CPUs or not.
Whether I will need new ECC RAM or not. Or even if Qubes will work with it or
not.
And will Qubes be able to handle multiple HDD's on install or not? Or will it
still just see the HDDs as 1? Is that a hardware fault/requirement or one that
is in the installer itself?
I'd love to know the answers to the issues sometimes.
And as has stated, will it be requiring some hardware that is not that good?
Hope to hear from you sometime regarding the requirements. Not "officially"
stating the requirements, but just what's being looked at as the MINIMUM requirements for
it will be enough, just to give me an idea of what you will be requiring for the O/S.
I was also looking at building Qubes to use on some of my other devices, but as
I said, if the hardware isn't up to requirements, then it won't work and not
something I will be able to do.
Please let me know ASAP.
If it is going to be FORCED to HAVE SLAT, then my CPUs aren't going to be able
to have Qubes 4.
And after you go to Qubes 4, you will not update any previous versions. So the
operating system will just become stagnant for most likely 75% of the people
that are using it now.
Stagnant!? Heh.....I'm still on R2.1.
However, In spite of recent revelations of a couple of XEN
vulnerabilities, I remain thoroughly satisfied with the still-potent
security of this box.
Had to do a couple of things:
1. Maintain applications from author or other distributions. No more
sudo yum update - first time it's a PITA; from then on it becomes routine.
2. Use DISPVMs for all online applications. This requires some
scripting, but is extremely reassuring anytime an application acts funky
on this aging OS. I don't have to fret about a possibly-infected user
application remaining permanently untrustworthy on an APPVM, and wonder
if this would have been avoided on a current version of Qubes; I simply
flush the DISPVM and load up another copy.
My point here is that if you have R3.x running satisfactorily, please
stick with it - it'll be less than leading edge, but plenty secure for a
few years, at which point you can buy a new box proven to work smoothly
on R7.x - perhaps a "stateless" box.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/e9c863e7-3215-2759-bab9-69e22df9ec61%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
