Hi adrian15,
On 18.08.2015 10:47, adrian15 wrote:
> Can you please explain why you are using: get_fstype () function which it's
> based
> on blkid instead of just using the old method of relying in auto function
> from the kernel itself?
The reason is simply that 'mount -tauto' didn't work, whi
Hi,
On 08.03.2014 02:13, Cyril Brulebois wrote:
Given the apt-cdrom regression we're hitting (#740673), I don't feel
like shipping this amount of additional modifications in jessie alpha 1
images;
Given that Bug #740673 is fixed and jessie alpha 1 is released, can you
review and upload these
On 19.03.2014 14:52, Cyril Brulebois wrote:
If you're getting a translated version of the website, and if the
translation for this page has not been updated for the announce yet,
you're likely getting a “Note: the original document is more recent than
this translation” in that language at the top
Package: debian-installer
Severity: normal
Dear Maintainer,
It is not possible to install GNOME with jessie alpha 1 netinst [1]:
Advanced options->Alternative desktop environments->GNOME is empty
except for the 'Back' option.
Please fix this.
Best regards,
Andreas
1:
http://cdimage.debian.
On 19.03.2014 14:42, Steve McIntyre wrote:
Sorry, I hadn't realised until just now. You're not looking at the
jessie alpha 1 release directory (from Tuesday), you're looking at the
last weekly build (from Monday). You need to see:
http://cdimage.debian.org/cdimage/jessie_di_alpha_1/
OK?
Th
On 19.03.2014 14:02, Steve McIntyre wrote:
On Wed, Mar 19, 2014 at 01:56:16PM +0100, Andreas Cadhalpun wrote:
* There is no installation image for GNOME on [1], but the Xfce
image is still there (and for some reason is 4MB smaller than the
default).
debian-jessie-DI-a1-amd64-gnome-CD-1.iso
Hi,
On 19.03.2014 02:42, Cyril Brulebois wrote:
Behavorial changes in this release
==
* Xfce is the default desktop environment for the time being. Quoting
tasksel's changelog: "this will be re-evaluated in August 2014, and
may change again before Jessi
olger Wansing wrote:
Andreas Cadhalpun wrote:
It works with the wheezy 7.1 CD.
Maybe it has to do with mtdev? The following line is in the jessie
Xorg.0.log, but not in the wheezy one.
evdev: SynPS/2 Synaptics TouchPad: Using mtdev for this device
Also the 'Found absolute multitouch axes'
Hi,
On 11.03.2014 21:03, Holger Wansing wrote:
So it's hardware specific?
It seems so.
I remember there are ones working in absolute mode and others with
relative mode? (or similar, just typed from mind)
From my /var/log/messages:
-snip -
synaptics: Touchpad model: 1, fw: 6.2, id:
Hi,
On 11.03.2014 02:03, Cyril Brulebois wrote:
It would be nice to know how it goes with a 3.13-based installation
image. (No need to test the whole installation, just trying to
figure out if there's still something that needs fixing.)
Daily d-i builds or upcoming jessie alpha 1 images should
Hi,
On 08.03.2014 19:04, Cyril Brulebois wrote:
Andreas Cadhalpun (2014-03-08):
I generally agree that it would be good to have an alpha 1 installer
to use for testing regressions of this patch, but on the other hand
using loopmount to install Debian *works*.
Sorry, but until it's
Hi,
On 08.03.2014 02:13, Cyril Brulebois wrote:
Given the apt-cdrom regression we're hitting (#740673), I don't feel
like shipping this amount of additional modifications in jessie alpha 1
images; on the other hand, not uploading what's in apt-setup's master
currently would mean not using update
Hi Steve,
On 11.02.2014 02:01, Steve McIntyre wrote:
Gah...
Just ended up playing with Colin's thinkpad; he'd reported problems
with installation that sounded odd. Worked through it, and found a
hole in what we recognise and support during installation (and maybe
later).
We have a machine with
On 12.02.2014 12:07, Andrew Louis wrote:
yes the old installation exists, it shows on the grub menu. i wasnt
anticipating an answer, sorry for my delayed response. i installed it on
the same partition, yes. The older setup does not open up. it gets stuck
at a login screen where the display goes b
Hi,
On 08.02.2014 19:19, andrewlouis6511 wrote:
* What led up to the situation?
My previous version encountered some problems during installing commodo
firewall and debian wouldnt start up. So i did a fresh install but couldnt
remove the previous installation from the GRUB menu.
* What e
Hi,
On 02.02.2014 02:32, Steven Chamberlain wrote:
The bug wasn't closed by spam, but by Ben Hutchings who said:
That was the first time it got closed, but the second time it was
definitely spam, unless Ben Hutchings changed his mail to:
"UNITED NATIONS"
Best regards,
Andreas
--
To UNSUBS
Control: reopen -1
Hi,
spam should not close bugs, thus I'm reopening this one.
Best regards,
Andreas
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52ecf807.8020..
Control: reassign -1 src:linux
Control: forcemerge 725714 -1
Hi,
On 28.01.2014 20:15, ano...@users.sourceforge.net wrote:
Preparing to install Debian on my new T430, which has an e1000e on eth0
and an Intel Centrino Advanced-N 6205 (supported with iwlwifi and
non-free firmware) as wlan0.
I for
Hi Josh,
On 22.01.2014 17:50, Josh Triplett wrote:
Odd. Please report a bug in the fd.o bugzilla on the i915 driver.
This seems to be already reported [1], as i915.disable_power_well=0
stops the errors (but there is still mode change).
I tried:
sudo journalctl -F BOOTCHART
This gave no ou
Hi Harri,
thanks for your installation report.
On 21.01.2014 11:13, Harri Kiiskinen wrote:
Problems:
- Network card: did not install drivers for wifi card, for iwlwifi-firmware was
not on netinst cd. Wired connection worked ok.
This firmware is not on the netinst CD, because it is non-free
On 22.01.2014 03:05, Josh Triplett wrote:
On Wed, Jan 22, 2014 at 02:53:51AM +0100, Andreas Cadhalpun wrote:
Why do you think it would be bad to enable 'splash' by default?
Because then the splash screen would show up. :)
See my previous mails in this thread; I would like to avoi
Hi Josh,
On 22.01.2014 01:30, j...@joshtriplett.org wrote:
On Wed, Jan 22, 2014 at 12:53:05AM +0100, Andreas Cadhalpun wrote:
So you agree that it is easy enough to manually remove the 'splash'
boot option if you don't like it (assuming it was enabled by
default)?
I don'
Hi Joey,
On 20.01.2014 16:28, Joey Hess wrote:
Josh Triplett wrote:
If the goal here is to hide the boot messages by default, note that
the default kernel command line includes "quiet", which hides most
kernel messages and systemd messages.
Note that the hiding of systemd messages is unintent
add a trigger if no boot loader is
installed yet...
But the installer could add the 'splash' boot option, when installing
the boot loader.
> On Tue, Jan 21, 2014 at 07:43:41PM +0100, Andreas Cadhalpun wrote:
>> On 21.01.2014 03:35, Josh Triplett wrote:
On current systems, there'
ns I wanted to compare the whole boot time with/without
plymouth, but unfortunately for me any difference vanishes in the noise.
If you don't have such varying boot times, it would help if you could
carry out this measurement.
> On Mon, Jan 20, 2014 at 11:12:21PM +0100, Andreas Cadhalpun wr
Control: reassign -1 linux-image-3.2.0-4-amd64
Control: retitle -1 network/USB not working on Gigabyte 990FXA-UD3
mainboard with IOMMU disabled in BIOS [BIOS bug?]
Control: tags -1 d-i
[An English translation of this message can be found at the end.]
Hallo Rainer,
vielen Dank für deinen Insta
Hi Josh,
On 20.01.2014 02:07, Josh Triplett wrote:
If the goal here is to hide the boot messages by default, note that
the default kernel command line includes "quiet", which hides most
kernel messages and systemd messages.
In my opinion the boot options 'quiet' (hide unnecessary kernel
messa
Hi,
On 05.01.2014 11:51, Julien Cristau wrote:
On Sun, Jan 5, 2014 at 08:29:24 +0100, Christian PERRIER wrote:
OK, then. Reassigning to tasksel (as we should have done for quite a
while, indeed
It is probably best to include plymouth in tasksel, but still the
installer would have to rec
Hi Heiko,
On 05.01.2014 12:16, Heiko Ernst wrote:
I have download the debian testing iso file from 05.01.20114. My laptop
have a intel centrino 1000 wlan card. this card needs non-free firmware
but the debian installer dont load the firmware from usb device. the usb
device ist fromated with FAT
On 04.01.2014 16:02, Cyril Brulebois wrote:
Andreas Cadhalpun (2014-01-04):
I just meant, that the touchpad cannot move the cursor, although
evdev is loaded.
Might be a kernel or driver bug. Can you please attach Xorg log and
kernel log from the installer?
I attached Xorg.0.log and syslog
Hi KiBi,
On 04.01.2014 15:37, Cyril Brulebois wrote:
Err. It should work with evdev (without touchpad-specific features
though). Can you please clarify what you meant?
I just meant, that the touchpad cannot move the cursor, although evdev
is loaded.
But when task-desktop is installed, this in
Hi,
I think #733948 is a duplicate of #697331.
Best regards,
Andreas
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52c81002.8000...@googlemail.com
Package: debian-installer
Severity: normal
Dear Maintainer,
the Debian installer does not contain the synaptics driver for touchpads
(xserver-xorg-input-synaptics). Therefore the touchpad does not work in
the graphical installer.
I think the driver should be added to the gtk/initrd.gz.
Best
On 04.01.2014 11:06, Daniel Baumann wrote:
there is no problem with plymouth on systems that do not have a display
attached.
Thanks for providing this information.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lis
On 04.01.2014 00:19, Steve McIntyre wrote:
No, please! Let's not add more fluff to the base system.
Maybe it is better to install plymouth only, if task-desktop is installed?
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
Hi Steve,
On 04.01.2014 00:17, Steve McIntyre wrote:
I think a better way to do this would be to add an extra grub menu
entry for the other installation; the namespace for UEFI is not
designed to work with multiple entries like this AFAICS.
This would also solve the problem.
It seems this does
Package: debian-installer
Severity: serious
Justification: causes data loss (in a way)
Dear Maintainer,
I recently installed Debian in a second partition (for testing purposes)
on an UEFI system.
The installer didn't ask, whether or not to install grub/an UEFI entry,
instead it happily overwro
On 03.01.2014 21:37, Lennart Sorensen wrote:
I like the fact a debian base system by default is a working base system,
with no useless junk for me to have to remove later.
Perhaps if I slected 'graphical desktop' in the task selector, then it
could be considered, but as part of the default base
Hi,
On 03.01.2014 20:59, Lennart Sorensen wrote:
> On Fri, Jan 03, 2014 at 07:03:26PM +0100, Andreas Cadhalpun wrote:
>> Package: debian-installer
>> Severity: wishlist
>> X-Debbugs-CC: Antoine Beaupré
>>
>> Dear Maintainer,
>>
>> in his installation
On 03.01.2014 20:50, Cyril Brulebois wrote:
Yes, I checked the BTS before replying. I'm just not sure end users
having troubles to boot are actually able to work around those issues
and to report bugs. (I've at least seen people switch distro instead of
figuring out what went wrong.)
That's of
Hi KiBi,
On 03.01.2014 20:05, Cyril Brulebois wrote:
Last I remember from squeeze (didn't check wheezy too much), plymouth
was quite buggy/broken, and has been RC buggy for a long while (hello
libdrm-nouveau); I'm not sure it's a good idea to install it by default,
but I'm happy to take opinions
Package: debian-installer
Severity: wishlist
X-Debbugs-CC: Antoine Beaupré
Dear Maintainer,
in his installation report [1] Antoine Beaupré requested to have
plymouth installed by default.
While some want to have it and some don't, I think it really might be a
good idea to install plymouth b
Hi,
On 03.01.2014 10:16, Gaudenz Steinlin wrote:
Michael Gilbert writes:
So, today I wrote init-select. It's a small tool that empowers users
to freely and simply choose among all of the available init systems.
It also empowers Debian contributors to devote their energy toward
their favorite
Hi,
On 03.01.2014 04:24, Michael Gilbert wrote:
So, I suppose this isn't immediately obvious, but there is another
solved problem here.
Say the TC ultimately does not choose systemd as the default, and one
day gnome entirely drops compatibility with the other inits. The
gnome maintainers can t
On 01.01.2014 18:56, Antoine Beaupré wrote:
In my days, you had to to move bits
around with a magnet to resize FAT12 partitions and NTFS was satan! You
kids have it t easy. ;)
Oh yeah, the good old days... ;)
Yes, there was a firmware folder, it only contained a .deb of
linux-firmware
Hi,
On 31.12.2013 16:23, Luca Capello wrote:
On Tue, 31 Dec 2013 15:50:39 +0100, Antoine Beaupré wrote:
On 2013-12-31 05:45:01, Andreas Cadhalpun wrote:
Installing on UEFI firmware is supported, but is a little bit tricky,
see for example [1]. Particularly you need a GPT partitioned hard disk
Hi anarcat,
On 31.12.2013 05:00, anarcat wrote:
> Comments/Problems:
>
> Install went generally well and fast. There was a problem installing
> the boot loader during the install, and although I didn't investigate
> during the install, when I rebooted, grub was not installed in the
> MBR and I wa
On 29.12.2013 04:20, Buck Huppmann wrote:
Agreed; i was mostly just dutifully filing a success report, not looking
for any sort of resolution, since my system is working fine
It's good to know, that it sometimes even works. ;)
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
w
Hi Buck,
On 13.12.2013 00:29, Buck Huppmann wrote:
After failing to install using the latest image, because the md5sum.txt file had
a bad md5sum for one of the installation packages (e2fsprogs*udeb*),
This is usually due to an error while copying to the USB stick.
i downloaded
the image from
Control: reassign -1 src:linux
Hi,
as nobody objected to my proposal, I'm reassigning this bug back to linux.
In my opinion FW_LOADER_USER_HELPER should default to no, since the
functionality is not in udev anymore.
Furthermore it seems, that when this functionality was moved to the
kernel, it
Hi Manfred,
thanks for providing this information. I think your problem was similar
to the current ohci_hcd driver split, only for ehci_hcd, as in linux 3.8
the ehci-pci was introdced and linux 3.9.6-1 migrated to testing on
2013-06-21, where before that it was still 3.2. Apparently this has b
06:11:12PM +0100, Andreas Cadhalpun wrote:
I noticed one difference between my and Manfred's setup to Jason's:
It seems USB input works now on Intel hardware (hadn't worked in the
past), but not on AMD hardware (and also not on PowerPC).
I seriously doubt that this is the impor
Hi,
Thanks, Kay, for the very fast response and the detailed reasoning.
Your arguments convinced me, that it is technically a very good idea to
keep userspace out of the firmware loading. This should definitely not
be reintroduced upstream or in the Debian version of udev. (Originally
I thou
Hi,
On 12.12.2013 23:19, Kay Sievers wrote:
> On Thu, Dec 12, 2013 at 10:58 PM, Michael Biebl
wrote:
>> This was removed upstream [1] and is highly unlikely to be added back.
>> Especially considering that the user space firmware loader is scheduled
>> to be removed sooner rather then later.
>
Control: reassign -1 udev 204-5
Hi,
On 12.12.2013 19:43, Ben Hutchings wrote:
Yes. This is what is supposed to happen when firmware is missing:
1. The driver requests firmware.
2. The kernel tries to load a file under /lib/firmware, and fails.
(This is not implemented in the wheezy kernel
Hi,
I noticed one difference between my and Manfred's setup to Jason's:
It seems USB input works now on Intel hardware (hadn't worked in the
past), but not on AMD hardware (and also not on PowerPC).
Can someone else with AMD and/or Intel hardware test this hypothesis?
Best regards,
Andreas
Hi Ben,
On 12.12.2013 01:50, Ben Hutchings wrote:
Control: reassign -1 installation-reports
On Wed, 2013-12-11 at 21:56 +0100, Andreas Cadhalpun wrote:
It looks like a bug in the linux kernel.
I don't think so. The kernel log indicates that it got a negative
response from the user
Control: reassign 725714 linux
Control: tags 725714 d-i
Hi Manfred,
On 11.12.2013 05:55, Manfred Rebentisch wrote:
Burned the Jessie-Image on a CD and start the PC with the Logitech
Illuminated Keyboard.
I tried to use graphical and textual install. In both cases all have
worked. This installer
Hi Rick,
On 09.12.2013 22:19, Rick Thomas wrote:
As noted in bugreport 728936, I tried this with a recent amd64 netinst daily.
> It works fine. The problem only appears on PowerPC hardware.
I also have the impression that the amd64 installer works with USB
keyboards, which I find great, since
Hi Manfred,
I tried to reproduce the problem on my Laptop (i3-2330M) with a Logitech
USB keyboard, that Windows 7 reports as:
HID\VID_046D&PID_C312\7&26B80A52&0&
For me the external keyboard worked in the installer.
Furthermore I found the strikingly similar bug #728936 [1], where it was
On 03.12.2013 00:46, Cyril Brulebois wrote:
Andreas Cadhalpun (2013-12-02):
this is now the second time that I did not get your mail. If you
have any idea what could cause that, please let me know, because it
is not really practical to always check bugs.debian.org.
Gmail, spam folder? It
Hi,
this is now the second time that I did not get your mail. If you have
any idea what could cause that, please let me know, because it is not
really practical to always check bugs.debian.org.
On Topic: It's always better, if more people look at a patch, so I'd be
grateful for KiBi's though
Hi,
I have researched how to include the needed modules in the initrd.
If I understand it correctly, it would be possible to add the modules as
dependencies of cdrom-detect.
But that would not be feasible, because the kernel modules have the
version of the kernel in their name and therefore th
Hi,
On 24.11.2013 12:50, Christian PERRIER wrote:
That (imho) won't work : if that module is not in D-I kernel then it
should be added there.
Why do you think this wouldn't work?
The same stands here, but I suspect all these modules are already in
D-I kernel image packages. Needs to be carefu
Hi,
I just created patches against cdrom-detect-1.46, hw-detect-1.98 and
mountmedia-0.23. I hope that helps.
For the patch to work, the loop-module is needed in the initrd, so I
suggest to make it a dependency of cdrom-detect.
I furthermore highly recommend to make the ext4, ntfs and udf
modul
23.11.2013 22:31, Christian PERRIER wrote:
Quoting Andreas Cadhalpun (andreas.cadhal...@googlemail.com):
In general I think, that it would be good to include the patch now
and add any additional improvements later.
I just committed the changes to apt-setup. I will probably soon upload
the package
Hi,
I don't know why, but I didn't receive your email. I just read it on
bugs.debian.org.
Using the patched ISOs I noticed an error in the patch: In 41cdset
$filename was incorrectly used instead of $ISOname. Therefore too many
ISOs were considered as part of the set. The corrected patch is
Hi,
On 13.10.2013 10:21, ian_br...@fastmail.net wrote:
I'm not done with this yet. I'm working on a more general patch with new
features, which will be forthcoming shortly. I would ask that nothing
major be done until that is ready.
I'm curious, what features do you want to add?
"loopback" is
On 13.10.2013 09:38, Manfred Rebentisch wrote:
Hello Andreas,
thank you for the answer.
I have no time in the next few month to test the actual versions.
I am not a guru, but a professional debian user since many years - so
the problem *was* really a problem.
Next year I can test installing agai
Control: tags -1 + moreinfo unreproducible
Hi,
I do not have this problem with the recent Debian installer.
Have you tried it with the debian-testing-amd64-netinst.iso from the
following site?
http://cdimage.debian.org/cdimage/daily-builds/daily/20131012-1/amd64/iso-cd/
Please send a mail, wh
Control: affects -1 + hw-detect mountmedia
Hi,
the patch for this bug affects the following packages:
* apt-setup
* cdrom-detect
* hw-detect (check-missing-firmware)
* mountmedia
Since among the maintainers of all these packages is Christian Perrier,
I'm sending this to you.
A short summa
Package: debian-installer
Severity: important
Dear Maintainer,
I installed Debian using debian-7.1.0-amd64-CD-1.iso and
debian-7.2.0-amd64-CD-2.iso burned to CD.
However, the eject button of the drive does not work during installation
(afterwards, it works fine), so I have to switch to another
Control: retitle -1 ISO loopback support for Debian installer
Control: affects -1 + cdrom-detect + apt-setup
Hi,
I further improved the patch by solving three problems and merging with
the second patch from Ian.
First the solved problems:
* Filesystem support:
On 06.10.2013 04:06, Andreas
Package: installation-reports
Severity: serious
Dear Maintainer,
The current debian-testing-amd64-netinst.iso is broken: It does detect
missing firmware, but does not place this information in the correct
folder /run/udev/fimrware-missing. This directory does not exist, when
check-missing-fir
tags 724931 patch
tags 724933 patch
thanks
Hi,
I made some changes/improvements to the patch provided by Ian:
* Support a 'firmware' folder on the same device as the ISO: Due to
being mounted, it was not automatically checked with the old patch.
* Removed "DISTRIB_LABEL" variable: Such things
Hi,
@Ian: Thanks for working on this feature.
On 04.10.2013 11:27, ian_br...@fastmail.net wrote:
Testing seems to show that the patch works well; the relevant portion of
the installation log is reproduced below.
Sadly it only "seems" to work well, but in fact, your previous (and I
assume als
Hi,
this bug is strongly related with the following:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724931
Best regards,
Andreas
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://list
Hi,
Michael Biebl suggested a 'change one line' fix for this problem in:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717449#22
Would you be so kind as to commit this fix to git?
Thank you,
Andreas
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubsc
Hi,
The size difference in the ISO was due to an additional vmlinuz (2.5 MB)
in /install.amd/gtk.
If have created a shell script to patch an existing ISO and attached it
to this mail.
This script has to be executed with root privileges!
It expects to find a debian-testing-amd64-netinst.iso mou
tags 724931 patch
thanks
Hi,
On 30.09.2013 14:52, wrote ian_br...@fastmail.net:
Note that "loop.ko" is included on the ISO (but not the initrd), in the
form of /pool/main/l/linux/loop-modules-*.udeb packages.
Thank you for mentioning this. I didn't look there.
I have applied your patch to th
[Now follows a somewhat lengthy text. If you are bored, jump directly to
the conclusion.]
On 30.09.2013 01:58, wrote ian_br...@fastmail.net:
you wrote:
Please include the kernel module loop.ko in all installation ISOs.
It would be awesome, if you could also add iso-scan to the install
ISOs, s
Hi,
Did this install GNOME during installation? Or did you do that afterwards?
I choose the software 'Debian desktop environment' during installation
and this installed GNOME 3.4 as expected.
Best regards,
Andreas
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a sub
Hi,
this is still an issue:
When installing Debian from an USB stick, an entry for the USB stick is
added to /etc/fstab:
'/dev/sdb1 /media/usb0 autorw,user,noauto 0 0'
Therefore every stick inserted in the /dev/sdb1 slot is mounted without
permission for a normal user and
Package: debian-installer
Severity: important
Dear Maintainer,
When installing from the Debian netinstall ISO using Grub2's loopback
method, and manually mounting the ISO to /cdrom, the installation
process gets stuck at apt-setup only printing:
'apt-setup: /usr/lib/apt-setup/generators/50mir
Package: debian-installer
Severity: wishlist
Dear Maintainer,
The module 'loop.ko' is not shipped with the Debian testing netinstall ISO.
It should reside in /lib/modules/3.10-2-amd64/kernel/drivers/block/.
Because it is missing, it is impossible to mount ISO images during the
install and thus
Package: debian-installer
Severity: important
Dear Maintainer,
I recently installed Debian testing from the netinstall ISO using
internet via eth0.
The debian installer created the file /etc/network/interfaces with the
following content:
---
# This file describes the network interfaces availa
86 matches
Mail list logo
