summaryrefslogtreecommitdiffstats
path: root/etc/rc.firmware
Commit message (Collapse)AuthorAgeFilesLines
* Remove -U from mtree call used to restore files permissions, this is ↵Renato Botelho2015-03-111-1/+1
| | | | replacing symlink targets by the old values. Ticket #4328
* Firmware upgrade script text changesPhil Davis2015-02-041-10/+10
| | | | | while I am looking at this, might as well correct these. No function problems or impact.
* Make sure scripts have necessary attributes and use its shebang line instead ↵Renato Botelho2014-07-111-2/+8
| | | | of force sh to call it. This will help to prevent or workaround issues similar to #3749 in the future
* In some cases, new /bin/sh binary doesn't work properly before reboot during ↵Renato Botelho2014-07-111-2/+2
| | | | a upgrade, and because of that /etc/rc.reboot is not executed and system doesn't reboot. Source /etc/rc.reboot instead of open a new sh session to avoid it happening again in future versions (ticket #3749)
* Add one more seatbelt to prevent tar to attempt to overwrite /dev itemsRenato Botelho2014-07-041-1/+1
|
* Avoid keeping old files from previous sessions on /tmp/configbakRenato Botelho2014-06-131-0/+1
|
* Make sure check_reload_status is stopped so it can be upgraded and no events ↵Ermal2014-05-281-1/+3
| | | | disturb the upgrade.
* Update rc.firmwareky410832013-04-171-2/+3
| | | | | | | | | Previous USB patch to add 4MB to partition size calculation was not only not working, but worse, causing dev's to close all related tickets as duplicates when it clearly still needed fixing. Also, some dev's cited that "the CF install base is so much larger it's not worth breaking". Well, you've already broken it by adding a 4MB buffer for USB, which doesn't work. Either patch it right at 6MB, or completely take out the buffer all together to "fix" CF upgrades again. Why sit on a double broken patch? PoC: EVERY USB flash based install in place upgrade was failing by exactly 2MB. Added this patch to my 2.0.2 system after a failed 2.0.3 upgrade and boom, upgraded to 2.0.3 without issue. You're welcome ;-)
* gitsync: Add --minimal parameter that installs only the updated files.Erik Fonnesbeck2012-09-171-0/+3
|
* Be more verbose during upgrade to see why nanobsd isn't carrying over the ↵jim-p2012-07-081-0/+2
| | | | setting as expected.
* make use of the correct file to send notificationsWarren Baker2012-05-111-4/+4
|
* Setup serial bits after upgrade on NanoBSD, too.jim-p2011-10-311-1/+1
|
* Add option to perform full backup prior to upgrade. First commit of 2011 ↵Scott Ullrich2011-09-251-0/+6
| | | | pfSense hackathon!
* USB slices are under-reported even more than CF slices when viewed directly, ↵jim-p2011-08-031-1/+4
| | | | instead of when looking at the entire disk. Compensate by adding a few MB. Fixes NanoBSD upgrades when installed on USB thumbdrives. (Imaged after this fix, someone can apply this fix locally and then upgrade as well.)
* We no longer use /var/run/config.lock - catch up to other progress. Also, ↵jim-p2011-01-121-1/+0
| | | | use lockf to test if the config is locked now, with a 30 second timeout.
* Copy /boot/loader.conf.local to the newly imaged slice. Ticket #892Erik Fonnesbeck2010-11-141-0/+6
|
* Use rc.firmware_notify to send a message when upgrade starts and completedScott Ullrich2010-07-301-2/+6
|
* Broadcast when a firmware upgrade is completedScott Ullrich2010-07-301-0/+6
|
* Use cp -p to preserve permissions (exec)jim-p2010-07-291-1/+1
|
* Save the old shutdown binary in an attempt to smooth a firmware upgrade that ↵jim-p2010-07-291-0/+2
| | | | crosses to/from 32/64-bit.
* Remove logs from temp config backup so they aren't clobbered when restored.jim-p2010-05-251-0/+6
|
* Standardize upgrade log filenamesjim-p2010-05-251-2/+2
|
* Backup all of /conf including subdirectories during upgrade instead of just ↵jim-p2010-05-251-4/+4
| | | | files in /conf/
* Insulate some variables as they are used.jim-p2010-05-241-35/+20
|
* Add missing unmount calls.Ermal Luçi2010-03-081-1/+2
|
* Note that the file will be labeled nanobsd upgradesullrich2009-12-091-1/+1
|
* Patch from Ron Lockard that fixed restore_chflags due to a STDOUT ↵Scott Ullrich2009-11-131-3/+3
| | | | redirection issue
* Correctly note that the pfSenseupgrade is startingsullrich2009-10-221-1/+1
|
* Remove upgrade IMG file after failureScott Ullrich2009-10-131-0/+4
|
* Remove image file when error occour because image file is greater than ↵Renato Botelho2009-09-161-0/+1
| | | | partition size
* Add 1 meg to on size disk imageScott Ullrich2009-09-101-0/+1
|
* Remove /var/run/firmware.lock as wellScott Ullrich2009-09-101-3/+8
|
* Show what each of the numbers are during a upgrade size failure checkScott Ullrich2009-09-101-1/+1
|
* Show size of detected on disk partition and size of upgrade fileScott Ullrich2009-07-241-1/+1
|
* Minor commnetsScott Ullrich2009-07-231-1/+3
|
* Set kern.geom.debugflags=16Scott Ullrich2009-07-221-0/+4
|
* Add a seatbelt check to ensure the on disk partition is the same size (or ↵Scott Ullrich2009-07-071-0/+12
| | | | larger) and bail if it has any issues.
* Set boot slice correctly (reversed logic)Scott Ullrich2009-07-051-1/+0
|
* Add and use fdisk_upgrade_log.txtScott Ullrich2009-07-051-38/+39
|
* Send file list to its own logfileScott Ullrich2009-07-051-1/+1
|
* Remove foot shooting code that was commented out. It is not necessary for ↵Scott Ullrich2009-07-051-11/+2
| | | | this. Enhance a comment about why we need boot0cfg
* Use obs and gzip -dcScott Ullrich2009-07-051-2/+2
|
* Set active partition with boot0cfg tooScott Ullrich2009-07-051-3/+3
|
* Use bzcatScott Ullrich2009-07-051-2/+6
|
* Remove debugflags and boot0cfg. NanoBSD does not use either of these when ↵Scott Ullrich2009-07-051-12/+12
| | | | upgrading.
* Reset log file on each invocationScott Ullrich2009-07-041-0/+4
|
* Use fsck_ufsScott Ullrich2009-07-041-2/+2
|
* Get a complete find prinout of disk structureScott Ullrich2009-07-041-0/+4
|
* Use 64k block sizeScott Ullrich2009-07-041-1/+1
|
* Use same block size (64k) as builder scripts.Scott Ullrich2009-07-041-1/+1
|
OpenPOWER on IntegriCloud