linka-cloud / linka-cloud/d2vm
Temp file aka loop device on custom location
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 373
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
Can I manipulate the location of the loop device as my partition table is custom setup and overloading:
df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 126G 0 126G 0% /dev/shm
tmpfs 51G 15M 51G 1% /run
/dev/mapper/rl_kvm02--nikhef-root 16G 16G 365M 98% /
/dev/mapper/rl_kvm02--nikhef-home 2.0G 71M 2.0G 4% /home
/dev/sda1 1006M 353M 654M 36% /boot
/dev/mapper/rl_kvm02--nikhef-var_lib_libvirt 90G 33G 58G 37% /var/lib/libvirt
/dev/mapper/rl_kvm02--nikhef-var_log 2.0G 145M 1.9G 8% /var/log
tmpfs 26G 16K 26G 1% /run/user/0
/dev/mapper/loop0p1 9.8G 664M 8.6G 8% /tmp/d2vm/7bbba60b-9041-4741-a261-8bcd856e1461/mnt
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, entry points, or tests. Begin by tracing how d2vm creates and mounts the loop device, then clarify the supported configuration and expected behavior for placing it on a custom location before estimating implementation work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100