The only way around that would be to install the headers when installing the backports kernel
Can't we add the header dependency to the zfs plugin by adding
to the list of dependencies?
The only way around that would be to install the headers when installing the backports kernel
Can't we add the header dependency to the zfs plugin by adding
to the list of dependencies?
I would love to do it that way but the control file isn't a bash script so it doesn't evaluate the uname command.
The control file isn't a bash script so it doesn't evaluate the uname command.
But maybe it can run like a postinst script? with single line command, like the insserv removal?
You can't use apt/dpkg commands while installing a package with apt/dpkg. So, you can't do that in the postinst. That is why I moved it to when the repo is enabled. If they install the backports kernel after enabling the zfs repo, they will just have to disable and then re-enable the zfs repo to fix it.
I'll leave this in case someone for comparing features in zfs in different ports, this features might produce a fail to import pools from other systems.
http://open-zfs.org/wiki/Features#Feature_Flags
You are warned...check your flags/features before exporting from Freenas (especially 9.2, a little friend called com.delphix:hole_birth says hello!!)
And you shouldn't use apt in postinst either. Even though we use pip to install python packages in some places (mostly because no one have the patience to package) and wget in some, it's still a bad practice to install/download files within the installer.
In theory, if the package would depend on linux-headers-$(uname -r) it would depend on a specific version and be bound to that one. Depending on the linux-headers-amd64 package works correctly. It's just that when you install the backports kernel you could do this apt-get -t wheezy-backports install linux-image-amd64 linux-headers-amd64 to have the latest version of both. This continues to work with updates.
In the control file this would work as: Depends: linux-headers-i386 [i386], linux-headers-amd64 [amd64]
If omv-extras didn't install the headers when enabling the repo, they would still not have the right headers if they installed the plugin and then installed the backports kernel. The only true way to make it easy to fix is add a Fix button like virtualbox. I suppose both the 3.2 headers and 3.16 headers could be installed by the plugin but someone would complain because they have the 3.14 kernel installed.
Uh, if you tried to use apt/dpkg in postinst it wouldn't work because it would be locked. Since pip is not being used it could. Since when can you install 2 things at once with apt/dpkg?
Hi
I want to try the backports kernel AFTER I already installed ZFS. So reading the posts I need to install the backport kernel including the headers.
When I use:
apt-get -t wheezy-backports install linux-image-amd64 linux-head ers-amd64
Paketlisten werden gelesen... Fertig
E: Der Wert »wheezy-backports« ist für APT::Default-Release ungültig, da sol ch eine Veröffentlichung in den Paketquellen nicht verfügbar ist.
What would the correct command? thx!
Use the web interface in omv-extras for backport kernel
Also, uncheck the zfs repo checkbox and save. Then, check the zfs repo checkbox and save. The checkbox is in the secondary tab. This will install the headers for the 3.16 kernel.
Ok If I get it correctly:
1. disable ZFS
2. install backports
3. re-activate ZFS repo
thx
Yep.
Mhhh
Backports installed ok. After activating ZFS repo again I got this message:
Fehler
#4000:
exception 'OMVException' with message 'Failed to execute command
'omv-mkconf omvextrasorg 2>&1': Executing: gpg
--ignore-time-conflict --no-options --no-default-keyring
--secret-keyring /tmp/tmp.tsj2vKZ2DT --trustdb-name
/etc/apt//trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring
/etc/apt/trusted.gpg --keyring
/etc/apt/trusted.gpg.d//debian-archive-jessie-stable.gpg --keyring
/etc/apt/trusted.gpg.d//debian-archive-squeeze-automatic.gpg --keyring
/etc/apt/trusted.gpg.d//debian-archive-squeeze-stable.gpg --keyring
/etc/apt/trusted.gpg.d//debian-archive-wheezy-automatic.gpg --keyring
/etc/apt/trusted.gpg.d//debian-archive-wheezy-stable.gpg --keyserver
pgp.mit.edu --recv-keys 4D5843EA
gpg: fordere Schlüssel 4D5843EA von hkp-Server pgp.mit.edu an
gpgkeys: key 4D5843EA not found on keyserver
gpg: Keine gültigen OpenPGP-Daten gefunden.
gpg: Anzahl insgesamt bearbeiteter Schlüssel: 0' in
/usr/share/openmediavault/engined/module/omvextrasorg.inc:54
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/config.inc(180):
OMVModuleOmvExtrasOrg->applyConfig()
#1 [internal function]: OMVRpcServiceConfig->applyChanges(Array,
Array)
#2 /usr/share/php/openmediavault/rpcservice.inc(125):
call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc.inc(79):
OMVRpcServiceAbstract->callMethod('applyChanges', Array, Array)
#4 /usr/share/openmediavault/engined/rpc/omvextrasorg.inc(447):
OMVRpc::exec('Config', 'applyChanges', Array, Array)
#5 [internal function]:
OMVRpcServiceOmvExtrasOrg->setSecondary(Array, Array)
#6 /usr/share/php/openmediavault/rpcservice.inc(125):
call_user_func_array(Array, Array)
#7 /usr/share/php/openmediavault/rpc.inc(79):
OMVRpcServiceAbstract->callMethod('setSecondary', Array, Array)
#8 /usr/sbin/omv-engined(500): OMVRpc::exec('OmvExtrasOrg',
'setSecondary', Array, Array, 1)
#9 {main}
Alles anzeigen
But after reboot it showed running kernel 3.16 backports and my ZFS filesystem is online. So I think that all is good, I just cannot re-activate the ZFS repo without error.
The key is already added on your system. So, don't worry about it The mit keyserver must be having issues today.
Btw, maybe change the thread tag from OMV0.5 to OMV1.x, less confusing
Done.
Greetings
David
Hi,
is Btrfs still on the road? Can we expect it within the next 6 months?
thank you!
Basic support in the next release. Format and mount. You'll have to handle the rest by cli
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!