| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] RFC: Merge ip and root information just into kernel arguments |
| From: | Jeremy Katz <katzj@xxxxxxxxxx> |
| Date: | 2006年5月03日 15:21:59 -0400 |
| Delivery-date: | 2006年5月03日 12:22:24 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
As it currently stands, there are separate domain config options for things such as ip, gateway, root device, nfsroot, etc. All of these then end up getting put together and just put as arguments to the kernel command line for Linux guests. Is there a convincing reason to keep these separate or should they be deprecated and just included as part of the kernel argument string? Jeremy _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] [PATCH] Merge bootloader generated config with domain config , Jeremy Katz |
|---|---|
| Next by Date: | RE: [Xen-devel] xm-test results , Krysan, Susan |
| Previous by Thread: | [Xen-devel] [PATCH] Merge bootloader generated config with domain config , Jeremy Katz |
| Next by Thread: | RE: [Xen-devel] xm-test results , Krysan, Susan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |