On 2021-12-13, David Wright wrote:
> Having just swatted away this bug while installing bullseye
> on a laptop that has 1xUSB3, 2xUSB-C and no ethernet, I thought
> I should share the workaround here. This is only necessary,
> I'm led to believe, when installing by WiFi without the
> installation o
Bună seara, vă rog să mă sunați acum sau să răspundeți la mailul pe care vi
l-am trimis de ieri.
Having just swatted away this bug while installing bullseye
on a laptop that has 1xUSB3, 2xUSB-C and no ethernet, I thought
I should share the workaround here. This is only necessary,
I'm led to believe, when installing by WiFi without the
installation of a Desktop.
Before tearing down the WiFi in
On Tue 06 Mar 2018 at 11:07:59 +1100, Trent W. Buck wrote:
> Brian Potkin wrote:
> > The number of users affected by this issue over the years is not
> > insignificant. Not a single one has written in support of the
> > situation.
>
> This issue has bitten me at least twice so far.
>
> This issu
On Tue 06 Mar 2018 at 18:34:27 +, Ian Jackson wrote:
> bw writes ("Re: (solved) Re: wireless fail after stretch installation"):
> > I think the idea needs to be talked over a little better, because using
> > e/n/i for wireless by default after first boot has implications if the
> > user (who
bw writes ("Re: (solved) Re: wireless fail after stretch installation"):
> I think the idea needs to be talked over a little better, because using
> e/n/i for wireless by default after first boot has implications if the
> user (who is clueless) later installs a desktop environment.
If installing
Brian Potkin wrote:
> The number of users affected by this issue over the years is not
> insignificant. Not a single one has written in support of the
> situation.
This issue has bitten me at least twice so far.
This issue's history seems to be bogged down on whether interfaces(5) can be
mode 06
On Fri 23 Nov 2012 at 14:31:20 +, Brian Potkin wrote:
> I installed in expert mode over a wireless link from
>
> Debian GNU/Linux testing "Wheezy" - Official Snapshot i386 NETINST Binary-1
> 20121122-21:21
>
> This ISO has netcfg_1.102. Only "Standard system utilities" was selected
> as a t
I bumped into this issue when I recently installed Debian on my new laptop.
I only installed the "Standard system utilities", thus no network-manager and
while wpasupplicant was installed the wireless connection config I used during
installation wasn't written to a/the wpa_supplicant.conf file a
On Sun, Nov 25, 2012 at 05:30:28PM +0200, Sorina - Gabriela Sandu wrote:
> For most cases, I think not adding configuration for wireless in
> /e/n/i is good, however for the kind a situations you described I
> think the best solution would be to have the question asked, at least
> with a low priori
Hello,
On Sun, Nov 25, 2012 at 9:59 PM, Brian Potkin wrote:
> On Sun 25 Nov 2012 at 17:30:28 +0200, Sorina - Gabriela Sandu wrote:
>
> Hello Sorina.
>
>> For most cases, I think not adding configuration for wireless in
>> /e/n/i is good, however for the kind a situations you described I
>> think
On Sun 25 Nov 2012 at 17:30:28 +0200, Sorina - Gabriela Sandu wrote:
Hello Sorina.
> For most cases, I think not adding configuration for wireless in
> /e/n/i is good, however for the kind a situations you described I
> think the best solution would be to have the question asked, at least
> with
Hello,
On Fri, Nov 23, 2012 at 4:31 PM, Brian Potkin wrote:
> Package: netcfg
> Version: 1.102
> Severity: important
> Tags: d-i
>
>
>
> I installed in expert mode over a wireless link from
>
> Debian GNU/Linux testing "Wheezy" - Official Snapshot i386 NETINST Binary-1
> 20121122-21:21
>
> This
Package: netcfg
Version: 1.102
Severity: important
Tags: d-i
I installed in expert mode over a wireless link from
Debian GNU/Linux testing "Wheezy" - Official Snapshot i386 NETINST Binary-1
20121122-21:21
This ISO has netcfg_1.102. Only "Standard system utilities" was selected
as a task. Re-b
14 matches
Mail list logo
