I patched vlan to work with VLAN for linux and kfreebsd now.
While I have no idea whether we should load 8021q module manually.
I seems that 8021q module is not included in d-i (Linux).
Thanks for Aron Xu to write the templates.
--
YunQiang Su
vlan.diff
Description: Binary data
Hello,
On Mon, Feb 1, 2010 at 7:57 PM, Marco d'Itri wrote:
> j...@raven.inka.de wrote:
>
>> 8021q.ko 32328 bytes
>> garp.ko 13460 bytes
>> stp.ko 4456 bytes
>
> I still do not think that garp.ko and stp.ko are useful in d-i.
The problem is not usability but dependency:
ota...@neumann:
j...@raven.inka.de wrote:
> 8021q.ko 32328 bytes
> garp.ko 13460 bytes
> stp.ko4456 bytes
I still do not think that garp.ko and stp.ko are useful in d-i.
--
ciao,
Marco
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
Hello,
On Sat, Jan 30, 2010 at 11:22 AM, Josef Wolf wrote:
> On Sat, Jan 30, 2010 at 08:41:25PM +1100, Matthew Palmer wrote:
>>
>> At any rate, the size of the initrd isn't a download problem so much as an
>> installer memory footprint problem -- which isn't mitigated by using an
>> install CD.
>
On Sat, Jan 30, 2010 at 08:41:25PM +1100, Matthew Palmer wrote:
>
> At any rate, the size of the initrd isn't a download problem so much as an
> installer memory footprint problem -- which isn't mitigated by using an
> install CD.
> [ ... ]
> > > We usually don't do make such changes lightly.
> >
On Sat, Jan 30, 2010 at 09:48:38AM +0100, Josef Wolf wrote:
> On Sat, Jan 30, 2010 at 01:07:04AM +0100, Frans Pop wrote:
> > On Saturday 30 January 2010, Josef Wolf wrote:
> > > Would be just a change in a config option, right? So that's not really a
> > > big deal and could be done independently o
On Sat, Jan 30, 2010 at 01:07:04AM +0100, Frans Pop wrote:
> On Saturday 30 January 2010, Josef Wolf wrote:
> > This is why my original proposal was to decide from the value of
> > netcfg/chosen_interface whether to load/configure all the vlan stuff.
>
> So you would *always* show vlan interfaces,
On Sat, Jan 30, 2010 at 01:07:04AM +0100, Frans Pop wrote:
> On Saturday 30 January 2010, Josef Wolf wrote:
> > This is why my original proposal was to decide from the value of
> > netcfg/chosen_interface whether to load/configure all the vlan stuff.
>
> So you would *always* show vlan interfaces,
On Saturday 30 January 2010, Josef Wolf wrote:
> This is why my original proposal was to decide from the value of
> netcfg/chosen_interface whether to load/configure all the vlan stuff.
So you would *always* show vlan interfaces, even for regular users on
normal systems? I don't think I like that
On Fri, Jan 29, 2010 at 02:54:58PM +0100, Frans Pop wrote:
> On Friday 29 January 2010, Josef Wolf wrote:
> > But at that time the interface chosen interface is not known. So
> > deducing from chosen interface name (as outlined above) is not possible
> > and this method would only work with preseed
On Friday 29 January 2010, Josef Wolf wrote:
> But at that time the interface chosen interface is not known. So
> deducing from chosen interface name (as outlined above) is not possible
> and this method would only work with preseeding or if additional
> questions are asked.
No. The sequence shoul
On Friday 29 January 2010, Bastian Blank wrote:
> On Sun, Jan 17, 2010 at 09:35:47PM +0100, Josef Wolf wrote:
> > 2. Install vlan package into installer environment. Only the vconfig
> >binary (9kb) is really needed. But it needs libc6. Is this an
> > issue?
>
> Not needed:
> | config VCONFIG
>
On Fri, Jan 29, 2010 at 09:44:21AM +0100, Frans Pop wrote:
Thanks for your response, Frans!
> On Friday 29 January 2010, Josef Wolf wrote:
> > Since the interface name can be used to decide whether to activate vlan
> > support, no new debconf questions (like netcfg/enable_vlan or something)
> > a
On Sun, Jan 17, 2010 at 09:35:47PM +0100, Josef Wolf wrote:
> 2. Install vlan package into installer environment. Only the vconfig
>binary (9kb) is really needed. But it needs libc6. Is this an issue?
Not needed:
| config VCONFIG
| bool "vconfig"
| default n
| help
|
On Fri, Jan 29, 2010 at 01:25:42PM +0100, Josef Wolf wrote:
> On Fri, Jan 29, 2010 at 10:49:50AM +, Marco d'Itri wrote:
> > >The rest would be mostly straight forward: load stp, garp and 8021q
> > >modules,
> > Why do you believe that STP and GARP are needed for a network edge node?
> In most
On Fri, Jan 29, 2010 at 10:49:50AM +, Marco d'Itri wrote:
> j...@raven.inka.de wrote:
>
> >The rest would be mostly straight forward: load stp, garp and 8021q modules,
> Why do you believe that STP and GARP are needed for a network edge node?
In most cases, VLAN means _lots_ of interfaces, so
j...@raven.inka.de wrote:
>The rest would be mostly straight forward: load stp, garp and 8021q modules,
Why do you believe that STP and GARP are needed for a network edge node?
--
ciao,
Marco
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
On Friday 29 January 2010, Josef Wolf wrote:
> Since the interface name can be used to decide whether to activate vlan
> support, no new debconf questions (like netcfg/enable_vlan or something)
> are needed, IMHO.
Doesn't that already answer your question about the user interface? :-)
One request
On Sun, Jan 17, 2010 at 09:35:47PM +0100, Josef Wolf wrote:
> AFAICS, getting vlan support into the installer needs to be done in three
> steps:
>
> 1. Get 8021q kernel module into installer environment.
>
> 2. Install vlan package into installer environment. Only the vconfig
>binary (9kb) is
On Sat, Jan 09, 2010 at 01:37:50PM +0100, Ferenc Wagner wrote:
>
> I hacked VLAN support into the Sarge installer once upon a time. It
> wasn't a big deal, like adding the vconfig binary and extending netcfg
> here and there a little bit. The problem is that you can't just
> download it like the
20 matches
Mail list logo
