https://mirror-master.debian.org/status/mirror-info/nanomirrors.tuna.tsinghua.edu.cn.html
https://mirror-master.debian.org/status/mirror-info/neomirrors.tuna.tsinghua.edu.cn.html
可以监控 mirrors.
Some days(2024/06) ago I got one ROMA from DC donated for Debian Community. This week I have some time so to try run Debian sid on it.
The system on ROMA was Debian 11 with fixed version riscv64 Debian packages from debian-ports. Until now, we have no debian-ports any more, so this is a very interesting chanllenge.
The DC github is here 0, especially for docs which tells you how to flash image to ROMA.
From my observation, there is there image boot mode: emmc, sd and nvme. The default system from emmc(/dev/mmcblk0).
One key is that: riscv+t
can boot system from sd, then you can mount
devices to do everything you can do.
GPU drivers: https://github.com/starfive-tech/soft_3rdpart/blob/c43d4fab94b0ef3b492a6382e2282fa7a2695b9b/IMG_GPU/out/img-gpu-powervr-bin-1.19.6345021.tar.gz
mesa: https://github.com/starfive-tech/buildroot/tree/JH7110_VisionFive2_devel/package/mesa3d
Xorg: ?
On debian riscv64, until now we have xfce4 desktop.
lshw -c display
# to recongize kernel gpu driver, otherwise UNCLAIMED".
If you want to debug Desktop env, it is good to start to from startx
. Once you do not have any error from xorg, I think you have got it already.
Please also check the log file at "/home/vimer/.local/share/xorg/Xorg.0.log"
# permission issue generally
# normal to check issue from Xorg is from:
/var/log/Xorg.0.log
Due to some packages built from ourself, so we have to apt-mark some package to keep graphic display works
sudo apt-mark hold libegl-mesa0 libgbm1 libglapi-mesa mesa-vulkan-drivers
# partial
1 wiki
Many thanks for DeepComputing which offer the hardware and help from Songsong and RevysOS.
最近有一个需求是使用 neomutt 加密邮件内容。 相比较签名,加密确实更复杂一些。这里记录一下我探索的经历。
首先的一点是,必须提前把对方的 公钥 asc 导入到自己的主机, 这里我也不确认这是不是正确的方法,因为在实际操作中, neomutt找不到对应邮件的 keyid. 我的想法是,在这里我们应该把这些key放到一个配置目录中去,然后类似 source
的机制就应该识别到这些keys。 但是我没有找到这种方式,如果找到的话,恳请告知我一下。
可以参考这个 wiki, 如果对方是一个 asc 文件,直接 import
即可。
gpg --import public.asc
但是如何仅仅通过 keyid 直接转换得到 asc 文件呢? 比如大部分开发者会在邮件末尾附上自己的 gpg key。
经试验以下方法可行:
vimer@dev:~/git/yuzibo.github.io/_posts$ gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 12345678
gpg: key 786C63F330D7CB92: 13 duplicate signatures removed
gpg: key 786C63F330D7CB92: public key "example <[email protected]>" imported
gpg: Total number processed: 1
gpg: imported: 1
前提是这个 pubkey 的所有者将自己的key上传到 kerserver.
Debian DD 或者 DM 可以直接 fetch from Debian 的服务器, 以及如何更新过期的key,请参考这里
gpg --keyserver keyring.debian.org --recv-keys 0x2404C9546E145360
一旦 import, 请看下面的操作.
一些 config, 可以参考 wiki1.
在 neomutt 下, 如果想要加密的需要,编辑完邮件内容, 到发送界面:
y:Send q:Abort t:To c:CC s:Subj a:Attach file d:Descrip ?:Help
From: Bo YU <[email protected]>
To: [email protected]
Cc:
Bcc:
Subject: test for encrpting the email
Reply-To:
Fcc: +Sent
Security: Sign (PGP/MIME)
Sign as: <default>
Mix: <no chain defined>
Headers: X-PGP-Key: https://github.com/yuzibo/yuzibo.github.io/blob/master/_includes/subkey-signing-06-18-143E4BAF-pub.asc
-- Attachments
按下 p
或者 S
键, 出现:
PGP (e)ncrypt, (s)ign, sign (a)s, (b)oth, s/(m)ime or (c)lear?
然后选择 b
就是签名和加密一块选择.
此时 界面 的提示变为:
Subject: test for encrpting the email
Reply-To:
Fcc: +Sent
Security: Sign, Encrypt (PGP/MIME)
Sign as: <default>
Mix: <no chain defined>
一切准备完毕, 输入y
发送, 再次提示:
PGP keys matching <[email protected]>
ID has undefined validity. Do you really want to use the key? ([no]/yes)
输入 yes
并且 附带 签名的密码就可以发送了.
ansible doc: https://erdong.site/ansible-notes/ch01/1.3-ansible-config.html 实战: 首先,编辑或者创建 /etc/ansible/hosts 文件,用来存放远程主机的信息。你的公钥应该在这些机器的 authorized_keys 。您可以通过编辑/etc/ansible/ansible.cfg或~/.ansible.cfg来实现: 更简洁的可以参考这里: https://blog.51cto.com/395469372/2133486
ansible all -m ping
https://blog.csdn.net/Shyllin/article/details/123690458
sible all -m copy -a "src=/home/vimer/ansible/pubkey.debian-ci dest=/home/debian/"
ansible all -m shell -a "chmod +x /home/debian/add-user.sh"
4.1 sudo 命令:
debci-23 ansible_user=debian ansible_password="xx" ansible_ssh_user="xx" ansible_become_pass="xx"
a. 远程关机:
ansible all -m shell -a "poweroff" -become=true
b. 远程修改文件属性:
ansible all -m shell -a "usermod -aG sudo vimer" -become=true
打包 -dev 包含 so文件的包需要注意的事情 [1]: https://stackoverflow.com/questions/41383039/debian-package-naming-policy-for-soname 包名与so命名需要一致。 新的 需要总结:
https://elmarco.fedorapeople.org/gfxstream.spec https://src.fedoraproject.org/rpms/aemu/blob/rawhide/f/aemu.spec
git/aemu_2/aemu-0.1.2+dfsg$ new: ~/build/rfs/aemu_2/tag/aemu_0.1.2
有一些 upstream 的包使用 cmake 构建的,这时就需要对 cmake 有一个汇总。 这个页面就是将 cmake build system 打包的 tips 做一个汇总,以备不时之需。
multi arch 的 case
[gl4es]