| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 23/01/13 05:21 PM, Pacho Ramos wrote: |
| 5 |
> El mié, 23-01-2013 a las 23:45 +0200, Samuli Suominen escribió: |
| 6 |
>> On 23/01/13 23:21, Pacho Ramos wrote: |
| 7 |
>>> El mié, 23-01-2013 a las 15:14 +0200, Samuli Suominen |
| 8 |
>>> escribió: |
| 9 |
>>>> please review this news item, seems we need one after all |
| 10 |
>>> |
| 11 |
>>> Why don't you drop "~" from: CONFIG_CHECK="~DEVTMPFS" |
| 12 |
>>> |
| 13 |
>>> to ensure people really changes it in their kernel and prevent |
| 14 |
>>> breakage? |
| 15 |
>>> |
| 16 |
>> |
| 17 |
>> That won't work because the host you run the package isn't |
| 18 |
>> necessarily same as the one you are building it on The build host |
| 19 |
>> doesn't need DEVTMPFS |
| 20 |
>> |
| 21 |
>> |
| 22 |
> |
| 23 |
> And couldn't that be done at install time? I mean, you can build |
| 24 |
> and package new udev but installation will die if udev is going to |
| 25 |
> be installed on a system without DEVTMPFS |
| 26 |
|
| 27 |
|
| 28 |
There's too many variables, though -- firstly, /usr/src/linux/.config |
| 29 |
may not match /proc/config.gz. And even if both are checked there's |
| 30 |
nothing to say that the next boot is going to use a kernel that |
| 31 |
matches either one. |
| 32 |
|
| 33 |
Realistically, what udev needs is something at runtime to report the |
| 34 |
error and temporarily bypass the requirement, because this really is a |
| 35 |
runtime issue instead of something that can be properly controlled or |
| 36 |
contained at build/install time. |
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
-----BEGIN PGP SIGNATURE----- |
| 41 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 42 |
|
| 43 |
iF4EAREIAAYFAlEBVgIACgkQ2ugaI38ACPBzfQD/ZAE4UHgQJ3zB9wuVkCcPAhXS |
| 44 |
21C+7k+mjS2YSg8BgqcA/0iv12JreFnvmybX2H8a/g8BBKm30+Xbt1+bGC+rijYN |
| 45 |
=qA5Y |
| 46 |
-----END PGP SIGNATURE----- |
Archives