Re: [qubes-users] Qubes 4.0-rc3
On 13/01/2018 03.34, Andrew David Wong wrote:
> On 2018-01-12 08:00, 'awokd' via qubes-users wrote:
> > On Fri, January 12, 2018 1:09 pm, Holger Levsen wrote:
>
> >> I'm not so sure, why not use git branches?
>
>
> One reason that comes to mind:
>
> Segregating the documentation into two different branches would mean
> that contributions that apply to both Qubes versions would only end up
> in one branch, unless someone remembers to manually submit the same
> thing to the other branch and actually makes the effort to do so. Most
> of the time, this won't happen. When it does, it means a second pull
> request that has to be reviewed. Over time, the different branches
> will diverge in non-version-specific content. Good general content
> that was submitted only to the 3.2 branch will effectively disappear
> once 3.2 is deprecated. (Even if it's still on the website, no one
> will look at it, since it'll explicitly be in the subdirectory of a
> deprecated version. And there will be a motivation to remove it from
> the website so that search results aren't populated with out-of-date
> information.)
That ought to be part of the review process, don't you think? ("Have
you opened PRs for these other branches?")
--
Rudd-O
http://rudd-o.com/
--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/ae6779fd-2cfb-bcbb-273e-2c8536cf0fb0%40rudd-o.com.
Re: [qubes-users] Qubes 4.0-rc3
On 12/01/2018 14.09, Holger Levsen wrote: > On Fri, Jan 12, 2018 at 01:04:23PM +, 'Tom Zander' via qubes-users wrote: >> On Friday, 12 January 2018 11:18:19 GMT 'awokd' via qubes-users wrote: >>> Would it be of value if I went through the published Docs and added these >>> version headers? Should newer versions be added at the top (so 4.0 before >>> 3.2 content)? 4.0 might just be "TBD". >> I think that would be wonderful, > I'm not so sure, why not use git branches? This ought to be the chosen solution. Mount the release 4.0 branch on doc/ and the older releases on doc/, then provide links at the top (Doc for / <3.2>). -- Rudd-O http://rudd-o.com/ -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4e04b5cb-6366-e1de-4c27-2218f522e02a%40rudd-o.com.
Re: [qubes-users] Creating ones own Insurgo
On Thu, Apr 16, 2020 at 07:14:39PM +, 'awokd' via qubes-users wrote: > True, but he should be able to use a non-Intel USB wifi adapter for > networking and disable the on-board Intel wifi in BIOS config or remove > the card entirely. It's unlikely (but not impossible) ME has drivers > built in that support networking over a 3rd party USB adapter. Can't say either way. I would assume that if you can connect, the ME can connect. On the other hand, for most peoples thread scenario a zero-day exploit of the ME is probably not very high on the list. Just like XEN virtualization escapes. Qubes brings you very far in terms of security even when running on top of ME. Important here is proper compartmentalization and having sensitive data in offline qubes only. Beyond that social engineering is probably your biggest worry. But I am getting rapidly off topic. Sorry. /Sven -- public key: https://www.svensemmler.org/0x8F541FB6.asc fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200416210403.GA1293%40app-email-private. signature.asc Description: PGP signature
Re: [qubes-users] Build USB install with kernel 5+
>> >> -> Updating sources for linux-kernel... >> --> Fetching from https://github.com/QubesOS/qubes-linux-kernel.git >> kernel-5.6... >> fatal: Remote branch kernel-5.6 not found in upstream origin >> > There is a typo in 3.2. It should be : > > GIT_URL_linux_kernel=... > > instead of just > > URL_... > Also, if you wait a little bit, it will be in official repository soon. The PR has been merged few minutes ago and the build is in progress :) -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e1b9c33e-1512-6604-d158-311eaa5cfdba%40qubes-os.org. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Build USB install with kernel 5+
On 2020-04-16 22:34, 'Max Andersen' via qubes-users wrote:
>
> On 4/15/20 10:05 AM, Frédéric Pierret wrote:
>> On 2020-04-15 08:09, Max Andersen wrote:
Den 14. apr. 2020 kl. 08.02 skrev Frédéric Pierret
:
Hi,
I used to build newer ISO in the past for such troubles with kernel-latest
embedded. If you are interested, I can build you an 4.0.3 with
kernel-latest-5.6 for try?
>>> When I try, the builder script fails horribly. Can you write a stepguide?
>>> Maybe just commands and selections on how you build it(if it is not too
>>> much of a hassle)?
>> Sure, here are the procedure for building latest Qubes 4.0.3 ISO with
>> already built packages (templates included) using Qubes OS official
>> repositories:
>>
>> 1) In a working directory, e.g. `/home/user/`, clone `qubes-builder`:
>>
>> git clone https://github.com/QubesOS/qubes-builder
>>
>> 2) Download specific builder conf file for such process:
>>
>> wget
>> https://raw.githubusercontent.com/QubesOS/qubes-release-configs/master/R4.0/qubes-os-iso-full-online.conf
>> -O /home/user/qubes-builder/builder.conf
>>
>> 3) Enable QubesOS testing packages for the build and specify release branch
>> for the installer:
>>
>> echo 'USE_QUBES_REPO_TESTING=1' >> /home/user/qubes-builder/builder.conf
>> echo 'BRANCH_installer_qubes_os=release4.0' >>
>> /home/user/qubes-builder/builder.conf
>>
>> 4) Get sources:
>>
>> cd /home/user/qubes-builder/
>> make get-sources
>>
>> 5) Enable `kernel-latest` in the ISO build process:
>>
>> sed -i 's#\(> type="\)optional\(">kernel-latest.*$\)#\1mandatory\2#'
>> qubes-src/installer-qubes-os/conf/comps-qubes.xml
>>
>> 6) Build ISO:
>>
>> make iso
>>
>> 7) Get your freshly built ISO in `/home/user/qubes-builder/iso`
>>
>> The current kernel-5.6 is still at PR stage. If you want to try it you need
>> to build it:
>>
>> 3.1) Add `linux-kernel` in `COMPONENTS`:
>>
>> echo 'COMPONENTS+=linux-kernel'
>>
>> 3.2) Change URL and BRANCH of the git repository:
>>
>> echo 'URL_linux_kernel=https://github.com/fepitre/qubes-linux-kernel' >>
>> /home/user/qubes-builder/builder.conf
>> echo 'BRANCH_linux_kernel=kernel-5.6' >>
>> /home/user/qubes-builder/builder.conf
>>
>> 4.1) Get sources of it:
>>
>> make get-sources
>
>
> It went quite well with 5.5.13, but not with 5.6. I get the error:
>
> -> Updating sources for linux-kernel...
> --> Fetching from https://github.com/QubesOS/qubes-linux-kernel.git
> kernel-5.6...
> fatal: Remote branch kernel-5.6 not found in upstream origin
>
There is a typo in 3.2. It should be :
GIT_URL_linux_kernel=...
instead of just
URL_...
--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/95ab3e94-6d4a-7969-f461-885c71f9e368%40qubes-os.org.
signature.asc
Description: OpenPGP digital signature
Re: [qubes-users] Build USB install with kernel 5+
On 4/15/20 10:05 AM, Frédéric Pierret wrote:
> On 2020-04-15 08:09, Max Andersen wrote:
>>
>>> Den 14. apr. 2020 kl. 08.02 skrev Frédéric Pierret
>>> :
>>>
>>> Hi,
>>> I used to build newer ISO in the past for such troubles with kernel-latest
>>> embedded. If you are interested, I can build you an 4.0.3 with
>>> kernel-latest-5.6 for try?
>> When I try, the builder script fails horribly. Can you write a stepguide?
>> Maybe just commands and selections on how you build it(if it is not too much
>> of a hassle)?
> Sure, here are the procedure for building latest Qubes 4.0.3 ISO with already
> built packages (templates included) using Qubes OS official repositories:
>
> 1) In a working directory, e.g. `/home/user/`, clone `qubes-builder`:
>
> git clone https://github.com/QubesOS/qubes-builder
>
> 2) Download specific builder conf file for such process:
>
> wget
> https://raw.githubusercontent.com/QubesOS/qubes-release-configs/master/R4.0/qubes-os-iso-full-online.conf
> -O /home/user/qubes-builder/builder.conf
>
> 3) Enable QubesOS testing packages for the build and specify release branch
> for the installer:
>
> echo 'USE_QUBES_REPO_TESTING=1' >> /home/user/qubes-builder/builder.conf
> echo 'BRANCH_installer_qubes_os=release4.0' >>
> /home/user/qubes-builder/builder.conf
>
> 4) Get sources:
>
> cd /home/user/qubes-builder/
> make get-sources
>
> 5) Enable `kernel-latest` in the ISO build process:
>
> sed -i 's#\( type="\)optional\(">kernel-latest.*$\)#\1mandatory\2#'
> qubes-src/installer-qubes-os/conf/comps-qubes.xml
>
> 6) Build ISO:
>
> make iso
>
> 7) Get your freshly built ISO in `/home/user/qubes-builder/iso`
>
> The current kernel-5.6 is still at PR stage. If you want to try it you need
> to build it:
>
> 3.1) Add `linux-kernel` in `COMPONENTS`:
>
> echo 'COMPONENTS+=linux-kernel'
>
> 3.2) Change URL and BRANCH of the git repository:
>
> echo 'URL_linux_kernel=https://github.com/fepitre/qubes-linux-kernel' >>
> /home/user/qubes-builder/builder.conf
> echo 'BRANCH_linux_kernel=kernel-5.6' >>
> /home/user/qubes-builder/builder.conf
>
> 4.1) Get sources of it:
>
> make get-sources
It went quite well with 5.5.13, but not with 5.6. I get the error:
-> Updating sources for linux-kernel...
--> Fetching from https://github.com/QubesOS/qubes-linux-kernel.git
kernel-5.6...
fatal: Remote branch kernel-5.6 not found in upstream origin
The builder.conf contains:
vim: ft=make
VERBOSE ?= 2
BACKEND_VMM ?= xen
GIT_BASEURL ?= https://github.com
GIT_PREFIX ?= QubesOS/qubes-
RELEASE ?= 4.0
DIST_DOM0 ?= fc25
DISTS_VM ?=
COMPONENTS = \
installer-qubes-os \
linux-yum \
linux-kernel \
builder-rpm
BUILDER_PLUGINS ?= builder-rpm
USE_QUBES_REPO_VERSION = $(RELEASE)
INSTALLER_KICKSTART=/home/user/qubes-src/installer-qubes-os/conf/iso-full-online.ks
USE_QUBES_REPO_TESTING=1
BRANCH_installer_qubes_os=release4.0
URL_linux_kernel=https://github.com/fepitre/qubes-linux-kernel
BRANCH_linux_kernel=kernel-5.6
Thank you very much for your help. I really appreciate it.
Sincerely
Max
--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/8e51dca8-61e0-128b-ad12-427334b8363c%40militant.dk.
signature.asc
Description: OpenPGP digital signature
Re: [qubes-users] How to disable or set the qrexec timeout for more than 60 seconds? getting halted because "cannot connect to qrexec agent for 60 seconds"
Guerlan: > "Domain windows10 failed to start (after 60 seconds using it): cannot > connect to qrexec agent for 60 seconds" > > > After installing qubes-windows-tools, it failed on moving the users folder > to the D disk. I followed a guide: > https://www.tenforums.com/tutorials/1964-move-users-folder-location-windows-10-a.html > > but after doing it, it reboots. Upon startup, the windows keeps loding > (possibly moving the folder, I don't know). Then, since it wont start in > less than 60 seconds, Qubes closes it by saying 60 seconds has passed and > it couldn't communicate with qrexec. Sometimes it happens even if the > windows is up, I guess the windows qrexec fils to load sometimes. > > Anyways, setting it to 0 by doing > > > qvm-features windows10 qrexec 0 > > > has no effect > To give it more time to start up, you can do: qvm-prefs windows10 qrexec_timeout 300 where "300" is # of seconds allowed. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c367c417-41ec-a672-e382-5b6c5b5cf9f0%40danwin1210.me.
[qubes-users] How to disable or set the qrexec timeout for more than 60 seconds? getting halted because "cannot connect to qrexec agent for 60 seconds"
"Domain windows10 failed to start (after 60 seconds using it): cannot connect to qrexec agent for 60 seconds" After installing qubes-windows-tools, it failed on moving the users folder to the D disk. I followed a guide: https://www.tenforums.com/tutorials/1964-move-users-folder-location-windows-10-a.html but after doing it, it reboots. Upon startup, the windows keeps loding (possibly moving the folder, I don't know). Then, since it wont start in less than 60 seconds, Qubes closes it by saying 60 seconds has passed and it couldn't communicate with qrexec. Sometimes it happens even if the windows is up, I guess the windows qrexec fils to load sometimes. Anyways, setting it to 0 by doing qvm-features windows10 qrexec 0 has no effect -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8a66afb1-132f-415d-9642-e7114f8f397a%40googlegroups.com.
Re: [qubes-users] TALOSII for QubesOS
tukaisute: > I'm thinking of buying a Talos2 for QubesOS, which one do you recommend? > https://www.raptorcs.com/TALOSII/ > Is anyone using QubesOS with Talos2? > I looked for it, but it's not listed on HCL. > Unfortunately, Qubes can't currently run on that architecture. See https://github.com/QubesOS/qubes-issues/issues/4318. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/33c4afd6-f282-5cb4-2c2b-321b2a10a990%40danwin1210.me.
Re: [qubes-users] Creating ones own Insurgo
Sven Semmler: > On Thu, Apr 16, 2020 at 09:16:40AM -0700, Catacombs wrote: >> As I read on the git hub Skulls page. There is an individual who bricked >> his Lenovo X230 with trying to install CoreBoot. and can not reinstall his >> back up of his original BIOS/EFI. Not a lot of advice on that board. > > I share your reluctance, which is why my ME remains for now. > >> So my question is how do I disable the Intel WiFi driver. Might easier to >> just open back of computer and remove chip.Maybe the Intel Whitelist of >> WiFi is just a hoax. I should just try the Atheros chip. Probably lead to >> two hours of re installing QUBES. Any thoughts? > > The ME runs on a separate processor with it's own OS. Absolutely nothing > you do in your installed OS has any effect whatsoever on ME. True, but he should be able to use a non-Intel USB wifi adapter for networking and disable the on-board Intel wifi in BIOS config or remove the card entirely. It's unlikely (but not impossible) ME has drivers built in that support networking over a 3rd party USB adapter. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a1fc1915-d9ef-ff4a-273a-a0960f2cec31%40danwin1210.me.
Re: [qubes-users] Build USB install with kernel 5+
On 2020-04-16 20:55, 'Max Andersen' via qubes-users wrote: > New error emerges: > > [user@qubes-builder qubes-builder]$ make iso > -> Preparing for ISO build... > --> Removing old rpms from the installer repos... > ---> Cleaning up repo: dom0-updates... > ---> Cleaning up repo: installer... > ---> Cleaning up repo: qubes-dom0... > --> Copying installer-qubes-os RPMs... > ln: failed to access > 'pkgs/dom0-fc25/noarch/pykickstart-2.32-4.fc25.noarch.rpm': No such file or > directory > ln: failed to access > 'pkgs/dom0-fc25/noarch/python-kickstart-2.32-4.fc25.noarch.rpm': No such file > or directory > ln: failed to access > 'pkgs/dom0-fc25/noarch/python3-kickstart-2.32-4.fc25.noarch.rpm': No such > file or directory > ln: failed to access > 'pkgs/dom0-fc25/noarch/python-blivet-2.1.11-6.fc25.noarch.rpm': No such file > or directory > ln: failed to access > 'pkgs/dom0-fc25/noarch/python3-blivet-2.1.11-6.fc25.noarch.rpm': No such file > or directory > ln: failed to access 'pkgs/dom0-fc25/x86_64/lorax-25.19-1.fc25.x86_64.rpm': > No such file or directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/lorax-lmc-virt-25.19-1.fc25.x86_64.rpm': No such file > or directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/lorax-lmc-novirt-25.19-1.fc25.x86_64.rpm': No such > file or directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/lorax-templates-generic-25.19-1.fc25.x86_64.rpm': No > such file or directory > ln: failed to access > 'pkgs/dom0-fc25/noarch/lorax-templates-qubes-4.0.6-1.fc25.noarch.rpm': No > such file or directory > ln: failed to access 'pkgs/dom0-fc25/noarch/pungi-4.1.14-2.fc25.noarch.rpm': > No such file or directory > ln: failed to access > 'pkgs/dom0-fc25/noarch/pungi-utils-4.1.14-2.fc25.noarch.rpm': No such file or > directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/anaconda-25.20.9-17.fc25.x86_64.rpm': No such file or > directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/anaconda-core-25.20.9-17.fc25.x86_64.rpm': No such > file or directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/anaconda-gui-25.20.9-17.fc25.x86_64.rpm': No such file > or directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/anaconda-tui-25.20.9-17.fc25.x86_64.rpm': No such file > or directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/anaconda-widgets-25.20.9-17.fc25.x86_64.rpm': No such > file or directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/anaconda-widgets-devel-25.20.9-17.fc25.x86_64.rpm': No > such file or directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/anaconda-dracut-25.20.9-17.fc25.x86_64.rpm': No such > file or directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/anaconda-debuginfo-25.20.9-17.fc25.x86_64.rpm': No > such file or directory > ln: failed to access > 'pkgs/dom0-fc25/x86_64/anaconda-debugsource-25.20.9-17.fc25.x86_64.rpm': No > such file or directory > ln: failed to access > 'pkgs/dom0-fc25/noarch/qubes-anaconda-addon-4.0.11-1.fc25.noarch.rpm': No > such file or directory > ln: failed to access 'pkgs/dom0-fc25/noarch/qubes-release-4.0-8.noarch.rpm': > No such file or directory > ln: failed to access > 'pkgs/dom0-fc25/noarch/qubes-release-notes-4.0-8.noarch.rpm': No such file or > directory > ln: failed to access > 'pkgs/dom0-fc25/noarch/qubes-dom0-dist-upgrade-2.0-2.noarch.rpm': No such > file or directory > make[1]: *** > [/home/user/qubes-builder/qubes-src/builder-rpm/Makefile.rpmbuilder:158: > update-repo-do] Error 1 > make: *** [Makefile:493: iso.copy-rpms.installer-qubes-os] Error 2 > [user@qubes-builder qubes-builder]$ If you built kernel make iso COMPONENTS=linux-kernel else make iso COMPONENTS= As 'installer-qubes-os' is in COMPONENTS of builder.conf it thinks that the packages have been built where as it downloaded it. -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/308aa2d9-87d7-5bcb-bf0f-89a61f5419ce%40qubes-os.org. signature.asc Description: OpenPGP digital signature
[qubes-users] TALOSII for QubesOS
I'm thinking of buying a Talos2 for QubesOS, which one do you recommend? https://www.raptorcs.com/TALOSII/ Is anyone using QubesOS with Talos2? I looked for it, but it's not listed on HCL. -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f78785b5-6580-4272-cb8a-528f9c1e6bc7%40cock.li.
Re: [qubes-users] Build USB install with kernel 5+
On 4/16/20 8:44 PM, Frédéric Pierret wrote: >> When running make iso I get: >> >> [user@qubes-builder qubes-builder]$ make iso >> -> Preparing for ISO build... >> --> Removing old rpms from the installer repos... >> which: no createrepo_c in >> (/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools) >> which: no createrepo in >> (/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools) >> ---> Cleaning up repo: dom0-updates... >> ./clean_repos.sh: line 6: -q: command not found >> ---> Cleaning up repo: installer... >> ./clean_repos.sh: line 6: -q: command not found >> ---> Cleaning up repo: qubes-dom0... >> ./clean_repos.sh: line 6: -q: command not found >> make[1]: *** [Makefile:80: clean-repos] Error 127 >> make: *** [Makefile:485: iso.clean-repos] Error 2 >> [user@qubes-builder qubes-builder]$ >> >> Do I need some libraries or something? > Yes normally you ran: > > make install-deps > > Here it seems that 'createrepo' or 'createrepo_c' is not installed. > > Hum a little fix in the script 'clean_repos.sh' is needed for proper exit and > message. I'll fix that. I cloned a new machine from the newest fedora-template-31, so I know what is needed in the newest build. Running make install-deps. installing : Installed: annobin-8.78-3.fc31.x86_64 createrepo_c-0.15.5-1.fc31.x86_64 createrepo_c-libs-0.15.5-1.fc31.x86_64 drpm-0.4.1-1.fc31.x86_64 dwz-0.12-11.fc31.x86_64 efi-srpm-macros-4-3.fc31.noarch elfutils-0.179-1.fc31.x86_64 fonts-srpm-macros-2.0.3-1.fc31.noarch fpc-srpm-macros-1.2-2.fc31.noarch gdb-minimal-8.3.50.20190824-30.fc31.x86_64 ghc-srpm-macros-1.5.0-1.fc31.noarch gnat-srpm-macros-4-10.fc31.noarch go-srpm-macros-3.0.8-4.fc31.noarch libmodulemd-2.9.1-1.fc31.x86_64 nim-srpm-macros-3-1.fc31.noarch ocaml-srpm-macros-5-6.fc31.noarch openblas-srpm-macros-2-6.fc31.noarch patch-2.7.6-11.fc31.x86_64 perl-Digest-SHA-1:6.02-440.fc31.x86_64 perl-srpm-macros-1-33.fc31.noarch python-srpm-macros-3-54.fc31.noarch python3-sh-1.12.14-13.fc31.noarch qt5-srpm-macros-5.13.2-1.fc31.noarch redhat-rpm-config-143-1.fc31.noarch rpm-build-4.15.1-1.fc31.x86_64 rpm-sign-4.15.1-1.fc31.x86_64 rpmdevtools-8.10-9.fc31.noarch rust-srpm-macros-13-1.fc31.noarch xemacs-filesystem-21.5.34-34.20190323hgc0ed7ef9a5a1.fc31.noarch zstd-1.4.4-1.fc31.x86_64 New error emerges: [user@qubes-builder qubes-builder]$ make iso -> Preparing for ISO build... --> Removing old rpms from the installer repos... ---> Cleaning up repo: dom0-updates... ---> Cleaning up repo: installer... ---> Cleaning up repo: qubes-dom0... --> Copying installer-qubes-os RPMs... ln: failed to access 'pkgs/dom0-fc25/noarch/pykickstart-2.32-4.fc25.noarch.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/noarch/python-kickstart-2.32-4.fc25.noarch.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/noarch/python3-kickstart-2.32-4.fc25.noarch.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/noarch/python-blivet-2.1.11-6.fc25.noarch.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/noarch/python3-blivet-2.1.11-6.fc25.noarch.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/x86_64/lorax-25.19-1.fc25.x86_64.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/x86_64/lorax-lmc-virt-25.19-1.fc25.x86_64.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/x86_64/lorax-lmc-novirt-25.19-1.fc25.x86_64.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/x86_64/lorax-templates-generic-25.19-1.fc25.x86_64.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/noarch/lorax-templates-qubes-4.0.6-1.fc25.noarch.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/noarch/pungi-4.1.14-2.fc25.noarch.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/noarch/pungi-utils-4.1.14-2.fc25.noarch.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/x86_64/anaconda-25.20.9-17.fc25.x86_64.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/x86_64/anaconda-core-25.20.9-17.fc25.x86_64.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/x86_64/anaconda-gui-25.20.9-17.fc25.x86_64.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/x86_64/anaconda-tui-25.20.9-17.fc25.x86_64.rpm': No such file or directory ln: failed to access 'pkgs/dom0-fc25/x86_64/anaconda-widgets-25.20.9-17.fc25.x86_64.rpm': No such file or directory ln: failed to access 'pkgs/dom
Re: [qubes-users] Build USB install with kernel 5+
> When running make iso I get: > > [user@qubes-builder qubes-builder]$ make iso > -> Preparing for ISO build... > --> Removing old rpms from the installer repos... > which: no createrepo_c in > (/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools) > which: no createrepo in > (/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools) > ---> Cleaning up repo: dom0-updates... > ./clean_repos.sh: line 6: -q: command not found > ---> Cleaning up repo: installer... > ./clean_repos.sh: line 6: -q: command not found > ---> Cleaning up repo: qubes-dom0... > ./clean_repos.sh: line 6: -q: command not found > make[1]: *** [Makefile:80: clean-repos] Error 127 > make: *** [Makefile:485: iso.clean-repos] Error 2 > [user@qubes-builder qubes-builder]$ > > Do I need some libraries or something? Yes normally you ran: make install-deps Here it seems that 'createrepo' or 'createrepo_c' is not installed. Hum a little fix in the script 'clean_repos.sh' is needed for proper exit and message. I'll fix that. Best, Frédéric > Sincerely > > Max > -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5f66a10c-c3cd-6617-6e9b-b5f21ef0c648%40qubes-os.org. signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Build USB install with kernel 5+
On 4/15/20 10:05 AM, Frédéric Pierret wrote:
> On 2020-04-15 08:09, Max Andersen wrote:
>>
>>> Den 14. apr. 2020 kl. 08.02 skrev Frédéric Pierret
>>> :
>>>
>>> Hi,
>>> I used to build newer ISO in the past for such troubles with kernel-latest
>>> embedded. If you are interested, I can build you an 4.0.3 with
>>> kernel-latest-5.6 for try?
>> When I try, the builder script fails horribly. Can you write a stepguide?
>> Maybe just commands and selections on how you build it(if it is not too much
>> of a hassle)?
> Sure, here are the procedure for building latest Qubes 4.0.3 ISO with already
> built packages (templates included) using Qubes OS official repositories:
>
> 1) In a working directory, e.g. `/home/user/`, clone `qubes-builder`:
>
> git clone https://github.com/QubesOS/qubes-builder
>
> 2) Download specific builder conf file for such process:
>
> wget
> https://raw.githubusercontent.com/QubesOS/qubes-release-configs/master/R4.0/qubes-os-iso-full-online.conf
> -O /home/user/qubes-builder/builder.conf
>
> 3) Enable QubesOS testing packages for the build and specify release branch
> for the installer:
>
> echo 'USE_QUBES_REPO_TESTING=1' >> /home/user/qubes-builder/builder.conf
> echo 'BRANCH_installer_qubes_os=release4.0' >>
> /home/user/qubes-builder/builder.conf
>
> 4) Get sources:
>
> cd /home/user/qubes-builder/
> make get-sources
>
> 5) Enable `kernel-latest` in the ISO build process:
>
> sed -i 's#\( type="\)optional\(">kernel-latest.*$\)#\1mandatory\2#'
> qubes-src/installer-qubes-os/conf/comps-qubes.xml
>
> 6) Build ISO:
>
> make iso
When running make iso I get:
[user@qubes-builder qubes-builder]$ make iso
-> Preparing for ISO build...
--> Removing old rpms from the installer repos...
which: no createrepo_c in
(/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools)
which: no createrepo in
(/home/user/.local/bin:/home/user/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/home/user/qubes-builder/qubes-src/builder-rpm/tools)
---> Cleaning up repo: dom0-updates...
./clean_repos.sh: line 6: -q: command not found
---> Cleaning up repo: installer...
./clean_repos.sh: line 6: -q: command not found
---> Cleaning up repo: qubes-dom0...
./clean_repos.sh: line 6: -q: command not found
make[1]: *** [Makefile:80: clean-repos] Error 127
make: *** [Makefile:485: iso.clean-repos] Error 2
[user@qubes-builder qubes-builder]$
Do I need some libraries or something?
Sincerely
Max
--
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...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/d05519f3-5234-8eaf-ecdc-4b943060c1fd%40militant.dk.
signature.asc
Description: OpenPGP digital signature
Re: [qubes-users] Creating ones own Insurgo
On Thu, Apr 16, 2020 at 09:16:40AM -0700, Catacombs wrote: > As I read on the git hub Skulls page. There is an individual who bricked his > Lenovo X230 with trying to install CoreBoot. and can not reinstall his back > up of his original BIOS/EFI. Not a lot of advice on that board. I share your reluctance, which is why my ME remains for now. > So my question is how do I disable the Intel WiFi driver. Might easier to > just open back of computer and remove chip.Maybe the Intel Whitelist of > WiFi is just a hoax. I should just try the Atheros chip. Probably lead to > two hours of re installing QUBES. Any thoughts? The ME runs on a separate processor with it's own OS. Absolutely nothing you do in your installed OS has any effect whatsoever on ME. /Sven -- public key: https://www.svensemmler.org/0x8F541FB6.asc fingerprint: D7CA F2DB 658D 89BC 08D6 A7AA DA6E 167B 8F54 1FB6 -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200416165539.GB1354%40app-email-private. signature.asc Description: PGP signature
Re: [qubes-users] Creating ones own Insurgo
As I read on the git hub Skulls page. There is an individual who bricked his Lenovo X230 with trying to install CoreBoot. and can not reinstall his back up of his original BIOS/EFI. Not a lot of advice on that board. Day before yesterday I put a spinning hard drive into my X230 to experiment with. For any of you not familiar with the physical layout of an X230, replacing the drive is super easy. One screw removes the plate covering drive. Drive slides out, has soft rubber slides that pop off either side of drive. Put them on replacement drive. Slide it in. Put side plate on. Tighten down screw. I experimented by installing the Pure OS. I have an iPhone, on which I am typing this, which has unlimited data. And came with a gift of ten GBs HotSpot. I plugged the cable between the iPhone and X230 pure USB port to use data. Pure is like Debian in that it is FOSS and does not have driver for the already installed Intel Wireless. I spent several hours trying to get a Real Tek USB WiFi to install. Didn’t work for me. So I installed QUBES onto the spinning drive. Works. Point of all this being. If I could keep the Intel Management Engine from from phoning home. And use the Wireless of my choice. I might not itch so much to install Core Boot Skulls. I know that Qubes will let me see connections with a wireless dongle. Maybe I should just disable driver for Intel WiFi, and just toddle along. I am guessing that would be in the Xen Hypervisor. So my question is how do I disable the Intel WiFi driver. Might easier to just open back of computer and remove chip.Maybe the Intel Whitelist of WiFi is just a hoax. I should just try the Atheros chip. Probably lead to two hours of re installing QUBES. Any thoughts? -- 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...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7b877791-bacf-46b3-9222-3cc903926c33%40googlegroups.com.
