1 [gelöst] mkfs not found? 15. Februar 2023, 14:12 Sollte mkfs nicht standardmäßig da sein? Installiert war: Quellcode xfsprogs-mkfs/unknown,now 4.10.0-r0.0 arm64 [installed] XFS Filesystem Utilities Ich habe installiert: Quellcode util-linux-mkfs/unknown,now 2.29.1-r0.0 arm64 [installed] A suite of basic system administration utilities immer noch: Quellcode newnigma2@dreambox:~$ mkfs -bash: mkfs: command not found Wo mkfs?
2 15. Februar 2023, 14:21 Was geht ab mit dem newnigma2 user? Quellcode newnigma2@dreambox:~$ /usr/sbin/mkfs Usage: mkfs [options] [-t <type>] [fs-options] <device> [<size>] Make a Linux filesystem. Options: -t, --type=<type> filesystem type; when unspecified, ext2 is used fs-options parameters for the real filesystem builder <device> path to the device to be used <size> number of blocks to be used on the device -V, --verbose explain what is being done; specifying -V more than once will cause a dry-run -V, --version display version information and exit; -V as --version must be the only option -h, --help display this help text and exit For more details see mkfs(8). Alles anzeigen Da passt das environment / der PATH gar nicht? Quellcode newnigma2@dreambox:~$ echo $PATH /usr/script:/usr/local/bin:/usr/bin:/bin Verwirrung.
3 15. Februar 2023, 15:20 Probiere mal mit sudo: Quellcode newnigma2@dreambox:~$ sudo mkfs.ext4 Password: Usage: mkfs.ext4 [-c|-l filename] [-b block-size] [-C cluster-size] [-i bytes-per-inode] [-I inode-size] [-J journal-options] [-G flex-group-size] [-N number-of-inodes] [-d root-directory] [-m reserved-blocks-percentage] [-o creator-os] [-g blocks-per-group] [-L volume-label] [-M last-mounted-directory] [-O feature[,...]] [-r fs-revision] [-E extended-option[,...]] [-t fs-type] [-T usage-type ] [-U UUID] [-e errors_behavior][-z undo_file] [-jnqvDFSV] device [blocks-count] Quellcode newnigma2@dreambox:~$ sudo mkfs.xfs No device name specified Usage: mkfs.xfs /* blocksize */ [-b log=n|size=num] /* metadata */ [-m crc=0|1,finobt=0|1,uuid=xxx,rmapbt=0|1,reflink=0|1] /* data subvol */ [-d agcount=n,agsize=n,file,name=xxx,size=num, (sunit=value,swidth=value|su=num,sw=num|noalign), sectlog=n|sectsize=num /* force overwrite */ [-f] /* inode size */ [-i log=n|perblock=n|size=num,maxpct=n,attr=0|1|2, projid32bit=0|1,sparse=0|1] /* no discard */ [-K] /* log subvol */ [-l agnum=n,internal,size=num,logdev=xxx,version=n sunit=value|su=num,sectlog=n|sectsize=num, lazy-count=0|1] /* label */ [-L label (maximum 12 characters)] /* naming */ [-n log=n|size=num,version=2|ci,ftype=0|1] /* no-op info only */ [-N] /* prototype file */ [-p fname] /* quiet */ [-q] /* realtime subvol */ [-r extsize=num,size=num,rtdev=xxx] /* sectorsize */ [-s log=n|size=num] /* version */ [-V] devicename <devicename> is required unless -d name=xxx is given. <num> is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB), xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB). <value> is xxx (512 byte blocks). Alles anzeigen Anleitung zum Newnigma2 Image
4 15. Februar 2023, 16:47 Geht mit sudo! Dann kann ich ja */sbin für newnigma2 PATH in der /etc/profile wieder entfernen. Danke!