Two formulas. One nanoscale object. Two completely different futures for its energy.
The graph shows how quantum dot energy changes with size and compares two theories. The radius model predicts stronger confinement, while the diameter model suggests a weaker shift.
1/2
@atulit_gaur The question is where to publish it as an independent researcher. Arxiv needs a Professor kinda person to introduce you then only you can publish it independently.
Are there other forums where you can publish it? I heard about Vixra but there's a consensus that it's not worthy.
Camus to Peter :
The gods had condemned Sisyphus to ceaselessly rolling a rock to the top of a mountain, whence the stone would fall back of it's own weight. They had thought with some reason that there is no more dreadful punishment than futile and hopeless labor.
What are Linux Mount Namespaces and How Containers Use Them 🧐
When you create or modify a file in one Docker container, the change is usually not visible in another. However, this is not because these two containers use different mount (mnt) namespaces.
Each Linux container's root filesystem typically resides in a dedicated folder on the host. Thus, modifications to such filesystems would be isolated from each other even w/o the use of mount namespaces - simply because these are different folders.
At the same time, if you create a couple of mount namespaces manually with the "unshare --mount" command, changes to files in a certain folder in one namespace will be visible in the other (see the /etc example in the diagram).
What a mount namespace isolates is the list of mount points visible by processes in the namespace - i.e., the mount table.
For our example it means that if you mount a drive or bind-mount a folder in one namespace, its contents won't appear in another (see the /mnt example in the diagram). But how is it relevant for containers?
Modern containers "switch" to their dedicated rootfs using the pivot_root() system call, which changes the / mount. It is a much more reliable mechanism than "simple" chroot. But what you absolutely don't want to do is call pivot_root() from the main mount namespace of the host - it'd change the root mount not only for the container process but also for all other processes currently running on the host 💥
Hence, each container should reside in its own dedicated mount namespace.
Read more about how container filesystem works in this hands-on tutorial https://t.co/PC7c9Zy1SJ
Alright fellas,
I have built a program to tell me all the running PID.
cargo run -- list
also i can open firefox from the terminal
cargo run -- run "firefox"