Course 144 Supplementary Materials. SUSE Differences

Transcription

1 Course 144 Supplementary Materials SUSE Differences 1

2 SUSE Differences GRUB and Boot Scripts GRUB configuration Red Hat: a symbolic link makes /boot/grub/grub.conf and /boot/grub/menu.lst the same file SUSE: /etc/grub.conf just specifies the stage 2 boot loader, and /boot/grub/menu.lst specifies the booting details System initialization boot script specified in /etc/inittab: Red Hat: si::sysinit:/etc/rc.d/rc.sysinit SUSE: si::bootwait:/etc/init.d/boot Boot script directories and symbolic links on SUSE /etc/rc.d is a symbolic link to /etc/init.d /etc/init.d/rc?.d/* are symbolic links to /etc/init.d/* Logic of chkconfig on SUSE Instead of hard-coded default run levels and S/K numbers, a block within the initial comment specifies dependencies between scripts Add one service, and others may get added or renumbered! 2

3 SUSE Differences /etc/rc Logic Logic of /etc/rc to go from run state 3 to run state 5 Red Hat just uses the target run level links: If /etc/rc5.d/k??service exists, then: /etc/rc5.d/k??service stop If /etc/rc5.d/s??service exists, then: /etc/rc5.d/s??service start SUSE checks both the current and the target run level links: Stop it only if it is already running: if /etc/init.d/rc3.d/k??service exists, and /etc/init.d/rc5.d/s??service does not exist: /etc/init.d/rc3.d/k??service stop Start it only if it is not already running: if /etc/init.d/rc5.d/s??service exists, and either /etc/init.d/rc3.d/s??service does not exist or the system is currently booting up, then: /etc/init.d/rc5.d/s??service start 3

4 SUSE Differences Syslog vs Syslog-NG Uses Syslog-NG instead of Syslog Syslog-NG is potentially much more capable Select messages based on their contents Modify the message format before saving Listen on TCP sockets so Syslog traffic between machines can be secured with SSH or SSL tunnels But its configuration is much more complex! 4

5 SUSE Differences Default File Systems Distributions differ in their preferred partitioning schemes and whether they use LVM by default or not Even one distribution may change significantly from release to release! SUSE has used the Reiser File System by default Distributions vary widely in their use of hot-plug media Where is a USB file system mounted? What devices are recognized and given meaningful names? And what names are used? This also varies from release to release of one distribution! We will see how hot-plug devices are detected and named in Chapter 11 5

6 SUSE Differences Package Management Like most distributions, uses RPM for low-level package management YaST has included a good high-level dependency resolution system With SUSE 10.1, Novell seems to be in the middle of changing the high-level package management scheme It first used Ximian s Red Carpet, and Open Carpet Now moving to libzypp, a new package dependency resolver library Zenworks user tools: Command-line tool rug Graphical tools zen-installer, zen-updater, and zenremover Based on Mono, a Linux implementation of the.net framework Not at all integrated into YaST May be problematic with SUSE 10.1 The good news: what you learned in this course about rpm and yum will work on SUSE! 6

7 SUSE Configuration Differences Fully qualified domain name specified in /etc/hostname Interface IP details set in files /etc/sysconfig/network/* Not in /etc/sysconfig/network-scripts/* Interface files have unusual names For example, ifcfg-eth-id-00:0c:29:e0:33:4a Name specifies hardware, but not logical name eth0 versus eth1 Contain the same crucial fields: IPADDR, NETMASK, BOOTPROTO But they also contain many SUSE-specific details Default route set in /etc/sysconfig/network/routes Specifics are documented in detail on a SUSE system: /usr/share/doc/packages/sysconfig/* 7

8 SUSE Differences X and Display Management Configures X if necessary with SaX2 Although xorgcfg is still included, unlike Red Hat SUSE is among the distributions adding XGL/AIGLX and compiz/beryl Supports some very impressive 3D graphics on the desktop 8