Skip to content

Adding tun module as a vellum package#128

Open
esclee wants to merge 10 commits intovellum-dev:mainfrom
esclee:main
Open

Adding tun module as a vellum package#128
esclee wants to merge 10 commits intovellum-dev:mainfrom
esclee:main

Conversation

@esclee
Copy link
Copy Markdown

@esclee esclee commented Mar 30, 2026

Current plan is for me to build tun modules for ferrari and chiappa as rM releases toolchains and kernel for new OS versions and throw the compiled versions onto a github repo.

esclee added 2 commits March 29, 2026 20:35
Updated maintainer and upstream author information, modified package description and URL.
@esclee
Copy link
Copy Markdown
Author

esclee commented Mar 30, 2026

Ideally this could complement #116

Comment thread packages/tun/VELBUILD Outdated
Comment thread packages/tun/VELBUILD Outdated
Comment thread packages/tun/VELBUILD Outdated
Comment thread packages/tun/VELBUILD Outdated
depmod -a
modprobe tun
echo "tun" > /etc/modules-load.d/tun.conf
sleep 1s
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you waiting 1 second here before doing a mount-restore? It doesn't look like you are doing any async changes to /etc or / that would require waiting? If there is, perhaps a sync is in order instead of sleep?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for some reason /home/root/.vellum/bin/mount-restore was erroring out on me with mount: /: mount point is busy, this seemed to solve it. Open to suggestions!

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Try a sync to make sure all changes have been properly written to disk. It could be that it hasn't finished writing. If it's not that, we should track down what is writing to the root partition that shouldn't be, as you have finished your changes already.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tried sync, worked for install!

Copy link
Copy Markdown
Member

@rmitchellscott rmitchellscott Apr 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 doesn't mount-restore already run a sync?

echo "Remounting / as read-only..."
sync
mount -o remount,ro /

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

https://serverfault.com/a/439955
Perhaps the busybox version of sync that is in use still needs two calls to make sure everything is done?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not entirely sure what the root cause is but my experience is that running sync in there resolved the issue with mount-restore throwing an error in the post install step

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@esclee could you try swapping the mount-restore script to sync; sync and taking out your sync? If that works I'll just update mount-utils

esclee and others added 3 commits April 12, 2026 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants