<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Disqus - Latest Comments for royce</title><link>http://disqus.com/people/royce/</link><description></description><language>en</language><lastBuildDate>Thu, 15 Oct 2009 19:11:38 -0000</lastBuildDate><item><title>Re: Looking back at 100 blog posts</title><link>http://daemonicdispatches.disqus.com/looking_back_at_100_blog_posts/#comment-20161295</link><description>I like this idea!  I'm not so interested in tarsnap workflow (since it's still in the "public beta" phase, new website, etc).  But I'm quite interested in the FreeBSD security workflow.&lt;br&gt;&lt;br&gt;How much time do you spend on public/private email, how much time do you spend managing the security team (if at all -- and by "managing", I include both mentoring new members (if you do this at all) and assigning/discussing tasks)... and how much time do you spend actually looking at code?&lt;br&gt;&lt;br&gt;I find that in LilyPond, actually working on the docs or build system is almost a relief; about 70% of my time is spent on emails and management.  I'm wondering if that's something specific to documentation / website / releases  (since the first two are much more "front-line" issues that are highly visible to users), or a general curse facing high-ranked members of open-source projects.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">gperciva</dc:creator><pubDate>Thu, 15 Oct 2009 19:11:38 -0000</pubDate></item><item><title>Re: Looking back at 100 blog posts</title><link>http://daemonicdispatches.disqus.com/looking_back_at_100_blog_posts/#comment-20147498</link><description>Posts about your personal workflow methods would be educational - email handling, task management, and perhaps even motivation.  &lt;br&gt;&lt;br&gt;Either you have directed your analytical skills towards developing these methods ... or such posts would provide an opportunity to do so.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Thu, 15 Oct 2009 16:00:29 -0000</pubDate></item><item><title>Re: FreeBSD Update to 8.0-BETA1</title><link>http://daemonicdispatches.disqus.com/freebsd_update_to_80_beta1/#comment-16836810</link><description>I've often started a portupgrade run, and come back an hour later to see that it's been waiting for me to answer a configuration question.   This can be especially frustrating when performing upgrades like this one on a system with many ports.&lt;br&gt;&lt;br&gt;The solution is portupgrade's '-c' or '--config' option.  It makes portupgrade ask you all of the config dialogs at the *beginning* of the portupgrade run.  Much preferable.&lt;br&gt;&lt;br&gt;So I recommend:&lt;br&gt;&lt;br&gt;portupgrade -afc&lt;br&gt;&lt;br&gt;Enjoy!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Thu, 17 Sep 2009 17:23:31 -0000</pubDate></item><item><title>Re: scrypt version 1.1 released</title><link>http://daemonicdispatches.disqus.com/scrypt_version_11_released/#comment-9485311</link><description>i will look into that issue asap. i had to rewrite several parts of the code to work on native win32/64, /dev/urandom was one "issue".&lt;br&gt;&lt;br&gt;colin, have my mails reached your spam folder?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">akira</dc:creator><pubDate>Mon, 18 May 2009 00:01:22 -0000</pubDate></item><item><title>Re: scrypt version 1.1 released</title><link>http://daemonicdispatches.disqus.com/scrypt_version_11_released/#comment-9477695</link><description>Yep - I should have said as much.&lt;br&gt;&lt;br&gt;$ cat /dev/urandom | strings | head -1&lt;br&gt;h&amp;gt;E73</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Sun, 17 May 2009 15:04:09 -0000</pubDate></item><item><title>Re: scrypt version 1.1 released</title><link>http://daemonicdispatches.disqus.com/scrypt_version_11_released/#comment-9476282</link><description>Does /dev/urandom exist on your Cygwin machine?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cperciva</dc:creator><pubDate>Sun, 17 May 2009 14:34:44 -0000</pubDate></item><item><title>Re: scrypt version 1.1 released</title><link>http://daemonicdispatches.disqus.com/scrypt_version_11_released/#comment-9471001</link><description>$ uname -a&lt;br&gt;CYGWIN_NT-5.1 mycroft 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin&lt;br&gt;&lt;br&gt;$ ./scrypt enc scrypt.h scrypt.h.enc&lt;br&gt;Please enter passphrase: Please confirm passphrase: scrypt: Error reading salt: No error&lt;br&gt;&lt;br&gt;I threw some fprintfs into getsalt(), and neither successes nor failures seem to be triggered, which makes me think that something other than getsalt() is returning 4 to scryptenc_file.  Take that with a giant grain of salt, though; I know about two weeks' worth of C. :-)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Sun, 17 May 2009 10:49:35 -0000</pubDate></item><item><title>Re: scrypt version 1.1 released</title><link>http://daemonicdispatches.disqus.com/scrypt_version_11_released/#comment-9470609</link><description>Yes, it now builds.  Now getting the same error as da44en's Solaris 10 test:&lt;br&gt;&lt;br&gt;scrypt: Error reading clocks: Invalid argument</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Sun, 17 May 2009 10:16:48 -0000</pubDate></item><item><title>Re: scrypt version 1.1 released</title><link>http://daemonicdispatches.disqus.com/scrypt_version_11_released/#comment-9460493</link><description>If you edit config.h and take out the HAVE_SYS_ENDIAN_H line, does that unbreak the build?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cperciva</dc:creator><pubDate>Sat, 16 May 2009 20:24:52 -0000</pubDate></item><item><title>Re: scrypt version 1.1 released</title><link>http://daemonicdispatches.disqus.com/scrypt_version_11_released/#comment-9458991</link><description>Another stop - some semi-duplicate lines removed for brevity:&lt;br&gt;&lt;br&gt;gcc  -g -O2   -o scrypt main.o scryptenc.o  crypto_aesctr.o sha256.o memlimit.o  warn.o scrypt_cpuperf.o  scrypt-nosse.o -lcrypto -lrt&lt;br&gt;&lt;br&gt;scryptenc.o(.text+0x718): In function `scryptenc_setup':&lt;br&gt;/arpa/tz/t/tycho/src/scrypt-1.1.1/scryptenc.c:207: undefined reference to `be32enc'&lt;br&gt;&lt;br&gt;crypto_aesctr.o(.text+0x144): In function `crypto_aesctr_stream':&lt;br&gt;/arpa/tz/t/tycho/src/scrypt-1.1.1/crypto_aesctr.c:95: undefined reference to `be64enc'&lt;br&gt;&lt;br&gt;sha256.o(.text+0x10c):/arpa/tz/t/tycho/src/scrypt-1.1.1/sha256.c:58: undefined reference to `be32dec'&lt;br&gt;sha256.o(.text+0x3228): In function `PBKDF2_SHA256':&lt;br&gt;&lt;br&gt;scrypt-nosse.o(.text+0x8c8): In function `smix':&lt;br&gt;/arpa/tz/t/tycho/src/scrypt-1.1.1/scrypt-nosse.c:220: undefined reference to `le32enc'</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Sat, 16 May 2009 18:50:32 -0000</pubDate></item><item><title>Re: scrypt version 1.1 released</title><link>http://daemonicdispatches.disqus.com/scrypt_version_11_released/#comment-9458681</link><description>Thanks!  It looks like NetBSD only added RLIMIT_AS recently, in spite of it being required by POSIX.  Could you try wrapping the RLIMIT_AS check in memlimit.c with #ifdef RLIMIT_AS ... #endif and let me know if that fixes the build?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cperciva</dc:creator><pubDate>Sat, 16 May 2009 18:25:39 -0000</pubDate></item><item><title>Re: scrypt version 1.1 released</title><link>http://daemonicdispatches.disqus.com/scrypt_version_11_released/#comment-9458593</link><description>Compiles and verifies fine on CentOS 4.7 i686:&lt;br&gt;&lt;br&gt;$ uname -a&lt;br&gt;Linux &lt;a href="http://vps.alpca.org" rel="nofollow"&gt;vps.alpca.org&lt;/a&gt; 2.6.18-028stab060.8 #1 SMP Mon Feb 9 20:25:36 MSK 2009 i686 i686 i386 GNU/Linux&lt;br&gt;$ cat /proc/version&lt;br&gt;Linux version 2.6.18-028stab060.8 (root@rhel5-64-build) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Mon Feb 9 20:25:36 MSK 2009&lt;br&gt;$ cat /etc/redhat-release&lt;br&gt;CentOS release 4.7 (Final)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Sat, 16 May 2009 18:18:23 -0000</pubDate></item><item><title>Re: scrypt version 1.1 released</title><link>http://daemonicdispatches.disqus.com/scrypt_version_11_released/#comment-9458510</link><description>Your target demographic may not be running on a NetBSD 2.x system running on Alpha, but just in case ...&lt;br&gt;&lt;br&gt;tycho@sdf$ uname -a&lt;br&gt;NetBSD sdf 2.1.0_STABLE NetBSD 2.1.0_STABLE (sdf) #0: Fri Mar 30 02:24:32 UTC 2007  root@ol:/var/sys/arch/alpha/compile/sdf alpha&lt;br&gt;&lt;br&gt;tycho@sdf$ ./configure&lt;br&gt;checking for a BSD-compatible install... /usr/pkg/bin/ginstall -c&lt;br&gt;checking whether build environment is sane... yes&lt;br&gt;checking for a thread-safe mkdir -p... /usr/pkg/bin/gmkdir -p&lt;br&gt;checking for gawk... gawk&lt;br&gt;checking whether make sets $(MAKE)... yes&lt;br&gt;checking whether to enable maintainer-specific portions of Makefiles... no&lt;br&gt;checking for gcc... gcc&lt;br&gt;checking for C compiler default output file name... a.out&lt;br&gt;checking whether the C compiler works... yes&lt;br&gt;checking whether we are cross compiling... no&lt;br&gt;checking for suffix of executables...&lt;br&gt;checking for suffix of object files... o&lt;br&gt;checking whether we are using the GNU C compiler... yes&lt;br&gt;checking whether gcc accepts -g... yes&lt;br&gt;checking for gcc option to accept ISO C89... none needed&lt;br&gt;checking for style of include used by make... GNU&lt;br&gt;checking dependency style of gcc... gcc3&lt;br&gt;checking how to run the C preprocessor... gcc -E&lt;br&gt;checking for grep that handles long lines and -e... /usr/bin/grep&lt;br&gt;checking for egrep... /usr/bin/grep -E&lt;br&gt;checking for ANSI C header files... yes&lt;br&gt;checking for sys/types.h... yes&lt;br&gt;checking for sys/stat.h... yes&lt;br&gt;checking for stdlib.h... yes&lt;br&gt;checking for string.h... yes&lt;br&gt;checking for memory.h... yes&lt;br&gt;checking for strings.h... yes&lt;br&gt;checking for inttypes.h... yes&lt;br&gt;checking for stdint.h... yes&lt;br&gt;checking for unistd.h... yes&lt;br&gt;checking err.h usability... yes&lt;br&gt;checking err.h presence... yes&lt;br&gt;checking for err.h... yes&lt;br&gt;checking sys/endian.h usability... yes&lt;br&gt;checking sys/endian.h presence... yes&lt;br&gt;checking for sys/endian.h... yes&lt;br&gt;checking sys/sysinfo.h usability... no&lt;br&gt;checking sys/sysinfo.h presence... no&lt;br&gt;checking for sys/sysinfo.h... no&lt;br&gt;checking for clock_gettime in -lrt... yes&lt;br&gt;checking for clock_gettime... yes&lt;br&gt;checking for sysinfo... no&lt;br&gt;checking for posix_memalign... no&lt;br&gt;checking for struct sysinfo... no&lt;br&gt;checking for struct sysinfo.mem_unit... no&lt;br&gt;configure: creating ./config.status&lt;br&gt;config.status: creating Makefile&lt;br&gt;config.status: creating config.h&lt;br&gt;config.status: executing depfiles commands&lt;br&gt;&lt;br&gt;tycho@sdf$ make&lt;br&gt;make  all-am&lt;br&gt;gcc -DHAVE_CONFIG_H -I.      -g -O2 -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.c&lt;br&gt;mv -f .deps/main.Tpo .deps/main.Po&lt;br&gt;gcc -DHAVE_CONFIG_H -I.      -g -O2 -MT scryptenc.o -MD -MP -MF .deps/scryptenc.Tpo -c -o scryptenc.o scryptenc.c&lt;br&gt;mv -f .deps/scryptenc.Tpo .deps/scryptenc.Po&lt;br&gt;gcc -DHAVE_CONFIG_H -I.      -g -O2 -MT crypto_aesctr.o -MD -MP -MF .deps/crypto_aesctr.Tpo -c -o crypto_aesctr.o crypto_aesctr.c&lt;br&gt;mv -f .deps/crypto_aesctr.Tpo .deps/crypto_aesctr.Po&lt;br&gt;gcc -DHAVE_CONFIG_H -I.      -g -O2 -MT sha256.o -MD -MP -MF .deps/sha256.Tpo -c -o sha256.o sha256.c&lt;br&gt;mv -f .deps/sha256.Tpo .deps/sha256.Po&lt;br&gt;gcc -DHAVE_CONFIG_H -I.      -g -O2 -MT memlimit.o -MD -MP -MF .deps/memlimit.Tpo -c -o memlimit.o memlimit.c&lt;br&gt;memlimit.c: In function `memlimit_rlimit':&lt;br&gt;memlimit.c:138: error: `RLIMIT_AS' undeclared (first use in this function)&lt;br&gt;memlimit.c:138: error: (Each undeclared identifier is reported only once&lt;br&gt;memlimit.c:138: error: for each function it appears in.)&lt;br&gt;*** Error code 1&lt;br&gt;&lt;br&gt;Stop.&lt;br&gt;make: stopped in /arpa/tz/t/tycho/src/scrypt-1.1.1&lt;br&gt;*** Error code 1&lt;br&gt;&lt;br&gt;Stop.&lt;br&gt;make: stopped in /arpa/tz/t/tycho/src/scrypt-1.1.1</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Sat, 16 May 2009 18:11:59 -0000</pubDate></item><item><title>Re: Comments Enabled</title><link>http://umamichan.disqus.com/comments_enabled/#comment-7228355</link><description>I, for one, welcome our new comment overlords.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Sun, 15 Mar 2009 00:41:21 -0000</pubDate></item><item><title>Re: Amazon's Wish Lists ate my baby</title><link>http://roycebits.disqus.com/amazons_wish_lists_ate_my_baby/#comment-3324117</link><description>Hey, good idea to look at the &lt;a href="http://Amazon.com" rel="nofollow"&gt;Amazon.com&lt;/a&gt; source - I'll check it out.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Mon, 27 Oct 2008 10:19:22 -0000</pubDate></item><item><title>Re: Daemonic Dispatches: Now with comments</title><link>http://daemonicdispatches.disqus.com/thread/#comment-680942</link><description>Too many comments like that, and I'll turn off commenting entirely. :-)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">cperciva</dc:creator><pubDate>Sun, 15 Jun 2008 19:13:29 -0000</pubDate></item><item><title>Re: Daemonic Dispatches: Now with comments</title><link>http://daemonicdispatches.disqus.com/thread/#comment-680928</link><description>I, for one, welcome our new comment overlords.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Sun, 15 Jun 2008 19:08:27 -0000</pubDate></item><item><title>Re: moving to mars</title><link>http://roblef.disqus.com/moving_to_mars/#comment-582197</link><description>I agree - &lt;a href="http://www.space.com/news/060613_ap_hawking_space.html" rel="nofollow"&gt;and so does Stephen Hawking&lt;/a&gt;.&lt;br&gt;&lt;br&gt;Great minds think alike.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">royce</dc:creator><pubDate>Tue, 03 Jun 2008 16:24:31 -0000</pubDate></item><item><title>Re: comment here</title><link>http://roblef.disqus.com/comment_here/#comment-371782</link><description>These aren't the packets you're looking for.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Royce</dc:creator><pubDate>Wed, 23 Apr 2008 16:15:15 -0000</pubDate></item><item><title>Re: comment here</title><link>http://roblef.disqus.com/comment_here/#comment-371777</link><description>These aren't the packets you're looking for.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Royce</dc:creator><pubDate>Wed, 23 Apr 2008 16:14:33 -0000</pubDate></item><item><title>Re: Gmail Sender header</title><link>http://vafer.disqus.com/gmail_sender_header/#comment-18529304</link><description>If the non-Google domain that you're using in Gmail has a published SPF record that doesn't include Google in its list of authorized sending IP space, perhaps this provides for a workaround?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Royce Williams</dc:creator><pubDate>Fri, 11 Apr 2008 13:06:06 -0000</pubDate></item></channel></rss>