**** BEGIN LOGGING AT Mon Mar 30 02:59:57 2009 Mar 30 06:32:30 03bzhou * r9827 10optware/trunk/ (4 files in 2 dirs): Mar 30 06:32:30 inferno: svn r221 -> r381 Mar 30 06:32:30 packaged inferno-minimal for emu-g and minimal rootfs Mar 30 06:32:30 packaged inferno-devel for inferno toolchain binaries Mar 30 06:32:32 03bzhou * r9828 10optware/trunk/ (15 files in 2 dirs): inferno emu-g: a distributed OS, added & promoted for arm/x86 glibc targets Mar 30 07:41:12 i have a single disk connected to my nslu2 debian stable and considering getting another same-size disk and operating them in a raid 1 configuration. is it straightforward or does it involve any trickery to have it set up? Mar 30 14:53:48 mwester: just wanted to let you know slugos 5.4alpha seems stable so far for me. now if i could only find that memory leak in my robot code.. :) Mar 30 16:26:23 I need to rename jbot in here to one of apt, ibot, infobot, or purl. anyone care which? Mar 30 16:28:57 * TimRiker chooses infobot Mar 30 16:29:10 jbot: chanset #nslu2-linux autojoin infobot Mar 30 16:29:10 Setting autojoin for #nslu2-linux to 'infobot'; was 'jbot'. Mar 30 16:29:25 Leaving. (courtesy of timriker). Mar 30 16:29:43 ~logs Mar 30 16:29:45 All conversations are logged to http://ibot.rikers.org/channel, where "channel" is replaced by the URL-encoded channel name, such as %23freenode for #freenode. Lines starting with spaces are not logged. Mar 30 16:48:52 infobot: ? Mar 30 16:49:00 infobot: help Mar 30 16:50:02 infobot: 2^13 Mar 30 16:50:04 15 Mar 30 16:50:13 thanks infobot Mar 30 16:50:13 VoodooZ: no problem Mar 30 16:50:29 beats talking to myself.. :) Mar 30 16:53:53 2exp12 Mar 30 16:53:59 infobot: 2exp12 Mar 30 18:15:54 i have a single disk connected to my nslu2 debian stable and considering getting another same-size disk and operating them in a raid 1 configuration. is it straightforward or does it involve any trickery to have it set up? Mar 30 18:19:29 Depends on if you intend to mirror the rootfs or not. Mar 30 18:22:12 mwester: well, not necessarily. i don't mind mirroring it, but if it makes things difficult i'm willing to exclude it. i'm more concerned with my /home partition Mar 30 18:22:52 and i can always reinstall if my root fails Mar 30 18:23:16 It's debian. follow the debian instructions to mirror a non-rootfs drive, and it should Just Work(tm). Mar 30 18:23:39 If you want to mirror the rootfs, well, it's debian as well ---- but the problem there is that it's debian on the NSLU2. Mar 30 18:24:16 Debian's big achille's heel (sp?) on the NSLU2 is that it is non-recoverable if something goes wrong with your rootfs. Mar 30 18:24:35 (you have to put the disk on another Linux system, patch it up, plug it back in, and hope.) Mar 30 18:24:48 A console is almost certainly required to do the rootfs. Mar 30 18:25:08 * mwester decides not to mention that SlugOS 5.3 supports mirrored rootfs out-of-the-box. Mar 30 18:25:36 mike, you should be a salesman ;) Mar 30 18:25:42 :p I am. Mar 30 18:25:48 :D Mar 30 18:26:19 * mwester is a field tech guy, but his department actually ends up reporting to the VP of sales, rather than engineering. Mar 30 18:26:50 Rather odd, but they find that it really helps with customer satisfaction to have the tech guys part of sales at that level. An interesting idea... Mar 30 18:27:06 mwester: which would you recommend on the nslu2: rsync or raid1? (i just want to be protected against hardware disk failures) Mar 30 18:34:19 two different tools, for different purposes. RAID protects from hardware problems in a "near-fault-tolerant" manner, rsync is a backup solution that can protect data in event of any type of data loss. Mar 30 18:35:23 If you run rsync often enough, with the right flags, you can build a host-standby sort of solution. But your problem is that Debian won't boot to that drive, unlike RAID. Mar 30 18:36:03 I use both, on different systems, for different purposes. Mar 30 20:43:13 mwester: i backup from my desktop to the nslu2 (using incremental rdiff-backup), but would like to protect this backup as well as files stored solely on the nslu2 using either rsync or raid1 (can't decide). i'm not concerned about bootability (i can recreate the root partition on the event of its failure/corruption). ideally i'd mirror the whole disk, including the root partition, but i gather it's tricky with the nslu2/debian combination Mar 30 20:44:44 i tend to prefer raid1 because of its transparency Mar 30 20:46:22 and because i'm already running a backup tool daily, it seems to be tricky to find the right time for another layer of backup without overlap with the first backup or with other activity Mar 30 20:46:35 obviosly, i'm confusing myself! Mar 31 00:01:46 03bzhou * r9829 10optware/trunk/ (4 files in 2 dirs): inferno emu-g: added mipsel support; renamed inferno-devel to inferno-utils Mar 31 00:01:47 03bzhou * r9830 10optware/trunk/platforms/ (4 files): inferno emu: promoted on mipsel targets Mar 31 00:13:58 03bzhou * r9831 10optware/trunk/make/inferno.mk: inferno: made sensitive to INFERNO_PATCHES and .mk **** ENDING LOGGING AT Tue Mar 31 02:59:57 2009