[qubes-users] Re: Qubes R3.2, cannot find redshift{-gtk} packages on dom0
El viernes, 21 de octubre de 2016, 10:52:48 (UTC+2), vincent.ma...@gmail.com
escribió:
> On Thursday, October 20, 2016 at 3:47:56 AM UTC+2, Pablo Di Noto wrote:
> > Hello all,
> >
> > I have reinstalled R3.2 and want to install Redshift (and its GUI) on dom0
> > again.
> > I do not recall how I did it on R3.1, and successive updates.
> >
> > I see on a Fedora 23 VM that redshift and redshift-gtk are available in the
> > `updates` repository.
> >
> > But cannot find how to access these (or equivalent) repositories on dom0.
> > Used `qubes-dom0-update --enablerepo=XXX` with many different repositories
> > mentioned in FAQs and other posts here with XXX={updates,
> > qubes-dom0-current-testing, qubes-dom0-security-testing,
> > qubes-dom0-unstable, ...} but all return "Unable to find a match".
> >
> > What am I missing?
> >
> > Thanks in advance,
> > ///Pablo
>
>
>
>
>
> I know how to install redshift but whats the dom0 command to install the
> redshift-gtk ?
>
>
> sudo yum install redshift-gtk ?
>
> tried it and can not find it...
I guess this [1] link can help you.
[1] https://www.qubes-os.org/doc/software-update-dom0/
--
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 post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/677da3b0-b434-4b53-b5b0-d87b4dc55acf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: keepassX under debian 8
El miércoles, 17 de agosto de 2016, 10:26:23 (UTC+2), Foppe de Haan escribió: > On Wednesday, August 17, 2016 at 10:08:24 AM UTC+2, Foppe de Haan wrote: > > After switching the template for my vault to debian-8 (mainly because of > > the lower memory footprint), I noticed that, for reasons that elude me, > > Jessie comes with an extremely outdated keepassx build (.4.3), which > > doesn't support keepass 2 databases. (-> > > https://packages.debian.org/search?suite=default=all=any=names=keepassx > > ) > > As I am a bit of a novice wrt linux, is there a way to tell debian to > > (apt-)get the backported build? (And should I report this in the issue > > tracker?) > > (Oh, I figured out how to get the backported build. So that just leaves the > question whether I should report this somewhere, as I doubt it is intended > that the deb8 template would include a version of keepassx that doesn't > support keepass 2 databases.) Not sure it is a Qubes issue, since .4.3 is the version [1] of keepassx shipped Debian-stable (Jessie). Looks to me like Debian's fault. That being said I prefer Keepass 2, which I use both on windows host (.net framework dependency) and with linux (mono dependency) because if has a cool google drive syncronization plugin. [1] https://packages.debian.org/stable/allpackages -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/59c3277d-bf99-4dcf-b63d-66608b272460%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Can't seem to get my wireless working. Any help would be appreciated!
El jueves, 28 de julio de 2016, 10:24:10 (UTC+2), randal...@gmail.com escribió: > I cant get my bcm4360 drivers to install properly and when I paste the code > into sys-net terminal I get this error. please help me out thanks! > > > [user@sys-net ~]$ wget http://git.io/vuLC7 -v -O > fedora23_broadcom_wl_install.sh && sh ./fedora23_broadcom_wl_install.sh; > URL transformed to HTTPS due to an HSTS policy > --2016-04-16 17:47:47-- https://git.io/vuLC7 > Resolving git.io (git.io)... 23.23.173.104, 23.23.111.66, 54.243.161.116 > Connecting to git.io (git.io)|23.23.173.104|:443... connected. > HTTP request sent, awaiting response... 302 Found > Location: > https://gist.githubusercontent.com/onpubcom/7f41dc9cbe90556b2113/raw/a69939c941319741744bea28dadf273f118d67a2/fedora23_broadcom_wl_install.sh > [following] > --2016-04-16 17:47:47-- > https://gist.githubusercontent.com/onpubcom/7f41dc9cbe90556b2113/raw/a69939c941319741744bea28dadf273f118d67a2/fedora23_broadcom_wl_install.sh > > Resolving gist.githubusercontent.com (gist.githubusercontent.com)... > 23.235.47.133 > Connecting to gist.githubusercontent.com > (gist.githubusercontent.com)|23.235.47.133|:443... connected. > HTTP request sent, awaiting response... 200 OK > Length: 1058 (1.0K) [text/plain] > Saving to: ‘fedora23_broadcom_wl_install.sh’ > > fedora23_broadcom_w 100%[===>] 1.03K --.-KB/sin 0s > > > 2016-04-16 17:47:48 (74.5 MB/s) - ‘fedora23_broadcom_wl_install.sh’ saved > [1058/1058] > > Last metadata expiration check: 0:59:15 ago on Sat Apr 16 16:48:35 2016. > Package gcc-5.3.1-6.fc23.x86_64 is already installed, skipping. > Package kernel-devel-1000:4.1.13-9.pvops.qubes.x86_64 is already installed, > skipping. > Dependencies resolved. > Nothing to do. > Sending application list and icons to dom0 > Complete! > mkdir: cannot create directory ‘hybrid_wl_f23’: File exists > --2016-04-16 17:47:53-- > http://www.broadcom.com/docs/linux_sta/hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz > > Resolving www.broadcom.com (www.broadcom.com)... 209.132.249.240 > Connecting to www.broadcom.com (www.broadcom.com)|209.132.249.240|:80... > connected. > HTTP request sent, awaiting response... 200 OK > Length: 2928541 (2.8M) [application/octet-stream] > Saving to: ‘hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz.4’ > > hybrid-v35_64-nodeb 100%[===>] 2.79M 666KB/sin 4.3s > > > 2016-04-16 17:47:57 (668 KB/s) - > ‘hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz.4’ saved [2928541/2928541] > > Makefile > lib/ > lib/wlc_hybrid.o_shipped > lib/LICENSE.txt > src/ > src/include/ > src/include/typedefs.h > src/include/linuxver.h > src/include/bcmutils.h > src/include/siutils.h > src/include/packed_section_start.h > src/include/epivers.h > src/include/linux_osl.h > src/include/bcmendian.h > src/include/packed_section_end.h > src/include/pcicfg.h > src/include/bcmdefs.h > src/include/bcmcrypto/ > src/include/bcmcrypto/tkhash.h > src/include/wlioctl.h > src/include/osl.h > src/shared/ > src/shared/bcmwifi/ > src/shared/bcmwifi/include/ > src/shared/bcmwifi/include/bcmwifi_channels.h > src/shared/bcmwifi/include/bcmwifi_rates.h > src/shared/linux_osl.c > src/wl/ > src/wl/sys/ > src/wl/sys/wl_dbg.h > src/wl/sys/wlc_key.h > src/wl/sys/wl_linux.h > src/wl/sys/wl_linux.c > src/wl/sys/wlc_wowl.h > src/wl/sys/wl_iw.c > src/wl/sys/wlc_pub.h > src/wl/sys/wl_iw.h > src/wl/sys/wl_export.h > src/wl/sys/wl_cfg80211_hybrid.h > src/wl/sys/wlc_ethereal.h > src/wl/sys/wl_cfg80211_hybrid.c > src/wl/sys/wlc_utils.h > src/wl/sys/wlc_types.h > src/common/ > src/common/include/ > src/common/include/proto/ > src/common/include/proto/bcmeth.h > src/common/include/proto/ieee80211_radiotap.h > src/common/include/proto/ethernet.h > src/common/include/proto/802.1d.h > src/common/include/proto/bcmip.h > src/common/include/proto/bcmevent.h > src/common/include/proto/802.11.h > src/common/include/proto/wpa.h > KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd` clean > make[1]: Entering directory '/usr/src/kernels/4.1.13-9.pvops.qubes.x86_64' > CFG80211 API is prefered for this kernel version > /home/user/hybrid_wl_f23/Makefile:85: Neither CFG80211 nor Wireless Extension > is enabled in kernel > make[1]: Leaving directory '/usr/src/kernels/4.1.13-9.pvops.qubes.x86_64' > KBUILD_NOPEDANTIC=1 make -C /lib/modules/`uname -r`/build M=`pwd` > make[1]: Entering directory '/usr/src/kernels/4.1.13-9.pvops.qubes.x86_64' > CFG80211 API is prefered for this kernel version > Using CFG80211 API > LD /home/user/hybrid_wl_f23/built-in.o > CC [M] /home/user/hybrid_wl_f23/src/shared/linux_osl.o > CC [M] /home/user/hybrid_wl_f23/src/wl/sys/wl_linux.o > CC [M] /home/user/hybrid_wl_f23/src/wl/sys/wl_iw.o > CC [M] /home/user/hybrid_wl_f23/src/wl/sys/wl_cfg80211_hybrid.o > LD [M] /home/user/hybrid_wl_f23/wl.o >
Re: [qubes-users] Multi-drive computers installation
El jueves, 14 de julio de 2016, 12:48:14 (UTC+2), Drew White escribió: > On Thursday, 14 July 2016 20:26:03 UTC+10, Gorka Alonso wrote: > > What do you call 'multi-drive PC'? A computer with 2 physical drives (for > > example a SDD and a HDD)? > > Yes, Multi-Drive. It doesn't mean anything else. To read it as anything other > than what it says just means that someone is trying to make it mean something > that it does not. I think you were missing the term 'volume' in contrast with drive. Thanks for the explanation, wanted to make sure I understood it right. > > > Have you tried the advanced partitioning option in qubes installer? I think > > that what you want to do is to install Qubes without LVM (which makes > > several physical devices look like a single logical volume). If I recall > > correctly, long time since I dont install Qubes, there is an option to > > enable/disable LVM. > > I ALWAYS do custom, NOT automatic. > Automatic doesn't do anything right for me. > > I always do standard partitioning. But unfortunately when you have 2 drives > selected for install, it always has the data and partitions crossing the > drives. > > i.e. 2 drives become 1. > > I have 1 drive that I want Qubes on. It is a 60 GB SSD. > Then I have my 256 GB Mirror Raid, on which I want to map to /var/lib/qubes. > I'm not asking much, but the installer doesn't do what it's meant to. > So I have to install, then reconfigure, then get external drive and run > partitioning software, and then do a resize and move and shift and just stuff > around with it all. > > IF it was to work correctly, then I could use encryption and LVM on the 60 GB > and then standard on the raided. > > In other words, I could configure it all correctly the way I want it, instead > of being forced to have it a way that is not the way I want it. > > Since we can't always upgrade by downloading, due to the data usage > limitations here, we need to install by the DVD. So 1 download and update > multiple machines. > > If it's configured on multiple drives, then it can set to install on just the > first drive. Then all the VMs will be stored on the secondary drives. > > At this time, I have had to make all the adjustments manually by the XML only > after installation and then I have to restore backups to the system, and > since there's not always the right Kernel installed because it's not included > in the new versions, it makes it difficult. > > But anyway... I'll leave it at that for now. Should check it to make sure, but Qubes uses Anaconda in the installer in a encrypted LVM group. Check this[1] link, I think they are answering the exact same question you are asking. Have not checked if the Qubes installer has exact same options (modify the volume group, create a new one), hope it helps. [1]: http://forums.fedoraforum.org/newreply.php?s=4fdd575cdd983bdfd45ee7a42e28f1a7=newreply=1726897 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/40b06146-e346-4432-a7d3-7f7c867637b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
