Bug#930476: exim4 is no longer installed by default

2019-06-13 Thread Alan Jenkins

Package: installation-guide
Version: 20170614

> 8.5.1. Default E-Mail Configuration
>
> [...] For this reason the packages exim4 and mutt will be installed 
by default (provided you did not unselect the “standard” task during the 
installation).


I have been told by several people, exim4 is no longer installed by 
default :-).


In Debian 9 and above, exim4-daemon-light has been downgraded from 
"Priority: standard" to "optional".


Thanks
Alan



Bug#783358: installation-reports: Debian 8 CD - Graphical install is not the default (installation guide says it should be)

2015-04-26 Thread Alan Jenkins
Package: installation-reports
Severity: normal

I've just installed debian-8.0.0-amd64-CD-1.iso in a virtual machine.
By default, the Install entry was selected.
But the install guide says the default should be Graphical install.

So maybe the default needs changing on the CD.  I have _not_ tried the DVD,
but maybe that defaults to graphical and it's what the author checked.

Happy Debian release day!
Alan


-- Package-specific info:

Boot method: CD drive of virtual machine (GNOME Boxes)
Image version: debian-8.0.0-amd64-CD-1.iso
Date: Sun 26 Apr 2015

Machine: GNOME Boxes virtual machine host, from Fedora 21
Partitions:

$ lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda  8:00   20G  0 disk 
├─sda1   8:10 19.1G  0 part /
├─sda2   8:201K  0 part 
└─sda5   8:50  880M  0 part [SWAP]
sr0 11:01  627M  0 rom

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ O ]
Detect network card:[ O ]
Configure network:  [ O ]
Detect CD:  [ O ]
Load installer modules: [ O ]
Clock/timezone setup:   [ O ]
User/password setup:[ O ]
Detect hard drives: [ O ]
Partition hard drives:  [ O ]
Install base system:[ O ]
Install tasks:  [ O ]
Install boot loader:[ O ]
Overall install:[ O ]

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=8 (jessie) - installer build 20150422
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux debian-test 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-2 
(2015-04-13) x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE 
[Natoma/Triton II] [8086:7010]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: ata_piix
lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:02.0 VGA compatible controller [0300]: Red Hat, Inc. QXL 
paravirtual graphic card [1b36:0100] (rev 04)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 20)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: 8139cp
lspci -knn: 00:04.0 Multimedia audio controller [0401]: Intel Corporation 
82801AA AC'97 Audio Controller [8086:2415] (rev 01)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: snd_intel8x0
lspci -knn: 00:05.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #1 [8086:2934] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:05.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #2 [8086:2935] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:05.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB UHCI Controller #3 [8086:2936] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:05.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 
Family) USB2 EHCI Controller #1 [8086:293a] (rev 03)
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:1100]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:06.0 Communication controller [0780]: Red Hat, Inc Virtio 
console [1af4:1003]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:0003]
lspci -knn: Kernel driver in use: virtio-pci
lspci -knn: 00:07.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory 
balloon [1af4:1002]
lspci -knn: Subsystem: Red Hat, Inc Device [1af4:0005]
lspci -knn: Kernel driver in use: virtio-pci
usb-list: 
usb-list: Bus 01 Device 01: 

Bug#413642: debian-installer-manual: After debootstrap, /dev is too minimal to mount partitions

2015-04-26 Thread Alan Jenkins

Hi

I think someone could close this bug now.  The installer manual does now 
outline the process of creating device nodes with MAKEDEV.


D.3.4.1. Create device files 
https://www.debian.org/releases/jessie/amd64/apds03.html.en#idp8293600


(It also suggests bind-mounting /dev instead, which is what I would try 
nowadays.)


Alan


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/553cdb71.2020...@gmail.com



Bug#473217: Wishlist: Don't run ckbcomp at boot-time (use a saved keymap instead)

2008-03-29 Thread Alan Jenkins

Package: console-setup
Version: 1.16
Severity: wishlist

The setupcon command, as run by console-setup during boot, runs ckbcomp 
to generate a console keymap from the X keymap files.  This can take on 
the order of half a second CPU time.


setupcon already saves the resulting keymap in 
/etc/console-setup/boottime.kmap.gz, and has support for using that 
instead.  However this is only used when /usr is not mounted.  I'm not 
interested in repartitioning my system to use this feature.


My wish is that this method would be used even when /usr is mounted.  It 
may require some documentation but I think it's sane enough.


It looks like Ubuntu (my primary OS), have altered the console-setup 
init script to regenerate the keymap if run manually (i.e. not by init):


# Are we running from init?
run_by_init()
{
   ([ $previous ]  [ $runlevel ]) || [ $runlevel = S ]
}

...
elif ! run_by_init; then
log_action_begin_msg Saving console font and keymap for next boot
if setupcon --save-only; then
log_action_end_msg 0
else
log_action_end_msg $?
fi
fi

So if you edit /etc/default/console-setup manually, you then need to run 
/etc/init.d/console-setup restart to apply the changes and regenerate 
the keymap.  This happens automatically when dpkg-reconfigure is used.




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]