Answer incomplete questions

1 files changed, 62 insertions, 0 deletions

diff --git a/README.md b/README.md
index efa3e5a..02c42ae 100644
--- a/README.md
+++ b/README.md
@@ -1060,12 +1060,74 @@ Your report should include advice to other people attempting to do the same.
 		- https://docs.fedoraproject.org/en-US/Fedora/13/html/Installation_Guide/s1-rescuemode-booting-single.html
 
   e. What, if anything, do you notice that is different about booting into single-user mode compared to shutting down to single-user mode?
+
+    When booting into single user mode everthing appears to be the same.
+    However, when I look at the process listing many processes aren't started.
+    For example many services that usually start up with systemd are not
+    running. However, I was not able to switch to runlevel 1.
+    
   f. Shut the system down; then boot it normally. Look in the file /var/log/messages (often /var/adm/messages on some systems). How does the information in the “messages” file compare with what appears on the screen during boot?
 
+    The file `/var/log/messages` and `/var/adm/messages` does not exist. A
+    `/var/log/README` has the following explanation.
+
+    ```text
+    You are looking for the traditional text log files in /var/log, and
+    they are gone?
+
+    Here's an explanation on what's going on:
+
+    You are running a systemd-based OS where traditional syslog has been
+    replaced with the Journal. The journal stores the same (and more)
+    information as classic syslog. To make use of the journal and access
+    the collected log data simply invoke "journalctl", which will output
+    the logs in the identical text-based format the syslog files in
+    /var/log used to be. For further details, please refer to
+    journalctl(1).
+
+    Alternatively, consider installing one of the traditional syslog
+    implementations available for your distribution, which will generate
+    the classic log files for you. Syslog implementations such as
+    syslog-ng or rsyslog may be installed side-by-side with the journal
+    and will continue to function the way they always did.
+
+    Thank you!
+
+    Further reading:
+            man:journalctl(1)
+            man:systemd-journald.service(8)
+            man:journald.conf(5)
+            http://0pointer.de/blog/projects/the-journal.html
+    ```
+
+    Running `journalctl --folow -k` includes logs from the kernel which is
+    similar to what appears on screen during the boot process.
+
 3. Linux Startup
 
   a. Run the dmesg command, and list which devices are assigned to each of CD-ROM, HD, and floppy disk.
 
+    This system does not have a CD-ROM or floppy disk. `dmesg` shows that the
+    kernel identifier two disks. `sda` assigned to a 1TB disk and `sdb` assigned
+    to a 250 GB disk.
+
+    ```bash
+    モ dmesg | grep -E 'sd[ab]'
+    [    1.406725] sd 6:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
+    [    1.406763] sd 6:0:0:0: [sda] Write Protect is off
+    [    1.406766] sd 6:0:0:0: [sda] Mode Sense: 00 3a 00 00
+    [    1.406796] sd 6:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
+    [    1.421233]  sda: sda1
+    [    1.421910] sd 6:0:0:0: [sda] Attached SCSI disk
+    [    1.870382] sd 7:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/233 GiB)
+    [    1.870394] sd 7:0:0:0: [sdb] Write Protect is off
+    [    1.870396] sd 7:0:0:0: [sdb] Mode Sense: 00 3a 00 00
+    [    1.870414] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
+    [    1.870965]  sdb: sdb1 sdb2
+    [    1.871492] sd 7:0:0:0: [sdb] Attached SCSI disk
+    [    6.869352] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
+    ```
+
   b. What do you think the following (or a similar line) in dmesg output means?
 		```text
 		Linux version 2.6.5-1.358 (bhcompile@bugs.build.redhat.com) (gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Sat May 8 09:04:50 DT 2004