Skip to main content

I made a GIF!

Mounting ISO as file system for Linux and Solaris

For Linux, mount the ISO image "/iso/file.iso" to the mount point "/media/iso" using the command:
sudo mount -o loop,users -t iso9660 /iso/file.iso /media/iso
Mount the ISO image "/iso/file.iso" at boot by adding a line to the "/etc/fstab":
/iso/file.iso /media/iso udf,iso9660 ro,exec,users,loop 0 0
Sun Solaris always requires that extra effort to complete any task. Mounting an ISO on Solaris requires manually creating the loopback, then mounting it:
# /usr/sbin/lofiadm -a /export/iso/sol-companion.iso
/dev/lofi/1
# mount -F hsfs -o ro /dev/lofi/1 /mnt/iso
Afterward you can verify the block device with lofiadmin and df:
# /usr/sbin/lofiadm
Block Device File
/dev/lofi/1 /export/iso/sol-companion.iso
# df -h
Filesystem size used avail capacity Mounted on
rpool/ROOT/s10s_u7wos_08
37G 4.3G 31G 13% /
/devices 0K 0K 0K 0% /devices
[...]
/dev/lofi/1 647M 647M 0K 100% /mnt/iso
Both steps can be achieved as a single line (note that ` is not ' ):
mount -F hsfs -o ro `lofiadm -a /export/iso/sol-companion.iso` /mnt/iso
I am not covering mounting at boot because I have not tried it.

When paired w/ FTP/HTTP/NFS services, mounting ISO image allows for hosting the original ISO and the contents across a network w/o incurring double the local storage. Our Novell OES 2 Linux install source uses this capability.

Comments

Popular posts from this blog

Cisco ASA ICMP packet-tracer

Occasionally devices fail to respond to a ping.  This can result from devices being off-line, having a local firewall enabled or the perimeter firewall configuration.  The Cisco ASA ICMP packet-tracer options differ from the TCP or UDP command options.  An example is below: packet-tracer input outside icmp A.B.C.D 8 0 E.F.G.H The ICMP type is "8" (echo request) with code"0" (none).  There are no options on destination IPv4 address E.F.G.H. Complete ICMP documentation at URL http://www.iana.org/assignments/icmp-parameters/ Complete Cisco ASA packet-tracer documentation at URL http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/p.html#wp1878788

Xfce4 lock screen not working

Xfce4 would not start a screensaver on my Linux system.  Researching it, it ran xflock4 from the command line ad received an error: Property "/general/LockCommand" does not exist on channel "xfce4-session". To fix this, additional configuration needed, but no hacks. First, verify xflock4 and xfconf-query are available. $ which xflock4 xfconf-query /bin/xflock4 /bin/xfconf-query Next  install a lock screen package that provides 'xlock', 'slock', 'i3lock' or similar.  $ sudo yum install -y xlockmore-gtk i3lock Last, add an executable (with options) as /general/LockCommand in the xfce4-session settings. $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "xlock -mode matrix" --type  string $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "i3lock -c 000000" --type string Test by running xflock4 from the command line or through the GUI.

X11 Forwarding issue solved

TL;DR Disabling IPv6 necessitates SSHd AddressFamily is "inet" for X11 Forwarding to work. Issue OpenSSH assumes both IPv6 and IPv4 protocols are enabled, and default SSHd AddressFamily value "any" is valid. Quickly skimming the OpenSSH source code, it was not obvious why SSHd does not fail gracefully, selecting only an available IP address family. Therefore, for X11 Forwarding to work correctly, in /etc/ssh/sshd_config we must choose: Defaults - IPv6 enabled and SSHd AddressFamily value " any " Custom - IPv6 disabled and SSHd AddressFamily value " inet " Background PuTTY was not creating a $HOME/.Xauthority file on ssh login and no X11 applications would run, despite setting $DISPLAY.  PuTTY was correctly configured with: X11 Forwarding enabled X display location empty Remote authentication protocol MIT-Magic-Cookie-1 X authority file for local display empty On the initial ssh login there should be a .Xauthority notic