Creative Labs Sound Blaster Audigy 2 PCI does not work
I have the sound card Creative Labs Sound Blaster Audigy 2 PCI Sound
Card SB0240 on PCI port in my PC.
I am newbie in GuixSD and I have no idea how to get the Card to work.
I have also Debian installed on the current PC. On Debian the the card
works without configuration.
I do not now what to do. Any advice would be appreciated. My Desktop
Environment is Xfce. The Card is not present in Audio Mixer.
Perhaps anybody could show me the way to debug the card configuration?
I have been googling about Guix and sound cards for a month and found nothing.
Or at least tell me that GuixSD is not intended to support this kind
of cards and I should buy another one. Then what PCI sound card would
I buy? Here you are my config.scm:
(use-modules
(gnu)
(gnu system nss)
(gnu packages freedesktop)
(gnu packages admin)
(gnu services dbus)
(gnu services desktop)
(gnu services sound)
(gnu packages backup)
(gnu packages glib)
(gnu packages gnuzilla)
(gnu packages pulseaudio)
(gnu packages version-control)
(gnu packages haskell-apps)
(gnu packages emacs)
(gnu packages emacs-xyz)
(gnu packages cmake)
(gnu packages statistics)
(gnu packages finance)
(gnu packages protobuf)
(gnu packages guile)
(gnu packages gnupg)
(gnu packages graphviz)
(gnu packages wget)
(gnu packages curl)
(gnu packages image)
(gnu services networking))
(use-service-modules desktop xorg ssh)
(use-package-modules certs gnome ssh)
(operating-system
(host-name "s")
(timezone "Europe/Warsaw")
(locale "en_US.utf8")
(keyboard-layout (keyboard-layout "pl"))
(bootloader
(bootloader-configuration
(bootloader grub-bootloader)
(target "/dev/sda")
(menu-entries
(list
(menu-entry
(label "Debianek")
(linux "(hd0,6)/v")
(linux-arguments '("root=/dev/sda6 ro"))
(initrd "(hd0,6)/i"))
(file-systems (append
(list (file-system
(device (file-system-label "guixsd"))
(mount-point "/")
(type "ext4"))
(file-system
(device (file-system-label "debianek"))
(mount-point "/root/debianek")
(type "ext4")))
%base-file-systems))
(users (cons (user-account
(name "s")
(comment "s")
(group "users")
(supplementary-groups '("wheel" "netdev"
"audio" "video"))
(home-directory "/home/s"))
%base-user-accounts))
(packages
(append
(list
nss-certs
openssh
network-manager-openvpn
modem-manager
network-manager-applet
icecat
pavucontrol
file-roller
git
git-annex-remote-hubic
git-annex
emacs
emacs-ag
emacs-cmake-mode
emacs-ess
emacs-flycheck
emacs-guix
emacs-ledger-mode
emacs-linum-relative
emacs-magit
emacs-minimal
emacs-no-x
emacs-no-x-toolkit
emacs-powerline
emacs-protobuf-mode
emacs-rainbow-delimiters
emacs-rainbow-identifiers
emacs-smart-mode-line
emacs-undo-tree
emacs-xwidgets
m17n-db
m17n-lib
pinentry-emacs
graphviz
wget
curl
flameshot
gvfs)
%base-packages))
(services
(append
(list
(service gnome-desktop-service-type)
(service xfce-desktop-service-type)
(set-xorg-configuration
(xorg-configuration
(keyboard-layout keyboard-layout)))
)
%desktop-services))
(name-service-switch %mdns-host-lookup-nss))
Thanks
Re: How to configure Xorg to use [proprietary] Sis 771 driver on Guix?
Mark, Mark H Weaver wrote: Is this even the same driver? I don't understand the question. Same driver as what? Never mind, I guess we'll find out. Kind regards, T G-R signature.asc Description: PGP signature
Re: How to configure Xorg to use [proprietary] Sis 771 driver on Guix?
# cat /var/log/Xorg.0.log [10.574] X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 [10.583] Build Operating System: GNU GuixSD [10.586] Current Operating System: Linux antelope 5.0.14-gnu #1 SMP 1 x86_64 [10.586] Kernel command line: BOOT_IMAGE=/gnu/store/v0ziysnm86c9bi8wh8pf6cckkdzqsyjf-linux-libre-5.0.14/bzImage --root=/dev/sda1 --system=/var/guix/profiles/system-116-link --load=/var/guix/profiles/system-116-link/boot modprobe.blacklist=pcspkr,snd_pcsp,bluetooth,ideapad_laptop [10.596] Build Date: 01 January 1970 12:00:01AM [10.600] [10.603] Current version of pixman: 0.36.0 [10.610]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [10.610] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [10.625] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 18 06:41:36 2019 [10.675] (++) Using config file: "/gnu/store/m4w8mr4crlxwsh1acc3255rvkr5l3xgf-xserver.conf" [10.679] (++) Using config directory: "/gnu/store/2mi80p4sj8a0xxddfgyzqh647rifgiix-xorg.conf.d" [10.682] (==) Using system config directory "/gnu/store/6yar7xifqhywhwz72djqrz8v88y5i3vj-xorg-server-1.20.4/share/X11/xorg.conf.d" [10.692] (==) No Layout section. Using the first Screen section. [10.695] (==) No screen section available. Using defaults. [10.699] (**) |-->Screen "Default Screen Section" (0) [10.703] (**) | |-->Monitor "" [10.711] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [10.711] (**) Option "AllowMouseOpenFail" "on" [10.714] (==) Automatically adding devices [10.718] (==) Automatically enabling devices [10.721] (==) Automatically adding GPU devices [10.725] (==) Max clients allowed: 256, resource mask: 0x1f [10.771] (**) FontPath set to: /gnu/store/cn966w06mgzsbprs5cdzmv3ll8if3gr5-font-alias-1.0.3/share/fonts/X11/75dpi, /gnu/store/cn966w06mgzsbprs5cdzmv3ll8if3gr5-font-alias-1.0.3/share/fonts/X11/100dpi, /gnu/store/cn966w06mgzsbprs5cdzmv3ll8if3gr5-font-alias-1.0.3/share/fonts/X11/misc, /gnu/store/cn966w06mgzsbprs5cdzmv3ll8if3gr5-font-alias-1.0.3/share/fonts/X11/cyrillic, /gnu/store/sm8dqm4wgpac90zsv3y8li378qwc16pg-font-misc-misc-1.1.2/share/fonts/X11/misc, /gnu/store/2wa88yyr6vlmyhqzb0js9wfvfnfw7c3f-font-adobe75dpi-1.0.3/share/fonts/X11/75dpi [10.796] (**) ModulePath set to "/gnu/store/w2xryn7vr8vd6mddqln9jhmmdc5x6y0n-xf86-video-vesa-2.4.0/lib/xorg/modules/drivers,/gnu/store/6njzy2lv87fr9a9ay5cp205bqfssva74-xf86-video-fbdev-0.5.0/lib/xorg/modules/drivers,/gnu/store/d2wf4a3wby80053m7ijcly1ggbq4mcz5-xf86-video-amdgpu-19.0.1/lib/xorg/modules/drivers,/gnu/store/5prr3ix7i6lkjw36barc2hlh6ga1sx62-xf86-video-ati-19.0.1/lib/xorg/modules/drivers,/gnu/store/v454ijfrmyb0cd1a74mmz2yk03il8xsm-xf86-video-cirrus-1.5.3/lib/xorg/modules/drivers,/gnu/store/bw9l6744nmm3qa7i1smi91gql061dkj0-xf86-video-intel-2.99.917-13.6afed33/lib/xorg/modules/drivers,/gnu/store/yimnqfs9v6qf2k3i3psm1cv0dhm54qg3-xf86-video-mach64-6.9.6/lib/xorg/modules/drivers,/gnu/store/7rdfy1y6093cdqh3hk7scpx74fs2smpr-xf86-video-nouveau-1.0.16/lib/xorg/modules/drivers,/gnu/store/bgmya5sgd8q9vvj0wzrngmgx74ig5dkf-xf86-video-nv-2.1.21/lib/xorg/modules/drivers,/gnu/store/3h77x4bxb0lj876sy3i77l39ixc060yl-xf86-video-sis-0.10.9/lib/xorg/modules/drivers,/gnu/store/py75z016islwsdi116jca4mv07hzvrhb-xf86-input-libinpu [10.803] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [10.803] (II) Loader magic: 0x616d00 [10.803] (II) Module ABI versions: [10.803]X.Org ANSI C Emulation: 0.4 [10.803]X.Org Video Driver: 24.0 [10.803]X.Org XInput driver : 24.1 [10.803]X.Org Server Extension : 10.0 [10.812] (++) using VT number 7 [10.816] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [10.821] (II) xfree86: Adding drm device (/dev/dri/card0) [10.838] (--) PCI:*(0@0:2:0) 8086:0f31:17aa:3905 rev 14, Mem @ 0x9000/4194304, 0x8000/268435456, I/O @ 0x2050/8, BIOS @ 0x/131072 [10.843] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [10.843] (II) LoadModule: "glx" [10.907] (II) Loading /gnu/store/6yar7xifqhywhwz72djqrz8v88y5i3vj-xorg-server-1.20.4/lib/xorg/modules/extensions/libglx.so [10.947] (II) Module glx: vendor="X.Org Foundation" [10.947]compiled for 1.20.4, module version = 1.0.0 [10.951]ABI class: X.Org Server Extension, version 10.0 [10.954] (==) Matched modesetting as autoconfigured driver 0 [10.958] (==) Matched fbdev as autoconfigured
Re: How to configure Xorg to use [proprietary] Sis 771 driver on Guix?
zna...@disroot.org writes: > Mark, this is my lspci, lsmod, guix describe: Can you share the contents of your /var/log/Xorg.0.log ? That should show us which video driver(s) were loaded and any relevant error messages. Mark
Re: How to configure Xorg to use [proprietary] Sis 771 driver on Guix?
Tobias Geerinckx-Rice writes: > Mark H Weaver wrote: >> Guix already has 'xf86-video-sis', and it's already included in >> %default-xorg-modules in (gnu services xorg). So, now we just need >> to >> find out why it's not working. > > Is this even the same driver? I don't understand the question. Same driver as what? Mark
Re: editing /etc/sudoers
Thanks Jeff, Sounds good. Do you think this thread is effectively solved, then? You might consider opening a bug report for visudo. - John > On Jun 17, 2019, at 11:02 AM, Jeff Bauer wrote: > >> On Mon, Jun 17, 2019 at 10:03:20AM -0700, John Soo wrote: >> Sorry this is so confusing. Let me know if I’m missed something since >> I’ve been half-following this thread. I think what you may want to do >> is use the sudoers-file field when specifying your operating system >> rather than using visudo to edit the file. This way you will have >> persistent and declarative specification for the sudoers file. The >> sudoers-file field allows you to place an arbitrary file-like object in >> it, so you can put whatever you want to add using visudo there and it >> will work the same. Check the manual for >> reference: [1]https://www.gnu.org/software/guix/manual/en/html_node/ope >> rating_002dsystem-Reference.html#operating_002dsystem-Reference > > John, > > Correct, I got my local sudoers working a few > days ago, so there's no longer any confusion on > my end (but thanks for your reply). > > However, guix's visudo should probably be patched > to allow editing of a *local* ~/etc/sudoers file, > which currently won't work because /usr/bin/vi > appears to be hard-coded. > > -Jeff
Re: Servname not supported
Hello Dustin, Dustin Rayner writes: [...] > However, guix install hello and guix pull both fail. I've verified > network access, but the error I receive is: > > In procedure getaddrinfo: Servname not supported for ai_socktype What if you try `whois gnu.org` on that host? Do you get the same error? I can confirm that you were correct. This fixed my issue. I can also confirm that this is repeatable for a fresh install of Debian. I'm confirming here in case othrs encounter this problem. Thanks for your help! Dustin
Using Python and GExiv2
Hi,
I used to use a python script to clear image metadata in Debian:
import gi
gi.require_version("GExiv2", "0.10")
from gi.repository import GExiv2
metadata = GExiv2.Metadata("/tmp/something.png")
metadata.clear()
I'm trying to make this work in the GNU system I installed with Guix, but I
haven't been able to. So far, I have installed the following packages with guix:
gobject-introspection 1.56.1
python 3.70
python-pygobject 3.28.3
gexiv2 0.10.10
I've also added the output of "guix package --search-paths" to my
".bash_profile".
However, when I run the script above, I get the following error:
$ python3 img-clear-metadata.py
Traceback (most recent call last):
File "img-clear-metadata.py", line 2, in
gi.require_version("GExiv2", "0.10")
File
"/home/sirgazil/.guix-profile/lib/python3.7/site-packages/gi/__init__.py", line
130, in require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace GExiv2 not available
I don't know what I'm missing...
I'm using this guix:
$ LANG=C guix describe
Generation 3Jun 15 2019 09:49:31(current)
guix ddd401d
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: ddd401d28fb09f1f8ce96f2fc24226887a812412
---
https://sirgazil.bitbucket.io/
Re: How to configure Xorg to use [proprietary] Sis 771 driver on Guix?
Mark, this is my lspci, lsmod, guix describe: # lspci 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 671MX 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge) 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS968 [MuTIOL Media IO] (rev 01) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller (rev 01) 00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) 00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) 00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller 00:05.0 IDE interface: Silicon Integrated Systems [SiS] SATA Controller / IDE mode (rev 03) 00:06.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge 00:07.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge 00:0f.0 Audio device: Silicon Integrated Systems [SiS] Azalia Audio Controller 00:1f.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter (rev 10) 02:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) # lsmod Module Size Used by fuse 114688 2 ccm20480 9 uvcvideo 98304 0 videobuf2_vmalloc 20480 1 uvcvideo videobuf2_memops 20480 1 videobuf2_vmalloc videobuf2_v4l2 24576 1 uvcvideo videobuf2_common 45056 2 videobuf2_v4l2,uvcvideo videodev 204800 3 videobuf2_v4l2,uvcvideo,videobuf2_common media 53248 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common joydev 24576 0 usbmouse 16384 0 arc4 16384 2 ath9k 155648 0 ath9k_common 24576 1 ath9k ath9k_hw 479232 2 ath9k_common,ath9k coretemp 20480 0 ath32768 3 ath9k_common,ath9k,ath9k_hw mac80211 843776 1 ath9k snd_hda_codec_realtek 114688 1 snd_hda_codec_generic77824 1 snd_hda_codec_realtek ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_realtek cfg80211 704512 4 ath9k_common,ath9k,ath,mac80211 snd_hda_intel 45056 3 snd_hda_codec 135168 3 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec_realtek snd_hda_core 90112 4 snd_hda_codec_generic,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hwdep 20480 1 snd_hda_codec snd_pcm 110592 3 snd_hda_intel,snd_hda_codec,snd_hda_core input_leds 16384 0 psmouse 151552 0 r8169 81920 0 serio_raw 20480 0 realtek20480 1 snd_timer 40960 1 snd_pcm snd86016 13 snd_hda_codec_generic,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm soundcore 16384 1 snd asus_laptop32768 0 sparse_keymap 16384 1 asus_laptop input_polldev 20480 1 asus_laptop video 45056 1 asus_laptop mac_hid16384 0 sis_agp16384 1 virtio_rng 16384 0 virtio_console 32768 0 virtio_net 57344 0 virtio_blk 20480 0 virtio_balloon 24576 0 virtio_pci 24576 0 virtio 16384 6 virtio_rng,virtio_console,virtio_balloon,virtio_pci,virtio_blk,virtio_net virtio_ring32768 6 virtio_rng,virtio_console,virtio_balloon,virtio_pci,virtio_blk,virtio_net isci 143360 0 libsas 81920 1 isci scsi_transport_sas 40960 2 isci,libsas pata_atiixp16384 0 pata_acpi 16384 0 nls_iso8859_1 16384 0 wp512 36864 0 serpent_generic32768 0 xts16384 0 dm_crypt 40960 0 hid_apple 16384 0 hid_generic16384 0 usbhid 53248 0 hid 131072 4 usbhid,hid_apple,hid_generic uas24576 0 usb_storage69632 1 uas ahci 40960 0 libahci32768 1 ahci sata_sis 16384 2 # guix describe Generation 2Jun 17 2019 08:50:09(current) guix 0bc010d repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: 0bc010dacded4d89aa39f2d37fe75414b69b680e June 17, 2019 4:04 PM, "Mark H Weaver" wrote: > Hello, > > Tobias Geerinckx-Rice writes: > >> On a more positive note: have you looked at >> >> https://aur.archlinux.org/packages/xf86-video-sisimedia >> (or https://aur.archlinux.org/packages/xf86-video-sis)? > > Guix already has 'xf86-video-sis', and it's already included in >
Re: editing /etc/sudoers
On Mon, Jun 17, 2019 at 10:03:20AM -0700, John Soo wrote: >Sorry this is so confusing. Let me know if I’m missed something since >I’ve been half-following this thread. I think what you may want to do >is use the sudoers-file field when specifying your operating system >rather than using visudo to edit the file. This way you will have >persistent and declarative specification for the sudoers file. The >sudoers-file field allows you to place an arbitrary file-like object in >it, so you can put whatever you want to add using visudo there and it >will work the same. Check the manual for >reference: [1]https://www.gnu.org/software/guix/manual/en/html_node/ope >rating_002dsystem-Reference.html#operating_002dsystem-Reference John, Correct, I got my local sudoers working a few days ago, so there's no longer any confusion on my end (but thanks for your reply). However, guix's visudo should probably be patched to allow editing of a *local* ~/etc/sudoers file, which currently won't work because /usr/bin/vi appears to be hard-coded. -Jeff
Compiling Python 2.7.16
Hello again I'm trying to compile the version of python 2.7.16 but I get the following error WARNING: The Python readline extension was not compiled. Missing the GNU readline lib? ERROR: The Python zlib extension was not compiled. Missing the zlib? Please consult to the Wiki page to fix the problem. https://github.com/pyenv/pyenv/wiki/Common-build-problems BUILD FAILED (Linux 5.1.10 using python-build 1.2.12) I have installed those packages but when they die, they can not be located
Re: When is it appropriate to rename a file?
>Date: Sun, 16 Jun 2019 12:21:47 -0600 >From: ison >To: Jesse Gibbons >Cc: help-guix@gnu.org >Subject: Re: When is it appropriate to rename a file? >Message-ID: <20190616182146.asihmoclm4yghh6p@cf0> >Content-Type: text/plain; charset=us-ascii > >I'm not by any means the one who should be answering this question, but >just wanted to throw the idea out there that perhaps such things are >best saved for major version changes. >Because it would require every user to rethink the modules they're >using in their system config.scm Look at some of these examples: guile-wm jrnl musl sl wv How many users would put these in their config.scm? >(and possibly packages that aren't installed with "system" would have >to be re-installed manually). I have a package and moved it to a different module. I haven't needed to reinstall manually, and I upgraded it with a simple call to "guix upgrade". >So perhaps on Guix 2.0, 3.0, etc. is when it would be acceptable to do >house cleaning like renaming modules. Major changes that break over 1200 packages are pushed every 2.5 months or so according to the manual. Why should module refactoring be pushed more rarely? After much thought, I think I will make a new module for a new category of package when the need arises and leave module cleanup to the maintainers.
Re: How to configure Xorg to use [proprietary] Sis 771 driver on Guix?
Mark H Weaver wrote: Guix already has 'xf86-video-sis', and it's already included in %default-xorg-modules in (gnu services xorg). So, now we just need to find out why it's not working. Is this even the same driver? Kind regards, T G-R signature.asc Description: PGP signature
Re: How to configure Xorg to use [proprietary] Sis 771 driver on Guix?
Mark, let's start. As I've read in links Tobias offered Sis 771/671 is not mentioned there, but many other versions are presented. Is it reason? If you say what exactly to type in my config [1] I'll do it. [1] http://termbin.com/ni3a June 17, 2019 4:04 PM, "Mark H Weaver" wrote: > Hello, > > Tobias Geerinckx-Rice writes: > >> On a more positive note: have you looked at >> >> https://aur.archlinux.org/packages/xf86-video-sisimedia >> (or https://aur.archlinux.org/packages/xf86-video-sis)? > > Guix already has 'xf86-video-sis', and it's already included in > %default-xorg-modules in (gnu services xorg). So, now we just need to > find out why it's not working. Maybe one of the other video modules > guesses that it can support the hardware, but it actually fails? In > that case, it might help to move 'xf86-video-sis' higher up in the list > of modules to try. > > Regards, > Mark
Re: editing /etc/sudoers
Hi Jeff,
Sorry this is so confusing. Let me know if I’m missed something since I’ve been
half-following this thread. I think what you may want to do is use the
sudoers-file field when specifying your operating system rather than using
visudo to edit the file. This way you will have persistent and declarative
specification for the sudoers file. The sudoers-file field allows you to place
an arbitrary file-like object in it, so you can put whatever you want to add
using visudo there and it will work the same. Check the manual for reference:
https://www.gnu.org/software/guix/manual/en/html_node/operating_002dsystem-Reference.html#operating_002dsystem-Reference
Hope that helps,
John
> On Jun 17, 2019, at 8:44 AM, Jeff Bauer wrote:
>
>> On Mon, Jun 17, 2019 at 07:34:46AM -0700, Quiliro's lists wrote:
>> El 2019-06-17 02:17, Andreas Enge escribió:
>>> maybe my reply is off-topic and does not solve your problem, but to just
>>> give sudoer capabilities to a user, it is enough to add them to the "wheel"
>>> group in the system declaration, with something like:
>>>
>>> (operating-system
>>> (users (cons* (user-account
>>> (name "andreas")
>>> (comment "Andreas Enge")
>>> (group "users")
>>> (supplementary-groups '("wheel"))
>>> (home-directory "/home/andreas"))
>>>%base-user-accounts))
>>> ...
>>>
>>> This is in line with the principle that "global" files should not be edited,
>>> but instead be declared in some way in the operating system definition.
>>>
>>> For more sophisticated uses, the file could be declared in the operating
>>> system definition, I suppose, but I have no experience with this.
>>>
>>> Andreas
>>
>> Exactly: if you are using GuixSD, you do not use visudo; you use what
>> Andreas proposes. If you are using just Guix, then you use visudo from
>> the distro you are on.
>
> My needs go beyond adding a user to the wheel group. I want
> specific programs to run without a sudo password challenge,
> so editing my local copy of sudoers is necessary. I'm now
> using guix visudo as a command-line validation tool to
> ensure that sudoers isn't borked -- which is it's primary
> purpose.
>
> -Jeff
>
Re: editing /etc/sudoers
On Mon, Jun 17, 2019 at 07:34:46AM -0700, Quiliro's lists wrote:
> El 2019-06-17 02:17, Andreas Enge escribió:
> > maybe my reply is off-topic and does not solve your problem, but to just
> > give sudoer capabilities to a user, it is enough to add them to the "wheel"
> > group in the system declaration, with something like:
> >
> > (operating-system
> > (users (cons* (user-account
> > (name "andreas")
> > (comment "Andreas Enge")
> > (group "users")
> > (supplementary-groups '("wheel"))
> > (home-directory "/home/andreas"))
> > %base-user-accounts))
> > ...
> >
> > This is in line with the principle that "global" files should not be edited,
> > but instead be declared in some way in the operating system definition.
> >
> > For more sophisticated uses, the file could be declared in the operating
> > system definition, I suppose, but I have no experience with this.
> >
> > Andreas
>
> Exactly: if you are using GuixSD, you do not use visudo; you use what
> Andreas proposes. If you are using just Guix, then you use visudo from
> the distro you are on.
My needs go beyond adding a user to the wheel group. I want
specific programs to run without a sudo password challenge,
so editing my local copy of sudoers is necessary. I'm now
using guix visudo as a command-line validation tool to
ensure that sudoers isn't borked -- which is it's primary
purpose.
-Jeff
Re: editing /etc/sudoers
On Mon, Jun 17, 2019 at 09:53:46AM +0200, Hartmut Goebel wrote: > Try > > VISUAL=/path/tp/my/editor visudo > > See the man-page for details Nope, same error: $ VISUAL=~/.guix-profile/bin/vim visudo -f ~/etc/guix/config.scm visudo: no editor found (editor path = /usr/bin/vi) It appears /usr/bin/vi is hard-coded into the guix version of visudo. EDITOR or VISUAL works for me on non-guix systems. -Jeff
Re: How to configure Xorg to use [proprietary] Sis 771 driver on Guix?
Hello, Tobias Geerinckx-Rice writes: > On a more positive note: have you looked at > > https://aur.archlinux.org/packages/xf86-video-sisimedia/ > (or https://aur.archlinux.org/packages/xf86-video-sis/)? Guix already has 'xf86-video-sis', and it's already included in %default-xorg-modules in (gnu services xorg). So, now we just need to find out why it's not working. Maybe one of the other video modules guesses that it can support the hardware, but it actually fails? In that case, it might help to move 'xf86-video-sis' higher up in the list of modules to try. Regards, Mark
Re: editing /etc/sudoers
El 2019-06-17 02:17, Andreas Enge escribió:
> Hello,
>
> On Sun, Jun 16, 2019 at 06:20:54PM -0500, Jeff Bauer wrote:
>> Okay, to make it more clear: I was having a problem
>> trying to use visudo on a native Guix System. The
>> visudo packaged with the Guix System cannot actually
>> edit a sudoers file because it relies on /usr/bin/vi,
>> but it can be used as a command line validation checker.
>
> maybe my reply is off-topic and does not solve your problem, but to just
> give sudoer capabilities to a user, it is enough to add them to the "wheel"
> group in the system declaration, with something like:
>
> (operating-system
> (users (cons* (user-account
> (name "andreas")
> (comment "Andreas Enge")
> (group "users")
> (supplementary-groups '("wheel"))
> (home-directory "/home/andreas"))
> %base-user-accounts))
> ...
>
> This is in line with the principle that "global" files should not be edited,
> but instead be declared in some way in the operating system definition.
>
> For more sophisticated uses, the file could be declared in the operating
> system definition, I suppose, but I have no experience with this.
>
> Andreas
Exactly: if you are using GuixSD, you do not use visudo; you use what
Andreas proposes. If you are using just Guix, then you use visudo from
the distro you are on.
Re: On youtube-viewer first use (GTK)
On Sun, 16 Jun 2019 20:49:39 -0500 Tobias Geerinckx-Rice wrote > Sirgazil, > > Raghav Gururajan reported the same problem on IRC. > > While youtube-dl is technically an optional dependency (‘some’ > videos work without it, maybe even most), the failure mode is so > bad (complete silence, not even a ‘please install...’ hint) that > I've patched youtube-viewer to unconditionally refer to youtube-dl > on master. Thank you :)
Re: editing /etc/sudoers
Am 17.06.19 um 01:20 schrieb Jeff Bauer: > Okay, to make it more clear: I was having a problem > trying to use visudo on a native Guix System. The > visudo packaged with the Guix System cannot actually > edit a sudoers file because it relies on /usr/bin/vi, Try VISUAL=/path/tp/my/editor visudo See the man-page for details -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |
Re: editing /etc/sudoers
Hello,
On Sun, Jun 16, 2019 at 06:20:54PM -0500, Jeff Bauer wrote:
> Okay, to make it more clear: I was having a problem
> trying to use visudo on a native Guix System. The
> visudo packaged with the Guix System cannot actually
> edit a sudoers file because it relies on /usr/bin/vi,
> but it can be used as a command line validation checker.
maybe my reply is off-topic and does not solve your problem, but to just
give sudoer capabilities to a user, it is enough to add them to the "wheel"
group in the system declaration, with something like:
(operating-system
(users (cons* (user-account
(name "andreas")
(comment "Andreas Enge")
(group "users")
(supplementary-groups '("wheel"))
(home-directory "/home/andreas"))
%base-user-accounts))
...
This is in line with the principle that "global" files should not be edited,
but instead be declared in some way in the operating system definition.
For more sophisticated uses, the file could be declared in the operating
system definition, I suppose, but I have no experience with this.
Andreas
