I suppose I should have made it clear that just changing the amount of
memory reserved was not sufficient.

Perhaps it would be useful to print a message saying "hey, I know we set
something by default, but we don't expect that to actually work, so you
should probably test and adjust it"?

Because it sounds like it's not expected to work out of the box, and
configuring it to "on, but doesn't actually work or warn you" when you
install the package seems worse than not configuring it, similar to how
I wouldn't expect installing ccache to result in it sticking itself in
my PATH, reporting "ccache enabled and working" when asked, but then
defaulting to a max cache size of 4 kilobytes.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931779

Title:
  kdump just hung out of the box

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1931779/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to