Trying to install Julia on a machine with the following specification:
Operating System: Ubuntu 18.04.6 LTS
Kernel: Linux 5.4.0-1090-azure
Architecture: x86-64
I ran:
tar -xvzf julia-1.6.7-linux-x86_64.tar.gz
and got several error messages that look like these:
julia-1.6.7/lib/libjulia.so
tar: julia-1.6.7/lib/libjulia.so: cannot create symlink to ‘libjulia.so.1.6’: operation not supported
julia-1.6.7/lib/julia/libgfortran.so
tar: julia-1.6.7/lib/julia/libgfortran.so: Cannot create symlink to ‘libgfortran.so.4.0.0’: Operation not supported
Any suggestion on how to solve these error messages are much appreciated.
The typical problem is that not all operating systems are supporting symlinks.
Try df -Th and look what is going on with the drive you are trying to install:
root#LGPSZ:~# df -Th
Filesystem Type Size Used Avail Use% Mounted on
...
/dev/sdc ext4 1007G 8.0G 948G 1% /
...
In the example above my root drive is an ext4 type which supports symlinks.
On the other hand a Windows file system could be mounted on your Linux machine which type is denoted as ntfs or vfat. Those file system do not support symbolic links and hence the tar command will fail.
P.S.
[ugly workaround for desperate cases] If you really need to use ntfs partition on a Linux system a brutal workaround could be untarring the file on an ext4 file system and then tarring it again using --deference option - in that case you would get a tar archive without symlniks (I have not tested it with Julia though but should work).
I need to check some data in linux kernel while mounting NTFS, but if I use
mkfs.ntfs
or
mkntfs
and then
mount -t ntfs ...
The string containing info about file system in kernel is "fuseblk", not "ntfs" that i need.
Maybe that's because of "ntfs-3g" packs that i installed, as i know it contains fuse drivers.
How to mount NTFS without fuse?
I tried to change options in "mount" or "mkfs", but nothing helped.
I just deleted ntfs-3g packages and it worked as i wanted... Stranger things.
I run a Linux VM on VirtualBox and just made a mistake by moving the contents in /usr to a different partition mounted as /u01. My intention was to free up space for the / file system but realized I should have used cp instead of mv. It's not possible to run any command now. Is there any way I can recover the system?
Fixed by booting with iso image and mounting the root and restored the contents back to original partition.
I'm building an LFS (Linux From Scratch) system in a VM and so far I've managed to get a workable, desktop system, booting from a known device, /dev/sda1 in my case. I'm now trying to make a live system that boots from an ISO image. Instead of using /dev/sr0 as the root, which I've already established is possible (and, since it's more likely to be used from a USB stick than an actual CD-ROM, is too inflexible) I've set my mind on booting it into an initrd root. The idea is to use that as the system's root instead of using it as a temporal root to load the "real" root, and since it's already in memory, it saves me the trouble of setting up a tmpfs root, copy all the files, and switch to it.
I had been previously been experimenting with a squashfs image as I had seen that Ubuntu seemed to use that and has what I needed: a small sized root, being faster to load, using less memory, and is fast (xz is SSLLOOWW to extract and gzip is slow to load). At first I was having trouble booting it, so i switched to the cpio based initrd. After some initial trouble due to missing files on the archive I did manage to boot it.
I left that aside for the time being (around a month ago) to do other tasks on the system. I lost the original GRUB2 settings and kernel config so went about doing it again but Ive been running into a brick wall. I'm hoping someone here might know what I'm missing.
When I boot up I never see any message about the loading of the initrd file, it goes straight into the loading, uncompressing and booting up of the kernel. And this ends up in a kernel panic with the message
VFS: cannot open root device "(null)" or unknown-block (1,0): error -6
Please append the correct "root=" boot option; here are the available partitions:
No partitions are shown and following that is the "kernel panic" message, just repeating the first line. If I use the "rootfstype=ramfs" I get:
VFS: mounted root (ramfs filesystem) readonly on device 0:15.
devtmpfs: error mounting -2
Essentially, it's mounting an EMPTY ramfs file system as root, so mounting the devtmpfs fails because the /dev entry doesn't exist. But certain I used that boot option before.
Here's my GRUB 2 config:
menuentry = "LFS (inird test)" {
linux /boot/kernel/initrd/linux ro rdinit=/etc/init
initrd /boot/kernel/initrd/root.cpio.gz
}
Yes, /boot/kernel/initrd/ directory entry exists, linux is the kernel (the bzimage file produced by compiling the kernel), and root.cpio.gz is my compressed initrd root cpio archive.
Here's my kernel's .config file (sorry can't paste it here).
If any more info is needed, don't hesitate to ask. That you.
OK, I managed to solve the problem! Apparently, it wasn't the kernel's configuration, GRUB2, or even the bootup sequence. It was the initrd archive itself. Deep in the bowels of the Linux kernel's configuration lied the answer: the archive must be built using cpio's --newc option. The one I built manually lacked this option, so the kernel was ignoring the archive and just proceeding with the normal boot procedure.
This came about because I managed to stumble across an older script I used to build them and saw all the options in it for cpio. I checked the much more recent script I hastily put together and double-checked the kernel documentation (as well as the init/do_mounts.c and init/initramfs.c files) and realized what was going on. I tried it with the corrections and the system now happily boots into the initrd with no problem! :D
I have a rootfs boot image that I want to test by mounting on my local file system. How can I do this ?
EDIT: The file was a rootfs.img but it turned out I did not have the correct filesystem support in my custom kernel. pjz's answer works once the fs support is there.
Need more info - what kind of image is it?
is it a file that's a filesystem? if so you mount it like:
mount -o loop rootfs.img /mnt/rootfs
if it's a subdir of your filesystem that you'r exporting via nfs, you can simulat ethe environment you've created by chrooting to it:
chroot /path/to/nfs/rootdir/