Re: [suse-security-announce] SUSE Security Announcement: several kernel security problems (SUSE-SA:2005:018)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2005-03-24 at 17:29 +0100, Marcus Meissner wrote:
SUSE Security Announcement
Package: kernel Announcement-ID: SUSE-SA:2005:018 Date: Thu, 24 Mar 2005 15:00:00 +0000 Affected products: 8.2, 9.0, 9.1, 9.2 SUSE Linux Desktop 1.0 SUSE Linux Enterprise Server 8, 9 Novell Linux Desktop 9
Just for the record, YOU update for SuSE 9.1 of this patch forgets to run mkinitrd. The most visible problem is the missing splash in tty1. It is not the fisrt time this happens. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCR+IstTMYHG2NR9URAsMBAJsHj4SKDNeuaTUzsr2KB9koElYMowCgiLPl 5quBxpMZpmYVHuQZucMyZzs= =EY0s -----END PGP SIGNATURE-----
Carlos, On Monday 28 March 2005 02:53, Carlos E. R. wrote:
The Thursday 2005-03-24 at 17:29 +0100, Marcus Meissner wrote:
SUSE Security Announcement
Package: kernel Announcement-ID: SUSE-SA:2005:018 Date: Thu, 24 Mar 2005 15:00:00 +0000 Affected products: 8.2, 9.0, 9.1, 9.2 SUSE Linux Desktop 1.0 SUSE Linux Enterprise Server 8, 9 Novell Linux Desktop 9
Just for the record, YOU update for SuSE 9.1 of this patch forgets to run mkinitrd. The most visible problem is the missing splash in tty1. It is not the first time this happens.
If we want to do this manually, what is the proper invocation?
Carlos Robinson
Randall Schulz
Randall R Schulz wrote:
Carlos,
Just for the record, YOU update for SuSE 9.1 of this patch forgets to run mkinitrd. The most visible problem is the missing splash in tty1. It is not the first time this happens.
If we want to do this manually, what is the proper invocation?
If everything is stock, mkinitrd will suffice. man mkinitrd for more info. If customized, an example is mkinitrd -k vmlinuz2611 -i initrd2611 -m "jbd,ext" -s 1280x1024. If there is no -m, it takes which modules from /etc/sysconfig/kernel INITRD_MODULES. Default kernel image is vmlinuz, default initrd is initrd. If no -s it takes its size from grub's vga line. HTH -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Joe, On Monday 28 March 2005 06:50, Joe Morris (NTM) wrote:
Randall R Schulz wrote:
Carlos,
Just for the record, YOU update for SuSE 9.1 of this patch forgets to run mkinitrd. The most visible problem is the missing splash in tty1. It is not the first time this happens.
If we want to do this manually, what is the proper invocation?
If everything is stock, mkinitrd will suffice. man mkinitrd for more info.
Apart from ongoing YOU updates, the SuSE-supplied supplementary KDE updates (I'm currently at 3.4) and a few completely non-essential manual package installations (not updates), everything is stock. It was because I looked at the man page that I asked--too many options!
If customized, an example is mkinitrd -k vmlinuz2611 -i initrd2611 -m "jbd,ext" -s 1280x1024. If there is no -m, it takes which modules from /etc/sysconfig/kernel INITRD_MODULES. Default kernel image is vmlinuz, default initrd is initrd. If no -s it takes its size from grub's vga line. HTH
It does. Thanks.
Joe Morris
Randall Schulz
Just mkinitrd as root and a lilo if lilo ist used as bootloader... moria:~ # which mkinitrd /sbin/mkinitramfs moria:~ # mkinitrd -h Create initial ramdisk images that contain all kernel modules needed in the early boot process, before the root file system becomes available. This usually includes SCSI and/or RAID modules, a file system module for the root file system, or a network interface driver module for dhcp. mkinitrd [options] options: -h This Text. -k "kernel list" List of kernel images for which initrd files are created. Defaults to all kernels found in /boot. -i "initrd list" List of file names for the initrd; position have match to "kernel list". Defaults to all all kernels found in /boot. -m "module list" Modules to include in initrd. Defaults to the INITRD_MODULES variable in /etc/sysconfig/kernel. -b boot_dir Boot directory. Defaults to /boot. -d root_device Root device. Defaults to the device from which / is mounted. Overrides the rootdev enviroment variable if set. -s size Add splash animation and bootscreen to initrd. -t tmp_dir Temporary directory. Defaults to /var/tmp. -D interface Run dhcp on the specified interface. -a acpi_dsdt Attach compiled ACPI DSDT (Differentiated System Description Table) to initrd. This replaces the DSDT of the BIOS. Defaults to the ACPI_DSDT variable in /etc/sysconfig/kernel. -r Use initramfs instead of initrd. -g Use glibc instead of klibc binaries. -S Load policy file for SELinux if exist. But maybe someone could explain if one should use mkinitrd or mkinitramfs on newer systems... From /sbin/mkinitramfs on a SuSE Linux 9.2 i386: --- 8< --- # mkinitramfs - create an initramfs cpio archive, # useable with kernel 2.6.4 and newer --- 8< --- moria:~ # mkinitramfs -h Create compressed initramfs images that contain all kernel modules needed in the early boot process, before the root file system becomes available. This usually includes SCSI and/or RAID modules, a file system module for the root file system, or a network interface driver module for dhcp. mkinitramfs [options] options: -h This Text. -k "kernel list" List of kernel images for which initrd files are created. Defaults to all kernels found in /boot. -i "initrd list" List of file names for the initrd; position have match to "kernel list". Defaults to all all kernels found in /boot. -m "module list" Modules to include in initrd. Defaults to the INITRD_MODULES variable in /etc/sysconfig/kernel. -b boot_dir Boot directory. Defaults to /boot. -s size Add splash animation and bootscreen to initrd. -t tmp_dir Temporary directory. Defaults to /var/tmp. -a acpi_dsdt Attach compiled ACPI DSDT (Differentiated System Description Table) to initrd. This replaces the DSDT of the BIOS. Defaults to the ACPI_DSDT variable in /etc/sysconfig/kernel. (currently broken) -S Load policy file for SELinux if exist. -V Vendor specific script to run in initramfs On Montag 28 März 2005 16:18, Randall R Schulz wrote:
On Monday 28 March 2005 02:53, Carlos E. R. wrote:
Just for the record, YOU update for SuSE 9.1 of this patch forgets to run mkinitrd. The most visible problem is the missing splash in tty1. It is not the first time this happens.
If we want to do this manually, what is the proper invocation?
-- Eat, sleep and go running, David Huecking. Encrypted eMail welcome! GnuPG/ PGP-Key: 0x57809216. Fingerprint: 3DF2 CBE0 DFAA 4164 02C2 4E2A E005 8DF7 5780 9216
participants (4)
-
Carlos E. R. -
David Huecking -
Joe Morris (NTM) -
Randall R Schulz