**** BEGIN LOGGING AT Sat Sep 05 02:59:58 2015 Sep 05 03:00:13 ~sb Sep 05 03:00:13 [scratchbox] a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, hosted by maemo now. Also at http://maemo.merlin1991.at/files/SB Sep 05 03:00:28 == http://maemovmware.garage.maemo.org/2nd_edition/ Sep 05 03:02:29 and in ~flashing wiki you find all the info you need, basically Sep 05 03:03:13 (So what is the diff between...) simply look at the filenames, it's almost obvious Sep 05 03:03:24 SCANDINAVIA_PR_EMMC_MR0_ARM.bin Sep 05 03:03:33 SEAP_PR_EMMC_MR0_ARM.bin, Sep 05 03:03:45 CENTRAL-EUROPE_PR_EMMC_MR0_ARM.bin Sep 05 03:04:03 IBERIA_PR_EMMC_MR0_ARM.bin, Sep 05 03:04:18 DocScrutinizer05: Woo! Sep 05 03:04:46 I just made the thread post. Is it pretty much just language? Sep 05 03:06:23 DocScrutinizer05: Does installing one over the other screw up stuff or miss stuff, etc, etc, etc...? Sep 05 03:10:03 DocScrutinizer05: You say 1.3.1 comes with CSSU. Do I understand that you meant: Sep 05 03:10:13 - CSSU will do the same updates Sep 05 03:10:21 - 1.3.1 Actually HAS CSSU? Sep 05 03:10:26 Which of the two? =) Sep 05 03:10:30 no, pretty much just which songs come with it I guess Sep 05 03:11:13 And I say 1.3.1 comes with *one* update that CSSU shipped before 1.3.1 came out Sep 05 03:11:52 that's why CSSU asks for *either* 1.3 *or* 1.3.1, doesn't make a difference Sep 05 03:11:58 Copy that Sep 05 03:12:17 DocScrutinizer05: Ok, I can proceed with my work then. You're being VERY helpful with this and it is much appreciated! Sep 05 03:12:26 yw Sep 05 03:12:30 I'm converting the stock deb list to a CSV and will upload shortly Sep 05 03:20:16 let's see if there's more in the backscroll I could comment Sep 05 03:21:27 [2015-09-05 Sat 03:04:46] Interesting. No more ability to get the original software from Nokia I see Sep 05 03:21:28 [2015-09-05 Sat 03:05:55] 2015-09-04 21:05:47 ERROR 404: Not Found. Sep 05 03:21:30 incorrect Sep 05 03:22:19 [2015-09-05 Sat 02:14:25] fixed Sep 05 03:29:03 Yeah, I caught the link DocScrutinizer05 Sep 05 03:29:28 DocScrutinizer05: I mentioned that because I'm all about "trust", and though much trust goes into inheritance, for "this, whatever it is" to "work", trust must be involved. Sep 05 03:29:42 DocScrutinizer05: But, i was able to pull 1.3.1 from nokia domain Sep 05 03:30:26 Holy crap 1742 .debs by default Sep 05 03:30:27 wtf. Sep 05 03:30:56 for trust issues I added md5sum check Sep 05 03:32:24 DocScrutinizer05: yep, I saw that; it's how I do things too =) Sep 05 03:32:33 DocScrutinizer05: I think u and me see eye to eye on this stuff. Sep 05 03:32:37 DocScrutinizer05: Excited to work with you Sep 05 03:32:58 which has the 'funny' side effect that my script refuses to flash VANILLA patches for partition size Sep 05 03:54:27 anyway what the script *really* does is to make sure the needed files are available and then trigger the second flashing process (of vanilla) right after the first (COMBINED) ended, so it kicks in just in time to stop the device from booting. Which is highly important since when you let it boot for 0.5s into linux and then reboot it to flash VANILLA, it's borked Sep 05 03:54:40 ...and you can start all over again Sep 05 03:56:02 that's why the "foolproof procedure" in "flashing the firmware" wiki sugests to do a triple flashing combined, vanilla, combined, and to take out battery Sep 05 04:03:28 DocScrutinizer05: Interesting. I do Vanilla, remove bat, then combined. Never had an issue before =) ofc, I'm rdy and watching when it flashes Sep 05 04:20:51 when your rootfs system is borked, the softupd can't work and thus vanilla flashing can't work Sep 05 04:21:16 thus in that pathological case you *need* to flash COMBINED first Sep 05 04:22:05 COMBINED gets flashed by NOLO bootloader, VANILLA "flashing" is actually a job done in linux Sep 05 04:24:02 http://paste.opensuse.org/43021802 aaaaand BINGO, guess I bought me a reboot Sep 05 04:25:34 Way ahead of ya DocScrutinizer05 =) Sep 05 04:28:01 well, it's known that VANILLA "flashing" can't get terminated except by shutting down the system hard (or possibly by parameter -R and completing the flashhing process, never tested that) Sep 05 04:28:20 so yeah, I had to shut down a device which pretended to be dead Sep 05 04:28:45 exactly what happens with flashing VANILLA Sep 05 04:30:20 DocScrutinizer05: I'm almost done with this CSV. I'm using plaintext files for "trust" factors. Sep 05 04:30:26 at least that's what I seem to recall. Not 100% sure if it's actually softupd daemon that does VANILLA flashing Sep 05 04:30:36 DocScrutinizer05: I simply pull the battery, it works for me Sep 05 04:30:41 sure Sep 05 04:30:56 DocScrutinizer05: There have been cases, where i've had to do the triple flash, but those are rare now. Sep 05 04:32:31 funny: when I pressed power button first time, the indicator light started shining white and steady. 8s pressing power button then made NOKIA bootloader kick in and device shuts *down* Sep 05 04:33:16 all this stuff is *very* obscure and undocumented for maemo Sep 05 04:33:16 Ah, yeah, I go for the throat; Never trusted the power down method for flashing Sep 05 04:33:19 I figure it's all the same Sep 05 04:33:34 DocScrutinizer05: That's why I want a "new method" for the future =) Sep 05 04:33:50 DocScrutinizer05: And if I can help be a part of something that gives back, then I've done my part. Sep 05 04:33:56 new method of flashing? good luck Sep 05 04:34:20 DocScrutinizer05: Not flashing, but "Base Image" for maemo Sep 05 04:34:24 DocScrutinizer05: The proposal Sep 05 04:34:40 DocScrutinizer05: It'll be documented, from start to finish 100%. Already have a nice outline Sep 05 04:35:19 I don't see how to document the very beginning: the flashing process in NOLO and softupd Sep 05 04:35:24 DocScrutinizer05: http://termbin.com/kofx Sep 05 04:35:28 DocScrutinizer05: That's how we do it Sep 05 04:35:41 DocScrutinizer05: Keep in mind, that's pwnphone methodology, but it can be applied towards Maemo as a whole. Sep 05 04:35:59 DocScrutinizer05: And I say pwnphone, but it's not even pwnphone anymore, pwnieexpress stopped supporting the n900 Sep 05 04:36:03 sorry, too tired to look into that now Sep 05 04:36:04 DocScrutinizer05: It's nameless =) Sep 05 04:36:07 DocScrutinizer05: NO worries Sep 05 04:36:25 DocScrutinizer05: check it out when ya can, throughouly documented from start to finish Sep 05 04:36:44 aha. So they RE'd NOLO or what? Sep 05 04:37:16 Well, it was an attempt to make a true "Walkthrough" for those who have ZERO n900 experience Sep 05 04:37:32 ooh, THAT kind of "docs" Sep 05 04:37:45 DocScrutinizer05: Thus far, it has good reviews. The plan is to take those directions, and apply them towards a more uniform user experience, not just a pwnphone style methodology Sep 05 04:39:44 I thought about docs like you can find in 0xFFFF and http://www.omappedia.org/wiki/Bootloader_Project and http://talk.maemo.org/showthread.php?t=20465 Sep 05 04:40:20 DocScrutinizer05: Ah, yeah, nothing like that =) Not trying to make heads explore Sep 05 04:40:23 DocScrutinizer05: Ah, yeah, nothing like that =) Not trying to make heads explode Sep 05 04:46:58 http://talk.maemo.org/showthread.php?t=17665 Sep 05 04:47:38 ~l1_2 Sep 05 04:47:46 hmm Sep 05 04:50:08 https://www.google.de/search?q=Nokia_N900_RX-51_Service_Manual_Service_Level_1_2.pdf http://directoriopt.com/read/?file=http://directoriopt.com/donld/tYXZLT/nokia-n900-rx-51-service-manual-service-level-3-4.pdf Sep 05 04:52:41 sorry, forget the latter, it's nagware shit Sep 05 04:53:09 =) Sep 05 04:55:15 http://www.cpkb.org/wiki/Nokia_N900_service_manual_and_schematic_download Sep 05 04:55:23 was legit once Sep 05 04:55:38 L3_4 is really great doc Sep 05 04:56:23 DocScrutinizer05: How long u been playing the n900 game? Sep 05 04:56:33 DocScrutinizer05: I know your the "reason" for neo900, yea? Sep 05 04:56:45 hmm? Sep 05 04:58:39 dang, seems the public sources for L3_4 are ... dried Sep 05 04:58:55 ping me if you can't find it Sep 05 05:02:21 Woo! http://talk.maemo.org/showthread.php?p=1481135&posted=1#post1481135 First vote has been called for, check it out! Sep 05 05:02:32 DocScrutinizer05: The most recent post contains the package CSV file Sep 05 05:43:54 Alright, WORN the heck out, headed off to sleep. For those interested, check out the CSV and apply your thoughts as you see fit =) http://talk.maemo.org/showthread.php?p=1481123#post1481123 Sep 05 06:01:05 yawn Sep 05 06:01:09 'morning Sep 05 06:01:39 yeah, everything needed for boot goes to /, non-boot important packages to /usr Sep 05 06:02:31 will probably require updating some debs? Sep 05 06:03:57 and maybe changing optifier in installer to stop or check how much stuff goes to / just in case of bad packages Sep 05 06:04:11 and maybe bindmounting /opt into /usr Sep 05 06:05:42 stryngs: this is what i remove personally (might be bit too much tho): http://wiki.maemo.org/Slimming_OS Sep 05 06:12:14 What's the recommended app for youtube these days? Sep 05 06:12:22 cutetube2 Sep 05 06:12:57 in extras-devel I assume? Sep 05 06:13:04 most likely Sep 05 06:13:30 also is there any way to get ham to stop complaining about the nokia repos that were killed? Sep 05 06:13:42 ~maemo-repos Sep 05 06:13:42 methinks maemo-repos is http://wiki.maemo.org/Repository#List_of_Maemo_repositories Sep 05 06:13:57 also install cssu and use speedyham Sep 05 06:13:59 ~speedyham Sep 05 06:14:00 [speedyham] 30 times faster than HAM http://maemo.merlin1991.at/cssu/community-devel/pool/free/h/hildon-application-manager/hildon-application-manager_2.2.73-2_armel.deb Sep 05 06:14:07 I've got cssu Sep 05 06:14:20 is speedyham okay these days? Sep 05 06:14:25 wasnt it? Sep 05 06:14:31 it was fap that had problem Sep 05 06:14:33 ~fap Sep 05 06:14:33 extra, extra, read all about it, fap is good Sep 05 06:14:37 hum Sep 05 06:14:38 ~fam Sep 05 06:14:39 from memory, fapman is Faster Application Manager, a frontend for apt which uses own repositories catalog, and shouldn't be used to do system upgrades (like CSSU), or actually for anything since ~speedyHAM. It also does "apt-get autoremove" after every operation, by default. In short, it's been identified as source of system corruption and thus deprecated, or see ~hamvsfam Sep 05 06:14:42 ah Sep 05 06:14:49 I was probably mixing them up then Sep 05 07:39:28 * Maxdamantus is buying a new battery. Sep 05 07:40:00 Last Measured Discharge: 949 mAh Sep 05 07:43:27 me is buying second n900 Sep 05 09:13:04 hmm https://blog.mozilla.org/security/2015/09/04/improving-security-for-bugzilla/ not as important for our bugzilla but interesting attack route. Sep 05 09:48:00 KotCzarny: you've found one? happy for you. i wouldn't mind a third one Sep 05 09:48:33 sicelo: finding isnt a problem, getting my a** to actually buy it is in my case Sep 05 09:48:42 my 2nd N900 cost me only US$15 :) Sep 05 09:48:50 w00t Sep 05 09:49:33 of course it was broken, no usb, and no battery .. but i knew i could trust the guy, and took the jump. now it's even in better condition than my main N900 :) Sep 05 09:51:00 only money spent was usb port, flux, solder wick. the rest of the "investment" was just time Sep 05 09:51:12 well, this one i'm getting for ~50usd Sep 05 09:51:22 BUY IT FFS Sep 05 09:51:23 swedish version Sep 05 09:51:23 :D Sep 05 09:51:31 no problems otherwise Sep 05 09:51:41 what's delaying you? Sep 05 09:51:54 the guy has to send me the bank account number Sep 05 09:52:05 woke him this morning, he he Sep 05 09:52:14 :) Sep 05 09:52:23 best wishes man Sep 05 09:52:38 yeah, he seems ok Sep 05 09:53:17 can never go wrong with N900. i wouldn't mind getting an N9, but it's one i'd never get more than 1 of. but for N900 can buy as many as i can find and afford Sep 05 09:53:30 it will be my battlefield unit Sep 05 09:53:36 anyway, bbl Sep 05 09:53:48 Maxdamantus: that battery .. how long it lasts you now? Sep 05 09:57:41 Sicelo: probably 20 hours or so. Sep 05 09:58:02 I don't usually do anything crazy on it. Sep 05 10:04:45 stryngs: took a brief look to your list of packages. This is just me maybe but should we let the Adobe Flash die off already? :D is it really required anymore when major website are moving towards alternatives mainly HTML5 and such? Sep 05 10:05:17 *typos Sep 05 10:12:03 Maxdamantus: my batteries are roughly at that same capacity Sep 05 10:12:21 Regarding the / vs. /opt thing .. I just have pretty much everything on a single ext3. Sep 05 10:12:44 the ubifs is used as a sort of writable initramfs. Sep 05 10:13:42 so it has the modules for the kernels I might want to use, and a script to load the ones required to continue booting with the ext3 partition. Sep 05 10:15:38 The root of that ext3 isn't even a root filesystem: it's actually /home and also contains maemo5-root, debian-armel-root, shr-root (haven't tried that recently), opt and nix Sep 05 10:16:19 also, the fat32 on ~/MyDocs is a really bad idea. Sep 05 10:17:17 iirc, the OS doesn't make sure the filesystem is unmounted before making it visible through g_file_storage Sep 05 10:17:50 So it'd be pretty easy to accidentally have it mounted (rw) on two systems. Sep 05 10:18:02 it does ensure that Sep 05 10:18:46 btw, did you document your setup somewhere? :) Sep 05 10:19:29 Not really. I think I posted my hacky init script here a while ago. Sep 05 10:19:57 Are you sure it ensures that? I'm pretty sure at least it doesn't wait for you to interact with the dialogue that pops up. Sep 05 10:20:22 it waits. at least both my N900 do. Sep 05 10:20:50 Also related: the mmc module suddenly removing access to the SD card when the backcover is removed is also a really bad idea. Sep 05 10:21:14 it's like the opposite of "safely remove hardware" Sep 05 10:21:34 i believe it also unmounts it properly for backcover too :) Sep 05 10:21:42 I'm certain that it doesn't. Sep 05 10:22:04 I've modified the module. It completely blocks all access to it when it sees the GPIO status change. Sep 05 10:22:25 hmm, weird Sep 05 10:22:29 The kernel can't even force remount it read-only (as in sysrq u) Sep 05 10:26:55 Though the OS does unmount it itself, it only gets to remove it from the tree. It can't do a clean unmount. Sep 05 10:27:59 ok. i was just now thinking about what a computer would do on forcible removal of a usb stick Sep 05 10:31:56 Linux itself doesn't do much, but you can detect such a removal from userspace and try to unmount it, which just removes it from the tree. Sep 05 10:33:07 otherwise it'll stay mounted and you might get IO errors or something occasionally, depending on the filesystem. Sep 05 10:41:18 what's the reasoning behind cutting off the microsd, again? Sep 05 10:41:25 i thought it was hardware controlled tbh Sep 05 10:41:54 Not sure, but it's not hardware-controlled. Sep 05 10:42:26 I changed a line in the module to keep it visible, so I can keep accessing it while the backcover is open. Sep 05 10:43:30 Though apparently the logic to handle removing the card is also meant to be under that state, so I can't physically remove the card and use the slot again without reloading the module. Sep 05 10:43:42 would probably need a few more changes. Sep 05 11:51:16 Was it possible to change your username at Maemo.org? I think its bit confusing that everywhere else I go by Ras_Older but there I had a brainfart back in the day and used my old nick :D Sep 05 11:56:30 Apparently by dropping an email to techstaff. Sep 05 12:31:32 which package or config would cause N900 to "wake" up even when lockscreen was active? Sep 05 12:37:48 sorry .. wake up when camera door gets opened ... which package or config is responsible? Sep 05 12:38:13 maybe camera one Sep 05 12:38:30 would be logical Sep 05 12:40:22 iirc the camera-ui part does that Sep 05 12:47:59 main N900 doesn't have this, but 2nd one does. I want to disable it Sep 05 12:48:35 tried to look in dbus .. didn't see anything Sep 05 12:49:51 sniff dbus and see what sends unlock msg? Sep 05 12:49:55 (via ssh) Sep 05 12:53:36 that's what i did. will redo Sep 05 12:54:11 ah .. was checking wrong bus Sep 05 12:57:41 https://paste.debian.net/310473/ Sep 05 12:58:23 not sure what's sending the unlock .. other N900 has exactly the same, except the tklock Sep 05 12:58:45 google time Sep 05 13:06:13 http://talk.maemo.org/showthread.php?t=45883 someone once had same problem. but no one explained the "why" Sep 05 13:15:33 Sicelo: /apps/camera/settings/extra-settings/disable-show-on-lenscover-open Sep 05 13:15:35 in gconf Sep 05 13:18:21 thanks. let me check. thought i'd checked gconf too Sep 05 13:19:04 hmm, so it's an "extra" key :) will add Sep 05 13:19:45 i see now that my ohter N900 does have it. thanks merlin1991 Sep 05 14:01:07 Does anyone else have issues with yappari lately? For me it's quite unstable. Sep 05 14:36:28 KotCzarny: imho, optifier should be reduced to nothing more than a dummy package; Assuming we get everyone on board with FHS or bindmounting. Sep 05 14:36:54 KotCzarny: I'm all about redoing the .debs. I've already built a script to decompress them; would be hard to modify it to automate the whole process. Sep 05 14:37:19 KotCzarny: I've notated your Slimming_OS post and will check it out here in a bit. Sep 05 14:37:31 Ps... Reading scrollback =) Sep 05 14:39:19 KotCzarny: Yeah, my thoughts are to incorporate CSSU by default and speedyham to replace ham. Just haven't made that list just yet. Trying to keep the paths seperate until they're ready for convergance Sep 05 14:41:50 Ras_Older: I'm okay with murdering off of adobe flash. Some of those packages I wanted to REMOVE, but wasn't sure if they could be added back in. afaik, there are some .debs that ONLY exist in the binary image and aren't hosted. I figured flash might be one of em. Either way, if we can re-get flash, it's a definite "should be gone" from baseline. Sep 05 14:42:46 Maxdamantus: Ah, so you have done some Filesystem hacks I see =) Do you have a write-up somewhere of what you did, what it accomplished, and how you did it? Sep 05 14:43:57 Maxdamantus: Per Nokia, removing backcover; it SAFELY powers it down. Granted, this is from Nokia, but they wouldnt have it in writing if it wasn't true, imho. Sep 05 14:44:43 Ras_Older: Talk to warfare for namechanges, he's one of the maemo.org folks. Sep 05 14:45:51 Alright, be back a bit later. Catching traction with "unification" idea! =) CSV has been updated on first post with Ras_Older's votes. Sep 05 14:58:42 stryngs: Why not use "dpkg --root=foo" instead of manual decompressing? (I may have missed some context that was stated earlier) Sep 05 14:59:45 AFAICT, it was designed for this purpose (installing debs on a mounted root filesystem). Sep 05 16:00:55 Vajb: unstable in what way? Sep 05 16:04:39 * Ras_Older is really waiting for Cyber Security & ICT expo held in Finland, Jyväskylä 23.9 to 25.9 ^^ Sep 05 16:33:25 Vajb: unstable in what way? Sep 05 16:33:47 sorry for that .. mistake Sep 05 16:34:35 unstable as it aborts or segfaults often Sep 05 16:34:59 terminate called after throwing an instance of 'ProtocolException*' Sep 05 16:34:59 Aborted Sep 05 16:35:13 last two lines and then it crashes Sep 05 16:35:13 ok. does that for me too, not that pervious one was any better .. i was getting same thing Sep 05 16:35:21 *previous Sep 05 16:35:33 yes same problem with previous Sep 05 16:36:11 i removed one group conversation since it was always mentioned near crash time, but didn't help Sep 05 16:38:27 i'm not even in any groups Sep 05 16:43:35 hopefully ceene is working for a fix :) Sep 05 16:51:45 (( I've modified the module. It completely blocks all access to it when it sees the GPIO status change.)) useless, since the module itslf actually cuts VDD for the uSD card when battery lid opened Sep 05 17:00:02 iirc it does a lazy-umount (or somesuch), and then cuts the the power to uSD card, so it won't get damaged - or device getting damaged - when removing the card and inserting another one Sep 05 17:02:50 in Neo900 we slightly modified the concept, so it has a switch in card tray itself that signals "tray closed". Nevertheless we keep the magnet switch to detect battery lid removal, for whatever purposes (e.g. `sync; sync`) We also changed the red "privacy LED" in camera to a RGB type to signal different states like "uSD unmounted and safe to remove now" rtc Sep 05 17:03:19 #s/rst/etc/ Sep 05 17:37:46 ZetaR: What purpose would the dpkg --root=foo do? Not following Sep 05 17:40:01 installs to foo instead of / Sep 05 17:40:10 most likely Sep 05 17:43:10 Yes. It is similar to using chroot, but it uses dpkg from / rather than from the new root (IIRC). Sep 05 17:44:01 I am not sure how/why you are decompressing the debs some other way though, since I missed the context for your statement about it. Sep 05 17:44:53 anyone here in a hackerspace with spacenet? :P Sep 05 17:45:07 trying to get my N800 to connect to it, to no avail Sep 05 17:50:14 buzz: did you try oscp yet? Sep 05 17:51:04 no, i havent put any music on it yet :P Sep 05 17:51:16 it works with internet streams too Sep 05 17:51:17 :P Sep 05 17:52:39 ZetaR: That doesn't work for apt-get purposes though Sep 05 17:53:20 stryngs: What is the context/use here? Sep 05 17:53:43 but i'd rather go on wifi here @ hackerspace :P Sep 05 17:54:09 You have local deb files, and are trying to install them? Sep 05 17:54:15 ZetaR: I'm not sure, you kinda lost me when you wrote of dpkg --root=foo. Not sure where you're going with it. Sep 05 17:54:33 zetar: he tries to get rid of optification and few other things Sep 05 17:54:35 ZetaR: It's a neat use of dpkg, but I want a more world-scope plan, not a local hack. Sep 05 17:55:05 KotCzarny: Oh, I murdered off optification. What I'm curious now of though, is FHS or bindmounting... Sep 05 17:55:10 Ahh, okay, so you are repackaging debs to remove optification? Sep 05 17:55:14 does apt have option that gets added to every dpkg command? Sep 05 17:55:27 ZetaR: Not at all. I just use a naked pymaemo-optify .deb Sep 05 17:55:38 ZetaR: A deb is a deb is a deb. You ever built one? Sep 05 17:55:50 stryngs, give him the link to your manifesto Sep 05 17:56:03 manifesto, bwhahaha =) Sep 05 17:56:09 KotCzarny: i'd think it's rhe other way round. apt uses dpkg, dpkg does not even know about apt :) Sep 05 17:56:26 http://talk.maemo.org/showthread.php?t=95922 Sep 05 17:56:38 sicelo, but i asked if there is such config option for apt that will get passed to dpkg -i Sep 05 17:57:02 the answer would be no, :) Sep 05 17:57:20 So ZetaR, a deb is pretty much a smart tarball. It contains 6 things Sep 05 17:57:29 within the deb it looks like this: Sep 05 17:57:41 DEBIAN, and then usr, or etc, or opt Sep 05 17:57:42 etc.. Sep 05 17:57:54 Within DEBIAN you have 5 total possible files, 1 of which is mandatory Sep 05 17:57:56 control Sep 05 17:58:08 control is the configuration of a .deb file Sep 05 17:58:14 apt-cache show nmap for an example Sep 05 17:58:19 stryngs, unpack .deb via: ar x your.deb Sep 05 17:58:23 that's a basic control file, what u see with apt-cache show Sep 05 17:58:28 KotCzarny: Oh im getting there Sep 05 17:58:30 its a bit different Sep 05 17:58:34 KotCzarny: Negative =) Sep 05 17:58:37 one sec Sep 05 17:58:44 it has 3 files afaik Sep 05 17:58:53 fs and deb control and some pkg info Sep 05 17:58:56 Here u go Sep 05 17:58:58 http://termbin.com/xik9 Sep 05 17:58:59 grab that Sep 05 17:59:06 rename it to rebuild Sep 05 17:59:08 chmod +x it Sep 05 17:59:10 then do: Sep 05 17:59:14 ./rebuild Sep 05 17:59:25 That will unpack it properly Sep 05 17:59:28 So you can modify it Sep 05 17:59:35 So, back to the deb story Sep 05 17:59:35 no, i was just tlking about .deb contents in general Sep 05 17:59:44 I have taken apart debs before. I was replying to "stryngs: KotCzarny: I'm all about redoing the .debs. I've already built a script to decompress them; would be hard to modify it to automate the whole process." but I didn't have the previous comments, so it sounded like you were trying to install them in some odd way. Sep 05 17:59:45 Yeah, but dpkg -x is cleaner than ar -x Sep 05 17:59:57 ar allows u to see DEBIAN though. Sep 05 18:00:42 * stryngs is kind of lost on what the topic is right now, truth be told. Sep 05 18:00:51 heh Sep 05 18:01:21 I didn't really know what the topic was to begin with. :) Sep 05 18:01:48 zetar, topic is stryngs murdering optification and moving fremantle toward fhs Sep 05 18:02:11 ^^ Sep 05 18:02:30 Also, the Unification and moving away from the fragmentation that has become Maemo Sep 05 18:02:36 and changing cssu installation in the process into single pkg install Sep 05 18:02:40 ^ Sep 05 18:02:44 That about sums it up Sep 05 18:02:54 That is what I thought, but I was confused by the "not at all..." reply by stryngs. Sep 05 18:03:01 Also, the ability to give yourself a nice base system, 100% without being connected to the internet. Sep 05 18:03:20 13:55 < ZetaR> Ahh, okay, so you are repackaging debs to remove optification? Sep 05 18:03:29 That's when I said not at all, now i follow Sep 05 18:03:44 So ZetaR, aside from .debs we want to modify, we don't have to repackage anything Sep 05 18:04:00 ZetaR: All pymaemo-optify does is some nasty mounting to put everything on /opt Sep 05 18:04:15 You follow me not following? Heh. Sep 05 18:04:17 ZetaR: If you remove pymaemo-optify, you have a very clean filesystem Sep 05 18:04:36 ZetaR: The problem is though, if u remove it, you only have 256MB on / Sep 05 18:04:43 ZetaR: so, you must modify your filesystem layout Sep 05 18:04:44 Right. Sep 05 18:04:51 ZetaR: Which I have done, successfully Sep 05 18:04:52 one word, fhs Sep 05 18:05:19 KotCzarny: fhs or bindmounting, either way; we just all have to agree. And many people have said FHS, but no steps has been presented Sep 05 18:05:19 if you move boot things into / and non-boot critical stuff into /usr its clean Sep 05 18:05:35 it has to be clearly defined Sep 05 18:05:37 KotCzarny: We need steps for this =) I wish I had some? Sep 05 18:05:38 So, you are now going to mount the eMMC as /usr (like Nokia should have done)? Sep 05 18:05:57 once you have it, you can have /usr anywhere Sep 05 18:06:05 flash, emmc, sd Sep 05 18:06:28 ZetaR: Well, right now, I only know one way to proceed, and that is my bindmount hacks. I would LOVE the FHS method, but, I don't know how to implement it. Others have mentioned it, but no steps or guidance has been presented on paper yet. So, all I have to go with till then, is my bindmount techniques. Sep 05 18:07:33 if you have things in /usr, you can use normal mount, no need for binding Sep 05 18:07:36 I saw the text you posted about it. I am not sure why you are doing /lib and /sbin and stuff as bindmounts. Sep 05 18:07:42 KotCzarny: So how do we move them there? Sep 05 18:07:50 KotCzarny: Without repackaging and recompiling EVERY deb Sep 05 18:07:59 Yeah, just have NAND as / and eMMC as /usr. Sep 05 18:08:00 ZetaR: Because they take up space on / Sep 05 18:08:27 But stuff shouldn't generally install to /lib and /sbin. Sep 05 18:08:30 ZetaR: I moved as much stuff as I could, to alleviate the strain on NAND, only 256MB is easy to fill up when adding the types of .debs I do. Sep 05 18:08:38 Well, aircrack-ng Sep 05 18:08:44 Stuff goes to sbin Sep 05 18:08:50 It should go to /usr/sbin Sep 05 18:09:07 Right, but sometimes, it just doesn't and you have to account for that. Sep 05 18:09:30 Actually, I take that back, it does do usr/sbin Sep 05 18:09:45 Point being, I offloaded as much as I could to the larger hdd Sep 05 18:09:52 and in truth, It's still FHS compliant Sep 05 18:10:06 /home/rootfs_bind/usr on /usr Sep 05 18:10:15 usr is still under / Sep 05 18:10:19 Just mounted Sep 05 18:10:19 If a package is going to /sbin and it is not required for boot or basic CLI diagnostics, then it is probably wrong and needs to be fixed. Sep 05 18:11:00 would be nice to have system which can boot without /usr mounted, yet being able to charge, rescue itself etc Sep 05 18:11:10 and only needing /usr for full boot Sep 05 18:11:20 Right. Sep 05 18:11:20 KotCzarny: afaik, backupmenu ssh solution does this Sep 05 18:11:28 KotCzarny: You have to manually mount a whole bunch of stuff Sep 05 18:11:46 once i get my secondary n900 im going to hack it till it screams Sep 05 18:12:02 Alright, well I suppose it's time to make the FHS post. Sep 05 18:12:07 I'll be back here ina bit Sep 05 18:12:13 I'm just glad people like the idea. Sep 05 18:12:17 stryngs: It just seems unnecessarily complicated the way you are doing the mounts. Sep 05 18:12:18 I wasn't sure if it would gain traction Sep 05 18:12:35 ZetaR: What I do allows me to install any .deb I want, without overflowing / Sep 05 18:12:42 ZetaR: I can grab any kali armel deb i want Sep 05 18:12:59 ZetaR: Other user's however, cannot, unless they take similar actions as me, and this is due to optification bs. Sep 05 18:13:02 If /usr is the eMMC then you should be able to do that anyway. Sep 05 18:13:11 What about when /etc fills up? Sep 05 18:13:14 That is, if everything is propery deoptified. Sep 05 18:13:21 stryngs, some people do things using overlay mounts Sep 05 18:13:43 We don't want to have to repackage every single .deb though; we want the most efficient time saving manner possible, while still making maemo useful. Sep 05 18:13:44 ie. have a booting os in flash, and overlay in emmc Sep 05 18:13:45 It would be very difficult to fill up /etc, since stuff should never put much data in it. Sep 05 18:13:58 that way you can install every deb too Sep 05 18:14:08 ZetaR: My thoughts were not so much that it can be difficult, but that it could happen, hence the precautions I took. Sep 05 18:14:19 and also allows for easy snapshots Sep 05 18:14:20 Take for instance, /var/apt/cache/archives Sep 05 18:14:28 What's that mounted on Sep 05 18:14:42 /var/lib/dpkg rather Sep 05 18:15:03 Either way, I don't want to argue about it, I want us to come together and implement a solution! Sep 05 18:15:17 Whatever the majority decide, if folks want to cash in on this; is how we'll proceed. Sep 05 18:15:28 If the majority decides my current way sucks; and can make it better, I'll use what tey do. Sep 05 18:15:33 team effort. Sep 05 18:15:35 i wouldnt mind some cash Sep 05 18:15:45 Well KotCzarny, in that respect Sep 05 18:15:48 IMO, if something is filling up the NAND by putting stuff in /etc or /lib or /sbin, then it is wrong and needs to be fixed. I don't think it is the job of mount to fix it. But this is your project, just sharing my opinion. Sep 05 18:15:57 KotCzarny: If this goes mainstream, then you can put it on your resume. Sep 05 18:16:11 stryngs, unlikely Sep 05 18:16:15 ZetaR: That is exactly the feedback I want. Sep 05 18:16:17 (resume wise) Sep 05 18:16:27 ZetaR: Constructive Critisim with useful remarks. Sep 05 18:16:38 :) Sep 05 18:16:53 Nokia-N900:/lib# du -h . | tail -n 1 Sep 05 18:16:53 24.9M . Sep 05 18:16:58 thats 24.9M Sep 05 18:17:03 i think optification was a quick and dirty way of 'deb needs a fixing' Sep 05 18:17:15 KotCzarny: It was Sep 05 18:17:25 KotCzarny: it did the job, but it's time to update how we do things Sep 05 18:17:33 Alright, enough chattering from me, let me make Part III happen Sep 05 18:17:42 FHS -vs- Bind Mounting.......... FIGHT! Sep 05 18:17:49 i wonder if emmc could take the beating of having fs on it Sep 05 18:18:23 KotCzarny: You mean full fs? Sep 05 18:18:27 yes Sep 05 18:18:29 stryngs: du without pipe: "du -h -d 0 /etc" Sep 05 18:18:30 with ext3/4 Sep 05 18:18:30 KotCzarny: iirc, No. Sep 05 18:18:47 hum Sep 05 18:18:50 KotCzarny: Too slow was what I heard. Sep 05 18:18:58 slowness doesnt bother me Sep 05 18:19:02 KotCzarny: Performance issue, but, why the hell can't we try Sep 05 18:19:03 flash wear do Sep 05 18:19:45 when i get my n900, im going for a 'boot os in flash, full os in sd' Sep 05 18:19:55 and using emmc for media storage only Sep 05 18:20:02 What if a user can't use their SD card. Sep 05 18:20:15 KotCzarny: I know you can, but then your idea only applies to those who have working SD cards =( Sep 05 18:20:20 KotCzarny: Not a universal approach Sep 05 18:20:20 then its only changing pivot_root from sd mount to emmc mount Sep 05 18:20:32 it even could be boot menu selectable Sep 05 18:21:01 KotCzarny: So let's make it happen =) Sep 05 18:21:20 dont mind me too much, i had few ideas on my own for a long time, just didnt have the poor n900 for beatings Sep 05 18:21:43 KotCzarny: I'll saccrifice mine for the cause =) Sep 05 18:22:29 if i'll be successfull there will be my own flashable image for testing Sep 05 18:23:25 Under a fairly default Debian install: /bin 6.8MB, /etc 4.0MB, /sbin 8.5MB, /var 849MB (???), /boot 33MB, /home 9.1GB, /lib 170M (why?), /root 25kB, /tmp 44kB, /usr 2.6GB Sep 05 18:23:46 lib is big because it has to have most of glibc Sep 05 18:23:49 and kernel modules Sep 05 18:24:08 Ah. Let me check my N900 to see how big it is on that. Sep 05 18:24:10 unless you move boot process to klibc or uclibc there is no way around Sep 05 18:24:47 on my slackware /lib is 99M Sep 05 18:25:01 and /var is also big on regular distro for log files .. they grow real fast. maemo doesn't keep them, except one or two Sep 05 18:25:02 and most of it is in /lib/modules Sep 05 18:25:20 /var is 182M Sep 05 18:25:30 Yeah, I thought it might be log files, but it still seems huge. Sep 05 18:25:32 if you have setup logrotate with compression its not that big Sep 05 18:25:35 in fact, there can even be "config" files in /var Sep 05 18:25:46 sicelo, /var/cache Sep 05 18:25:50 most likely hogs it Sep 05 18:26:15 and if you have mailer/printer, then /var/spool Sep 05 18:28:25 On my N900: /bin 964k, /etc 5.9M, /sbin 1.9M, /var 26M, /home 495M, /lib 23.4M, /root 16k, /tmp 80k, /usr 245.2M Sep 05 18:28:45 use -x for du Sep 05 18:29:07 so it wont go across fs boundaries Sep 05 18:29:44 I didn't want it to. This way it doesn't care about /opt and such but rather tells you where files are in the hierarchy. Sep 05 18:30:07 oh well Sep 05 18:30:52 my /usr is 289M and 237M with -x Sep 05 18:31:05 i.e. /usr and /home need to be eMMC, but everything else can probably be NAND. Not sure about what to do with /var on the N900. Sep 05 18:31:57 you have to use emmc Sep 05 18:32:16 otherwise your deb catalogs would hog space Sep 05 18:32:23 also intermediate package downloads Sep 05 18:32:28 /var on N900 is generally small .. i don't se it hogging anything. Sep 05 18:32:55 Are /var and /home safe to symbolically link, rather than doing bind mounts? AFAICT, that is what symbolic links are for. Sep 05 18:32:59 thats because /var/cache is symlinked to /opt Sep 05 18:33:19 symlinks are a bit slower than bind mounts Sep 05 18:33:25 not that much tho Sep 05 18:33:29 Ah. Sep 05 18:33:36 but there is still danger of circular loops Sep 05 18:34:09 Only if you are careless. Sep 05 18:35:10 hmm Sep 05 18:35:11 I know some programs try and resolve the absolute path and such. Not sure when this becomes a problem. Sep 05 18:35:37 right now we are already having big hunk of fs on emmc Sep 05 18:37:21 im more and more inclined to move it to emmc or ssd in whole Sep 05 18:37:31 SSD :) Sep 05 18:37:38 :) Sep 05 18:37:54 piggybacked 1.8" ssd ? ;) Sep 05 18:38:12 which was the Nokia with a hard-drive by the way? Sep 05 18:38:17 swap my b*tch up! Sep 05 18:38:59 N91 Sep 05 18:39:35 Just use a very small PATA drive! https://en.wikipedia.org/wiki/Microdrive Sep 05 18:39:46 nah, microdrives are slow Sep 05 18:39:52 ssd baby Sep 05 18:40:45 i think even cf cards are faster than microdrives Sep 05 18:41:07 Microdrives are just more fun. Sep 05 18:41:16 had pcmcia one Sep 05 18:41:28 it was slow as hell Sep 05 18:41:41 parking head just about after every operation Sep 05 18:50:45 btw. tracker is needed for people who use system image viewer/player Sep 05 18:51:03 (i dont so it doesnt bother me, just saying) Sep 05 18:52:05 * Sicelo has learned to come to terms with it Sep 05 19:29:41 tracker SUCKS, so do all apps that rely on it. Braindamaged concept of a phantom filesystem Sep 05 19:30:12 gnome invention, I guess Sep 05 19:30:31 or rather freedesktop Sep 05 19:31:00 nice invention, but tricky to get right Sep 05 19:32:11 tracker is fine for a "desktop document search engine" like err spotlight(?), abusing it for the primary and even only "filesystem" access method in any app is really braindead Sep 05 19:32:45 yes, that's true. Sep 05 19:33:05 the problem is the "apps" though, not tracker itself Sep 05 19:33:17 yes, of course Sep 05 19:33:27 and thats why oscp was born Sep 05 19:33:30 :) Sep 05 19:34:47 Maemo's stock apps are definitely bad for not giving other other options besides tracker :) Sep 05 19:35:03 luckily we can have any app compiled/used Sep 05 19:35:18 that's a "apple me-too" attitude Sep 05 19:35:19 since i don't like to have 10 apps for images, and 5 for music, etc, then I stick with tracker Sep 05 19:35:49 and I criticized that from very beginning of tracker, with maemo5 Sep 05 19:35:51 otherwise i may as well go Android, and have 99 apps for sudoku :D Sep 05 19:36:10 sicelo, oscp can handle almost any file format Sep 05 19:36:25 (audio file format, that is) Sep 05 19:36:27 :) i'm sure it can Sep 05 19:36:52 and oscv can handle most popular image ones Sep 05 19:36:58 it's about adding meta info to plain old unix filesystems Sep 05 19:37:27 even animated gifs and multipage tiffs/pdfs Sep 05 19:37:28 tracker is the wrong solution to an inexistent problem Sep 05 19:37:51 doc, tracker was for lazy-clicky people that didnt know where their files were Sep 05 19:37:57 trying to push a "filesystem agnostic" approach Sep 05 19:38:08 KotCzarny: *exactly* Sep 05 19:38:26 i look at it as a database (which it is) Sep 05 19:38:36 its bad database Sep 05 19:38:46 good for ideal world Sep 05 19:38:49 possibly, but works :) Sep 05 19:38:51 bad for real one Sep 05 19:38:52 >>users don't know what's a directory<< original text of some evangelist of that concept in maemo5 Sep 05 19:39:26 * Sicelo has yet to see the real problem with tracker (besides the hogging cpu while indexing) Sep 05 19:39:35 umm Sep 05 19:39:42 my files are laid out nicely Sep 05 19:39:44 Sicelo: oh really? Sep 05 19:39:49 tracker just makes a mess out of them Sep 05 19:39:57 but i agree 100% that apps which make tracker the only way to access files are broken Sep 05 19:40:04 mess? how? Sep 05 19:40:09 Sicelo: pretty simple: have two mp3 of same metatags, one on eMMC and one on uSD Sep 05 19:40:17 have fun¡ Sep 05 19:40:38 sicelo: untagged files, some tagged badly Sep 05 19:40:43 but filenames/dirnames are ok Sep 05 19:40:48 Sicelo: another one: you keep your pr0n in a folder ~/.pr0n Sep 05 19:40:50 i thought people have their files "laid out nicely" .. Sep 05 19:40:57 open up gallery Sep 05 19:41:01 now tracker categorizes them in different places Sep 05 19:41:17 DocScrutinizer05: tracker won't index that pr0n. you know it. Sep 05 19:41:24 aha Sep 05 19:41:35 .files are hidden Sep 05 19:41:39 and .dirs Sep 05 19:41:40 isn't that what you want? Sep 05 19:41:46 then maxe that ~/foobar Sep 05 19:41:54 or *whatever* you like Sep 05 19:42:04 * Sicelo doesn't get DocScrutinizer05's argument Sep 05 19:42:26 tracker is superfluous and bad at what it has to achieve Sep 05 19:42:54 the argument is: there's ZILCH tools to *group* your tracker-indexed stuff in a meaningful manageable way Sep 05 19:43:11 or what KotCzarny said Sep 05 19:43:58 if we think tracker means we should forget file organization, then that's where the real problem is Sep 05 19:44:17 I honestly don't _need_ tracker, it's crap for the purpose to select which files get shown in gallery or mediaplayer Sep 05 19:44:30 no, problem is DIRECTORY/FILE structure was invented for file organization Sep 05 19:44:34 i still organize my files and directories as best as i can Sep 05 19:44:45 metadata is nice only if ALL files have it proper Sep 05 19:45:05 or if you have magic algo that can guess author/title from the content Sep 05 19:45:20 ~sb Sep 05 19:45:20 somebody said scratchbox was a cross-compiling system that uses binfmt_misc, rpc calls, and an nfs mount to make a cross-build appear to be 100% native, and is found at http://www.scratchbox.org/, hosted by maemo now. Also at http://maemo.merlin1991.at/files/SB Sep 05 19:45:58 as long as tracker is there on the N900, rather use it .. it's already using up your resources anyway :) Sep 05 19:46:11 if you've removed it, then .. different story Sep 05 19:46:22 tracker as used in maemo reinvents the wheel (or rather the filesystem with all the goodies it has) - *very* poorly Sep 05 19:46:23 sicelo, i've disabled it on mine Sep 05 19:46:29 uninstalled? Sep 05 19:46:33 disabled Sep 05 19:46:37 not tracking anything Sep 05 19:46:48 I downloaded the SDK 1.1.2 from here: ftp://ftp.informatik.hu-berlin.de/pub/Mirrors/ftp.troll.no/QT/qtsdk/, but it doesnt contain the Maemo toolchain. There is a tool to download the toolchain but the servers are down. Sep 05 19:46:51 so my point is correct .. it's still eating up your space :) Sep 05 19:46:57 i didnt try uninstalling it as most likely bazillion of debs depend on it Sep 05 19:47:07 maemo's stock image viewer .. still eating up your space too Sep 05 19:47:09 eating up space is passive Sep 05 19:47:11 Does someone knows how to download Maemo toolchain and integrate it to the SDK 1.1.2? Sep 05 19:47:20 i care about function and battery life Sep 05 19:47:33 sla_erick_: nobody ever did this afaik Sep 05 19:48:15 oops, sorry Sep 05 19:48:17 this is precisely what i don't want ... having many apps for each of these functions. if i can remove the stock media player, image viewer, etc, then i remove tracker immediately Sep 05 19:48:32 of course it been done, but actually you're better off just using a VM Sep 05 19:48:43 http://maemo.merlin1991.at/files/SB Sep 05 19:48:50 sicelo, dependency can be as simple as depending on some lib, even if particular deb doesnt use tracker Sep 05 19:48:54 DocScrutinizer05 do you know any Qt SDK that comes ready for developing and deploying to the N900, I know that you are not a developer, just wondering Sep 05 19:49:55 err all should be in http://maemo.merlin1991.at/files/SB already. And what's missing should be installable from maemo-sdk and maemo-tools repos Sep 05 19:50:00 yes indeed KotCzarny. Sep 05 19:50:23 fair enough, thanks :) Sep 05 19:51:52 just cant wait to get hacking once my second n900 comes Sep 05 19:52:21 DocScrutinizer05: wasn't there a BM image released at some point? Sep 05 19:52:39 hmm? Sep 05 19:52:53 BM image of what? Sep 05 19:53:52 i guess not then Sep 05 19:54:35 I don't know of any publicly available BM backup files so far, though they would be extremely cool to have. Just everybody been too worried about disclosing privacy-related info and too busy to scan and clean the BM tarball Sep 05 19:55:40 I fail to completely understand the question though, what's a "BM image"? Sep 05 19:56:09 there's a fiasco image that contains BM already, see Sep 05 19:56:11 ~bm Sep 05 19:56:12 i guess backupmenu is http://talk.maemo.org/showthread.php?t=63975 Sep 05 19:57:30 or are you asking about a bm image that contains Qt SDK ? Sorry, you lost me Sep 05 19:59:57 doc, what are your thoughts about running whole os from emmc? Sep 05 20:00:00 or sd? Sep 05 20:00:01 oooooh, stryngs!! you *ever* used osso-backup to restore a system on N900? it basically is a very smart way to have a opt-in/out list of apps to install from repos Sep 05 20:00:11 ah yes .. that one in the link .. tha's what i meant Sep 05 20:00:46 KotCzarny: I'm no fan of moving more than necessary to eMMC or even uSD Sep 05 20:01:10 but for now we are already running most things from there Sep 05 20:01:35 so i guess nand would be nice place for rescue/boot etc, and os on emmc/sd Sep 05 20:01:37 well, then are we facing an XY problem? Sep 05 20:02:05 because most things in use are not on nand Sep 05 20:02:14 why not the other way around? rescue system on eMMC and normal system unchanged Sep 05 20:02:16 so, why not? Sep 05 20:04:17 A) precisely define the problem at hand, B) check if those are *real* problems and think about solutions if they are real. only then C) design and implement the fix Sep 05 20:05:11 a) fs fragmentation Sep 05 20:05:30 how's that a problem? Sep 05 20:05:42 I don't even understand the term Sep 05 20:05:48 little space on / without optification hack Sep 05 20:06:17 there been a solution to that already and you mentioned it Sep 05 20:06:37 so your *real* problem seems to be: you don't like optification-hack Sep 05 20:06:40 I agree Sep 05 20:06:49 ~optification Sep 05 20:06:49 optification is a inventive duct tape workaround to reclaim space in fs root, done due to the fact the systeminit *and* partitioning is FUBAR, http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing/Installing_under_opt_and_MyDocs, or ""OMG - I wish they looked into FHS and moved /usr to eMMC"", http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE2 bullet1,2 and fhs-2.3.html#PURPOSE16 dot3" Sep 05 20:07:05 but my real question is, can emmc take the wear from being used for os? Sep 05 20:07:09 ""OMG - I wish they looked into FHS and moved /usr to eMMC"" Sep 05 20:07:15 yes, it can Sep 05 20:07:17 and i think about ext3/4 Sep 05 20:07:42 you need to adjust operation parameters aka options of ext3/ext4 Sep 05 20:08:10 you generaly don't want journal usually. And you want noatime etc Sep 05 20:08:30 yes, i run noatime everywhere Sep 05 20:08:41 but i would like journal too Sep 05 20:09:00 yournal is a *very* bad idea on flash storage Sep 05 20:09:18 for flash storage without wear leveling Sep 05 20:09:36 or with heavy writes Sep 05 20:09:46 hum Sep 05 20:10:00 think about what journal does, and you'll see it's not compatible with the wy how flash works Sep 05 20:10:16 yes, constant writing at limited space Sep 05 20:10:44 you can't rewrite aka "extend" a file on flash Sep 05 20:11:43 each byte written to journal causes *complete* jounal to get rewritten on flash, then eventually read out again and transformed into *real* filesystem actions Sep 05 20:13:28 well Sep 05 20:13:56 then metadata journal maybe? Sep 05 20:13:57 anyway I heard ext4 performs extremely well on eMMC, with the right parameters Sep 05 20:14:31 metadata journal might make sense. i'm no fs expert Sep 05 20:15:31 evaluation of performance and stability of a fs on flash/SSD is a very tricky and involved task Sep 05 20:24:51 another question is how stable was ext4 in 2.6.28 Sep 05 20:29:18 What about btrfs instead of ext? Sep 05 20:35:05 Copy on write gives you the FS protection that the journal does, but doesn't have the problems with flash that a journal would. Sep 05 20:35:13 same question Sep 05 20:35:20 how stable it was in 2.6.28? Sep 05 20:35:26 or, can it be backported? Sep 05 20:35:59 Hm, let me see if I can find the answer to that. Sep 05 20:38:08 Yeah, it's not stable for that version. Sep 05 20:41:22 05:00:02 < DocScrutinizer05> iirc it does a lazy-umount (or somesuch), and then cuts the the power to uSD card, so it won't get damaged - or device getting damaged - when removing the card and inserting another one Sep 05 20:41:27 It doesn't. Sep 05 20:42:22 unless you mean a lazy unmount after the card has been forcefully made inaccessible. Sep 05 20:44:52 It might safely power down the card, so it doesn't result in some sort of hardware damaged, but there's no way to prevent filesystem damage from non-safe removal. Sep 05 20:46:01 yes, for other fs than fat32 that could be a problem Sep 05 20:46:43 fat32 is still subject to similar corruption, unless maybe you mount it with -o sync Sep 05 20:46:52 even for fat32 they do a fsck afaik, to repair any such damage Sep 05 20:47:26 "any such damage" can't be easily detected on fat32. Sep 05 20:47:30 it doesn't have a journal. Sep 05 20:47:50 sorry afk Sep 05 20:48:53 You could scan all the metadata for inconsistency and try to fix that, but if you get corruption that doesn't lead to inconsistency (at the filesystem level), there's no way to detect where such corruption might be. Sep 05 20:49:12 so? Sep 05 20:49:26 So you can end up with partially written files. Sep 05 20:49:33 I just can tell you what's in there Sep 05 20:49:39 which look perfectly valid from the filesystem's perspective. Sep 05 20:50:13 yes, I know all that. Thanks anyway Sep 05 20:52:40 We should all be using copy-on-write filesystems by now anyway -_- Sep 05 20:52:47 should we, really Sep 05 20:52:51 Yes. Sep 05 20:53:05 even on ext3, you can't recover from corruption. Sep 05 20:53:06 well Sep 05 20:53:06 http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing/Installing_under_opt_and_MyDocs doesn't explicitly mention it, but I could figure that apps who write to uSD are supposed to listen to dbus signals and act accordingly Sep 05 20:53:18 you can only fix filesystem inconsistency, and detect that corruption might have happened. Sep 05 20:53:24 unless you use full journalling. Sep 05 20:53:33 (ie, where you write the data twice) Sep 05 20:53:40 there is always zfs :P Sep 05 20:53:42 (ext3 and ext4) Sep 05 20:53:54 Yes, ZFS handles it, but you can't practically run that on a phone atm. Sep 05 20:54:03 btrfs is practical for usage on phones though. Sep 05 20:54:15 i had some fun with pivot_root'ed zfsfuse Sep 05 20:54:20 it was unstable tho Sep 05 20:54:41 even journalling doesn't solve your problem, which is: "you cannot write to a medium that's not connected to the system" Sep 05 20:54:58 That's not the problem. Sep 05 20:54:59 raid1 Sep 05 20:55:03 or 5 Sep 05 20:55:05 That's another problem. Sep 05 20:55:13 raid1 and raid5 are very bad. Sep 05 20:55:23 They just make this worse. Sep 05 20:55:32 how so? Sep 05 20:55:36 Write holes. Sep 05 20:55:47 unless i mixed up numbers Sep 05 20:56:02 i meant the one with data duplication Sep 05 20:56:20 If you disconnect two raid1 drives, you don't know that they're going to be in the same state when you reconnect them. Sep 05 20:56:41 yes, but point is, as long you dont disconnect both, its all good Sep 05 20:56:43 unless you do journalling at the RAID level or do an entire scrub afterwards. Sep 05 20:57:07 but even when you get it back into sync, you still have the exact same corruption issues on the filesystem. Sep 05 20:57:48 .. or if you have a hardware RAID controller with lots of NVRAM to buffer writes over power cycles. Sep 05 20:58:13 but that's a horrible solution for something that can be solved using a CoW filesystem. Sep 05 20:58:19 pity they dont make internally daisychained raided sd cards Sep 05 20:58:20 :) Sep 05 20:58:31 though its not it, hum Sep 05 20:59:45 listen folks, when you interrupt a write to a storage medium, the data gets corrupted, no matter what. When you want to write data to a removable meduim, it's your responsibility to make sure the medium doesn't get removed while you write. If you can't guarantee that, you have to live with data not getting written or even getting crippled. Unrelated to this, N900 has means that avoid *physical* damage to uSD or N900 itself: powering down Sep 05 20:59:47 the card as soon as battery lid gets opened, which enables two threats - uSD card removal and inadvertent battery removal (while writes happen) Sep 05 21:00:25 Yes, but you can at least make sure the filesystem is in some previously intended state. Sep 05 21:00:34 using either CoW or full data journalling. Sep 05 21:00:45 the latter means you write everything twice. Sep 05 21:00:59 or just minimize writes Sep 05 21:01:53 aha, writing twice and mimimize writing serve same purpose? hardly. I prefer the latter Sep 05 21:01:55 Databases like sqlite3 are written such that they can operate under that assumption. Sep 05 21:02:34 If you're removing a non-journalled drive with a sqlite3 database on it in the middle of a write, there's no guarantee your database isn't corrupt. Sep 05 21:02:57 removing medium during writes is BAD IDEA Sep 05 21:03:01 no matter what Sep 05 21:03:03 if it's fully journalled or CoW, you do get that guarantee: the database might have lost the last few seconds, but it won't be corrupt. Sep 05 21:03:16 Of course, but it hapeens. Sep 05 21:03:20 So it should be handled. Sep 05 21:03:24 journalling does NOT help writing that very data to the medium. It only helps not even *trying* to write aborted transactions to the medium Sep 05 21:04:19 from an app's perspective that photo doesn't get stored nevertheless Sep 05 21:05:10 plus journaling not only doubles but at least triples writing to media Sep 05 21:06:04 If you're doing full journalling (data included) it basically means double. Sep 05 21:06:25 There's of course extra metadata around the journalling itself, but that's not going to be as large as writing the data twice. Sep 05 21:06:25 aha, and who's deleting the jounal after commit? Sep 05 21:06:26 yea but how can i avoid not unplugging the uSD if i remove the back cover? Sep 05 21:06:52 kerio: modify the kernel module. Sep 05 21:06:52 I'm not talking about volume, i'm talking about IO ops Sep 05 21:07:02 Maxdamantus: ayy lmao Sep 05 21:07:11 um Sep 05 21:07:18 or keeping sd journal on emmc Sep 05 21:07:19 :) Sep 05 21:07:46 KotCzarny: that might be a nice idea Sep 05 21:07:57 If it's a full journal, that's going to halve write speeds. Sep 05 21:07:58 I already pondered that approach Sep 05 21:08:16 i wouldnt bother personally tho Sep 05 21:08:27 user is the weakest link Sep 05 21:08:45 It wouldn't really be any better than journalling on the same SD card, since the write speed on the N900 doesn't seem to be bottlenecked by the SD card. Sep 05 21:08:51 but by the controller. Sep 05 21:08:59 which the eMMC is also on. Sep 05 21:09:06 add an electric lock to the battery cover ;-D Sep 05 21:09:16 electroshocking lock? Sep 05 21:09:18 :) Sep 05 21:09:27 only unlocks when uSD is properly unmounted Sep 05 21:09:35 https://talk.maemo.org/showpost.php?p=1457369&postcount=4 Sep 05 21:09:45 such locks would be a pita Sep 05 21:10:06 last time when some app locked my cdtray i was .. unhappy Sep 05 21:10:34 cya l8r Sep 05 21:12:22 (that bottleneck comment is assuming you have an SD card that is meant to be able to write at more than 8 MiB/s or so, can't remember the actual number) Sep 05 21:12:35 * Maxdamantus tries. Sep 05 21:19:26 seems to be about 6 MiB/s Sep 05 21:19:56 what is iops@512b for internal flash? Sep 05 21:20:01 and for emmc? Sep 05 21:20:18 I don't want to try that on the flash. Sep 05 21:20:37 test can be short, 10-20s Sep 05 21:21:02 there are sd cards capable of ~100 iops Sep 05 21:21:30 most are in 0.1-10 range tho Sep 05 21:24:43 Okay, not 6 MiB/s .. can do 13 MiB/s Sep 05 21:26:07 and yeah, that's shared across the SD card an eMMC. Sep 05 21:26:34 oh, no, nvm .. I'm writing 11 MiB/s to the SD card now and 9 MiB/s to the eMMC. Sep 05 21:28:53 try reading to one and writing to other Sep 05 21:30:40 reading from eMMC at 14 MiB/s, writing to SD card at 10 MiB/s Sep 05 21:31:57 so they use independent controllers in chip Sep 05 21:32:40 arm chips usually have 2-4 mmc controllers Sep 05 21:33:11 Maybe it would be nice to use btrfs with its "raid0" mode. Sep 05 21:33:14 but most of the time only 1 is connected to some slot Sep 05 21:36:13 actually, the things I said were inverted: when I said SD card before I meant eMMC and vice versa. Sep 05 22:34:31 To answer the question about ext4 stability: "On 11 October 2008, the patches that mark ext4 as stable code were merged in the Linux 2.6.28 source code repositories, denoting the end of the development phase and recommending ext4 adoption." (Wikipedia) Sep 05 23:11:11 DocScrutinizer05: I've never used osso-backup for those purposes. Sep 05 23:11:27 you should give it a try Sep 05 23:12:15 (ext4) we got stable ext4 support on maemo Sep 05 23:12:47 not for rootfs though Sep 05 23:17:00 afk for a bit, bbib Sep 05 23:20:19 Why not rootfs? Sep 05 23:21:07 Just in terms of it not being there by default? Sep 05 23:54:46 stryngs: I have determined the optimal ext4 parameters for the N900's eMMC geometry: "-b 4096 -E stride=2,stripe-width=256". This will make ext4 respect the write block size of 8192, and stripe the eMMC in sections respecting the erase group size of 256 write blocks. Sep 06 00:17:22 * Maxdamantus is now using ext4 on his root. Sep 06 00:17:43 Though the boot process seems very unreliable. Sep 06 00:18:14 Booting is too complicated .. hard to debug issues. Sep 06 00:19:08 * Maxdamantus wonders if there's an option to make it start a shell instead of rebooting. Sep 06 00:47:04 I wouldn't use ext4 for root. I would probably use ext3 for / and ext4 for /usr and then link other things to /usr Sep 06 00:47:49 Or rather rootfs. Sep 06 00:50:59 Why not? Sep 06 00:52:29 ext4 isn't as widely supported for booting. Not sure what is supported on the N900 besides rootfs (if anything). Sep 06 00:52:29 I haven't actually enabled any ext4 features yet, just using the ext4 module. Sep 06 00:52:49 N900 normally uses ubifs on NAND for root. Sep 06 00:53:07 AFAICT, mounting as ext4 improves performance even if it was created as an ext2 or ext3 partition. Sep 06 00:53:14 and ext2 iirc for /opt Sep 06 00:54:14 er, ext2 for /home, which includes /opt Sep 06 00:55:28 By "widely supported for booting" are you talking about non-N900 distributions, because of lack of ext4 in an initramfs or something? Sep 06 00:56:33 It was sort of a vague general statement made with little confidence in my knowledge of the N900-specific booting process. Sep 06 00:58:41 The normal kernel has ubifs and the relevant MTD support built-in, so the mounts that itself and executes /sbin/preinit which is some shell script that checks some stuff then execs the upstart init system. Sep 06 01:01:03 So the easiest way to use something else as root is probably to just replace /sbin/preinit with something that loads the modules required (omap_hsmmc, ext{3,4}, ..), mount the desired root filesystem then pivot_root/chroot and exec /sbin/preinit from there. Sep 06 01:01:08 ubifs is a pretty good choice for the NAND, since it is unmanaged. Sep 06 01:01:38 Indeed. Sep 06 01:01:39 Come to think of it, since it is unmanaged that would mean that ext2/3/4 would be a pretty bad choice. Sep 06 01:02:08 You would need to manage it somehow to use ext2/3/4 Sep 06 01:02:44 It isn't designed for it. Sep 06 01:02:45 but iirc the simple things in Linux are unsuitable for that, since they just make all the blocks visible as a single large block device. Sep 06 01:03:17 Theoretically, you could have something more intelligent to provide that block device. That's pretty much what the controllers in SSDs and SD cards do. Sep 06 01:03:41 Well, performance on / probably isn't as critical as performance on /usr and /home Sep 06 01:04:01 So fiddling with filesystems won't get you much. Sep 06 01:04:15 /usr is normally part of / iirc Sep 06 01:04:22 It's /opt that's on a different filesystem. Sep 06 01:04:52 Yeah, I know, but I am thinking of the deoptified layout. Sep 06 01:04:55 so packagers are encouraged to put their data in /opt. Sep 06 01:05:09 i.e. what stryngs is working on. Sep 06 01:05:14 I don't think it's very useful having a separate /usr Sep 06 01:05:30 but I think the NAND is likely to perform better than the eMMC. Sep 06 01:05:46 Why? Get rid of opt and just mount /usr as the eMMC. Sep 06 01:06:16 because otherwise why would they have it? Sep 06 01:06:18 That is what was being discussed earlier anyway. Sep 06 01:06:35 is it just meant to be like a large initramfs? Sep 06 01:06:56 I don't follow. Sep 06 01:07:08 Why wouldn't they put everything on the eMMC in the first place? Sep 06 01:07:24 and avoid putting an extra tiny NAND chip in? Sep 06 01:08:09 Honestly, I am not sure. Sep 06 01:08:39 I guess you mentioned that it might perform better, but that doesn't seem like a great reason to increase the complexity. Sep 06 01:09:19 It probably does. Sep 06 01:09:30 Especially considering everything to do with booting is on it. Sep 06 01:10:20 I guess it could help ensure some sort of minimum required boot time, set by whatever design groups Nokia had. Sep 06 01:11:05 It could also have to do with filesystem reliability. Sep 06 01:11:12 So what do you think of stryngs' proposal then? Sep 06 01:11:24 I have a feeling ubifs is probably more reliable than ext2 across unexpected shutdowns. Sep 06 01:11:41 it's probably a log-based filesystem, since it's meant for MTDs. Sep 06 01:13:34 Reliability for the root filesystem is not as important if you don't typically modify it. Sep 06 01:15:10 Ideally you would have a full separation between user-installed applications and system applications so that you could mount the root filesystem as read-only during normal use. Sep 06 01:15:45 I don't really like that distinction. Sep 06 01:16:06 I like the idea of just having one filesystem and not having to worry about allocating certain sizes to things. Sep 06 01:16:15 especially on something as restricted as a phone. Sep 06 01:16:25 Filesystem Size Used Avail Use% Mounted on Sep 06 01:16:25 /dev/sdc2 11T 7.6T 3.3T 70% / Sep 06 01:17:23 Having / as a rarely modified partition would allow for diagnostic booting even if the other filesystems get screwed up. Sep 06 01:17:53 That is the main reason to have it IMO. Sep 06 01:19:35 That's a reason to have another system to boot into. Sep 06 01:19:42 possibly just an initramfs. Sep 06 01:20:35 Possibly. So what would you do with the NAND if it was easy to shuffle everything around? Sep 06 01:20:45 If I had greater control over kernel versions, I'd just have a single btrfs filesystem over the eMMC and the SD card. Sep 06 01:20:54 (except for a boot partition and swap) Sep 06 01:21:44 depending on its abilities, possibly swap, but dunno if that's a good idea. Sep 06 01:21:54 I don't really know much about MTD, so don't know what should be done with it. Sep 06 01:22:10 so atm it's basically just a writable initramfs. Sep 06 01:23:30 Well, you need some sort of management for it so that you don't destroy it. Sep 06 01:23:47 Either that, or just don't write to it often. Sep 06 01:23:47 It's still using ubifs. Sep 06 01:24:20 You need some sort of "management", or you can't mount it. Sep 06 01:24:29 Why would you combine eMMC and SD? Your system would fail if you removed the SD card. Sep 06 01:24:30 it's an MTD, not a block device. Sep 06 01:24:52 Why would I remove the SD card? Sep 06 01:25:04 Or it broke. Sep 06 01:25:14 It just seems more frail. Sep 06 01:25:33 I have backups already. Sep 06 01:25:34 Personally I would use the SD for booting other OSes. Sep 06 01:25:46 Or storing files to transfer to other systems. Sep 06 01:26:11 You can already store files in a filesystem. Sep 06 01:26:15 That's what it's for. Sep 06 01:26:30 But you cant pull the eMMC out and put it in another computer. Sep 06 01:26:52 Not practically anyway. Sep 06 01:27:03 I wouldn't want to be constantly pulling the SD card out anyway. Sep 06 01:27:14 They seem physically fragile. Sep 06 01:27:55 That is actually one of the few things I don't like about the N900. I would prefer a slot on the exterior for the SD card, and with a more robust mechanism. Sep 06 01:28:38 i.e. a push-push insertion/ejection slot. Sep 06 01:28:46 I'd find that very inconvenient. Sep 06 01:29:06 You should be unmounting it every time you do it. Sep 06 01:29:25 Oops. Accidentally closed the chat. Sep 06 01:29:29 and to do that you need to think about what processes you have running depending on it. Sep 06 01:29:31 Why would you find it inconvenient? Sep 06 01:29:34 13:29:06 < Maxdamantus> You should be unmounting it every time you do it. Sep 06 01:30:05 eg, I have mpd running with files open from the SD card. Sep 06 01:30:21 so it wouldn't let my unmount it cleanly without stopping mpd. Sep 06 01:30:55 It wouldn't be less convenient, because you could just choose not to remove it. Sep 06 01:31:15 I just transfer things over the network, either WiFi or USB (g_ether). Sep 06 01:31:37 if I choose not to remove it, there's still an annoyingly convenient way to remove it. Sep 06 01:31:56 What about having a safe-eject button? Sep 06 01:32:13 I don't see the point if I don't intend to eject it. Sep 06 01:32:24 I'm also currently using a partition on the SD card as swap. Sep 06 01:32:32 You might not, but I think most users would find it much more useful. Sep 06 01:33:05 Yeah, I'm saying what would be more convenient for me, not others. Sep 06 01:33:22 Though tbh, it does seem silly having removable devices nowadays. Sep 06 01:34:25 Networking already facilitates transferring data. Sep 06 01:34:34 So you just aren't a fan of the sneakernet. :P Sep 06 01:34:45 Not really. Sep 06 01:35:06 People usually still use it because they're not running ssh on their computers. Sep 06 01:35:22 my phone and all my computers already all run ssh. Sep 06 01:36:57 I do remember when floppy disks were the most convenient form of transport for me though. Sep 06 01:38:11 Floppy drives are pretty cool. Very simple electrically. Sep 06 01:38:48 I was still relying on a floppy drive until a couple of weeks ago. Sep 06 01:39:39 Have you seen the strange things people do with floppy drives and microcontrollers? Here is an example: https://www.youtube.com/watch?v=cM_sAxrAu7Q Sep 06 01:39:58 Yes. Sep 06 01:40:10 :) Sep 06 01:41:21 That view count is 88 views off 2^19 Sep 06 01:55:53 Another thing I'd quite like to have which seems slightly relevant to these discussions is .. GRUB. Sep 06 01:56:09 but I couldn't get that to work last time I tried it. Sep 06 01:57:12 (GRUB2 supposedly has the ability to build to load from uboot and use its terminal etc) Sep 06 01:57:56 Yes, more boot options would definitely be nice. I'm not sure what stryngs has set up now, but he said it supports some diagnostics and OS selection IIRC. Sep 06 02:00:39 atm I just have this: https://gist.github.com/Maxdamantus/949e81b445ffaa068449 Sep 06 02:01:04 (you can run that Python script (it just prints stuff to standard output) and laugh at it) Sep 06 02:21:52 ZetaR: Interesting thought on the ext4. tbh, I've not considered filesystem type, for this unification. I believe it's a good thought to add though. Sep 06 02:23:58 So, I've almost got this post written up. I believe it's one of the core arguments to be made for unification. I'll post when it's done. Sep 06 02:24:08 Hmm .. looking at /usr/sbin/osso-mmc-umount.sh it looks like it normally does a lazy unmount of ~/MyDocs, presumably before letting g_file_storage see it. Sep 06 02:24:19 That is basically *COMPLETELY AND UTTERLY* wrong Sep 06 02:24:31 lazy unmount just means it's removed from the filesystem tree. Sep 06 02:24:54 if another process is still in a directory on it or has a filehandle open, it can continue writing to the filesystem. Sep 06 02:26:10 ie, if you rely on the UMS feature in Maemo, you can easily have the same filesystem mounted writable on multiple devices (computer and phone) Sep 06 02:27:25 * Maxdamantus doesn't understand why Linux doesn't seem to have a way to actually force unmount a particular filesystem. Sep 06 02:28:01 seems like the only way to do it is using sysrq to force unmount (or remount readonly) all filesystems Sep 06 02:28:54 .. or you could just reexport the block device as a file in FUSE or an nbd device and make sure only one thing has it writable there. Sep 06 02:30:17 unless it does something like that, it should simply fail if it can't unmount non-lazily. Sep 06 02:47:06 Alright. I have laid out the argument for bindmounts. Sep 06 02:47:26 If anyone has any "Move /usr to eMMC" knowloedge, PLEASE PLEASE PLEASE, respond accordingly. Sep 06 02:48:02 This post for the thread, is actually one of the more "core" issues towards unification. Sep 06 02:48:55 DocScrutinizer05: ^^, you mentioned "movement of /usr". If ya got it written down would love your insight. Sep 06 02:49:10 * stryngs goes back to packaging Sep 06 02:51:36 Just put everything on eMMC. Sep 06 02:51:40 HOW Sep 06 02:51:42 HOW Sep 06 02:51:42 HOW Sep 06 02:51:46 Do ya have it written down!?! Sep 06 02:51:53 If so, please describe Sep 06 02:51:54 No. Sep 06 02:52:00 Maxdamantus: Then it's a pointless point. Sep 06 02:52:11 It's probably not something I'd encourage to people who can't figure it out :\ Sep 06 02:52:11 Maxdamantus: if you can provide instructions, then we can definately use it. Sep 06 02:52:27 Maxdamantus: That's not the point! Let's GIVE BACK to this community. Let us, unify. Sep 06 02:52:40 Maxdamantus: None of us wrote the original Linux kernel, but we all use it. Sep 06 02:52:52 Maxdamantus: I doubt, you or I, could have figured out how to do so. Sep 06 02:53:04 Maxdamantus: yet, we all encourage people to use linux dont we? =) Sep 06 02:53:25 stryngs: the easiest way is to create a different script to replace /sbin/preinit that loads the necessary kernel modules and mounts the appropriate filesystem then chroots into it and execs the original preinit from there. Sep 06 02:53:41 Maxdamantus: Very cool, could you write something up? Sep 06 02:53:45 Maxdamantus: I'd test on my own device. Sep 06 02:54:08 Not sure. I might've had to modify some other things in /etc to stop it complaining. Sep 06 02:54:26 Maxdamantus: if you "start" something, I'm willing to experiment on my own box. Sep 06 02:54:41 But if you're prepared to go through figuring it out, I can show my current init script. Sep 06 02:54:43 Maxdamantus: I would do it myself, but as you see in my post, I'm not knowledgable enough in that lowlevel to do so. Sep 06 02:55:24 Maxdamantus: When you say "my current init" script, you refer to something you use on a live n900? Sep 06 02:56:33 Yes. Sep 06 02:56:37 https://gist.github.com/Maxdamantus/c931687be8fdee4cb60c Sep 06 02:56:39 Word. Sep 06 02:56:41 * stryngs checks it out Sep 06 02:57:38 Maxdamantus: Line 14 is your failsafe? Sep 06 02:58:43 Maxdamantus: You're doing an fsck. does that significantly increase boottime? tbh, do most systems fsck before boot? Again, I know 'nothing' about the 'boot' process on this level. Sep 06 02:58:43 That just sets up networking over USB so I can do things over ssh rather than trying to type on the keyboard. Sep 06 02:59:03 Maxdamantus: I see Sep 06 02:59:04 if false; then Sep 06 02:59:17 So it looks more like a failsafe than anything. Is it always false? Sep 06 02:59:22 It's the wording of the logic I guess Sep 06 02:59:32 If I want to actually use it I'll just modify it. **** ENDING LOGGING AT Sun Sep 06 02:59:58 2015