Qubes OS Installation Resolution

[[NOTIFICATION]]

It appears the USB stick that was used to flash the ISO was not sufficient. Switched to a 16GB USB stick as the previous was only 8GB. The 16GB USB stick worked. After installing the QUBES OS it was pretty straightforward thereafter. The reason was because had already experienced PARROT OS. Now...

The problem with QUBES OS is not the security architecture. The problem is the ease of convenience when it comes to to eh various VM instances. As a new user to QUBES OS, it seems more complicated than usual. One of the main issues was the ethernet tethering passthrough. That was so difficult to set up due to the lack of or vague instructions. QUBES OS should have a more user friendly interface or framework. While it does seem simple as it can get, The ability to maneuver in the infrastructure can be confusing. Sometimes just using VIRTUALBOX can seem much more easier because of its visual compartmentalization. Along with the extension pack to share data between, QUBES OS does not have this setting options. In QUBES OS, you have to do it each time? Anyways, hope to some QUBES OS improvement in terms of interface and ease of use?

You should give PARROT OS a try to get familiar with some features that QUBES OS can truly benefit from. Had to revert to PARROT OS again to use the tethering that was difficult to setup in QUBES OS.

FOOTER~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Communicative Correspondence per procurationem /s/ in esse S.J. Agent

Express Actual Notice: ELECTRONIC SIGNATURES IN GLOBAL AND NATIONAL COMMERCE ACT (PUBLIC LAW 106–229—JUNE 30, 2000) & UNIFORM ELECTRONIC TRANSACTIONS ACT (1999) & UNIFORM COMMERCIAL CODE 3-401 SIGNATURE. This message is deemed private or confidential. Unless for criticism or news-report or research or scholarship or teaching or comment or opinion, this message may also be deemed copyright. Due to existence of sophisticated data collection programs globally, assume or presume by default that all digital data associated with this account is subject to intercepts, storage, surveillance or monitoring by intelligence systems and agencies, anytime or anywhere regardless of privacy or security or encryption (EO10995). Sender(s) or agent(s) accepts no liability for any message(s) or its attachment(s). All typing errors are not intended or intentional. Keep sent attachment size less than inbox size of 1 GB. Without Prejudice. All Rights Reserved. Special Deposit.

If server failure, use alternative emergency secondary secure email(s): agen...@bitmsg.ch (1GB) or agen...@elude.in (50MB)

Test your Net Security @ https://www.grc.com/x/ne.dll?rh1dkyd2

Test your browser SSL/TLS @ https://www.ssllabs.com/ssltest/viewMyClient.html

You are receiving this due to possible time zone conflicts & to reduce and save forever paper, ink, phone minutes, fax, travel fuel and national-international mail postage expenses, excluding incurred data costs.

Sent with ProtonMail Secure Email.

[awokd]

'[NOTIFICATION]' via qubes-users:

> The problem is the ease of convenience when it comes to to eh various VM instances. As a new user to QUBES OS, it seems more complicated than usual. One of the main issues was the ethernet tethering passthrough. That was so difficult to set up due to the lack of or vague instructions. QUBES OS should have a more user friendly interface or framework. While it does seem simple as it can get, The ability to maneuver in the infrastructure can be confusing. Sometimes just using VIRTUALBOX can seem much more easier because of its visual compartmentalization. Along with the extension pack to share data between, QUBES OS does not have this setting options. In QUBES OS, you have to do it each time? Anyways, hope to some QUBES OS improvement in terms of interface and ease of use?

Glad you were able to get it installed and try it out. 8GB should be
sufficient- I wonder if it's not a bad stick. I missed having a
graphical representation of networking too, when I came to Qubes from
other OS/virtualization products.

Not sure what you mean by ethernet tethering passthrough in context of
Qubes. What were you trying to do, and where did you have trouble?

[Jon deps]

you probably are not going to get far comparing VBox and Qubes, I
believe your talking about VB extensions to do things.

Qubes are designed Not to share easily, I think that is the point. So,
if your wanting a permanent data sharing between Qubes, afaik, not
possible, what would be the point ?

maybe you can make a HVM and install VBox on it and see how far you get
https://www.qubes-os.org/doc/hvm/

it's probably as complicated as you make it