167 reputation
5
bio website
location
age
visits member for 2 years, 3 months
seen Nov 17 at 19:34

Sep
26
awarded  Popular Question
May
20
accepted Ignore Symlinks when Extracting Tarball
May
20
comment Ignore Symlinks when Extracting Tarball
Handy little tidbit to know, thanks! For those who may come looking later: AVFS does work, however it is not immediately available for Fedora 18 x64. It can, however be download without issue and locally installed via yum (use yum; it will grab the FUSE dependency for you). Once I was 'in' the *.tgz archive, the copy went off without a hitch.
May
20
asked Ignore Symlinks when Extracting Tarball
Apr
26
comment Creating an Alias to Loopback Interface with an Arbitrary Name
Sure. I think the approach has merit, my only concern is registering two loopback devices in the same namespace. I may be able to create another namespace that is exposed to the app stack and work around the limitation that way. Will certainly take some time, so unfortunately the results may not come quickly.
Apr
26
accepted Creating an Alias to Loopback Interface with an Arbitrary Name
Apr
26
comment Creating an Alias to Loopback Interface with an Arbitrary Name
Wow, thanks for the complete patch!
Apr
25
comment Creating an Alias to Loopback Interface with an Arbitrary Name
An interesting approach. Certainly one I am open to exploring. Reading through the source, though, raises one question. It specifically states that there is only ever allowed to be one loopback device per network namespace. Won't the existing lo and my new proposed eth0 clash in the root namespace? Or are you advocating outright replacing lo with a newly compiled driver? And, if so, will that have negative repercussions on existing apps on the system?
Apr
24
asked Creating an Alias to Loopback Interface with an Arbitrary Name
Nov
30
accepted Determining the Source of a Given File System Mount on Unix
Nov
30
awarded  Teacher
Nov
29
answered Determining the Source of a Given File System Mount on Unix
Nov
27
comment Determining the Source of a Given File System Mount on Unix
My rc.conf is pretty bare bones. I am at work, other wise I would post it directly. Long story short: it enables ZFS, sets the host name, and a few other items (Mostly related to jails). All configurations were present before the upgrade, and I verified that rc.conf was not altered. I even tried commenting out almost everything but ssh_enable, zfs_enable (note: the system root is NOT zfs), and setting the host name with no change. Can you explain a bit more on the permissions on /var and how that might cause it to be mounted to a memory disk?
Nov
25
asked Determining the Source of a Given File System Mount on Unix
Aug
16
awarded  Scholar
Aug
16
accepted FreeBSD: Remove symlinks in devfs
Aug
16
comment FreeBSD: Remove symlinks in devfs
Thanks for the detailed answer. A bit of clarification on your first point: if I am understanding correctly, the symlinks are created by the operating system for compatibility and, for example, ada0 is the drive in the first SATA port which is then linked to ad4 to provide an other style name for the same device? If that is the case, is one better to use than the other when passing in a device node to the zpool command?
Aug
16
awarded  Student
Aug
16
awarded  Supporter
Aug
16
asked FreeBSD: Remove symlinks in devfs