Date: Tue, 15 Oct 2013 23:28:14 +0000 From: "Teske, Devin" <Devin.Teske@fisglobal.com> To: "freebsd-sysinstall@freebsd.org" <freebsd-sysinstall@freebsd.org> Cc: Florian Smeets <flo@FreeBSD.org>, Devin Teske <dteske@freebsd.org>, "Teske, Devin" <Devin.Teske@fisglobal.com> Subject: [CFT] head/usr.sbin/bsdinstall -- Improve debugging (Round 1) Message-ID: <13CA24D6AB415D428143D44749F57D720FC6BF78@LTCFISWMSGMB21.FNFIS.com>
next in thread | raw e-mail | index | archive | help
Hi, flo@ reported to me that he was having some issues with deployment to his Soekris boxen using bsdinstall. bsdinstall wouldn't even start on his Soekris because in his deployment setup, /tmp is read-only (flo@ can provide more details than I). I wrote a patchset to fix flo@'s woes and they appear to be working. The patchset is here: http://druidbsd.cvs.sf.net/viewvc/druidbsd/bsdinstall_debug/ NOTE: There's a "Download GNU Tarball" link at the bottom. NOTE: You should use "svn patch" to apply this, not "patch" The patchset introduces: 1. Make bsdinstall(8) test to see if it can write its log file. 2. If it can't write $BSDINSTALL_LOG, it doesn't log. 3. If able to write its log file, you won't notice any functional changes. NOTE: But the log file will have more data and slightly different format. 4. You can now pass `-D file' to bsdinstall to set the log file path. -- Cheers, Devin _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13CA24D6AB415D428143D44749F57D720FC6BF78>