| History log of /src/distrib/amd64/ramdisks/Makefile |
| Revision | | Date | Author | Comments |
| 1.6 |
| 05-Jun-2024 |
riastradh | ramdisk-zfsroot: Only enable if zfs is enabled.
PR port-amd64/58316
PR port-amd64/57948 (followup pullup)
|
| 1.5 |
| 19-Feb-2024 |
riastradh | ramdisk-zfsroot: Enable build by default on amd64.
XXX Should maybe copy this to other ports like evbarm64 too.
PR port-amd64/57948
|
| 1.4 |
| 21-May-2017 |
riastradh | branches: 1.4.20;
Remove MKCRYPTO option.
Originally, MKCRYPTO was introduced because the United States
classified cryptography as a munition and restricted its export. The
export controls were substantially relaxed fifteen years ago, and are
essentially irrelevant for software with published source code.
In the intervening time, nobody bothered to remove the option after
its motivation -- the US export restriction -- was eliminated. I'm
not aware of any other operating system that has a similar option; I
expect it is mainly out of apathy for churn that we still have it.
Today, cryptography is an essential part of modern computing -- you
can't use the internet responsibly without cryptography.
The position of the TNF board of directors is that TNF makes no
representation that MKCRYPTO=no satisfies any country's cryptography
regulations.
My personal position is that the availability of cryptography is a
basic human right; that any local laws restricting it to a privileged
few are fundamentally immoral; and that it is wrong for developers to
spend effort crippling cryptography to work around such laws.
As proposed on tech-crypto, tech-security, and tech-userlevel to no
objections:
https://mail-index.netbsd.org/tech-crypto/2017/05/06/msg000719.html
https://mail-index.netbsd.org/tech-security/2017/05/06/msg000928.html
https://mail-index.netbsd.org/tech-userlevel/2017/05/06/msg010547.html
P.S. Reviewing all the uses of MKCRYPTO in src revealed a lot of
*bad* crypto that was conditional on it, e.g. DES in telnet... That
should probably be removed too, but on the grounds that it is bad,
not on the grounds that it is (nominally) crypto.
|
| 1.3 |
| 30-Jun-2016 |
pgoyette | Omit cgd based ramdisks and miniroot modules if MKCRYPTO=no
Final part of PR kern/51282
|
| 1.2 |
| 15-Jul-2013 |
khorben | Build the cgdroot ramdisk by default (for full-disk encryption support). It currently contains the same utilities found in an amd64 sysinst ramdisk, which should be useful in case of emergency.
|
| 1.1 |
| 02-Jun-2006 |
hubertf | branches: 1.1.20; 1.1.44; 1.1.50;
Prepare creation of boot CDs:
* Move files in distrib/amd64:
floppies/instkernel/Makefile -> instkernel/Makefile
floppies/ramdisk/Makefile -> ramdisks/ramdisk/Makefile
floppies/ramdisk/disktab.preinstall -> ramdisks/ramdisk/disktab.preinstall
floppies/ramdisk/list -> ramdisks/ramdisk/list
floppies/ramdisk/list.inet6 -> ramdisks/ramdisk/list.inet6
floppies/common/Makefile.ramdisk -> ramdisks/common/Makefile.ramdisk
floppies/common/dot.profile -> ramdisks/common/dot.profile
floppies/common/list.ramdisk -> ramdisks/common/list.ramdisk
floppies/common/termcap.mini -> ramdisks/common/termcap.mini
* Adjust paths
|
| 1.1.50.1 |
| 19-Aug-2014 |
tls | Rebase to HEAD as of a few days ago.
|
| 1.1.44.1 |
| 22-May-2014 |
yamt | sync with head.
for a reference, the tree before this commit was tagged
as yamt-pagecache-tag8.
this commit was splitted into small chunks to avoid
a limitation of cvs. ("Protocol error: too many arguments")
|
| 1.1.20.1 |
| 05-Oct-2008 |
mjf | Sync with HEAD.
|
| 1.4.20.2 |
| 24-Jul-2024 |
martin | Pull up following revision(s) (requested by ozaki-r in ticket #766):
distrib/amd64/ramdisks/Makefile: revision 1.6
ramdisk-zfsroot: Only enable if zfs is enabled.
PR port-amd64/58316
PR port-amd64/57948 (followup pullup)
|
| 1.4.20.1 |
| 23-Feb-2024 |
martin | Pull up following revision(s) (requested by riastradh in ticket #602):
distrib/amd64/ramdisks/Makefile: revision 1.5
ramdisk-zfsroot: Enable build by default on amd64.
XXX Should maybe copy this to other ports like evbarm64 too.
PR port-amd64/57948
|
