We all know what 127.0.0.1 is used for (loopback).
What are uses cases for the rest of the reserved 127.0.0.0/8 loopback space?
This may be a bit of a noobish question, but I was taking a look at /etc/hosts on my new Xubuntu install and saw this:
127.0.0.1 localhost
127.0.1.1 myhostname
On most 'nixes I've used, the second line is omitted, and if I want to add my hostname to the hosts file, I'd just do this:
127.0.0.1 localhost myhostname
Is there a difference between these two files in any practical sense?
I wonder if it is tied to my NIC at all or if the OS or driver intercepts and immediately returns data sent to the loopback address?
Does the signal actually travel to my NIC then the NIC returns it?
I have a development environment set up where I have a separate loopback address for multiple websites.
For example, I have the following:
127.0.0.1 www.example.com
127.0.0.2 foo.example.com
127.0.0.3 bar.example.com
127.0.0.4 waffles.example.com
I'd like an equivalent solution for IPv6.
I already know that you can use ::1 as a loopback address, but ::2, ::3, etc don't seem to work.
Are there any other loopback addresses in IPv6? Is there a way to have multiple unique loopback addresses?
How can block files be mounted on osx? I tried
hdiutil attach filename
however this is terminating with
hdiutil: attach failed - not recognized
hdiutil only seems to work for iso/dmg images. On ubuntu the block file can easily be mounted with
mount -o loop filename mountpoint
Background: I used vdfuse (http://forums.virtualbox.org/viewtopic.php?f=26&t=33355&start=0) to mount virtual disk files (e.g. vhd). vdfuse itself works fine and the partitions contained in the virtual disc appear as block files on the mount point.
VHD File -> /my/mountpoint/Partition1, Partition2, ...
On ubuntu the block files can be mounted via
mount -o loop /my/mountpoint/Partition1
however the -o loop option does not exist on osx.