try
try copied to clipboard
Inspect a command's effects before modifying your live system
> Talking with @angelhof about this, we realized there's a tricky interaction with `process_changes` when you have multiple lowerdirs: you have to replay the merge to do the comparison. >...
``` [ +0.002145] overlayfs: upperdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior. [ +0.000003] overlayfs: workdir is in-use as upperdir/workdir...
``` eric@ide0:~/try$ ./try ping -c1 1.1 ping: socktype: SOCK_RAW ping: socket: Operation not permitted ```
When @ericzty demoed `try` installing rust at the recent pash retreat, try was fast but the summary was painfully slow and very noisy. The problem is in the `summary()` routine....
`openat(AT_FDCWD, "/tmp", O_RDWR|O_EXCL|O_CLOEXEC|O_TMPFILE, 0600) = -1 EOPNOTSUPP (Operation not supported)` Motivation: `apt update` on future branch mostly works besides being unable to make tmpfiles for signature verification, emitting warnings. Everything...
When attempting to merge two directories residing under the same overlayfs mountpoint within try, the operation fails, rendering the common directory unmountable within try. #### Error Reproduction: ```ShellSession $ ./try...
some of the pure_mountpoint logic were missed when merging commits over. this PR addresses them by copying those changes from the hs branch.
I found overlayfs somehow are not compatible with WSL when using `try`. **Solution:** It can be solved by installing unionfs so I add the **WSL** subtitle in README-Installing
symlinks /dev/std{in,out,err} to /proc/self/fd/{0,1,2} and cleanup after tests included