Summary: | Add 'msed' to Portage for management of Self-Encrypting hard Drives | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jesse Adelman <jesse> |
Component: | Current packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
Status: | UNCONFIRMED --- | ||
Severity: | enhancement | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/Drive-Trust-Alliance/sedutil | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jesse Adelman
2015-10-05 01:56:37 UTC
P.S. Why am I interested? I'm thinking of getting this: http://www.crucial.com/usa/en/ssd/CT1000MX200SSD1 :) Hello, If you have an interest in this package, you're welcome to contribute ebuild and become a proxy maintainer, see https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers for details. FYI, the source is now available at: https://github.com/Drive-Trust-Alliance/sedutil/tree/master however, this package also requires a customized build of syslinux: https://github.com/Drive-Trust-Alliance/syslinux/tree/master I'm working on an ebuild for possible inclusion, with me as a proxy-maintainer. However, the fact that this package really has two repo'd components seems to make the ebuild process complex. Should I split it into two separate ebuilds to handle the 'syslinux' PBA fork and the 'msedutil' code separately? Thanks. |