FreeNAS Code

Set MTU back to 1500 in case it was removed

Set MTU back to 1500 in case it was removed

Looks like dojo.hitch was not doing the right thing to destroy dialogs

This should fix a lot of strange behavior in the GUI related to
dialogs, including:
- Funky volume manager
- Tooltips not showing up in the second time for same dialog

python-pep8 test

Use editable atribute for builtin users/groups

While I'm here do some PEP8

Take leverage of editable option in django models

It excludes the fields by default from ModelForm.
This is useful for fields that shouldn' be exposed in the UI

Merge changes from trunk to 8.0.4
------------------------------------------------------------------------
r10092 | yaberauneya | 2012-02-09 22:34:38 -0800 (Thu, 09 Feb 2012) | 35 lines

make updatep* more robust

1. Use mount -o noatime to match other logic done by delphij in r9942
to reduce potential filesystem metadata corruption race by reducing
necessary filesystem updates.
2. Use temporary directories instead of hardcoded mountpoints. The
problem was twofold with the previous code:
a. Simultaneous upgrades from multiple sources could cause
corruption; this still can still happen if the update is run after
fsck+tunefs is run -- but the race is reduced.
b. Mounting the new root slice in /mnt in updatep1 has the side
effect that data could be lost in the window where */etc/fstab was
being edited; the potential window for this happening was
miniscule, but it could result in up to a couple seconds worth of
data loss if the root device media was under heavy I/O at the time
and a process or processes wrote to the root media while the pseudo
temporary mountpoint was mounted.
3. Use tar cf - | tar xpvf - instead of cp -Rf to preserve additional
file properties (cp -Rf mashes hardlinks for example).
4. Drop overly complicated pseudo mktemp -d code as real mktemp -d
is being employed.
5. Move the trap set operation further up in the code to apply to both
the first and second mount case in updatep1.
6. Fix the trap reset operation at the end of updatep2 (the previous
code executed "1" if a SIGINT or SIGTERM was received or atexit(3)
was called at the end of /bin/sh's lifetime).

More work will need to be done to "lock the system" so multiple
concurrent upgrades cannot be attempted or the user is at least
prompted to break an upgrade lock, but this is a step forward.

Verified via 2 GUI upgrades (s1 -> s2 -> s1 again) that the logic
functioned as expected.

Signed-off-by: Garrett Cooper <yanegomi@...>
------------------------------------------------------------------------
r10091 | yaberauneya | 2012-02-09 22:34:24 -0800 (Thu, 09 Feb 2012) | 9 lines

Unmount /data before reboot on failure in ix-update

/data isn't unmounted before reboot on failure which can cause filesystem
corruption if blocks aren't synched to the backing media (especially
because shutdown -r now isn't being called in ix-update). The attached
change unmounts /data which also handles sync'ing of the filesystem
according to mount(2) semantics.

Signed-off-by: Garrett Cooper <yanegomi@...>
------------------------------------------------------------------------
r10090 | yaberauneya | 2012-02-09 22:34:09 -0800 (Thu, 09 Feb 2012) | 11 lines

Add system .shrc and add mountrw alias to .cshrc and .shrc

1. Adds .shrc for the root system account (it's the interactive user
rc file used by /bin/sh, but also /usr/local/bin/bash).
2. Adds aliases for mount -wu -o noatime that we can provide to users,
support techs, devs, etc, to decrease potential for filesystem
metadata corruption. This wasn't done via a generalized script for the
simple reason that it's a generic idea that for the most part just
impacts interactive use.

Signed-off-by: Garrett Cooper <yanegomi@...>
------------------------------------------------------------------------
r10089 | yaberauneya | 2012-02-09 22:33:53 -0800 (Thu, 09 Feb 2012) | 13 lines

Use /var/home indirection instead of manipulating /home for AD/LDAP.

This change adds a single layer of indirection from /home -> /var/home
in the install image such that we no longer have to touch /home in the
when home directories are specified in the CIFS configuration when
ix-activedirectory and ix-ldap are run.

Verified sane via the AD code path with both trusted domains being set
and not being set. Please note that the ix-ldap code path is a simpler
pattern than the one found in ix-activedirectory, and thus covering
ix-activedirectory is sufficient.

Signed-off-by: Garrett Cooper <yanegomi@...>
------------------------------------------------------------------------
r10063 | yaberauneya | 2012-02-08 08:52:02 -0800 (Wed, 08 Feb 2012) | 7 lines

Using shutdown -r now instead of reboot calls rc.shutdown, which
in turn allows the system to reboot more gracefully by notifying
services that they need to stop before the system is rebooted.

Discussed-with: delphij
Reviewed-by: jpaetzel

------------------------------------------------------------------------
r10051 | yaberauneya | 2012-02-07 14:45:11 -0800 (Tue, 07 Feb 2012) | 12 lines

Remove mount -wu / and mount -ru / in ix-ldap, ix-samba, and
ix-smbpasswd as CERT_FILE is located on /usr/local/etc (which is a
memory backed disk) and smbpasswd acts on /var, which is assumed to be
either a memory disk or UFS volume (the former which doesn't require
it at all, the latter which shouldn't require it either). This should
reduce the potential for filesystem corruption.

Verified sane by running the commands standalone and analyzing the
output in truss.

Reviewed-by: delphij, jhixson

------------------------------------------------------------------------
r9942 | delphij | 2012-01-31 11:49:30 -0800 (Tue, 31 Jan 2012) | 3 lines

Use -onoatime when mounting system partitions read-write in the hope of
reducing write wearing.

Upgrade firefly to 1696_6 for feature parity with 8.0.4-*_MULTIMEDIA.

Upgrade transmission{,-cli,-daemon} to 2.42.

make updatep* more robust

1. Use mount -o noatime to match other logic done by delphij in r9942
to reduce potential filesystem metadata corruption race by reducing
necessary filesystem updates.
2. Use temporary directories instead of hardcoded mountpoints. The
problem was twofold with the previous code:
a. Simultaneous upgrades from multiple sources could cause
corruption; this still can still happen if the update is run after
fsck+tunefs is run -- but the race is reduced.
b. Mounting the new root slice in /mnt in updatep1 has the side
effect that data could be lost in the window where */etc/fstab was
being edited; the potential window for this happening was
miniscule, but it could result in up to a couple seconds worth of
data loss if the root device media was under heavy I/O at the time
and a process or processes wrote to the root media while the pseudo
temporary mountpoint was mounted.
3. Use tar cf - | tar xpvf - instead of cp -Rf to preserve additional
file properties (cp -Rf mashes hardlinks for example).
4. Drop overly complicated pseudo mktemp -d code as real mktemp -d
is being employed.
5. Move the trap set operation further up in the code to apply to both
the first and second mount case in updatep1.
6. Fix the trap reset operation at the end of updatep2 (the previous
code executed "1" if a SIGINT or SIGTERM was received or atexit(3)
was called at the end of /bin/sh's lifetime).

More work will need to be done to "lock the system" so multiple
concurrent upgrades cannot be attempted or the user is at least
prompted to break an upgrade lock, but this is a step forward.

Verified via 2 GUI upgrades (s1 -> s2 -> s1 again) that the logic
functioned as expected.

Signed-off-by: Garrett Cooper <yanegomi@...>