Simply installed sshfs and got this warning.
It refers to pve-cluster and ceph-fuse, so I ask if this can be something to considered.
I suppose Proxmox Team had his good reasons for maintaining the "old" fuse instead of fuse3.
It refers to pve-cluster and ceph-fuse, so I ask if this can be something to considered.
I suppose Proxmox Team had his good reasons for maintaining the "old" fuse instead of fuse3.
# apt install sshfs
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
fuse3
The following packages will be REMOVED:
fuse
The following NEW packages will be installed:
fuse3 sshfs
0 upgraded, 2 newly installed, 1 to remove and 0 not upgraded.
Need to get 81.6 kB of archives.
After this operation, 94.2 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ftp.it.debian.org/debian bookworm/main amd64 fuse3 amd64 3.14.0-4 [35.9 kB]
Get:2 http://ftp.it.debian.org/debian bookworm/main amd64 sshfs amd64 3.7.3-1.1 [45.6 kB]
Fetched 81.6 kB in 0s (330 kB/s)
dpkg: fuse: dependency problems, but removing anyway as you requested:
pve-cluster depends on fuse.
ceph-fuse depends on fuse.
(Reading database ... 60650 files and directories currently installed.)
Removing fuse (2.9.9-6+b1) ...
update-initramfs: deferring update (trigger activated)
Selecting previously unselected package fuse3.
(Reading database ... 60641 files and directories currently installed.)
Preparing to unpack .../fuse3_3.14.0-4_amd64.deb ...
Unpacking fuse3 (3.14.0-4) ...
Selecting previously unselected package sshfs.
Preparing to unpack .../sshfs_3.7.3-1.1_amd64.deb ...
Unpacking sshfs (3.7.3-1.1) ...
Setting up fuse3 (3.14.0-4) ...
Installing new version of config file /etc/fuse.conf ...
update-initramfs: deferring update (trigger activated)
Setting up sshfs (3.7.3-1.1) ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.2.16-19-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.
Alternatively, use --esp-path= to specify path to mount point.
Processing triggers for man-db (2.11.2-2) ...
# pveversion
pve-manager/8.0.4/d258a813cfa6b390 (running kernel: 6.2.16-19-pve)
