Friday, February 2, 2018

A few other (advanced) differences between RHEL7.x & RHEL6.x

Extracting initramfs image :--

Using "skipcpio" command in RHEL7.x, otherwise, we use "gunzip" in earlier RHEL versions. So, the command to extract initramfs image file in RHEL7.x is " /usr/lib/dracut/skipcpio /boot/initramfs-$(uname -r).img | gunzip -c | cpio -id ". In earlier versions, we could do this by using the command gunzip "gunzip -c /boot/initramfs-$(uname -r).img | cpio -i -d ".

Default Inode size :--

In case of XFS file system this has been changed to “512 bytes” which is “256 bytes” in RHEL6.x version.

-- RHEL7.x

   [root@managed1 ]# xfs_info /dev/sda1|grep isize

   meta-data=/dev/sda1 isize=512 agcount=4, agsize=65536 blks

-- RHEL6.x

   [root@local ~]# tune2fs -l /dev/sda1|grep -i 'inode size'

   Inode size: 128

iostat command :--

Now, in RHEL7.x there is a separate r_await (read await) & w_await (write await) added along with "await" which produces total (changed in sysstat version 10). It is just "await" parameter to get total average time in milliseconds which took to complete IO requests in case of RHEL6.x version.

Network persistent device file deprecated :-

There is no such file which maintains persistent network/device names as seen earlier versions. It has been deprecated. []. This was maintained by "/etc/udev/rules.d/70-persistent-network.rules" file in earlier versions.

free command :-

Now, the “used” column of “free” command output calculates used memory size by considering “buffers/cache” value as well. So, in RHEL7.x version it is “used = total - free - buff/cache”. In earlier version it is “used = total - free”.

“tuned” installed by default:-

The “tuned” package is installed and service is started unless disabled during installation. This has to be installed in earlier versions.

Resizing an lvm :-

As with XFS file system, resize is not possible (can't be reduced, however, file system can be increased) ( However, EXT family of file systems could be resized if built on a logical volume as a block device.

"dmesg" can print time-stamp along with data:- 

The new "util-linux" package to which "dmesg" command belongs to can print time-stamp along with messages as storaged in /var/log/dmesg. Now, users can print human readable kernel ring buffer messages using "dmesg -T" command. Most of the user utility commands under /bin are moved to /usr/bin in RHEL7.x architecture.

In case of RHEL6.x, "dmesg" command belongs to "util-linux-ng" package and which by default doesn't record time stamp and hence, data produced doesn't state when those messages are generated.

"Btrfs" has been deprecated from RHEL7.4 on-wards:- 

The "Btrfs" was made available as technology preview since RHEL6 and now Red Hat has decided to remove it from future release of RHEL7.4 on-wards. To view all functions/features which are deprecated in RHEL7, please visit the below link:

Change in wheel group membership:-

Any users added as members of the "wheel" group would by default get to execute root (administrative) commands by using 'sudo' and authenticate with their own password. However, in RHEL6.x, an administrator has to un-comment the line in /etc/sudoers so that wheel group users could get to run root commands. 

Yum groups is more meangfull now:-

There is a change in how 'yum grouplist' or 'yum groupinfo' command works in RHEL7.x. Information about a group could be displayed by using 'yum groupinfo <Group_name>' or 'yum group info <Group_name>' commands. Like-wise, 'yum grouplist' or 'yum group list' would show the installed & available groups.  The 'yum groupinfo' command would list out mandatory, default & optional packages with an indicator prefix i.e '=' (which signifies that package installed as part of group), '+' (this says that package not installed and will be installed if group is installed or updated), '-' (indicates that package is not installed, will not be installed if group is installed or updated), no marker (package is installed, but not installed as part of groupinstall). 

Root password is required to boot into rescue target:-

Since the concept of 'runlevel' changed in RHEL7 to 'targets', if a user wish to boot the system into rescue mode to resolve any early boot issues, then need to append required target as kernel parameter. Being said that, there is "" & "" could be used. So, to boot system into "", append "" to the respective kernel command line and hit "Ctrl+x". 

In earlier version, root shell would by default gets presented when booted into runlevel 1 or rescue or emergency mode, however, in RHEL7 root password is required to successfully boot into '' or ''. 


Anonymous said...

great document, helps understanding some things. However the LVM resize is not entirely correct. RedHat say only reducing size is not possible on xfs filesystem, grow while mounted still works.

SimplyLinuxFAQ said...

Yes, that is correct. I had missed to fine-tune my statement, which I've corrected now. Thanks for bringing to my notice.

Polanki Venkata padmini said...

Nice and good article.It will helpful for interview perspective.I have suggested to my friends to go through this blog. Thanks for sharing this useful information. If you want to learn Linux course in online, please visit below site.
Linux Online Training
linux course
Linux Online Training in kurnool
Linux Online Training in Hyderabad
Linux Online Training in Bangalore
Linux Online Training in Chennai
online training
online education
online learning
best career courses
trending courses