I have to learn some usage about lvm on linux, so this is my notice about this. But this is not complete.
sudo lvdisplay
[sudo] password for debian-buildd:
Sorry, try again.
[sudo] password for debian-buildd:
--- Logical volume ---
LV Path /dev/vg0/swap
LV Name swap
VG Name vg0
LV UUID hmY5Dt-S0GH-wxrN-fE9M-BwU9-bFMP-j2e05Z
LV Write Access read/write
LV Creation host, time unmatched05, 2022-08-10 21:43:43 +0800
LV Status available
# open 2
LV Size 100.00 GiB
Current LE 25600
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
--- Logical volume ---
LV Path /dev/vg0/srv
LV Name srv
VG Name vg0
LV UUID T8nIYl-WdwX-hfYr-Yg3N-FiD1-7M1j-R54cGN
LV Write Access read/write
LV Creation host, time unmatched05, 2022-08-10 21:43:43 +0800
LV Status available
# open 1
LV Size 40.00 GiB
Current LE 10240
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
This is to check lv (logical volume) for existing lv.
sudo vgdisplay
--- Volume group ---
VG Name vg0
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 3
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 2
Open LV 2
Max PV 0
Cur PV 1
Act PV 1
VG Size 1.80 TiB
PE Size 4.00 MiB
Total PE 472163
Alloc PE / Size 35840 / 140.00 GiB
Free PE / Size 436323 / 1.66 TiB
VG UUID VCkz6D-Di19-Oh0a-GtaN-d9Th-sAqQ-ODNswr
This is vg (volume group) info. I think it can give you a picture of whole disk from lvm’s view.
From above info, you will get the information about lv with its path.
sudo lvextend -L +200G /dev/vg0/srv
Size of logical volume vg0/srv changed from 40.00 GiB (10240 extents) to 240.00 GiB (61440 extents).
Logical volume vg0/srv successfully resized.
The command is to extend
lv with path.
debian-buildd@unmatched05:~$ sudo resize2fs /dev/vg0/srv
resize2fs 1.46.6-rc1 (12-Sep-2022)
Filesystem at /dev/vg0/srv is mounted on /srv; on-line resizing required
old_desc_blocks = 5, new_desc_blocks = 30
The filesystem on /dev/vg0/srv is now 62914560 (4k) blocks long.
Using resize2fs
to resize fs.
Verity again:
debian-buildd@unmatched05:~$ df -h /srv
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg0-srv 236G 479M 226G 1% /srv
Now I have one package which needs systemd unit, so this is a basic wiki collected.
https://bunn.cc/2017/debian-packaging-with-systemd/ [not right]
[refer to here] https://askubuntu.com/questions/746094/how-to-package-a-systemd-service
To send the keys. You can refer to the wiki
TODO: The encryption for the password does not work now.
To config MAILER_SENDER
with msmtp
.
$ENV{'PERL_MAILERS'} = 'sendmail:/usr/bin/msmtp';
.caffrc
:
vimer@debian:~$ cat ~/.caffrc
# .caffrc -- vim:ft=perl:
# This file is in perl(1) format - see caff(1) for details.
$CONFIG{'owner'} = 'xx';
$CONFIG{'email'} = 'xx@xx';
#$CONFIG{'reply-to'} = '[email protected]';
# You can get your long keyid from
# gpg --keyid-format long --list-key <yourkeyid|name|emailaddress..>
#
# If you have a v4 key, it will simply be the last 16 digits of
# your fingerprint.
#
# Example:
$CONFIG{'keyid'} = [ qw{954E6A70100598A2} ];
# or, if you have more than one key:
# $CONFIG{'keyid'} = [ qw{0123456789ABCDEF 89ABCDEF76543210} ];
#$CONFIG{'keyid'} = [ qw{0123456789ABCDEF 89ABCDEF76543210} ];
# Select this/these keys to sign with
#$CONFIG{'local-user'} = [ qw{0123456789ABCDEF 89ABCDEF76543210} ];
# Additionally encrypt messages for these keyids
#$CONFIG{'also-encrypt-to'} = [ qw{0123456789ABCDEF 89ABCDEF76543210} ];
$ENV{'PERL_MAILERS'} = 'sendmail:/usr/bin/msmtp';
#$CONFIG{'mail-cmd'} = [ 'mutt', '-e', "set from='$CONFIG{owner} <$CONFIG{email}>" pgp_autoencrypt'
# , '-s', "Your signed PGP key 0x$recipient{keyid}"
# , '-i', $recipient{'template-file'}
# , '-a', $recipient{'signature-file'}
# , '--'
# , $recipient{address} ]
# Mail template to use for the encrypted part
$CONFIG{'mail-template'} = << 'EOM';
Hi,
please find attached the user id{(scalar @uids >= 2 ? 's' : '')}
{foreach $uid (@uids) {
$OUT .= "\t".$uid."\n";
};}of your key {$key} signed by me.
If you have multiple user ids, I sent the signature for each user id
separately to that user id's associated email address. You can import
the signatures by running each through `gpg --import`.
Note that I did not upload your key to any keyservers. If you want this
new signature to be available to others, please upload it yourself.
With GnuPG this can be done using
gpg --keyserver hkp://pool.sks-keyservers.net --send-key {$key}
If you have any questions, don't hesitate to ask.
Regards,
--
{$owner}
EOM
Source: commons-daemon
Version: 1.0.15-8
Severity: normal
Tags: ftbfs patch
User: [email protected]
Usertags: riscv64
X-Debbugs-Cc: [email protected]
see #1010381
Source: ironseed
Version: 0.4.0-5
Severity: important
User: [email protected]
Usertags: flaky
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:libsdl2
See #1077847
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.