[gentoo-user] apache 2.4 - deny access to directory
I'm trying to deny access to all except specific IP address in a directory, just testing it. In modules.d/00_default_settings.conf Options MultiViews AllowOverride All Require all granted in admin/.htaccess Require all denied Require ip 10.0.0.100 My IP is 10.0.0.112 and I can still access the server /admin directory What am I missing? -- Thelma
[gentoo-user] Trouble on first install with LUKS & BtrFS
I've done a basically vanilla install (*) of gentoo hardened with disks prepared at luks/btrfs. I've used `genkernel --btrfs --luks all`. I am getting the following error when trying to boot the system and arrive at the point of unlocking a disk (note the spaces, "on ... failed"): device-mapper: reload ioctl on failed: No such file or directory Dropping into the initramfs and trying `cryptsetup open`, I get the same error, though `cryptsetup isLuks` is responding positively. Does anyone have any suggestions on how I might proceed? - (*) Almost. I'm actually using two LUKS disks continaing a BtrFS RAID-1. So I'm using a patch: https://bugs.gentoo.org/694778
Re: [gentoo-user] Re: nvidia x server settings doesn't open
Thelma On 11/28/2020 07:19 AM, Nikos Chantziaras wrote: > On 27/11/2020 02:56, the...@sys-concept.com wrote: >> I just installed nvidia-drivers-455.28-r1 and can not start "nvidia x >> server setting" it doesn't open. >> >> running: $ nvidia-smi >> NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA >> driver. Make sure that the latest NVIDIA driver is installed and running. > > What's the output of: > > lsmod > > and: > > emerge --info Here it is. lsmod Module Size Used by ipv6 581632 602 crc_ccitt 16384 1 ipv6 cfg80211 835584 0 8021q 36864 0 garp 16384 1 8021q mrp20480 1 8021q stp16384 1 garp llc16384 2 stp,garp dm_mod155648 0 hid_logitech_hidpp 49152 0 eeepc_wmi 16384 0 asus_wmi 36864 1 eeepc_wmi sparse_keymap 16384 1 asus_wmi rfkill 28672 2 asus_wmi,cfg80211 wmi_bmof 16384 0 joydev 28672 0 snd_hda_codec_hdmi 73728 1 edac_mce_amd 32768 0 nouveau 2273280 4 snd_hda_codec_realtek 139264 1 snd_hda_codec_generic94208 1 snd_hda_codec_realtek kvm_amd 110592 0 ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_realtek kvm 786432 1 kvm_amd mxm_wmi16384 1 nouveau snd_hda_intel 53248 3 video 53248 2 asus_wmi,nouveau snd_intel_nhlt 20480 1 snd_hda_intel ttm 122880 1 nouveau snd_hda_codec 155648 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek drm_kms_helper217088 1 nouveau snd_hda_core 102400 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hwdep 16384 1 snd_hda_codec irqbypass 16384 1 kvm efi_pstore 16384 0 crct10dif_pclmul 16384 1 snd_pcm 118784 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core ghash_clmulni_intel16384 0 drm 593920 7 drm_kms_helper,ttm,nouveau snd_timer 40960 1 snd_pcm efivars20480 1 efi_pstore snd98304 14 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm pcspkr 16384 0 hid_logitech_dj28672 0 sp5100_tco 20480 0 soundcore 16384 1 snd ccp 102400 1 kvm_amd backlight 20480 3 video,asus_wmi,nouveau i2c_piix4 28672 0 k10temp16384 0 pinctrl_amd32768 0 mac_hid16384 0 wmi36864 4 asus_wmi,wmi_bmof,mxm_wmi,nouveau acpi_cpufreq 28672 0 efivarfs 16384 1 ext4 774144 1 mbcache16384 1 ext4 jbd2 131072 1 ext4 crc32_pclmul 16384 0 crc32c_intel 24576 2 aesni_intel 372736 0 igb 249856 0 crypto_simd16384 1 aesni_intel nvme 53248 1 cryptd 24576 2 crypto_simd,ghash_clmulni_intel xhci_pci 20480 0 glue_helper16384 1 aesni_intel i2c_algo_bit 16384 2 igb,nouveau ahci 40960 0 xhci_hcd 299008 1 xhci_pci i2c_core 94208 6 drm_kms_helper,i2c_algo_bit,igb,i2c_piix4,nouveau,drm nvme_core 110592 3 nvme libahci40960 1 ahci dca16384 1 igb emerge --info Portage 3.0.9 (python 3.7.9-final-0, default/linux/amd64/17.1/desktop, gcc-9.3.0, glibc-2.32-r2, 5.4.72-gentoo-x86_64 x86_64) = System uname: Linux-5.4.72-gentoo-x86_64-x86_64-AMD_Ryzen_7_3800XT_8-Core_Processor-with-gentoo-2.7 KiB Mem:32848924 total, 8851448 free KiB Swap: 0 total, 0 free Timestamp of repository gentoo: Tue, 24 Nov 2020 20:30:01 + Head commit of repository gentoo: c1218edbc9b95afbbd0bb97f70e40473d64229c5 sh bash 5.0_p18 ld GNU ld (Gentoo 2.34 p6) 2.34.0 app-shells/bash: 5.0_p18::gentoo dev-java/java-config: 2.3.1::gentoo dev-lang/perl:5.30.3::gentoo dev-lang/python: 3.7.9::gentoo, 3.9.0::gentoo dev-util/cmake: 3.17.4-r1::gentoo sys-apps/baselayout: 2.7::gentoo sys-apps/openrc: 0.42.1::gentoo sys-apps/sandbox: 2.20::gentoo sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r5::gentoo sys-devel/automake: 1.16.2-r1::gentoo sys-devel/binutils: 2.34-r2::gentoo sys-devel/gcc:9.3.0-r1::gentoo sys-devel/gcc-config: 2.3.2-r1::gentoo sys-devel/libtool:2.4.6-r6::gentoo sys-devel/make: 4.2.1-r4::gentoo
Re: [gentoo-user] what's the difference between the emerge options -u and -n?
n952162 wrote: > Assuming no "emerge --sync" has been done, e.g. > > I've been using -u to mean, "don't update if there's nothing new" (which > I would actually think would be the default). Maybe that's wrong? -n > is better? > > > You may want to check the man page for emerge. I don't think -n is what you think it is. From the man page: --noreplace, -n Skips the packages specified on the command-line that have already been installed. Without this option, any package atoms or package sets you specify on the command-line will cause Portage to remerge the package, even if it is already installed. Note that Portage will not remerge dependencies by default. This option can be used to update the world file without rebuilding the packages. Here's another. --update, -u Updates packages to the best version available, which may not always be the highest version number due to masking for testing and development. Package atoms specified on the command line are greedy, meaning that unspecific atoms may match multiple versions of slotted packages. This option also implies the --selective option. I've been using Gentoo since about 2003. Over the years, I've learned some ways to keep as sane a install as possible even when running some keyworded packages. Between the command line options and default options set in make.conf, this is what it ends up looking like: emerge --newuse --oneshot --unordered-display --update --ask --backtrack=100 --deep --jobs=5 --keep-going --with-bdeps=y --reinstall=changed-use --quiet-build=n --regex-search-auto=y --usepkg As far as I know, all those options are still valid. I haven't checked into it in a while tho. When I finish a sync and issue the command, I do this: emerge -aUDN world Each person has their own needs but if you check into those options, you may find them working for you as well. From make.conf: EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going -v -j5 --quiet-build=n -1 --unordered-display" To me, the most important option is the -1, --oneshot, option. It helps keep the world file from getting cluttered. Hope that helps. If you need more info, just ask. I may have to make a change myself if something has changed how it is used. Dale :-) :-)
Re: [gentoo-user] what's the difference between the emerge options -u and -n?
On Sat, 28 Nov 2020 at 21:04, n952162 wrote: > > Assuming no "emerge --sync" has been done, e.g. > > I've been using -u to mean, "don't update if there's nothing new" (which > I would actually think would be the default). Maybe that's wrong? -n > is better? In my book, there's only one reason to ever use -n, and that's if you've installed a package with -1 (--oneshot), and want to add it to your world file, so that it doesn't get depcleaned. Use -u for your regular system updates. Regards, Arve
[gentoo-user] what's the difference between the emerge options -u and -n?
Assuming no "emerge --sync" has been done, e.g. I've been using -u to mean, "don't update if there's nothing new" (which I would actually think would be the default). Maybe that's wrong? -n is better?
[gentoo-user] Re: nvidia x server settings doesn't open
On 27/11/2020 02:56, the...@sys-concept.com wrote: I just installed nvidia-drivers-455.28-r1 and can not start "nvidia x server setting" it doesn't open. running: $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. What's the output of: lsmod and: emerge --info
