Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | The following is a list of files and features that are going to be |
2 | removed in the kernel source tree. Every entry should contain what | |
3 | exactly is going away, why it is happening, and who is going to be doing | |
4 | the work. When the feature is removed from the kernel, it should also | |
5 | be removed from this file. | |
6 | ||
7 | --------------------------- | |
8 | ||
45a5c8ba DG |
9 | What: USER_SCHED |
10 | When: 2.6.34 | |
11 | ||
12 | Why: USER_SCHED was implemented as a proof of concept for group scheduling. | |
13 | The effect of USER_SCHED can already be achieved from userspace with | |
14 | the help of libcgroup. The removal of USER_SCHED will also simplify | |
15 | the scheduler code with the removal of one major ifdef. There are also | |
16 | issues USER_SCHED has with USER_NS. A decision was taken not to fix | |
17 | those and instead remove USER_SCHED. Also new group scheduling | |
18 | features will not be implemented for USER_SCHED. | |
19 | ||
20 | Who: Dhaval Giani <dhaval@linux.vnet.ibm.com> | |
21 | ||
22 | --------------------------- | |
23 | ||
4d8cd268 LR |
24 | What: PRISM54 |
25 | When: 2.6.34 | |
26 | ||
27 | Why: prism54 FullMAC PCI / Cardbus devices used to be supported only by the | |
28 | prism54 wireless driver. After Intersil stopped selling these | |
29 | devices in preference for the newer more flexible SoftMAC devices | |
30 | a SoftMAC device driver was required and prism54 did not support | |
31 | them. The p54pci driver now exists and has been present in the kernel for | |
32 | a while. This driver supports both SoftMAC devices and FullMAC devices. | |
33 | The main difference between these devices was the amount of memory which | |
34 | could be used for the firmware. The SoftMAC devices support a smaller | |
35 | amount of memory. Because of this the SoftMAC firmware fits into FullMAC | |
36 | devices's memory. p54pci supports not only PCI / Cardbus but also USB | |
37 | and SPI. Since p54pci supports all devices prism54 supports | |
38 | you will have a conflict. I'm not quite sure how distributions are | |
39 | handling this conflict right now. prism54 was kept around due to | |
40 | claims users may experience issues when using the SoftMAC driver. | |
41 | Time has passed users have not reported issues. If you use prism54 | |
42 | and for whatever reason you cannot use p54pci please let us know! | |
43 | E-mail us at: linux-wireless@vger.kernel.org | |
44 | ||
45 | For more information see the p54 wiki page: | |
46 | ||
47 | http://wireless.kernel.org/en/users/Drivers/p54 | |
48 | ||
49 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> | |
50 | ||
51 | --------------------------- | |
52 | ||
9d9b8fb0 RG |
53 | What: IRQF_SAMPLE_RANDOM |
54 | Check: IRQF_SAMPLE_RANDOM | |
55 | When: July 2009 | |
56 | ||
57 | Why: Many of IRQF_SAMPLE_RANDOM users are technically bogus as entropy | |
58 | sources in the kernel's current entropy model. To resolve this, every | |
59 | input point to the kernel's entropy pool needs to better document the | |
60 | type of entropy source it actually is. This will be replaced with | |
61 | additional add_*_randomness functions in drivers/char/random.c | |
62 | ||
63 | Who: Robin Getz <rgetz@blackfin.uclinux.org> & Matt Mackall <mpm@selenic.com> | |
64 | ||
65 | --------------------------- | |
66 | ||
6ee7d330 | 67 | What: The ieee80211_regdom module parameter |
8a5117d8 | 68 | When: March 2010 / desktop catchup |
6ee7d330 LR |
69 | |
70 | Why: This was inherited by the CONFIG_WIRELESS_OLD_REGULATORY code, | |
71 | and currently serves as an option for users to define an | |
72 | ISO / IEC 3166 alpha2 code for the country they are currently | |
73 | present in. Although there are userspace API replacements for this | |
74 | through nl80211 distributions haven't yet caught up with implementing | |
75 | decent alternatives through standard GUIs. Although available as an | |
76 | option through iw or wpa_supplicant its just a matter of time before | |
77 | distributions pick up good GUI options for this. The ideal solution | |
78 | would actually consist of intelligent designs which would do this for | |
79 | the user automatically even when travelling through different countries. | |
80 | Until then we leave this module parameter as a compromise. | |
81 | ||
82 | When userspace improves with reasonable widely-available alternatives for | |
83 | this we will no longer need this module parameter. This entry hopes that | |
84 | by the super-futuristically looking date of "March 2010" we will have | |
85 | such replacements widely available. | |
86 | ||
87 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> | |
88 | ||
89 | --------------------------- | |
90 | ||
8a5117d8 LR |
91 | What: CONFIG_WIRELESS_OLD_REGULATORY - old static regulatory information |
92 | When: March 2010 / desktop catchup | |
93 | ||
b2e1b302 LR |
94 | Why: The old regulatory infrastructure has been replaced with a new one |
95 | which does not require statically defined regulatory domains. We do | |
96 | not want to keep static regulatory domains in the kernel due to the | |
97 | the dynamic nature of regulatory law and localization. We kept around | |
98 | the old static definitions for the regulatory domains of: | |
8a5117d8 | 99 | |
b2e1b302 LR |
100 | * US |
101 | * JP | |
102 | * EU | |
8a5117d8 | 103 | |
b2e1b302 | 104 | and used by default the US when CONFIG_WIRELESS_OLD_REGULATORY was |
8a5117d8 LR |
105 | set. We will remove this option once the standard Linux desktop catches |
106 | up with the new userspace APIs we have implemented. | |
107 | ||
b2e1b302 LR |
108 | Who: Luis R. Rodriguez <lrodriguez@atheros.com> |
109 | ||
110 | --------------------------- | |
111 | ||
471d0558 | 112 | What: dev->power.power_state |
1ebfd79e PM |
113 | When: July 2007 |
114 | Why: Broken design for runtime control over driver power states, confusing | |
115 | driver-internal runtime power management with: mechanisms to support | |
116 | system-wide sleep state transitions; event codes that distinguish | |
117 | different phases of swsusp "sleep" transitions; and userspace policy | |
118 | inputs. This framework was never widely used, and most attempts to | |
119 | use it were broken. Drivers should instead be exposing domain-specific | |
120 | interfaces either to kernel or to userspace. | |
121 | Who: Pavel Machek <pavel@suse.cz> | |
122 | ||
123 | --------------------------- | |
124 | ||
42d12f5a MCC |
125 | What: Video4Linux API 1 ioctls and from Video devices. |
126 | When: July 2009 | |
127 | Files: include/linux/videodev.h | |
128 | Check: include/linux/videodev.h | |
11a5a10e | 129 | Why: V4L1 AP1 was replaced by V4L2 API during migration from 2.4 to 2.6 |
875c296b MCC |
130 | series. The old API have lots of drawbacks and don't provide enough |
131 | means to work with all video and audio standards. The newer API is | |
132 | already available on the main drivers and should be used instead. | |
133 | Newer drivers should use v4l_compat_translate_ioctl function to handle | |
134 | old calls, replacing to newer ones. | |
135 | Decoder iocts are using internally to allow video drivers to | |
136 | communicate with video decoders. This should also be improved to allow | |
137 | V4L2 calls being translated into compatible internal ioctls. | |
11a5a10e MCC |
138 | Compatibility ioctls will be provided, for a while, via |
139 | v4l1-compat module. | |
140 | Who: Mauro Carvalho Chehab <mchehab@infradead.org> | |
875c296b MCC |
141 | |
142 | --------------------------- | |
143 | ||
bf45d9b0 DB |
144 | What: PCMCIA control ioctl (needed for pcmcia-cs [cardmgr, cardctl]) |
145 | When: November 2005 | |
146 | Files: drivers/pcmcia/: pcmcia_ioctl.c | |
147 | Why: With the 16-bit PCMCIA subsystem now behaving (almost) like a | |
148 | normal hotpluggable bus, and with it using the default kernel | |
149 | infrastructure (hotplug, driver core, sysfs) keeping the PCMCIA | |
150 | control ioctl needed by cardmgr and cardctl from pcmcia-cs is | |
151 | unnecessary, and makes further cleanups and integration of the | |
152 | PCMCIA subsystem into the Linux kernel device driver model more | |
153 | difficult. The features provided by cardmgr and cardctl are either | |
154 | handled by the kernel itself now or are available in the new | |
155 | pcmciautils package available at | |
156 | http://kernel.org/pub/linux/utils/kernel/pcmcia/ | |
157 | Who: Dominik Brodowski <linux@brodo.de> | |
7af4cc3f HW |
158 | |
159 | --------------------------- | |
160 | ||
7058cb02 EB |
161 | What: sys_sysctl |
162 | When: September 2010 | |
163 | Option: CONFIG_SYSCTL_SYSCALL | |
164 | Why: The same information is available in a more convenient from | |
165 | /proc/sys, and none of the sysctl variables appear to be | |
166 | important performance wise. | |
167 | ||
168 | Binary sysctls are a long standing source of subtle kernel | |
169 | bugs and security issues. | |
170 | ||
171 | When I looked several months ago all I could find after | |
172 | searching several distributions were 5 user space programs and | |
173 | glibc (which falls back to /proc/sys) using this syscall. | |
174 | ||
175 | The man page for sysctl(2) documents it as unusable for user | |
176 | space programs. | |
177 | ||
178 | sysctl(2) is not generally ABI compatible to a 32bit user | |
179 | space application on a 64bit and a 32bit kernel. | |
180 | ||
181 | For the last several months the policy has been no new binary | |
182 | sysctls and no one has put forward an argument to use them. | |
183 | ||
184 | Binary sysctls issues seem to keep happening appearing so | |
185 | properly deprecating them (with a warning to user space) and a | |
186 | 2 year grace warning period will mean eventually we can kill | |
187 | them and end the pain. | |
188 | ||
189 | In the mean time individual binary sysctls can be dealt with | |
190 | in a piecewise fashion. | |
191 | ||
192 | Who: Eric Biederman <ebiederm@xmission.com> | |
193 | ||
194 | --------------------------- | |
195 | ||
ac515898 CH |
196 | What: remove EXPORT_SYMBOL(kernel_thread) |
197 | When: August 2006 | |
198 | Files: arch/*/kernel/*_ksyms.c | |
f0a594c1 | 199 | Check: kernel_thread |
ac515898 CH |
200 | Why: kernel_thread is a low-level implementation detail. Drivers should |
201 | use the <linux/kthread.h> API instead which shields them from | |
202 | implementation details and provides a higherlevel interface that | |
203 | prevents bugs and code duplication | |
204 | Who: Christoph Hellwig <hch@lst.de> | |
205 | ||
206 | --------------------------- | |
207 | ||
f71d20e9 AV |
208 | What: Unused EXPORT_SYMBOL/EXPORT_SYMBOL_GPL exports |
209 | (temporary transition config option provided until then) | |
210 | The transition config option will also be removed at the same time. | |
211 | When: before 2.6.19 | |
212 | Why: Unused symbols are both increasing the size of the kernel binary | |
213 | and are often a sign of "wrong API" | |
214 | Who: Arjan van de Ven <arjan@linux.intel.com> | |
215 | ||
216 | --------------------------- | |
217 | ||
d81d9d6b | 218 | What: PHYSDEVPATH, PHYSDEVBUS, PHYSDEVDRIVER in the uevent environment |
acbd39fb | 219 | When: October 2008 |
d81d9d6b KS |
220 | Why: The stacking of class devices makes these values misleading and |
221 | inconsistent. | |
222 | Class devices should not carry any of these properties, and bus | |
223 | devices have SUBSYTEM and DRIVER as a replacement. | |
224 | Who: Kay Sievers <kay.sievers@suse.de> | |
225 | ||
226 | --------------------------- | |
6c805d2c | 227 | |
b981c591 | 228 | What: ACPI procfs interface |
8b8eb7d8 ZR |
229 | When: July 2008 |
230 | Why: ACPI sysfs conversion should be finished by January 2008. | |
231 | ACPI procfs interface will be removed in July 2008 so that | |
232 | there is enough time for the user space to catch up. | |
b981c591 ZR |
233 | Who: Zhang Rui <rui.zhang@intel.com> |
234 | ||
235 | --------------------------- | |
236 | ||
1bb67c25 LB |
237 | What: /proc/acpi/button |
238 | When: August 2007 | |
239 | Why: /proc/acpi/button has been replaced by events to the input layer | |
240 | since 2.6.20. | |
241 | Who: Len Brown <len.brown@intel.com> | |
242 | ||
243 | --------------------------- | |
54b290a2 | 244 | |
14e04fb3 LB |
245 | What: /proc/acpi/event |
246 | When: February 2008 | |
247 | Why: /proc/acpi/event has been replaced by events via the input layer | |
248 | and netlink since 2.6.23. | |
249 | Who: Len Brown <len.brown@intel.com> | |
250 | ||
251 | --------------------------- | |
252 | ||
914d97fd | 253 | What: i386/x86_64 bzImage symlinks |
19b4e7f4 | 254 | When: April 2010 |
914d97fd TG |
255 | |
256 | Why: The i386/x86_64 merge provides a symlink to the old bzImage | |
257 | location so not yet updated user space tools, e.g. package | |
258 | scripts, do not break. | |
259 | Who: Thomas Gleixner <tglx@linutronix.de> | |
038a5008 LT |
260 | |
261 | --------------------------- | |
262 | ||
f9ef8a23 | 263 | What (Why): |
079aa88f JE |
264 | - xt_recent: the old ipt_recent proc dir |
265 | (superseded by /proc/net/xt_recent) | |
266 | ||
f9ef8a23 JE |
267 | When: January 2009 or Linux 2.7.0, whichever comes first |
268 | Why: Superseded by newer revisions or modules | |
269 | Who: Jan Engelhardt <jengelh@computergmbh.de> | |
eb189d8b MB |
270 | |
271 | --------------------------- | |
272 | ||
8a0cecff DB |
273 | What: GPIO autorequest on gpio_direction_{input,output}() in gpiolib |
274 | When: February 2010 | |
275 | Why: All callers should use explicit gpio_request()/gpio_free(). | |
276 | The autorequest mechanism in gpiolib was provided mostly as a | |
277 | migration aid for legacy GPIO interfaces (for SOC based GPIOs). | |
278 | Those users have now largely migrated. Platforms implementing | |
279 | the GPIO interfaces without using gpiolib will see no changes. | |
280 | Who: David Brownell <dbrownell@users.sourceforge.net> | |
281 | --------------------------- | |
282 | ||
eb189d8b | 283 | What: b43 support for firmware revision < 410 |
c557289c MB |
284 | When: The schedule was July 2008, but it was decided that we are going to keep the |
285 | code as long as there are no major maintanance headaches. | |
286 | So it _could_ be removed _any_ time now, if it conflicts with something new. | |
eb189d8b MB |
287 | Why: The support code for the old firmware hurts code readability/maintainability |
288 | and slightly hurts runtime performance. Bugfixes for the old firmware | |
289 | are not provided by Broadcom anymore. | |
290 | Who: Michael Buesch <mb@bu3sch.de> | |
e88bb415 DM |
291 | |
292 | --------------------------- | |
293 | ||
fae9a0d8 GC |
294 | What: usedac i386 kernel parameter |
295 | When: 2.6.27 | |
296 | Why: replaced by allowdac and no dac combination | |
297 | Who: Glauber Costa <gcosta@redhat.com> | |
298 | ||
52f7c21b MF |
299 | --------------------------- |
300 | ||
c80cfb04 BH |
301 | What: print_fn_descriptor_symbol() |
302 | When: October 2009 | |
303 | Why: The %pF vsprintf format provides the same functionality in a | |
304 | simpler way. print_fn_descriptor_symbol() is deprecated but | |
305 | still present to give out-of-tree modules time to change. | |
306 | Who: Bjorn Helgaas <bjorn.helgaas@hp.com> | |
307 | ||
308 | --------------------------- | |
309 | ||
52f7c21b MF |
310 | What: /sys/o2cb symlink |
311 | When: January 2010 | |
312 | Why: /sys/fs/o2cb is the proper location for this information - /sys/o2cb | |
313 | exists as a symlink for backwards compatibility for old versions of | |
314 | ocfs2-tools. 2 years should be sufficient time to phase in new versions | |
315 | which know to look in /sys/fs/o2cb. | |
316 | Who: ocfs2-devel@oss.oracle.com | |
d2f5e808 MW |
317 | |
318 | --------------------------- | |
319 | ||
2584e517 RT |
320 | What: Ability for non root users to shm_get hugetlb pages based on mlock |
321 | resource limits | |
322 | When: 2.6.31 | |
323 | Why: Non root users need to be part of /proc/sys/vm/hugetlb_shm_group or | |
324 | have CAP_IPC_LOCK to be able to allocate shm segments backed by | |
325 | huge pages. The mlock based rlimit check to allow shm hugetlb is | |
326 | inconsistent with mmap based allocations. Hence it is being | |
327 | deprecated. | |
328 | Who: Ravikiran Thirumalai <kiran@scalex86.org> | |
329 | ||
330 | --------------------------- | |
331 | ||
16d75239 RH |
332 | What: CONFIG_THERMAL_HWMON |
333 | When: January 2009 | |
334 | Why: This option was introduced just to allow older lm-sensors userspace | |
335 | to keep working over the upgrade to 2.6.26. At the scheduled time of | |
336 | removal fixed lm-sensors (2.x or 3.x) should be readily available. | |
337 | Who: Rene Herman <rene.herman@gmail.com> | |
22bb1be4 JB |
338 | |
339 | --------------------------- | |
340 | ||
341 | What: Code that is now under CONFIG_WIRELESS_EXT_SYSFS | |
342 | (in net/core/net-sysfs.c) | |
343 | When: After the only user (hal) has seen a release with the patches | |
344 | for enough time, probably some time in 2010. | |
345 | Why: Over 1K .text/.data size reduction, data is available in other | |
346 | ways (ioctls) | |
347 | Who: Johannes Berg <johannes@sipsolutions.net> | |
58401572 KPO |
348 | |
349 | --------------------------- | |
350 | ||
351 | What: CONFIG_NF_CT_ACCT | |
352 | When: 2.6.29 | |
353 | Why: Accounting can now be enabled/disabled without kernel recompilation. | |
354 | Currently used only to set a default value for a feature that is also | |
355 | controlled by a kernel/module/sysfs/sysctl parameter. | |
356 | Who: Krzysztof Piotr Oledzki <ole@ans.pl> | |
357 | ||
46dfa040 FT |
358 | --------------------------- |
359 | ||
753b7aea DJ |
360 | What: sysfs ui for changing p4-clockmod parameters |
361 | When: September 2009 | |
362 | Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and | |
363 | e088e4c9cdb618675874becb91b2fd581ee707e6. | |
364 | Removal is subject to fixing any remaining bugs in ACPI which may | |
365 | cause the thermal throttling not to happen at the right time. | |
366 | Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com> | |
0e57aa11 TG |
367 | |
368 | ----------------------------- | |
369 | ||
370 | What: __do_IRQ all in one fits nothing interrupt handler | |
371 | When: 2.6.32 | |
372 | Why: __do_IRQ was kept for easy migration to the type flow handlers. | |
373 | More than two years of migration time is enough. | |
374 | Who: Thomas Gleixner <tglx@linutronix.de> | |
cb065c06 TG |
375 | |
376 | ----------------------------- | |
377 | ||
f110ca48 AC |
378 | What: fakephp and associated sysfs files in /sys/bus/pci/slots/ |
379 | When: 2011 | |
380 | Why: In 2.6.27, the semantics of /sys/bus/pci/slots was redefined to | |
381 | represent a machine's physical PCI slots. The change in semantics | |
382 | had userspace implications, as the hotplug core no longer allowed | |
383 | drivers to create multiple sysfs files per physical slot (required | |
384 | for multi-function devices, e.g.). fakephp was seen as a developer's | |
385 | tool only, and its interface changed. Too late, we learned that | |
386 | there were some users of the fakephp interface. | |
387 | ||
388 | In 2.6.30, the original fakephp interface was restored. At the same | |
389 | time, the PCI core gained the ability that fakephp provided, namely | |
390 | function-level hot-remove and hot-add. | |
391 | ||
392 | Since the PCI core now provides the same functionality, exposed in: | |
393 | ||
394 | /sys/bus/pci/rescan | |
395 | /sys/bus/pci/devices/.../remove | |
396 | /sys/bus/pci/devices/.../rescan | |
397 | ||
398 | there is no functional reason to maintain fakephp as well. | |
399 | ||
400 | We will keep the existing module so that 'modprobe fakephp' will | |
401 | present the old /sys/bus/pci/slots/... interface for compatibility, | |
402 | but users are urged to migrate their applications to the API above. | |
403 | ||
404 | After a reasonable transition period, we will remove the legacy | |
405 | fakephp interface. | |
406 | Who: Alex Chiang <achiang@hp.com> | |
3f307fb3 JD |
407 | |
408 | --------------------------- | |
409 | ||
c64fb016 JB |
410 | What: CONFIG_RFKILL_INPUT |
411 | When: 2.6.33 | |
412 | Why: Should be implemented in userspace, policy daemon. | |
413 | Who: Johannes Berg <johannes@sipsolutions.net> | |
9cbc1cb8 | 414 | |
cdc321ff EP |
415 | --------------------------- |
416 | ||
417 | What: CONFIG_INOTIFY | |
418 | When: 2.6.33 | |
419 | Why: last user (audit) will be converted to the newer more generic | |
420 | and more easily maintained fsnotify subsystem | |
421 | Who: Eric Paris <eparis@redhat.com> | |
422 | ||
45f458e9 AK |
423 | ---------------------------- |
424 | ||
37c90e88 | 425 | What: lock_policy_rwsem_* and unlock_policy_rwsem_* will not be |
426 | exported interface anymore. | |
427 | When: 2.6.33 | |
428 | Why: cpu_policy_rwsem has a new cleaner definition making it local to | |
429 | cpufreq core and contained inside cpufreq.c. Other dependent | |
430 | drivers should not use it in order to safely avoid lockdep issues. | |
431 | Who: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> | |
93fe4483 TH |
432 | |
433 | ---------------------------- | |
434 | ||
435 | What: sound-slot/service-* module aliases and related clutters in | |
436 | sound/sound_core.c | |
437 | When: August 2010 | |
438 | Why: OSS sound_core grabs all legacy minors (0-255) of SOUND_MAJOR | |
439 | (14) and requests modules using custom sound-slot/service-* | |
440 | module aliases. The only benefit of doing this is allowing | |
441 | use of custom module aliases which might as well be considered | |
442 | a bug at this point. This preemptive claiming prevents | |
443 | alternative OSS implementations. | |
444 | ||
445 | Till the feature is removed, the kernel will be requesting | |
446 | both sound-slot/service-* and the standard char-major-* module | |
447 | aliases and allow turning off the pre-claiming selectively via | |
448 | CONFIG_SOUND_OSS_CORE_PRECLAIM and soundcore.preclaim_oss | |
449 | kernel parameter. | |
450 | ||
451 | After the transition phase is complete, both the custom module | |
452 | aliases and switches to disable it will go away. This removal | |
453 | will also allow making ALSA OSS emulation independent of | |
454 | sound_core. The dependency will be broken then too. | |
455 | Who: Tejun Heo <tj@kernel.org> | |
d0153ca3 AK |
456 | |
457 | ---------------------------- | |
458 | ||
459 | What: Support for VMware's guest paravirtuliazation technique [VMI] will be | |
460 | dropped. | |
461 | When: 2.6.37 or earlier. | |
462 | Why: With the recent innovations in CPU hardware acceleration technologies | |
463 | from Intel and AMD, VMware ran a few experiments to compare these | |
464 | techniques to guest paravirtualization technique on VMware's platform. | |
465 | These hardware assisted virtualization techniques have outperformed the | |
466 | performance benefits provided by VMI in most of the workloads. VMware | |
467 | expects that these hardware features will be ubiquitous in a couple of | |
468 | years, as a result, VMware has started a phased retirement of this | |
469 | feature from the hypervisor. We will be removing this feature from the | |
470 | Kernel too. Right now we are targeting 2.6.37 but can retire earlier if | |
471 | technical reasons (read opportunity to remove major chunk of pvops) | |
472 | arise. | |
473 | ||
474 | Please note that VMI has always been an optimization and non-VMI kernels | |
475 | still work fine on VMware's platform. | |
476 | Latest versions of VMware's product which support VMI are, | |
477 | Workstation 7.0 and VSphere 4.0 on ESX side, future maintainence | |
478 | releases for these products will continue supporting VMI. | |
479 | ||
480 | For more details about VMI retirement take a look at this, | |
481 | http://blogs.vmware.com/guestosguide/2009/09/vmi-retirement.html | |
482 | ||
483 | Who: Alok N Kataria <akataria@vmware.com> | |
484 | ||
485 | ---------------------------- |