Skip to content
Advertisement

Remove ext2 file with rootfs while it’s already mounted

What happens after mounting filesystem from file? Example: I have rootfs.ext2 file which is located in data directory and mounted under /mnt directory mount rootfs.ext2 /mnt After removing rootfs.ext2 I still can use files under /mnt directory, cat file, run binaries, etc. rm -f rootfs.ext2 I was thinking that rootfs.ext2 file still exists in data directory however it was deleted.

Should fsync() be called before or after write() call?

I understand the working of write() call wherein it writes the data only to kernel’s buffers which is later written to disk by kernel after sorting the data optimally. Calling fsync() on file descriptor makes sure that data is written to disk as soon as it’s posted in the kernel’s buffer. My question is, whether fsync() should be called before

how to use untar() in R linux?

I’m getting this error when I use untar() command used: untar(tarfile = “a.rar”, list = TRUE) It works when I use on my PC (Windows 10) but does not works on another PC (Linux 20.04) Thanks Answer This isn’t correct: You should specify a tape archive file such as “a.tar”, rather than a RAR-format file. The underlying utility on Windows

“PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/lib/php/20160303/http.so'” after downgraded PHP from 8.1 to 7.1

We have a requirement that needs to downgrade PHP from 8.1 to 7.1 in our Ubuntu 18 server. After the downgrade, we’re seeing PHP Startup error everytime we check php -v Below is the exact error text: The missing libraries are really not found in the said directory as I checked. We have tried reinstalling as suggested from other forum

Trying to install Docker on RHEL – docker-ce conflicts with Podman-docker

Getting this error: Updating Subscription Management repositories. Red Hat Enterprise Linux 8 for x86_64 – AppStream (RPMs) 22 MB/s | 45 MB 00:02 Last metadata expiration check: 0:00:01 ago on Mon 01 Aug 2022 17:36:44 BST. Error: Problem: problem with installed package podman-docker-2:4.0.2-6.module+el8.6.0+14877+f643d2d6.noarch package docker-ce-3:20.10.17-3.el8.x86_64 conflicts with docker provided by podman-docker-2:4.0.2-6.module+el8.6.0+14877+f643d2d6.noarch package docker-ce-3:20.10.17-3.el8.x86_64 conflicts with docker provided by podman-docker-1.0.0-2.git921f98f.module+el8+2785+ff8a053f.noarch package

Advertisement