**** BEGIN LOGGING AT Mon Aug 11 02:59:57 2008 Aug 11 08:56:07 03oleo * r8882 10optware/trunk/ (20 files in 3 dirs): Transmission: split transmission and transmssiond - Clutch will depend on transmissiond until upgraded Aug 11 13:50:54 03oleo * r8883 10optware/trunk/Makefile: transmissiond: added to packages Aug 11 18:01:20 03fcarolo * r8884 10optware/trunk/ (4 files in 2 dirs): torrentflux: fixes for search modules Aug 11 18:08:00 03fcarolo * r8885 10optware/trunk/sources/torrentflux/sqlite_torrentflux.sql: torrentflux: fixes for search modules Aug 11 22:35:51 heyyyy... anyone still up? Aug 11 23:55:50 does anyone know why my /share/flash/data directory seems to have a mirror of my root? Aug 11 23:56:28 that is the main directory, that is pivot-rooted to the root directory Aug 11 23:56:54 bash-3.2# df Aug 11 23:56:55 Filesystem 1K-blocks Used Available Use% Mounted on Aug 11 23:56:55 rootfs 240125792 105413980 134711812 44% / Aug 11 23:57:46 so on bootup i believe a pivotroot is done, this is for unslung so that the original linksys stuff can still work without having to edit all the paths to point to /opt etc Aug 11 23:58:34 So unslung is actually installed into /share/flash/data Aug 11 23:59:58 and on bootup, the linksys stuff in the root (/) is initially loaded as per stock NSLU2, it is then pivoted so that the flash linksys stuff is "logically" moved across to /initrd, and the /share/flash/data is logically moved across to /. Aug 12 00:01:47 i was afraid it would be something complicated sounding like that :) so i guess it is not wise to delete this folder? Aug 12 00:02:27 no. It isn't a mirror, just a virtual representation so to speak. It is actually root that is the virtual representation, /share/flash/data is the real deal Aug 12 00:02:51 mount and df are your friends, learn their output Aug 12 00:03:15 omg, so when i'm browsing /, im actually browsing and editing files in /shared/flash/data? Aug 12 00:03:24 yep Aug 12 00:03:25 i will learn it, soon :) Aug 12 00:03:38 this is for unslung Aug 12 00:04:07 i guess for a f/w that completely replaces all the linksys stuff, there is no need to do the pivoting from HDD etc if it is setup right Aug 12 00:05:05 right. i guess this is all done, like you say, so that when linksys stuff looks for things it. Aug 12 00:05:15 i will probably install debian soon anyhow Aug 12 00:05:24 yep, this is so you can run the linksys code but off the HDD Aug 12 00:05:52 all the good stuff goes into /opt Aug 12 00:06:28 do you know what the stuff in /share/flash/data/share/hdd/data is for also? is the contents of /data there important as i deleted it a few days ago. it doesnt seem to have messed anything up tho... Aug 12 00:07:08 hmm, have you rebooted it since then? Aug 12 00:07:14 yep Aug 12 00:07:34 Remember, /share/flash/data/share/hdd/data is a virtual representation, and the real deal is /share/hdd/data Aug 12 00:07:47 kind of backwards to before I suppose Aug 12 00:07:59 ah, yep, sry...i meant: /share/hdd/data Aug 12 00:08:22 It is /share/flash/conf (or /share/hdd/conf) that you can't delete actually Aug 12 00:08:51 no i didnt touch that as i saw a load of confs there and thought otherwise ;) Aug 12 00:09:02 it was just the /data stuff Aug 12 00:09:15 If your normal unslung is on /share/flash/data, then /share/hdd/data is the other usb port Aug 12 00:09:38 it should be empty if you don't have a second usb drive connected Aug 12 00:09:56 right, yes, i havent connected a flash as yet Aug 12 00:10:20 (this /share/hdd/data /share/hdd/conf are mount points for when you put in a natively formatted drive to mount its file system to) Aug 12 00:10:37 bash-3.2# mount Aug 12 00:10:38 usbdevfs on /proc/bus/usb type usbdevfs (rw) Aug 12 00:11:13 See, this shows the scsi/usb port sda, parition1 mounted to root and to /share/flash/data Aug 12 00:11:52 the only confusing bit is that /initrd, which is the internal flash point (when it is pivoted) shows /dev/sda1 too, but you can tell it is flash because of the jff2 Aug 12 00:11:55 jffs2 Aug 12 00:13:30 right, i think i get you. so if i write any scripts to access a connected usb, for example, /share/flash/hdd/data is what i use? Aug 12 00:13:43 to access foiles on it? Aug 12 00:13:48 *files Aug 12 00:13:48 the real issue is that on unslung, the mounting of disks is controlled by Linksys proprietary binary applications. Aug 12 00:13:59 if it was formatted by the linksys app... hello rod Aug 12 00:14:24 and lynksys is lame :) Aug 12 00:14:36 ahh yes, so we are stuck with /share/flash based on the linksys ideas Aug 12 00:15:07 i dunno where a fat32 usb stick mounts to Aug 12 00:15:14 or an ntfs pc hdd Aug 12 00:15:15 Linksys produce a consumer device which does pretty much what it's intended to do. They don't intend to create a user-expandable device, so don't need to have clear mount points. Aug 12 00:15:50 Anyone who knows what a mount point is should probably move to SlugOS or Debian firmware anyway. Aug 12 00:15:58 :-) Aug 12 00:16:08 yep, thats true. i guess the easy solution is to just install debian later Aug 12 00:16:27 rwhitby, i barely know it...which is why i wioill stick to unslung for a little longer ;) Aug 12 00:16:30 I stuck with the linksys/unslung because it does what i need mainly Aug 12 00:17:06 which is a network file share reasonably easily controlled from a web page, and a tonne of mods from unslung ipkg Aug 12 00:17:20 and a few mods from Tony Incorporated (c) :-) Aug 12 00:17:24 tonymy01: I actually intentionally installed Unslung on a slug the other month, specifically to get the 2.4 kernel USB implementation, cause recent kernels do not work better (and actually work worse) with the strange Topfield USB interface. Aug 12 00:17:58 I cut it down so I now have Unslung-lite running from flash, with ftpd-topfield in the internal flash. Aug 12 00:18:16 so you have a few spare slugs rod I suppose Aug 12 00:19:18 I have 4 - BlueSlug and ToppySlug at home, then ObeseSlug and DevSlug on the test rig at work. Aug 12 00:19:24 None spare :-) Aug 12 00:20:02 guys, just one thing. i am setting up a rsync backup script. with all this virtual root linking stuff, should i be backing-up the "real" root (/) or this root in "shared"? Aug 12 00:20:34 and in any case, i guess i should exclude "shared" itself from the backup as it would be recursive? Aug 12 00:23:59 i think do /share/hdd/data, to avoid any recursive, but you may miss other mounted filesystems that you may want to back up Aug 12 00:27:08 I think rsync itself can be made to avoid recursion also Aug 12 00:32:39 hehe, ok, well that wont work because i deleted all the stuf in /share/hdd/data a few days ago :) Aug 12 00:32:51 urgh, i think i might have messed things up Aug 12 00:33:32 i might have meant /share/flash/data, it depends on where you have your drive plugged in Aug 12 00:33:56 ah, ok, so flash and hdd are bound to the physical ports? Aug 12 00:34:19 yep, kind of Aug 12 00:34:22 i have my hd in disk 2 port Aug 12 00:34:24 ok Aug 12 00:34:48 so all i deleted was my "flash" drive contents Aug 12 00:34:51 thats ok Aug 12 00:35:05 I think things changed when linksys introduced ntfs support, but essentially if you have the same f/w version, it should be the some Aug 12 00:35:38 (or was that "which drive should I unsling to" recommendations changed.... that might be it, fading brain cells) Aug 12 00:36:39 just type "df" to find out where you are definitely unslung to Aug 12 00:36:50 hehe, im finding it a bit confussing...but its gradually sinking in :) Aug 12 00:36:58 ill do that Aug 12 00:37:03 this will tell you the device also (sda or sdb) Aug 12 00:38:03 i find it confusing too, and I have been playing with it for maybe 4 years Aug 12 00:39:10 try plugging in a second (bigger) drive, and copying your old stuff across and getting it to work the same way again, lots of mounts all over the place, linksys decides to use a bit of both drives for the system info, lots of fiddling and *finally* get it to bootup as you wanted Aug 12 00:39:31 with your passwords etc intact Aug 12 00:40:20 ok, df says sda1 has used 1.3 mb, and sda2 only 4k. so I guess its unslung on sda1 which is mounted as /share/flash/data Aug 12 00:40:47 that makes sense as i had no bad effects deleting fron hdd Aug 12 00:40:53 those are 1k blocks remember, so is that meg or gig? Aug 12 00:41:11 ah, ok...so 1gig? Aug 12 00:41:21 i guess Aug 12 00:41:49 so this is my drive size: 240125792 Aug 12 00:42:06 which is 240,125,792x1K=240G Aug 12 00:42:37 my sda2 is 116meg Aug 12 00:42:59 this is the linksys partition that contains all the passwords and stuff Aug 12 00:44:52 er, it is saying sda1 has 57431292 1k-blocks and of those blocks 1339952 are used Aug 12 00:44:57 for sda2... Aug 12 00:45:15 ok, right i see ! Aug 12 00:46:16 So you are using a 60G drive by the looks of it Aug 12 00:47:31 yep its a 60G drive Aug 12 00:47:49 so sda1 and sda2 are just partitions on the same drive :/ Aug 12 00:47:54 yep Aug 12 00:48:01 urgh, linux is confussing :P Aug 12 00:48:06 and there is a third partition used for the swap space Aug 12 00:48:31 thats /dev/root right? Aug 12 00:48:39 6528 blocks Aug 12 00:49:21 for some reason the mount command I have doesn't show the swap mount to /dev/sda3 Aug 12 00:49:54 my print out doesnt even show a "swap" :D Aug 12 00:50:08 it is the "slingbox" mount, I have noticed other linux mount commands will show it Aug 12 00:50:44 right, dogy compiler settings on mount/df commands ... i guess :) Aug 12 00:50:47 nope, /dev/root is the root filesystem that the slug boots off, from the flash Aug 12 00:50:58 notice it is mounted to /initrd? Aug 12 00:51:08 yep, i see that Aug 12 00:51:52 So /share/blah/data and / are pivoted, and the old / is pivoted to /initrd (so you can still alter the behavour of the flash if you really want) Aug 12 00:53:47 when you say "pivoted" are you saying that they are considered as the same when referenced? is that what pivoting is? Aug 12 00:53:55 i need to install putty. WinSCP's native command shell suxx! Aug 12 00:54:22 no, pivoting is telling the filesystem to refer to that point a different way Aug 12 00:54:57 so instead of accessing the flash stuff (original linksys with some unslung tweaks only) with "/", once pivoted you access with /initrd Aug 12 00:55:24 i am trying to find the bootup sequence to find out exactly the process just now Aug 12 00:56:24 bingo... in /initrd, there is a file called "linuxrc". This does all the magic Aug 12 00:57:17 so when it first boots, it loads that up, and that is what detects the HDD and sees the little ".sda1root" or ".sda2root" unslung "signals" to tell it how to mount and pivot Aug 12 00:58:45 that is the beginning stage of the bootup, then it starts loading stuff in /etc/rc.d Aug 12 00:59:27 anyway, this is "advanced slug bootup and mounting"... more than you need to know for a new introduction to the nslu2 Aug 12 01:00:09 yes, definitely more than i need...but interesting! i'm kind of getting it :) Aug 12 01:00:19 but ill need to do a LOT more reading forst :) Aug 12 01:00:49 at least i now know what the shared stuff is now and how to best backup. which is really what was bugging me Aug 12 01:01:39 I have spent about a year looking at 2 or 3 embedded system type linux setups (in my Asus ADSL2 wireless router, and in a High Definition PVR, and of course in the SLUG) so am slowly getting familiar with some of the bootup sequence. I still don't know any kernel stuff yet though.. Aug 12 01:06:05 the kernel stuff is just scary :) but i recently bought a GP2X (linux handheld game console) and my eeepc with linux installed will arrive tommorow. plus, i am really getting sick of Windows (shitty Vista) so i cant put off learning a bit more of linux, really. :) Aug 12 01:06:28 i just wish all these years with Windows hadnt turnt me into such a lamer :) Aug 12 01:06:45 the slug is what got me into linux actually Aug 12 01:06:57 i still run xp on my main machine though Aug 12 01:07:07 i am typing to you from trillian running on my xp machine Aug 12 01:07:42 (with a remote desktop session from work.. it is 11am here in Aussieland, tunnelling thru an SSH session to my slug) Aug 12 01:08:11 this is one of the nice things with putty actually Aug 12 01:08:41 you setup ssh on the slug, and run putty on your remote machine, and then can tunnel any port you want from the remote machine to your local network **** ENDING LOGGING AT Tue Aug 12 02:59:56 2008