* Thomas Neumann [20091122 15:45]:
> > * bootoption ethdevice: use specified network device for network booting
> > (PXE) instead of default (being eth0). Feature contributed by Helge
> > Wagner. Usage example: ethdevice=eth1
> [...]
> > I think about adding a newer live-initramfs package to the
Moins,
just for clarification:
"network NFS DHCP boot fails on multiple NIC machine"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/182940
"initramfs-tools: Network configuration can't work with multiple
interfaces"
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467078
Regar
On Mon, Nov 23, 2009 at 03:22:30PM +0100, Michael Goetze wrote:
> Toomas Tamm wrote:
> > On Sun, Nov 22, 2009 at 01:38:16PM +0100, Thomas Lange wrote:
> >
> >> * bootoption ethdevice: use specified network device for network booting
> >> (PXE) instead of default (being eth0). Feature contributed b
Toomas Tamm wrote:
> On Sun, Nov 22, 2009 at 01:38:16PM +0100, Thomas Lange wrote:
>
>> * bootoption ethdevice: use specified network device for network booting
>> (PXE) instead of default (being eth0). Feature contributed by Helge
>> Wagner. Usage example: ethdevice=eth1
>
> Does anyone know/rem
On Sun, Nov 22, 2009 at 01:38:16PM +0100, Thomas Lange wrote:
> * bootoption ethdevice: use specified network device for network booting
> (PXE) instead of default (being eth0). Feature contributed by Helge
> Wagner. Usage example: ethdevice=eth1
Does anyone know/remember, why the problem cannot
Le Mon, 23 Nov 2009 10:11:25 +0100,
Thomas Lange a écrit :
> > On Mon, 23 Nov 2009 10:05:47 +0100, Frédéric Boiteux
> > said:
>
> > has a cable plugged, to run ipconfig on this one. I can give it
> > if someone is interested?
> Yes, please post it here on this list, and alo give
> On Mon, 23 Nov 2009 10:05:47 +0100, Frédéric Boiteux
> said:
> has a cable plugged, to run ipconfig on this one. I can give it if
> someone is interested?
Yes, please post it here on this list, and alo give it to the
live-initramfs (the project is called debian live) guys.
--
Le Sun, 22 Nov 2009 13:38:16 +0100,
Thomas Lange a écrit :
> In the past, several people had problems booting a host with multiple
> network cards. IIRC Dell hardware often had this problem.
> In newer versions of live-initramfs a new bootoption is available.
>
> * bootoption ethdevice: use spec
Good Morning,
On Sun, 22 Nov 2009 13:38:16 +0100
Thomas Lange wrote:
> In the past, several people had problems booting a host with multiple
> network cards. IIRC Dell hardware often had this problem.
> In newer versions of live-initramfs a new bootoption is available.
>
> * bootoption ethdevi
hiya
>> Currently interface are assigned as follows:
[...]
>> Who knows how long this is going to stay this way? Next kernelrelease?
>> Next hardware revision?
> Forever?
... or possibly just until I decide to put in a new network card,
shuffling around the order of enumeration during the next i
> Sorry for the self-followup, I forgot something
>
> > I don't care which interface is configured, as long as a usable interface
> > is configured. (If there's no dhcp on this network then it's not "usable"
> > - at least for mounting the nfs shares.)
>
> I have servers with up to 8 network inte
On Sun, Nov 22, 2009 at 03:33:37PM +0100, Thomas Lange wrote:
> > On Sun, 22 Nov 2009 15:21:07 +0100, Henning Glawe
> > said:
> > I think that there would be still the problem of interface
> names/enumeration
> > of the network devices. Is there any way to detect which interface
Sorry for the self-followup, I forgot something
> I don't care which interface is configured, as long as a usable interface
> is configured. (If there's no dhcp on this network then it's not "usable"
> - at least for mounting the nfs shares.)
I have servers with up to 8 network interfaces (2 quad
hiya
> The kernel itself does not know anything about were it was loaded
> from. It even does not know if it was loaded from network or disk or
> whatever device.
Could this be of any use? At least it doesn't work out of the box. I was
hoping that the kernel detects that the / a interface is stil
hiya
> * bootoption ethdevice: use specified network device for network booting
> (PXE) instead of default (being eth0). Feature contributed by Helge
> Wagner. Usage example: ethdevice=eth1
[...]
> I think about adding a newer live-initramfs package to the FAI
> repository, so you will automatical
> On Sun, 22 Nov 2009 15:21:07 +0100, Henning Glawe
> said:
> On Sun, Nov 22, 2009 at 01:38:16PM +0100, Thomas Lange wrote:
>> * bootoption ethdevice: use specified network device for network booting
>> (PXE) instead of default (being eth0). Feature contributed by Helge
>
On Sun, Nov 22, 2009 at 01:38:16PM +0100, Thomas Lange wrote:
> * bootoption ethdevice: use specified network device for network booting
> (PXE) instead of default (being eth0). Feature contributed by Helge
> Wagner. Usage example: ethdevice=eth1
I think that there would be still the problem of in
In the past, several people had problems booting a host with multiple
network cards. IIRC Dell hardware often had this problem.
In newer versions of live-initramfs a new bootoption is available.
* bootoption ethdevice: use specified network device for network booting
(PXE) instead of default (bein
18 matches
Mail list logo
