didnt think you were still on this thread.
when im stuck on hardware or a workload that qubes doesnt work for, i
usually do vagrant with virtualbox or kvm depending. its not as good, of
course, so still be careful. use packer to make your vagrant boxes.
github has a lot of great starting
You may want to take a look at Fedora's Silverblue immutable desktop
operating system. I had problems installing the latest version but
conceptually the OS in time will be a good alternative to Qubes which I use
as my daily driver.
--
You received this message because you are subscribed to
On Monday, August 26, 2019 at 1:24:48 AM UTC-7, panina wrote:
>
> Hi!
>
> This is not strictly Qubes-OS related, rather inspired by Qubes.
>
> I've been struggling with some parts of Qubes usage. Most of the time,
> it is overkill for me, and putting some strain on my computer. The
>
Dear Andrew,
thanks for the reminder. After my last dom0 update ("current testing")
my laptop does no longer wake up after lip-close: the screen keeps
black, nothing can be done but reboot. That is not very critical, of
course.
I find no hints in journalctl what could be the reason. Happy to
Hi!
I've used this instructions to install 2 programs using snap:
https://github.com/QubesOS/qubes-issues/issues/2766
Unfortunatelly, it happens on a regulary basis (weekly), that starting these
apps results in the following error:
[user@b ~]$ slack
internal error, please report: running
At 14:04 29/08/2019, unman wrote:
>I have to point out that you can run Qubes fine with HDD and 12GB RAM -
>even 8GB is doable.
>quick ebay suggests you can get x230 with *that* config regularly for less than
>$200 - i7 with 16GB went for $175 recently.
>If you drop down to an i5 (still workable)
Couple more:
- As windows 7 does not support SCSI unmap, and C and E are on virtual SCSI
devices: install sdelete by default and schedule sdelete.exe -z C:\ and
sdelete -z E:\ ... largish zero writes are caught at the lvm later and
unallocated from storage - plus passed on as discards to physical
Hi crazyqube,
I've used this to generate 20-30 VMs.
I've noticed some incomplete installs (50/50). There do seem to be come
timing dependencies that sometimes cause failures. I'll be investigating
these further next week.
I have some thoughts on changes I'll work on, if you're not planning
On Thu, Aug 29, 2019 at 3:02 AM rec wins wrote:
>
> OTP won't , if the key does more than U2F you may need to get a
> configuration application for the key and make sure it's U2F only
> slot 1 , 2 etc
>
Yubikey OTP works through a keyboard-like HID, which are blacklisted by
default
On Mon, Aug 26, 2019 at 05:27:00PM +, qtpie wrote:
> panina:
> >
> >
> > On 8/26/19 6:27 PM, 799 wrote:
> >> If you buy the right hardware you'll not run into lots of bugs and get
> >> enough performance to run qubes. You can buy a Lenovo T530/430, W530,
> >> X230 for not much money, add a
On Wed, Aug 28, 2019 at 09:01:46PM -1000, rec wins wrote:
> On 5/27/19 6:09 AM, Stumpy wrote:
> > I am trying to use an onlykey U2F but have run into some issues like it
> > showing up in dom0 and sys-usb but seems like i cant use it.
> >
> > in sys-usb:
> > [user@sys-usb ~]$ lsusb | grep Only
>
Awokd,
One of the machines is a B117-M and the other is a B116-M. The previous boot
debug is from the B116-M.
1) BIOS was updated to the latest available 1.23 and 1.24 on the B116-M and
B117-M respectively - still getting the KERNEL PANIC on both machines.
2) Tried disabling all non essential
On 5/27/19 6:09 AM, Stumpy wrote:
> I am trying to use an onlykey U2F but have run into some issues like it
> showing up in dom0 and sys-usb but seems like i cant use it.
>
> in sys-usb:
> [user@sys-usb ~]$ lsusb | grep Only
> Bus 004 Device 010: ID 1d50:60fc OpenMoko, Inc. OnlyKey Two-factor
>
13 matches
Mail list logo
