On 4/9/19 12:58 PM, Ray Joseph wrote:
Thank you for your support. I don't know what 'panel' I should see the
nm-applet opening in. I opened a terminal in sys-net and entered nm-applet and
obtained a response that said it was not meant to run in terminal and to use
NetworkManager in the
Thank you for your support. I don't know what 'panel' I should see the
nm-applet opening in. I opened a terminal in sys-net and entered nm-applet and
obtained a response that said it was not meant to run in terminal and to use
NetworkManager in the desktop. I don't see a way to open a
I have stated this many times before.
The PS/2 thing is from 2011 which is 8 years ago and applies to systems
without more than one USB controller.
Using PS/2 sends your keystrokes out on the ground wire.
It is far better to purchase a motherboard with a second USB controller
with separate
as you may have noticed by the mirage-firewall discussions, one
impressive point is the size of mirage -- 32M. That is not yet the 640K
I grew up with, but much more memory-friendly than the
standard-sys-firewall (which took 384M in my system). Another (to me:
inexplicably large) qube in my
On Tuesday, April 9, 2019 1:42 AM, 799 wrote:
> Thanks for the summary, this is what I was looking for. I am using
> fedora-29-minimal for all my AppVM's, therefore I didn't thought that the
> problem might be template related.
> I'll run the same steps you did tomorrow.
Yes I noticed after
Hello qmirfw,
'qmirfw' via qubes-users schrieb am Di., 9.
Apr. 2019, 00:51:
> On Monday, April 8, 2019 11:40 PM, 799 wrote:
> > Any ideas what I am missing?
>
> I don't know. I just did a build using fedora (based on unmodified Qubes
> fedora-29 template) and got no error, final checksum
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Qubes Community,
We have published Qubes Canary #19. The text of this canary is
reproduced below. This canary and its accompanying signatures will
always be available in the Qubes Security Pack (qubes-secpack).
View Qubes Canary #19 in the
On Monday, April 8, 2019 11:40 PM, 799 wrote:
> Any ideas what I am missing?
I don't know. I just did a build using fedora (based on unmodified Qubes
fedora-29 template) and got no error, final checksum checks out. This is what I
did:
# # # In dom0 root terminal:
qvm-create
Hello,
I got the qubes-mirage-firewall working in a simple
sys-net --> sys-mirage-fw --> disp1234
situation, but when I wanted to include it in my normal chain, as in
sys-net --> sys-mirage-fw --> sys-firewall --> AppVMs
my AppVMs can't access the network.
Is this supposed to work?
In Xen
On Monday, April 8, 2019 11:40 PM, 799 wrote:
> I tried to build mirage in a new template VM which is based on
> fedora-29-minimal, but run into an error.
I don't understand why you want to do all that in a TemplateVM, and not an
AppVM.
Also why fight with Fedora, if my simple Debian based
@ 799, I got these errors when using the repo-version of docker instead
of docker-ce directly (see my last 2-3 posts) here.
See https://docs.docker.com/install/linux/docker-ce/debian/
and https://docs.docker.com/install/linux/docker-ce/fedora/
for download instructions.
@Thomas Leonard: YES,
Hello,
I've created a howto page in the Qubes Community docs to collect all
information which is needed to build/install the mirage firewall for qubes
OS.
https://github.com/Qubes-Community/Contents/blob/master/docs/customization/mirage-firewall.md
I tried to build mirage in a new template VM
On Monday, April 8, 2019 at 8:32:09 PM UTC+2, tai...@gmx.com wrote:
> On 02/25/2019 04:02 PM, John Mitchell wrote:
> > If I may ask what OS do you use for the host?
> >
>
> Devuan, it is debian without systemd.
>
> I compile most of the related packages though like libvirtd, qemu etc
> cause the
qubes123 wrote on 4/8/19 6:08 PM:
...distribution kernels (fedora, debian) with xen 4.11.1 still have issues with
suspend & g505s...
Understood, thank you! That will save a lot of testing time. I'm still
getting my build environment stood up, but will update once I can
confirm the
Hello Jayen,
I have realtek wifi adapter in my lenovo laptop ideapad 330 15arr model. It
> is not recognised by sys-net VM.
I have a similar laptop to you (Ideapad 330S-15ARR).
I was not able to compile the kernel module when using the Qubes provided
virtual machine kernel. I switched sys-net
On 02/25/2019 04:02 PM, John Mitchell wrote:
> If I may ask what OS do you use for the host?
>
Devuan, it is debian without systemd.
I compile most of the related packages though like libvirtd, qemu etc
cause the ones from the distro are way too outdated to support what I need.
You should get a
On 03/01/2019 09:21 PM, unman wrote:
> On Fri, Mar 01, 2019 at 07:27:08PM +, Achim Patzner wrote:
>> On 28.02.2019 15:10:21, "unman" wrote:
>>
>>
>>> On Thu, Feb 28, 2019 at 11:03:12AM +0100, Achim Patzner wrote:
On 20190227 at 22:30 -0800 cooloutac wrote:
Whenever I
On 03/05/2019 03:22 PM, cooloutac wrote:
> I agree with Chris its more a compatibility issue then an installation issue.
>
> You really have to research the machine on linux before using it in Qubes.
> And have to make sure the bios has the nescessary options before purchase,
> which is one of
System seventysuck, pur.idiots etc are LYING about having "open source
firmware"
System seventysuck also lies about having "made in usa" hardware
literally all they did was make a metal case here and somehow a metal
box equals a computer in their world.
Their "coreboot" is nothing more than a
...distribution kernels (fedora, debian) with xen 4.11.1 still have issues with
suspend & g505s...
--
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
Hi,
I bought a brand new Inspiron 3480 just for Qubes. It has the most recent
bios/firmware and an i5-8265 cpu/platform. When trying to boot the
installer from USB the screen just blinks up once with 6 lines of text and
then goes black and nothing happens.
I have tried other USB Sticks but the
On 4/8/19 11:24 AM, unman wrote:
On Mon, Apr 08, 2019 at 10:30:23PM +1000, haaber wrote:
Dear qubes-users,
is there a comprehensive way how to down-size a (template) VM ? Let us
assume, that a df shows the template uses 9.2G as root volume. Assume
further that for some reason I had temporarily
Hello,
'qmirfw' via qubes-users schrieb am Mo., 8.
Apr. 2019, 16:08:
> (...)
> This is what I do:
(...)
>
Unfortunately I don't understand all steps, for example what ...
# Fix the reproducible build
git pull origin pull/52/head
... means.
As the firewall is very (!) important to keep Qubes
On Mon, Apr 08, 2019 at 10:30:23PM +1000, haaber wrote:
> Dear qubes-users,
> is there a comprehensive way how to down-size a (template) VM ? Let us
> assume, that a df shows the template uses 9.2G as root volume. Assume
> further that for some reason I had temporarily increased the root vol to
>
‐‐‐ Original Message ‐‐‐
On Monday, April 8, 2019 2:29 PM, haaber wrote:
> > Addition: but even after successful compilation, the hash still didn't
> > match for me, probably because of what Thomas Leonard already mentioned (
> > https://github.com/mirage/qubes-mirage-firewall/pull/52
On Monday, April 8, 2019 at 1:29:53 PM UTC+1, haaber wrote:
[...]
> Q2: How do you integrate the pull/52 into the qubes-mirage-firewall
> folder without fiddling files by hand?
To test that PR:
git pull origin pull/52/head
rm -rf _build
sudo ./build-with-docker.sh
--
You received this message
On Monday, April 8, 2019 at 12:29:30 PM UTC+1, haaber wrote:
> here is some build-news. next hint: give your template a lot of *disk
> space*. My last error was due to that, but of course it did not tell me
> "disc full" but some random other message. So now I am getting closer:
> sudo
Addition: but even after successful compilation, the hash still didn't match
for me, probably because of what Thomas Leonard already mentioned (
https://github.com/mirage/qubes-mirage-firewall/pull/52 ). Can we get a 0.5.1
release? I'd contribute with a more step-by-step build instructions doc
Addition: but even after successful compilation, the hash still didn't match
for me, probably because of what Thomas Leonard already mentioned (
https://github.com/mirage/qubes-mirage-firewall/pull/52 ). Can we get a 0.5.1
release? I'd contribute with a more step-by-step build instructions doc
here is some build-news. next hint: give your template a lot of *disk
space*. My last error was due to that, but of course it did not tell me
"disc full" but some random other message. So now I am getting closer:
sudo ./build-with-docker.sh
Step 9/9:
Successfully tagged
> I believe that the Qubes sys-firewall by default prevents template
VMs > from connecting to anything except their package repositories.
It's OK > to install Docker in a template VM if you want, but everything
else
> should be done in an AppVM.
no, I use a StandAlone debian buster with net
On Monday, April 8, 2019 at 2:20:28 AM UTC+1, haaber wrote:
> > 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
>
On Sunday, April 7, 2019 at 9:23:13 PM UTC+1, 799 wrote:
> 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
So I have briefly read README.md about this and does this thing really have to
run as a PV VM and cannot be a PVH VM?
--
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
On Sunday, April 7, 2019 at 8:23:13 PM UTC, 799 wrote:
> 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
On 4/7/19 7:40 PM, Cranix wrote:
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
36 matches
Mail list logo
