*** This bug is a duplicate of bug 1431523 ***
https://bugs.launchpad.net/bugs/1431523
I see, should I notify the zfs guys taking into account the comments in
https://github.com/zfsonlinux/pkg-zfs/issues/132 ? Or is this taken into
account in the roadmap for systemd somehow?
Always available for testing!
Cheers!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1432122
Title:
mountall service unavailable on systemd, preventing full zfs
integration
Status in systemd package in Ubuntu:
New
Bug description:
I am test-driving Vivid and made the switch to systemd. I'd like to
report that the mountall service is now unavailable.
root# systemctl status mountall
mountall.service
Loaded: masked (/dev/null)
Active: inactive (dead)
root# ll /lib/systemd/system/mountall.service
lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service ->
/dev/null
Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is
what is keeping all of my zfs filesystems from being automounted at
boot.
Things worked fine with upstart.
zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145
mountall bug report:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1432123
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432122/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
