Searched hist:"650 ea0d6" (Results 1 – 2 of 2) sorted by relevance
/freebsd/sys/amd64/conf/ |
H A D | GENERIC | 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days
|
/freebsd/sys/i386/conf/ |
H A D | GENERIC | 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days 650ea0d6 Tue Jan 13 12:35:33 GMT 2009 Luigi Rizzo <luigi@FreeBSD.org> Documentation-only change:
- add a reference to the config(5) manpage; - hopefully clarify the format of the 'env FILENAME' directive.
I am putting these notes in sys/${arch}/conf/GENERIC and not in sys/conf/NOTES because:
1. i386/GENERIC already had reference to a similar option (hints..) and to documentation (handbook)
2. GENERIC is what most users look at when they have to modify or create a new kernel config, so having the suggestion there is more effective.
I am only touching i386 and amd64 because the other GENERIC files are already out of sync, and I am not sure what is the overall plan.
MFC after: 3 days
|