Stephen Boston's questions

我不明白这里的问题。rtl8821cu 已安装，但我无法将modprobe其安装到位。安装过程是否有问题，还是我遗漏了某个步骤。

> pacman -Q | grep rtl
rtl8188gu-dkms-git r12.9dec829-1
rtl8812au-dkms-git 5.13.6.r189.gd4638de-1
rtl8821cu-dkms-git 5.12.0.1853eacc28-1
rtl8xxxu-dkms-git r54.fbb6d1a-1

[stephen@carb:~]
:> modprobe rtl8821cu
modprobe: FATAL: Module rtl8821cu not found in directory /lib/modules/6.9.7-arch1-1

在eyoan100评论之后

`Packages (1) rtl8821cu-dkms-git-5.12.0.1853eacc28-1
`
`Total Installed Size:  36.99 MiB
`Net Upgrade Size:       0.00 MiB
`

...

==> Leaving fakeroot environment.
==> Finished making: rtl8821cu-dkms-git 5.12.0.1853eacc28-1 (Mon Jul  8 12:33:34 2024)
==> Installing package rtl8821cu-dkms-git with pacman -U...

...

-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> WARNING: Possibly missing firmware for module: 'cfg80211'
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful


[stephen@carb:~/external/rtl8821cu-dkms-git]
:> uname -r
6.9.7-arch1-1

[stephen@carb:~/external/rtl8821cu-dkms-git]
:> dkms status
rtl8188gu/r12.9dec829, 6.6.36-1-lts, x86_64: installed
rtl8812au/5.13.6.r189.gd4638de, 6.6.36-1-lts, x86_64: installed
rtl8821cu/5.12.0.1853eacc28, 6.6.36-1-lts, x86_64: installed
rtl8821cu/5.12.0.1853eacc28, 6.9.7-arch1-1, x86_64: installed
rtl8xxxu/r54.fbb6d1a, 6.6.36-1-lts, x86_64: installed
rtl8xxxu/r54.fbb6d1a, 6.9.7-arch1-1, x86_64: installed

我之前没有在我的df输出中看到过这些 tmpfs /run/credentials ... 列出的挂载。

那是关于什么的

:> df -h
Filesystem                     Size  Used Avail Use% Mounted on
tmpfs  1.0M     0  1.0M   0% /run/credentials/systemd-udev-load-credentials.service
tmpfs  1.0M     0  1.0M   0% /run/credentials/systemd-network-generator.service
tmpfs  1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs  1.0M     0  1.0M   0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs  1.0M     0  1.0M   0% /run/credentials/systemd-tmpfiles-setup-dev.service
tmpfs  1.0M     0  1.0M   0% /run/credentials/systemd-sysctl.service
tmpfs  1.0M     0  1.0M   0% /run/credentials/systemd-networkd.service
tmpfs  1.0M     0  1.0M   0% /run/credentials/systemd-vconsole-setup.service
tmpfs  1.0M     0  1.0M   0% /run/credentials/systemd-tmpfiles-

我正在尝试使用wmctrl将窗口移动到工作区。

通过wmctrl -l窗口是

 0x03e00057  9 meer montazo - Google Search — Mozilla Firefox

命令和输出是

 /usr/local/bin/wmctrl -v -i 0x03e00057 -t 3
 envir_utf8: 0
 No window was specified.

我的理解是它-i指向窗口的十六进制ID（输出列表中的第一个字段？），在我简单的头脑中我在这里做的。我哪里迷路了？

我一直假设这journalctl是系统日志的综合聚合器，但我发现这是不正确的。

例如，dmesg在 systemd 完全激活之前提供系统日志记录，并提供更精确的硬件状态和进程视图。

知识渊博的系统管理员在 Linux 中是否使用其他标准或有用的系统日志记录工具？

运行全局更新

:: Synchronizing package databases...
core is up to date
extra is up to date
:: Starting full system upgrade...
:: Replace libblockdev-utils with extra/libblockdev? [Y/n] Y
resolving dependencies...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: libblockdev and libblockdev-utils are in conflict

所以我尝试手动删除 libblockdev-utils

sudo pacman -R libblockdev-utils
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing libblockdev-utils breaks dependency 'libblockdev-utils' required by libblockdev
:: removing libblockdev-utils breaks dependency 'libbd_utils.so=3-64' required by libblockdev
:: removing libblockdev-utils breaks dependency 'libblockdev-utils' required by libblockdev-crypto
:: removing libblockdev-utils breaks dependency 'libbd_utils.so=3-64' required by libblockdev-crypto
:: removing libblockdev-utils breaks dependency 'libblockdev-utils' required by libblockdev-fs
:: removing libblockdev-utils breaks dependency 'libbd_utils.so=3-64' required by libblockdev-fs
:: removing libblockdev-utils breaks dependency 'libblockdev-utils' required by libblockdev-loop
:: removing libblockdev-utils breaks dependency 'libbd_utils.so=3-64' required by libblockdev-loop
:: removing libblockdev-utils breaks dependency 'libblockdev-utils' required by libblockdev-mdraid
:: removing libblockdev-utils breaks dependency 'libbd_utils.so=3-64' required by libblockdev-mdraid
:: removing libblockdev-utils breaks dependency 'libblockdev-utils' required by libblockdev-nvme
:: removing libblockdev-utils breaks dependency 'libbd_utils.so=3-64' required by libblockdev-nvme
:: removing libblockdev-utils breaks dependency 'libblockdev-utils' required by libblockdev-part
:: removing libblockdev-utils breaks dependency 'libbd_utils.so=3-64' required by libblockdev-part
:: removing libblockdev-utils breaks dependency 'libblockdev-utils' required by libblockdev-swap
:: removing libblockdev-utils breaks dependency 'libbd_utils.so=3-64' required by libblockdev-swap
:: removing libblockdev-utils breaks dependency 'libblockdev-utils' required by udisks2
:: removing libblockdev-utils breaks dependency 'libbd_utils.so=3-64' required by udisks2

现在做什么？

我的日记里充斥着这样的内容：

    journalctl -r
    2024-01-10T20:07:01.947911-08:00 dell kernel: pci 0000:01:00.0:    [ 0] RxErr                  (First)
    2024-01-10T20:07:01.947686-08:00 dell kernel: pci 0000:01:00.0:   device [10ec:8136] error status/mask=00000001/00006000
    2024-01-10T20:07:01.947423-08:00 dell kernel: pci 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    2024-01-10T20:07:01.946988-08:00 dell kernel: pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:01:00.0
    2024-01-10T20:07:01.694824-08:00 dell kernel: pci 0000:01:00.0:    [ 0] RxErr                  (First)
    2024-01-10T20:07:01.694573-08:00 dell kernel: pci 0000:01:00.0:   device [10ec:8136] error status/mask=00000001/00006000
    2024-01-10T20:07:01.694279-08:00 dell kernel: pci 0000:01:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
    2024-01-10T20:07:01.693781-08:00 dell kernel: pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:01:00.0
    2024-01-10T20:07:01.601284-08:00 dell kernel: pci 0000:01:00.0:    [ 0] RxErr                  (First)
    
    

RTL810xE PCI Express Fast Ethernet controller根据https://linux-hardware.org/index.php?id=pci:10ec-8136-1028-056a，该卡需要Realtek r8169驱动程序。

https://wiki.archlinux.org/title/Network_configuration/Ethernet页面有一个部分表明此驱动程序在 Windows 双启动中存在问题。Realtek no link / WOL problem这不是双启动机器。这是arch linux 6.6.10-arch1-1

我可以使卡片栩栩如生，modprobe r8169但这不会影响该设备的日志错误消息。

使用 feh 图像查看器，我可以在图像上打开一个无框窗口。这很好。

但是现在我想在屏幕上移动窗口，为此我想我需要一个框架。

那么有没有一种方法可以移动窗口或切换frameless功能。

~/.config/feh/keys我没有在或 中看到选项man feh。

geeqie 2.0.1-4
mate-desktop 1.26.0-1
Linux 6.1.5-arch2-1

geeqie 图像查看器有一个菜单项“复制路径到剪贴板”。

这个“剪贴板”是全局剪贴板吗，这样我就可以将路径粘贴到电子邮件中。

如果是这样，那么这是行不通的。我的粘贴缓冲区不受此功能的影响。

Arch 5.18/ MATE 桌面版

我有一个为我的面板设置值的用户服务

[Unit]
Description=Set values for panel widgets
After=mnt-ram
After=sys-subsystem-net-devices-eno1.device

[Service]
ExecStart=/home/stephen/bin/panel-setup.sh 
Type=oneshot
RemainAfterExit=True

[Install]
WantedBy=default.target

两者mnt-ram和都sys-subsystem-net-devices-enp0s8.device显示为活跃于systemctl --user list-units。

启动时日志报告

 systemd[669]: /home/stephen/.config/systemd/user/panel-setup.service:3: Failed to add dependency on mnt-ram, ignoring: Invalid argument
 

但是，在桌面加载后，我可以毫无错误地发出预期效果：systemctl user restart panel-setup

有了这个.gitignore，我希望目录下的 *.log 文件test不会包含在任何 git 事务中

:> cat ~/test/.gitignore
*/*/*.log
*/*/*__pycache__*
*/*/*out

然而，我有这样的对话，这表明我的 gitignore 没有被定义为我所期望的。

我的错误在哪里？我是误解了对话还是我的 .gitignore 不符合我的预期。

:> git add .
===
:> git status
On branch master
Your branch is up to date with 'origin/master'.
===
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
    new file:   ftp.log
===
:> git restore --staged ftp.log 
===
:> git status
Untracked files:
(use "git add <file>..." to include in what will be committed)
    ftp.log
nothing added to commit but untracked files present (use "git add" to track)

我有一个基于 inotify 的服务，可以将 LAN 的 git 目录备份到 Dropbox。我尝试将 git 目录保留在 Dropbox 中，但我有多个 git 客户端，因此经常在那里收到错误文件。

在这个开发的早期阶段，这是一个相当繁忙和健谈的系统服务，它想要登录到 ram 驱动器。我不想使用/tmp，因为其他应用程序依赖于那里的空间。

要在我的 fstab 中创建 ram 驱动器，我有这个：

 tmpfs       /mnt/ram tmpfs   nodev,nosuid,noexec,nodiratime,size=1024M   0 0

我需要确保在备份服务启动之前安装了 ram 驱动器。我想为延迟启动的服务设置一个条件。

我看到人们将*.mnt服务作为先决条件的建议，但我没有看到任何文件/lib/systemd/system可以提供我需要的服务的名称。

我如何识别这个坐骑？还有另一种方法吗？

环顾四周，我发现标准修复是将其添加到内核启动参数中。

使用 systemd-boot，我的 arch.conf 看起来像这样：

 title   Arch Linux
 linux   /vmlinuz-linux
 initrd  /intel-ucode.img
 initrd  /initramfs-linux.img
 options root=PARTUUID="98b3b4f7-e7f9-6f49-be81-a2ee709c7a3e" rw

如何将 CONFIG_TASK_DELAY_ACCT 添加到options条目中？

另一条线？

或者通过使用一些分隔符，将其添加到现有行？

我应该将其设置为什么值？

在我的系统上进行一次电源循环和一次 smartctl 长时间测试后，我的三星 EVO 1T SSD ：

 ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

...

 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       6

...
 

那是VALUE:099关于什么的？考虑到自动化的 QA 周期，我希望肯定会少于 10 个。这是二手盘吗？或者 ...

我使用 Brave 浏览器（Chromium 的一个分支）每秒将会话状态写入磁盘，这种活动会不必要地消耗我的 SSD。

我从来没有兴趣恢复我的浏览器会话。从不。所以我尝试了所有可能适用的设置，但 Brave 坚持。我怀疑有关使用统计信息的一些事情。

我想知道我是否可以创建一个内存文件。我尝试了一个先进先出但锁定了浏览器。

是否有其他一些基于内存的设备。我看到有一个 RAM 驱动器，但我不想阻止浏览器的所有写入。

我怎样才能做到这一点？

刚刚注意到我正在使用 SDD 作为 SSD。已更正

我需要帮助解释这种情况。/dev/sda是备份的数据磁盘并具有可重现的数据，因此这不是系统关键，但我想避免恢复/重建数据的工作，其中一些将非常耗时

是否可以恢复/修复？

如果有怎么办？如果我擦除磁盘以重新使用它的可靠性是什么？

摘要（详细报告如下）：

• 不会安装：坏超级块
• badblocks 没有发现坏块
• smartctl 没有报错
• fsck 无法设置超级块标志
• fdisk 显示干净的分区
• dmesg 显示写入错误
• parted 显示 792 GB 可用 1 TB 驱动器

挂载 ssd 失败，如下所示：

 [stephen@meer ~]$ sudo mount /dev/sda1 /mnt/sda
 mount: /mnt/sda: can't read superblock on /dev/sda1.
        dmesg(1) may have more information after failed mount system call.
 [stephen@meer ~]$ 
 

但 badblocks 没有发现坏块

 [root@meer stephen]# badblocks -v /dev/sda1              
 Checking blocks 0 to 976760831
 Checking for bad blocks (read-only test): done                                                 
 Pass completed, 0 bad blocks found. (0/0/0 errors)

但是 smartctl 没有发现错误

 [root@meer stephen]# smartctl -a /dev/sda 
 smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.17.9-arch1-1] (local build)
 Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
 
 === START OF INFORMATION SECTION ===
 Model Family:     WD Blue / Red / Green SSDs
 Device Model:     WDC  WDS100T2B0A-00SM50
 Serial Number:    213159800516
 LU WWN Device Id: 5 001b44 8bc4fdc6e
 Firmware Version: 415020WD
 User Capacity:    1,000,204,886,016 bytes [1.00 TB]
 Sector Size:      512 bytes logical/physical
 Rotation Rate:    Solid State Device
 Form Factor:      2.5 inches
 TRIM Command:     Available, deterministic, zeroed
 Device is:        In smartctl database 7.3/5319
 ATA Version is:   ACS-4 T13/BSR INCITS 529 revision 5
 SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 1.5 Gb/s)
 Local Time is:    Tue May 24 16:06:23 2022 PDT
 SMART support is: Available - device has SMART capability.
 SMART support is: Enabled
 
 === START OF READ SMART DATA SECTION ===
 SMART overall-health self-assessment test result: PASSED
 
 General SMART Values:
 Offline data collection status:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
 Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever 
                    been run.
 Total time to complete Offline 
 data collection:       (    0) seconds.
 Offline data collection
 capabilities:           (0x11) SMART execute Offline immediate.
                    No Auto Offline data collection support.
                    Suspend Offline collection upon new
                    command.
                    No Offline surface scan supported.
                    Self-test supported.
                    No Conveyance Self-test supported.
                    No Selective Self-test supported.
 SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
 Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
 Short self-test routine 
 recommended polling time:   (   2) minutes.
 Extended self-test routine
 recommended polling time:   (  10) minutes.
 
 SMART Attributes Data Structure revision number: 4
 Vendor Specific SMART Attributes with Thresholds:
 ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
   5 Reallocated_Sector_Ct   0x0032   100   100   ---    Old_age   Always       -       124
   9 Power_On_Hours          0x0032   100   100   ---    Old_age   Always       -       1470
  12 Power_Cycle_Count       0x0032   100   100   ---    Old_age   Always       -       134
 165 Block_Erase_Count       0x0032   100   100   ---    Old_age   Always       -       4312400063
 166 Minimum_PE_Cycles_TLC   0x0032   100   100   ---    Old_age   Always       -       1
 167 Max_Bad_Blocks_per_Die  0x0032   100   100   ---    Old_age   Always       -       65
 168 Maximum_PE_Cycles_TLC   0x0032   100   100   ---    Old_age   Always       -       14
 169 Total_Bad_Blocks        0x0032   100   100   ---    Old_age   Always       -       630
 170 Grown_Bad_Blocks        0x0032   100   100   ---    Old_age   Always       -       124
 171 Program_Fail_Count      0x0032   100   100   ---    Old_age   Always       -       128
 172 Erase_Fail_Count        0x0032   100   100   ---    Old_age   Always       -       0
 173 Average_PE_Cycles_TLC   0x0032   100   100   ---    Old_age   Always       -       2
 174 Unexpected_Power_Loss   0x0032   100   100   ---    Old_age   Always       -       90
 184 End-to-End_Error        0x0032   100   100   ---    Old_age   Always       -       0
 187 Reported_Uncorrect      0x0032   100   100   ---    Old_age   Always       -       0
 188 Command_Timeout         0x0032   100   100   ---    Old_age   Always       -       64
 194 Temperature_Celsius     0x0022   070   053   ---    Old_age   Always       -       30 (Min/Max 18/53)
 199 UDMA_CRC_Error_Count    0x0032   100   100   ---    Old_age   Always       -       0
 230 Media_Wearout_Indicator 0x0032   001   001   ---    Old_age   Always       -       0x002600140026
 232 Available_Reservd_Space 0x0033   097   097   004    Pre-fail  Always       -       97
 233 NAND_GB_Written_TLC     0x0032   100   100   ---    Old_age   Always       -       2703
 234 NAND_GB_Written_SLC     0x0032   100   100   ---    Old_age   Always       -       2842
 241 Host_Writes_GiB         0x0030   253   253   ---    Old_age   Offline      -       466
 242 Host_Reads_GiB          0x0030   253   253   ---    Old_age   Offline      -       622
 244 Temp_Throttle_Status    0x0032   000   100   ---    Old_age   Always       -       0
 
 SMART Error Log Version: 1
 No Errors Logged
 
 SMART Self-test log structure revision number 1
 Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
 # 1  Extended offline    Completed without error       00%      1470         -
 
 Selective Self-tests/Logging not supported
 
 

并且 fsck 失败了：

 [root@meer ~]# e2fsck -cfpv /dev/sda1
 /dev/sda1: recovering journal
 e2fsck: Input/output error while recovering journal of /dev/sda1
 e2fsck: unable to set superblock flags on /dev/sda1
 
 
 /dev/sda1: ********** WARNING: Filesystem still has errors **********
 
 
 
 
 
 May 24 15:38:29 meer kernel: I/O error, dev sda, sector 121899008 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
 May 24 15:38:29 meer kernel: sd 2:0:0:0: [sda] tag#31 CDB: Write(10) 2a 00 07 44 08 00 00 00 08 00
 May 24 15:38:29 meer kernel: sd 2:0:0:0: [sda] tag#31 Add. Sense: Unaligned write command
 May 24 15:38:29 meer kernel: sd 2:0:0:0: [sda] tag#31 Sense Key : Illegal Request [current] 
 May 24 15:38:29 meer kernel: sd 2:0:0:0: [sda] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
 May 24 15:38:29 meer kernel: ata3.00: configured for UDMA/33
 May 24 15:38:29 meer kernel: ata3.00: error: { ABRT }
 May 24 15:38:29 meer kernel: ata3.00: status: { DRDY ERR }
 May 24 15:38:29 meer kernel: ata3.00: cmd ca/00:08:00:08:44/00:00:00:00:00/e7 tag 31 dma 4096 out
                                       res 51/04:08:00:08:44/00:00:07:00:00/e7 Emask 0x1 (device error)
 May 24 15:38:29 meer kernel: ata3.00: failed command: WRITE DMA
 May 24 15:38:29 meer kernel: ata3.00: irq_stat 0x40000001
 May 24 15:38:29 meer kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
 May 24 15:38:29 meer kernel: ata3: EH complete
 May 24 15:38:29 meer kernel: ata3.00: configured for UDMA/33
 May 24 15:38:29 meer kernel: ata3.00: error: { ABRT }
 May 24 15:38:29 meer kernel: ata3.00: status: { DRDY ERR }
 May 24 15:38:29 meer kernel: ata3.00: cmd ca/00:08:00:08:44/00:00:00:00:00/e7 tag 6 dma 4096 out
                                       res 51/04:08:00:08:44/00:00:07:00:00/e7 Emask 0x1 (device error)
 May 24 15:38:29 meer kernel: ata3.00: failed command: WRITE DMA
 May 24 15:38:29 meer kernel: ata3.00: irq_stat 0x40000001
 May 24 15:38:29 meer kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
 

fdisk 看到的分区。

 Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
 Disk model: WDC  WDS100T2B0A
 Units: sectors of 1 * 512 = 512 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disklabel type: gpt
 Disk identifier: 3F701164-2CF8-6D48-A94E-478634C140BE
 
 Device     Start        End    Sectors   Size Type
 /dev/sda1   2048 1953523711 1953521664 931.5G Linux filesystem

来自 dmesg

 [ 5292.895300] ata3.00: configured for UDMA/33
 [ 5292.895315] ata3: EH complete
 [ 5293.021851] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
 [ 5293.021859] ata3.00: irq_stat 0x40000001
 [ 5293.021864] ata3.00: failed command: WRITE DMA
 [ 5293.021866] ata3.00: cmd ca/00:08:00:08:44/00:00:00:00:00/e7 tag 18 dma 4096 out
                         res 51/04:08:00:08:44/00:00:07:00:00/e7 Emask 0x1 (device error)
 [ 5293.021874] ata3.00: status: { DRDY ERR }
 [ 5293.021877] ata3.00: error: { ABRT }

分开：

 root@meer stephen]# parted /dev/sda
 GNU Parted 3.5
 Using /dev/sda
 Welcome to GNU Parted! Type 'help' to view a list of commands.
 (parted) print free                                                       
 Model: ATA WDC WDS100T2B0A (scsi)
 Disk /dev/sda: 1000GB
 Sector size (logical/physical): 512B/512B
 Partition Table: gpt
 Disk Flags: 
 
 Number  Start   End     Size    File system  Name  Flags
         17.4kB  1049kB  1031kB  Free Space
  1      1049kB  1000GB  1000GB  ext4
         1000GB  1000GB  729kB   Free Space
 

我想要我的设备（以太网和 wifi）的静态 LAN IP地址，但在我平常的一周中，我连接到两个 LAN：两个网关，两个 IP 范围：一个10.0...网络和一个192.168..网络。

我一直保留两组 *.network 文件，我使用脚本切换它们，但我想知道是否有我可以使用的配置设置。

我查看了文档，特别是在该[Match]部分，但这似乎完全是关于设备的。

是否有可用于这种情况的 *.network 文件配置，或者我必须继续我当前的策略？

注意：我不想使用 NetworkManager

我的控制台背景很暗，所以有相当多的 journalctl 输出不可读。

我看到很多关于如何添加颜色的信息！但是我如何完全禁用它呢？

我正在运行传输远程并希望使用 g+w 权限创建所有新的 torrent 下载。

传输下载目录符号链接到Downloads第二个驱动器上的目录

作为用户斯蒂芬（传输组的成员）我可以运行

 [stephen@flip:/mnt/sdb/Downloads]
 :> umask g+w .

 [stephen@flip:/mnt/sdb/Downloads]
 :> umask -S
 u=rwx,g=rwx,o=rx

这似乎是成功的，但是传输正在创建新目录drwxr-xr-x

我想我应该运行 umask 命令作为传输，但这可能是一个nologin用户有充分的理由，所以我会尝试 sudo ...

:> sudo -u transmission umask g+w .
sudo: umask: command not found

好的，所以我会通过它的路径调用 umask，但是：

[stephen@flip:/mnt/sdb/Downloads]
:> which umask
which: no umask in <PATH>

[stephen@flip:/mnt/sdb/Downloads]
:> alias umask
bash: alias: umask: not found

我能/应该做什么？

拱最新。

通过 QEMU 管理器，我最近创建了一个映射到我的无线设备的 NAT 网络。计划是为虚拟机使用无线，为主机使用以太网。在此之前，VM 和未绑定的主机都可以。

没有其他系统变化。

现在，系统重新启动后，unbound 无法启动，抱怨它无法获取端口 53。通过 lsof 我看到 dnsmasq 占用了 53。即使我的虚拟网络无法在启动时启动，也会发生这种情况。

我不想更改未绑定的端口，因为这需要重新配置其客户端。

为什么 dnsmasq 启动？

最简单且影响最小的配置更改是什么？

我的蓝牙耳机视频延迟和口吃。

我最近切换到 pipewire，发现文档太高级而无法导航。配置层数太多，而且该服务的采用时间还不够长，无法获得良好的支持。

所以我想回滚到拥有更多开发文档和支持的 Pulse。

我在 Arch 上，发现当我尝试移除 pi​​pewire 时，我发现它有很多依赖项，我对它们的集成理解得不够好，无法自信地解决。

 # pacman -R pipewire
 checking dependencies...
 error: failed to prepare transaction (could not satisfy dependencies)
 :: removing pipewire breaks dependency 'pipewire' required by helvum
 :: removing pipewire breaks dependency 'pipewire' required by obs-studio
 :: removing pipewire breaks dependency 'pipewire' required by pipewire-media-session
 :: removing pipewire breaks dependency 'libpipewire-0.3.so=0-64' required by pipewire-media-session
 :: removing pipewire breaks dependency 'libpipewire-0.3.so=0-64' required by pipewire-pulse
 

如何移除或禁用管道线并返回脉冲？

或者，也许有人对解决蓝牙问题有建议。