Releases: RainbowHackerHorse/vzvol
Releases · RainbowHackerHorse/vzvol
This life...follows you. It clings to you
Changelog:
- The Debian and Ubuntu repos are now live!
- Deprecated --help
- Added manpages!
- vzvol Linux packages now install to /usr/local/sbin/vzvol
- Various minor bugfixes mostly related to Linux packaging
Errata:
vzvol --file-system zfs
does not currently create a zpool. Something broke and I don't know what. It worked before.
you happen to know the way to Shell Beach?
Changelog:
- Resolved an issue where a VMDK was being created with root permissions, and not permissions for the calling user.
- Now building .deb and .rpm files.
You went looking in the wrong place
Changelog:
- Broke something horribly last version. Here's the fix.
(I forgot that variables and singlequotes dont mix)
Errata:
- vzvol doesn't correctly set permissions on the VMDK. This will be resolved in a new version push tonight, and is already fixed in master
It seems you have discovered your unpleasant nature, Mr. Murdoch
Changelog:
- Moved usage of
$HOME
to$ZUSERHOME
, which resolves an issue wheresudo
was nuking$HOME
for everyone, resolving #32 - Re-implemented automatic guessing of the user who ran the command, via
logname
call
Milestone plans for 0.7.0:
- Official manpage (Thanks to @Alhadis )
- Removal of requirement for using
sudo
to runvzvol --list
- Removal of
vzvol --help
in favor of the manpage
That annoying "Are you sure?" dialogue box
Changelog:
- Resolve issue where --delete would error out if more than one zvol existed
We destroy parts of ourselves everyday
- Remove internal su(do) weirdness, and require the user to just run it as sudo/root. THIS IS A BREAKING CHANGE WITH OLDER VERSIONS! Eventually,
vzvol --list
will be restored to being able to run as a normal user, and only listing zvols for which the user has grants. - vzvol now requires you to specify -u on the commandline, as it can't grok your user automatically anymore
- fix use of $HOME for root (used to default for all users to /home/user)
- made sourcing of vzvol/lib files more bettererererer.
You will cooperate, my son. I will make you, because I own you.
- Various syntactical fixes, courtesy of @freebsdfrau
- Fixed a bug in --delete preventing it from ever failing the zvol_exists? check.
You just have to take away what they already have
- Modularize vzvol to allow for easier code maintenance, and further expansion
- Fix some of the logic for checking status
- vzvol now only loads functions appropriate to the OS, as well as common functions from ./lib/shared/
Even though I created you, it makes no difference
- Various syntax fixes
- Fixed a bug in
vzvol --list
where output would be duplicated if no vzvols existed - Fixed an issue where
--import
wasn't actually running thedd
command - Set a check to ensure
--import
dd
's directly to the device in question without having to follow the symlink - Alter logic for chown on new zvol create prior to devfs modification to allow instant access to the zvol by the user
--import
can now be used on an existing zvol. Simply runvzvol -v volumename --import importfile.img
Always the same. I'm on a loop.
- Fix a bug that arose earlier that caused
vzvol --list
to erroneously print unformatted output multiple times to STDOUT