On Sat, Apr 06, 2019 at 07:06:41PM -0700, Ray Joseph wrote:
> I would like to config sys-net to access my wireless AP. I have not found a
> method to config the network. I looked for /etc/network/interface to see if
> anything was there but the network folder does not exist.
>
> I found
On Sunday, April 7, 2019 at 6:06:13 AM UTC+1, haaber wrote:
> Hey Thomas,
>
> I are right, it that was definitely better to put the FAQ on the site
> (and this list). I did set up a standalone debian-10 to build, and the
> process went through smoothly. Thank you. The 'but' comes now: BUT, in
>
Hello Thomas,
Thomas Leonard schrieb am Do., 4. Apr. 2019, 12:27:
> I'd like to announce the release of qubes-mirage-firewall 0.5:
> https://github.com/mirage/qubes-mirage-firewall/releases/tag/v0.5
> (...)
> For installation instructions, see:
>
By mistake i sent direct answer, not mail to list sorry for that.
I have checked logs and found
dom0 kernel: sp5100_tco: I/O address 0x0cd6 already in use
TBD: tbd_open_ex could not open file /var/lib/xenstored/tbd no such file
or directory
xen free = too small for satisy assignments!
I'm not aware of that. I think for CB'd fam15h we need a xen patch, that will
not check the CPU features after resume, as microcode update never happens...
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
Hi 799,
Arezo using a standalone Debian VM to build the docket image?
Additionally, does it have to be a Debian 10?
As far as I know debian-10 is in testing (?).
If you look at the instructions in
https://github.com/mirage/qubes-mirage-firewall/blob/master/README.md
you'll see that building
So I was doing some security checks on a whim in my Qubes machine until I
stumbled upon discovery that my the INPUT chain of iptables in my net VM has a
rule of accepting all tcp connections to port 8082 coming from anywhere
I checked my other VMs and discovered that they didn't have this rule
So I was doing some security checks on a whim in my Qubes machine until I
stumbled upon discovery that my the INPUT chain of iptables in my net VM has a
rule of accepting all tcp connections to port 8082 coming from anywhere
I checked and confirm the same line in my sys-net:
-A INPUT -i vif+
@haaber thank you for your response and information provided to my inquiry
Unfortunately I have already performed a full update of VMs before I discovered
this but I will check up on this through an update/install whenever I'm free
from my work in order to provide an update about this
--
You
On Sunday, April 7, 2019 at 6:06:13 AM UTC+1, haaber wrote:
Hey Thomas,
I are right, it that was definitely better to put the FAQ on the site
(and this list). I did set up a standalone debian-10 to build, and the
process went through smoothly. Thank you. The 'but' comes now: BUT, in
the end the
Hello haaber,
As you have at least some more progress and are currently busy resolving
issues with the build process, maybe you can help me coming to this point.
haaber schrieb am Mo., 8. April.
> (...) So: I did it, actually
> three times, more and more frustrated.
Arezo using a standalone
On Sat, 2019-04-06 at 06:31 -0700, Thomas Leonard wrote:
> I got a few emails about this. I'm going to answer the questions here
> because this is a community project and everyone should see the
> discussion.
>
> Q: The build-with-docker script hard-codes /home/opam. What if your
> user has a
12 matches
Mail list logo
