From owner-svn-doc-head@FreeBSD.ORG Tue Apr 22 17:49:42 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D9EB3FAA; Tue, 22 Apr 2014 17:49:42 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C528B15B2; Tue, 22 Apr 2014 17:49:42 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3MHngVo049374; Tue, 22 Apr 2014 17:49:42 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3MHngEA049373; Tue, 22 Apr 2014 17:49:42 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404221749.s3MHngEA049373@svn.freebsd.org> From: Dru Lavigne Date: Tue, 22 Apr 2014 17:49:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44628 - head/en_US.ISO8859-1/books/handbook/boot X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Apr 2014 17:49:42 -0000 Author: dru Date: Tue Apr 22 17:49:42 2014 New Revision: 44628 URL: http://svnweb.freebsd.org/changeset/doc/44628 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Tue Apr 22 16:40:50 2014 (r44627) +++ head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Tue Apr 22 17:49:42 2014 (r44628) @@ -19,12 +19,12 @@ The process of starting a computer and loading the operating system is referred to as the bootstrap process, - or booting. &os;'s boot process provides - a great deal of flexibility in customizing what happens when - the system starts, including the ability to select from - different operating systems installed on the same computer, - different versions of the same operating system, or a different - installed kernel. + or booting. &os;'s boot process provides a great + deal of flexibility in customizing what happens when the system + starts, including the ability to select from different operating + systems installed on the same computer, different versions of + the same operating system, or a different installed + kernel. This chapter details the configuration options that can be set. It demonstrates how to customize the &os; boot process, @@ -53,7 +53,7 @@ The basics of setting device hints. - + How to boot into single- and multi-user mode and how to properly shut down a &os; system. @@ -77,13 +77,13 @@ operating system, and the operating system programs are on the disk, how is the operating system started? - This problem parallels one in the book - The Adventures of Baron Munchausen. A - character had fallen part way down a manhole, and pulled himself - out by grabbing his bootstraps and lifting. In the early days - of computing the term bootstrap was - applied to the mechanism used to load the operating system, - which has become shortened to booting. + This problem parallels one in the book The + Adventures of Baron Munchausen. A character had + fallen part way down a manhole, and pulled himself out by + grabbing his bootstraps and lifting. In the early days of + computing the term bootstrap was applied + to the mechanism used to load the operating system, which has + become shortened to booting. BIOS @@ -92,15 +92,15 @@ On x86 hardware, the Basic Input/Output System (BIOS) is responsible for loading the - operating system. The BIOS - looks on the hard disk for the Master Boot Record - (MBR), which must be located in a specific - place on the disk. The BIOS has enough - knowledge to load and run the MBR, and - assumes that the MBR can then carry out the - rest of the tasks involved in loading the operating system, - possibly with the help of the BIOS. - + operating system. The BIOS looks on the hard + disk for the Master Boot Record (MBR), which + must be located in a specific place on the disk. The + BIOS has enough knowledge to load and run the + MBR, and assumes that the + MBR can then carry out the rest of the tasks + involved in loading the operating system, possibly with the help + of the BIOS. + amd64 hardware is backward compatible as it understands BIOS instructions. Newer hardware uses @@ -123,22 +123,21 @@ The code within the MBR is usually referred to as a boot manager, especially - when it interacts with the user. The boot - manager usually has more code in the first - track of the disk or within the file - system. Examples of boot managers - include the standard &os; boot - manager boot0, also called - Boot Easy, and Grub, - which is used by many &linux; distributions. + when it interacts with the user. The boot manager usually has + more code in the first track of the disk or within the file + system. Examples of boot managers include the standard &os; + boot manager boot0, also called + Boot Easy, and + Grub, which is used by many &linux; + distributions. If only one operating system is installed, the MBR searches for the first bootable (active) slice on the disk, and then runs the code on that slice to load the remainder of the operating system. If multiple operating - systems are present, a different boot - manager can be installed which displays the list of operating - systems so that the user can choose which one to boot. + systems are present, a different boot manager can be installed + which displays the list of operating systems so that the user + can choose which one to boot. The remainder of the &os; bootstrap system is divided into three stages. The first stage knows just enough to get the @@ -146,73 +145,73 @@ second stage can do a little bit more, before running the third stage. The third stage finishes the task of loading the operating system. The work is split into three stages because - the MBR puts limits on the size of the programs that can be - run at stages one and two. Chaining the tasks together allows - &os; to provide a more flexible loader. + the MBR puts limits on the size of the + programs that can be run at stages one and two. Chaining the + tasks together allows &os; to provide a more flexible + loader. kernel &man.init.8; - The kernel is then started and begins to probe for - devices and initialize them for use. Once the kernel boot - process is finished, the kernel passes control to the user - process &man.init.8;, which makes sure the disks are in a - usable state, starts the user-level resource - configuration which mounts file systems, sets up network cards - to communicate on the network, and starts the processes which - have been configured to run at startup. - - This section describes these stages in more detail and - demonstrates how to interact with the &os; boot process. - - - The Boot Manager - - Boot Manager - - Master Boot Record - (MBR) - - The boot manager code in the MBR is - sometimes referred to as stage zero of the - boot process. By default, &os; uses the - boot0 boot manager. + The kernel is then started and begins to probe for devices + and initialize them for use. Once the kernel boot process is + finished, the kernel passes control to the user process + &man.init.8;, which makes sure the disks are in a usable state, + starts the user-level resource configuration which mounts file + systems, sets up network cards to communicate on the network, + and starts the processes which have been configured to run at + startup. + + This section describes these stages in more detail and + demonstrates how to interact with the &os; boot process. + + + The Boot Manager + + Boot Manager + + Master Boot Record + (MBR) + + The boot manager code in the MBR is + sometimes referred to as stage zero of + the boot process. By default, &os; uses the + boot0 boot manager. The MBR installed by the &os; installer - is based on - /boot/boot0. The size and capability of - boot0 is restricted to 446 bytes - due to the slice table and 0x55AA - identifier at the end of the MBR. If - boot0 and multiple operating - systems are installed, a message similar to this example will - be displayed at boot time: + is based on /boot/boot0. The size and + capability of boot0 is restricted + to 446 bytes due to the slice table and + 0x55AA identifier at the end of the + MBR. If boot0 + and multiple operating systems are installed, a message + similar to this example will be displayed at boot time: - - <filename>boot0</filename> Screenshot + + <filename>boot0</filename> Screenshot - F1 Win + F1 Win F2 FreeBSD Default: F2 - + - Other operating systems will - overwrite an existing MBR if they are - installed after &os;. If this happens, or to replace the - existing MBR with the &os; - MBR, use the following command: - - &prompt.root; fdisk -B -b /boot/boot0 device - - where device is the boot disk, - such as ad0 for the first - IDE disk, ad2 for the - first IDE disk on a second - IDE controller, or da0 - for the first SCSI disk. To create a - custom configuration of the MBR, refer to - &man.boot0cfg.8;. + Other operating systems will overwrite an existing + MBR if they are installed after &os;. If + this happens, or to replace the existing + MBR with the &os; MBR, + use the following command: + + &prompt.root; fdisk -B -b /boot/boot0 device + + where device is the boot disk, + such as ad0 for the first + IDE disk, ad2 for the + first IDE disk on a second + IDE controller, or da0 + for the first SCSI disk. To create a + custom configuration of the MBR, refer to + &man.boot0cfg.8;. @@ -225,25 +224,26 @@ Default: F2 /boot/boot by the &os; installer or bsdlabel. - These two stages are located outside file systems, in the first track - of the boot slice, starting with the first sector. This is - where boot0, or any other + These two stages are located outside file systems, in the + first track of the boot slice, starting with the first sector. + This is where boot0, or any other boot manager, expects to find a program to run which will continue the boot process. - The first stage, boot1, is very simple, since it can - only be 512 bytes in size. It knows just enough about the - &os; bsdlabel, which stores - information about the slice, to find and execute + The first stage, boot1, is very + simple, since it can only be 512 bytes in size. It knows just + enough about the &os; bsdlabel, which + stores information about the slice, to find and execute boot2. - Stage two, boot2, is slightly more sophisticated, - and understands the &os; file system enough to find files. It - can provide a simple interface to choose the kernel or loader - to run. It runs loader, which is much more sophisticated and - provides a boot configuration file. If the boot process is - interrupted at stage two, the following interactive screen is - displayed: + Stage two, boot2, is slightly more + sophisticated, and understands the &os; file system enough to + find files. It can provide a simple interface to choose the + kernel or loader to run. It runs + loader, which is much more + sophisticated and provides a boot configuration file. If the + boot process is interrupted at stage two, the following + interactive screen is displayed: <filename>boot2</filename> Screenshot @@ -253,23 +253,21 @@ Default: 0:ad(0,a)/boot/loader boot: - To replace the installed - boot1 and + To replace the installed boot1 and boot2, use bsdlabel, where diskslice is the disk and - slice to boot from, such as ad0s1 - for the first slice on the first IDE - disk: + slice to boot from, such as ad0s1 for the + first slice on the first IDE disk: &prompt.root; bsdlabel -B diskslice If just the disk name is used, such as - ad0, bsdlabel will create the disk in - dangerously dedicated mode, without slices. - This is probably not the desired action, so double check the - diskslice - before pressing + ad0, bsdlabel will + create the disk in dangerously dedicated + mode, without slices. This is probably not the + desired action, so double check the + diskslice before pressing Return. @@ -279,20 +277,21 @@ boot: boot-loader - The loader is the final stage of the three-stage - bootstrap process. It is located on the file system, usually as + The loader is the final stage + of the three-stage bootstrap process. It is located on the + file system, usually as /boot/loader. - The loader is intended as an interactive method for - configuration, using a built-in command set, backed up by a - more powerful interpreter which has a more complex command - set. - - During initialization, loader will probe for a - console and for disks, and figure out which disk it is - booting from. It will set variables accordingly, and an - interpreter is started where user commands can be passed from - a script or interactively. + The loader is intended as an + interactive method for configuration, using a built-in command + set, backed up by a more powerful interpreter which has a more + complex command set. + + During initialization, loader + will probe for a console and for disks, and figure out which + disk it is booting from. It will set variables accordingly, + and an interpreter is started where user commands can be + passed from a script or interactively. loader loader configuration @@ -306,15 +305,15 @@ boot: these variables, loading whichever modules and kernel are selected. - Finally, by default, loader issues a 10 second wait - for key presses, and boots the kernel if it is not - interrupted. If interrupted, the user is presented with a - prompt which understands the command set, where the user may - adjust variables, unload all modules, load modules, and then - finally boot or reboot. lists the most - commonly used loader commands. For - a complete discussion of all available commands, refer to + Finally, by default, loader + issues a 10 second wait for key presses, and boots the kernel + if it is not interrupted. If interrupted, the user is + presented with a prompt which understands the command set, + where the user may adjust variables, unload all modules, load + modules, and then finally boot or reboot. lists the most commonly + used loader commands. For a + complete discussion of all available commands, refer to &man.loader.8;. @@ -326,145 +325,142 @@ boot:VariableDescription - - + + - autoboot seconds + autoboot + seconds Proceeds to boot the kernel if not interrupted within the time span given, in seconds. It displays a countdown, and the default time span is 10 seconds. - - boot - -options - kernelname - Immediately proceeds to boot the kernel, with any - specified options or kernel name. Providing a kernel - name on the command-line is only applicable after an - unload has been issued. + + boot + -options + kernelname + Immediately proceeds to boot the kernel, with + any specified options or kernel name. Providing a + kernel name on the command-line is only applicable + after an unload has been issued. Otherwise, the previously-loaded kernel will be used. - - boot-conf - Goes through the same automatic configuration of + + boot-conf + Goes through the same automatic configuration of modules based on specified variables, most commonly kernel. This only makes sense if unload is used first, before changing some variables. - - help - topic - Shows help messages read from + + help + topic + Shows help messages read from /boot/loader.help. If the topic given is index, the list of available topics is displayed. - - include filename - … - Reads the specified file and interprets it line by line. An - error immediately stops the include. + + include filename + … + Reads the specified file and interprets it line + by line. An error immediately stops the + include. - - load -t - type - filename - Loads the kernel, kernel module, or file of the + + load -t + type + filename + Loads the kernel, kernel module, or file of the type given, with the specified filename. Any arguments after filename are passed to the file. - - ls -l - path - Displays a listing of files in the given path, or + + ls -l + path + Displays a listing of files in the given path, or the root directory, if the path is not specified. If is specified, file sizes will also be shown. - - lsdev - -v - Lists all of the devices from which it may be + + lsdev -v + Lists all of the devices from which it may be possible to load modules. If is specified, more details are printed. - - lsmod - -v - Displays loaded modules. If + + lsmod -v + Displays loaded modules. If is specified, more details are shown. - - more filename - Displays the files specified, with a pause at each - LINES displayed. - - - - reboot - Immediately reboots the system. - - - - set variable, set - variable=value - Sets the specified environment variables. - - - - unload - Removes all loaded modules. + + more filename + Displays the files specified, with a pause at + each LINES displayed. + + + + reboot + Immediately reboots the system. + + + + set variable, set + variable=value + Sets the specified environment variables. + + + + unload + Removes all loaded modules. -
+ - Here are some practical examples of - loader usage. To boot the usual kernel in single-user - modesingle-user - mode: + Here are some practical examples of loader usage. To boot + the usual kernel in single-user mode + single-user + mode: - boot -s + boot -s - To unload the usual kernel and modules and then - load the previous or another, specified kernel: + To unload the usual kernel and modules and then load the + previous or another, specified kernel: - unload + unload load kernel.old - Use kernel.GENERIC to refer to - the default kernel that comes with an installation, or - kernel.old - kernel.old - to refer to the previously installed kernel before a - system upgrade or before configuring a custom - kernel. + Use kernel.GENERIC to refer to the + default kernel that comes with an installation, or + kernel.oldkernel.old + to refer to the previously installed kernel before a system + upgrade or before configuring a custom kernel. - Use the following to load the usual modules with - another kernel: + Use the following to load the usual modules with another + kernel: - unload + unload set kernel="kernel.old" boot-conf - To load an automated kernel configuration - script: + To load an automated kernel configuration script: - load -t userconfig_script /boot/kernel.conf + load -t userconfig_script /boot/kernel.conf kernel @@ -472,163 +468,168 @@ boot: - - Last Stage + + Last Stage - - &man.init.8; - - Once the kernel is loaded by either loader or - by boot2, which bypasses - loader, it examines any boot - flags and adjusts its behavior as necessary. + &man.init.8; + + + Once the kernel is loaded by either + loader or by + boot2, which bypasses + loader, it examines any boot flags + and adjusts its behavior as necessary. lists the commonly used boot flags. - Refer to &man.boot.8; for more information on the other - boot flags. + Refer to &man.boot.8; for more information on the other boot + flags. kernel bootflags - - Kernel Interaction During Boot +
+ Kernel Interaction During Boot - - - - Option - Description - - - - - - - During kernel initialization, ask for the device - to mount as the root file system. - - - - - Boot the root file system from a CDROM. - - - - - Boot into single-user mode. - - - - - Be more verbose during kernel startup. - - - -
- - Once the kernel has finished booting, it passes control to - the user process &man.init.8;, which is located at - /sbin/init, or the program path specified - in the init_path variable in - loader. This is the last stage of the boot - process. + + + + Option + Description + + - The boot sequence makes sure that the file systems available - on the system are consistent. If a UFS file - system is not, and fsck - cannot fix the inconsistencies, - init drops the system into single-user mode so that the - system administrator can resolve the problem directly. Otherwise, - the system boots into multi-user mode. - - - Single-User Mode - - single-user mode - console - - A user can specify this mode by - booting with , or by - setting the boot_ single variable in - loader. It can also be reached by - running shutdown now from - multi-user mode. Single-user mode begins with this message: + + + + During kernel initialization, ask for the device + to mount as the root file system. + + + + + Boot the root file system from a + CDROM. + + + + + Boot into single-user mode. + + + + + Be more verbose during kernel startup. + + + + + + Once the kernel has finished booting, it passes control to + the user process &man.init.8;, which is located at + /sbin/init, or the program path specified + in the init_path variable in + loader. This is the last stage of the boot + process. + + The boot sequence makes sure that the file systems + available on the system are consistent. If a + UFS file system is not, and + fsck cannot fix the inconsistencies, + init drops the system into + single-user mode so that the system administrator can resolve + the problem directly. Otherwise, the system boots into + multi-user mode. + + + Single-User Mode + + single-user mode + console + + A user can specify this mode by booting with + , or by setting the boot + _ single variable in + loader. It can also be reached + by running shutdown now from multi-user + mode. Single-user mode begins with this message: Enter full pathname of shell or RETURN for /bin/sh: - If the user presses Enter, the system - will enter the default Bourne shell. To specify a different - shell, input the full path to the shell. - - Single-user mode is usually used to repair a system that will not - boot due to an inconsistent file system or an error in a boot - configuration file. It can also be used to reset the - root password when - it is unknown. These actions are possible as the single-user - mode prompt gives full, local access to the system and its - configuration files. There is no networking in this mode. - - While single-user mode is useful for repairing a system, - it poses a security risk unless the system is in a physically - secure location. By default, any user who can gain physical - access to a system will have full control of that system after - booting into single-user mode. - - If the system console is changed to - insecure in /etc/ttys, - the system will first prompt for the root password before - initiating single-user mode. This adds a measure of security - while removing the ability to reset the root password when it is - unknown. - - - Configuring an Insecure Console in - <filename>/etc/ttys</filename> + If the user presses Enter, the system + will enter the default Bourne shell. To specify a different + shell, input the full path to the shell. + + Single-user mode is usually used to repair a system that + will not boot due to an inconsistent file system or an error + in a boot configuration file. It can also be used to reset + the root password + when it is unknown. These actions are possible as the + single-user mode prompt gives full, local access to the + system and its configuration files. There is no networking + in this mode. + + While single-user mode is useful for repairing a system, + it poses a security risk unless the system is in a + physically secure location. By default, any user who can + gain physical access to a system will have full control of + that system after booting into single-user mode. + + If the system console is changed to + insecure in + /etc/ttys, the system will first prompt + for the root + password before initiating single-user mode. This adds a + measure of security while removing the ability to reset the + root password when + it is unknown. + + + Configuring an Insecure Console in + <filename>/etc/ttys</filename> - # name getty type status comments + # name getty type status comments # # If console is marked "insecure", then init will ask for the root password # when going to single-user mode. console none unknown off insecure - + An insecure console means that physical security to the console is considered to be insecure, so only someone who knows the root password may use single-user mode. - + - - Multi-User Mode + + Multi-User Mode - multi-user mode + multi-user mode - If init finds the file systems to be in order, or - once the user has finished their commands in single-user mode - and has typed exit to leave single-user mode, - the system enters - multi-user mode, in which it starts the resource configuration - of the system. - - rc files - - The resource configuration system reads in configuration - defaults from /etc/defaults/rc.conf and - system-specific details from - /etc/rc.conf. It then proceeds to mount - the system file systems listed in - /etc/fstab. It starts up networking - services, miscellaneous system daemons, then the startup - scripts of locally installed packages. - - To learn more about the resource configuration system, - refer to &man.rc.8; and examine the scripts located in - /etc/rc.d. - + If init finds the file + systems to be in order, or once the user has finished their + commands in single-user mode and has typed + exit to leave single-user mode, the + system enters multi-user mode, in which it starts the + resource configuration of the system. + + rc files + + The resource configuration system reads in configuration + defaults from /etc/defaults/rc.conf and + system-specific details from + /etc/rc.conf. It then proceeds to + mount the system file systems listed in + /etc/fstab. It starts up networking + services, miscellaneous system daemons, then the startup + scripts of locally installed packages. + + To learn more about the resource configuration system, + refer to &man.rc.8; and examine the scripts located in + /etc/rc.d. + - - - Configuring Boot Time Splash Screens + + + Configuring Boot Time Splash Screens @@ -653,122 +654,117 @@ console none - Typically when a &os; system boots, it displays its - progress as a series of messages at the console. A boot splash - screen creates an alternate boot screen that - hides all of the boot probe and service - startup messages. A few boot loader messages, including the boot options - menu and a timed wait countdown prompt, are displayed at - boot time, even when the splash screen is enabled. The display of the splash screen - can be turned off by hitting any - key on the keyboard during the boot process. - - There are two basic environments available in &os;. The - first is the default legacy virtual console command line - environment. After the system finishes booting, a console - login prompt is presented. The second environment is a configured - graphical environment. Refer to - for more information on how to install - and configure a graphical display manager and a graphical - login manager. - - Once the system has booted, the splash screen defaults to being a screen saver. - After a time period of non-use, the splash screen - will display and will cycle through steps of changing - intensity of the image, from bright to very dark and over - again. The configuration of the splash screen saver can be - overridden by adding a saver= line to - /etc/rc.conf. Several built-in screen - savers are available and described in &man.splash.4;. The - saver= option only applies to virtual - consoles and has no effect on graphical display - managers. - - Sample splash screen files can be downloaded from the - gallery at http://artwork.freebsdgr.org. - By installing the - sysutils/bsd-splash-changer package or port, a random splash - image from a collection will display at - boot. - - The splash screen function supports 256-colors in the - bitmap (.bmp), ZSoft - PCX (.pcx), or - TheDraw (.bin) formats. The .bmp, - .pcx, or .bin image - has to be placed on the root partition, for example in - /boot. The splash image - files must have a resolution of 320 by 200 pixels or less in - order to work on standard VGA adapters. - For the default boot display resolution of 256-colors and - 320 by 200 pixels or less, add the following lines to - /boot/loader.conf. - Replace splash.bmp with the name of - the bitmap file to use: + Typically when a &os; system boots, it displays its progress + as a series of messages at the console. A boot splash screen + creates an alternate boot screen that hides all of the boot + probe and service startup messages. A few boot loader messages, + including the boot options menu and a timed wait countdown + prompt, are displayed at boot time, even when the splash screen + is enabled. The display of the splash screen can be turned off + by hitting any key on the keyboard during the boot + process. + + There are two basic environments available in &os;. The + first is the default legacy virtual console command line + environment. After the system finishes booting, a console login + prompt is presented. The second environment is a configured + graphical environment. Refer to for more + information on how to install and configure a graphical display + manager and a graphical login manager. + + Once the system has booted, the splash screen defaults to + being a screen saver. After a time period of non-use, the + splash screen will display and will cycle through steps of + changing intensity of the image, from bright to very dark and + over again. The configuration of the splash screen saver can be + overridden by adding a saver= line to + /etc/rc.conf. Several built-in screen + savers are available and described in &man.splash.4;. The + saver= option only applies to virtual + consoles and has no effect on graphical display managers. + + Sample splash screen files can be downloaded from the + gallery at http://artwork.freebsdgr.org. + By installing the sysutils/bsd-splash-changer + package or port, a random splash image from a collection will + display at boot. + *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***