The file was successfully copied to dom0. Thank you very much for all your
advice!
--
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...@google
On October 12, 2017 4:25:29 PM MDT, Person wrote:
>l tried the former commands again, with “ls -lh” and “pwd”, but the
>terminal remained unresponsive, even if it was formerly responsive.
>
>So I tried changing the command around a little. The Qubes site
>mentions to enter this command: “qvm-run -
l tried the former commands again, with “ls -lh” and “pwd”, but the terminal
remained unresponsive, even if it was formerly responsive.
So I tried changing the command around a little. The Qubes site mentions to
enter this command: “qvm-run --pass-io 'cat
/path/to/file_in_src_domain' > /path/t
On Mon, Oct 09, 2017 at 08:20:44PM -0700, Person wrote:
> I have copied the file to dom0 several times without error messages, so it is
> unlikely that the transferral was unsuccessful.
>
Here are some basic Linux commands that you should use in a terminal in
dom0:
pwd - this will show you the
I have copied the file to dom0 several times without error messages, so it is
unlikely that the transferral was unsuccessful.
--
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
Once again, dom0 did not reply. I took this as a sign that the iso was
successfully copied, but the Standalone VM did not register something to boot
from and I could not find it in the dom0 filesystem again. This puzzles me,
because I am sure that the file was originally at the exact location I
On 10/03/2017 09:37 PM, Person wrote:
Because the terminal didn’t respond with an error message, I am relatively sure
that the ISO was successfully copied to dom0. Copying it to dom0 wasn’t a
problem, really, but finding it in dom0 was. And the “find” commands don’t seem
to work for finding in
Because the terminal didn’t respond with an error message, I am relatively sure
that the ISO was successfully copied to dom0. Copying it to dom0 wasn’t a
problem, really, but finding it in dom0 was. And the “find” commands don’t seem
to work for finding in dom0.
--
You received this message be
Apparently the brackets were one of my mistakes. My bad (and thank you for
pointing that out).
I ran the copy-to-dom0 and attach-to-VM commands again, and dom0 didn’t
respond. So I opened the Standalone VM and it didn’t register anything to boot
from, even though I’m sure that I copied the ISO
On Sun, Oct 01, 2017 at 09:41:03PM -0600, Ron Hunter-Duvar wrote:
> On 10/01/2017 06:59 PM, Person wrote:
> > The file was in Home/User/Downloads, and I did make sure to include the
> > command. Also, the Ubuntu file did end in “.iso”.
> >
> > I did run qvm-start in dom0. I believe I typed “qvm-s
On 10/01/2017 06:59 PM, Person wrote:
The file was in Home/User/Downloads, and I did make sure to include the
command. Also, the Ubuntu file did end in “.iso”.
I did run qvm-start in dom0. I believe I typed “qvm-start
--cdrom=sys-net:/home/user/Downloads/”, or I did the
same thing but replac
The file was in Home/User/Downloads, and I did make sure to include the
command. Also, the Ubuntu file did end in “.iso”.
I did run qvm-start in dom0. I believe I typed “qvm-start
--cdrom=sys-net:/home/user/Downloads/”, or I did
the same thing but replaced “Ubuntu” with “hvm”. (“Ubuntu” is the
On Sat, Sep 30, 2017 at 08:31:52PM -0700, Person wrote:
> When I said “I can’t find Ubuntu in dom0”, I meant that I could find the file
> in sys-net, but she. I copied it to dom0, I could not find the file in dom0,
> even though the transferral received no error messages. I apologize for any
> m
When I said “I can’t find Ubuntu in dom0”, I meant that I could find the file
in sys-net, but she. I copied it to dom0, I could not find the file in dom0,
even though the transferral received no error messages. I apologize for any
misunderstandings.
I added the XTerm to sys-net, and I used the
On Fri, Sep 29, 2017 at 07:46:19PM -0700, Person wrote:
> I tried copying the Ubuntu ISO to dom0 instead of the standalone VM directly,
> because the standalone VM only finds things to boot from in dom0.
>
> I have not received any messages from Qubes that this transfer does not work,
> but when
On Sat, Sep 23, 2017 at 07:24:25PM -0700, Person wrote:
> I believe I downloaded to [sys-net] Downloads. I can find the file easily if
> I just go to sys-net and click "Files".
>
> However, I can't find the terminal you are speaking of in sys-net
> specifically. I tried it on dom0 instead, but i
I tried copying the Ubuntu ISO to dom0 instead of the standalone VM directly,
because the standalone VM only finds things to boot from in dom0.
I have not received any messages from Qubes that this transfer does not work,
but when I look in dom0, the Ubuntu file is gone.
--
You received this m
On Sunday, September 24, 2017 at 10:24:25 AM UTC+8, Person wrote:
> I believe I downloaded to [sys-net] Downloads. I can find the file easily if
> I just go to sys-net and click "Files".
>
> However, I can't find the terminal you are speaking of in sys-net
> specifically. I tried it on dom0 inst
I believe I downloaded to [sys-net] Downloads. I can find the file easily if I
just go to sys-net and click "Files".
However, I can't find the terminal you are speaking of in sys-net specifically.
I tried it on dom0 instead, but it doesn't work.
--
You received this message because you are sub
On Wed, Sep 13, 2017 at 05:40:48PM -0700, Person wrote:
> I tried again. The website qubes-os.org had instructions to enter this code:
> --cdrom=[appvm]:[/path/to/iso/within/appvm] in dom0. How exactly do I find
> the path to the ISO?
>
You said that you downloaded the iso on sys-net - where d
20 matches
Mail list logo