On Jul 14, 2007, at 5:08 AM, Bernardo Innocenti wrote:
For code licensed under GPLv2 or later, there should
be no (legal) requirement to ask anybody's permission.
I have strong feelings about this matter, but let's please drop the
discussion for now. We have bigger things to worry about, such
On Jul 10, 2007, at 5:54 PM, C. Scott Ananian wrote:
Unless we're actually going to do a full cryptographic authentication
of the entire FS image at every boot, the kernel checking is just
security theater.
I missed this message when originally following the thread. This is
incorrect.
On Fri, 2007-07-13 at 11:00 -0700, Greg KH wrote:
Isn't there a concern that the on-board security firmware in XO would
constitute tivoization essentially of the same sort that GPLv3 aims to
block?
Which is one reason the Linux kernel developers do not agree with that
part of the GPLv3
On Jul 14, 2007, at 9:07 AM, C. Scott Ananian wrote:
This seems to imply a much beefier initramfs than is currently the
case, and one that is invoked on every boot.
It can be done without beefing up the initramfs much, but you have a
good point about it requiring one for every boot. Let me
An incredible amount of features was integrated and started to work!
Now that feature integration is complete, everyone should be spending
most efforts on testing and bug fixing.
Please take a step back for a few minutes or hours hours, go over your
bug lists, close out the ones you've already
On 7/14/07, Jim Gettys [EMAIL PROTECTED] wrote:
2) if you have a package/bundle that should go in the build, please
include a change log with references to each bug you are fixing.
Include it directly in trac; having to excavate your change log out of a
rpm or bundle is a bit too painful.
2)
Marco,
H. If that is the current rate of change, it may be we should delay
instituting this process a few days or a week longer.
For the moment, then, I'll urge everyone to start being more careful
about testing packages before submitting them, and to be careful about
choosing which bugs are
