Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
<GNUtoo> DocScrutinizer05, I guess theses laptops aren't cheap
<GNUtoo> there are 2 rugged laptops supported by coreboot btw
<DocScrutinizer05> aqctually quite cheap, on fleabay and refurbished
<GNUtoo> ok
<DocScrutinizer05> ~330EUR
<DocScrutinizer05> for a CF-29 in top condition
<GNUtoo> ok
<GNUtoo> personally I'm more interested in the Getac P470 or the Roda RK886EX (Rocky III+) which are supported by coreboot, or simply a lenovo x60/t60
<DocScrutinizer05> T500 typing here
<kristianpaul> DocScrutinizer05: getting ready for next deluge?
<DocScrutinizer05> just preparing to finally sniper poettering
<kristianpaul> :)
<DocScrutinizer05> fucktards
<kristianpaul> soon you'll read, booting without paying to microsoft a tax is ilegal :)
<DocScrutinizer05> >>Due to this, many upstream developers have decided to consider the problem of a separate /usr that is not mounted during early boot an outdated question, and started to close bugs regarding these issues as WONTFIX. We certainly cannot blame them, as the benefit of supporting this is questionable and brings a lot of additional work with it.<< BWAHAHAAAHAAAA does this guy really think we'll buy his lame excuse for lazyness and not
<DocScrutinizer05> maintaining his system properly?
<DocScrutinizer05> A)mount /usr *early*! B) move stuff you need before mounting /usr to /[s]bin C) don't use friggin useless stuff like PA in early boot, for the "questionable benefit" of e.g. playing a powerup jingle with the default PA shite
<kristianpaul> GNUtoo: x60 is really cheap !
<kristianpaul> interesting
<kristianpaul> anyway .. :-)
* kristianpaul argghh not get distracted again :)
<GNUtoo> kristianpaul, it's a computer, and the support is close to 100% complete
<GNUtoo> so I guess you just need to :
<GNUtoo> 1) take information on it
<GNUtoo> 2)buy it
<GNUtoo> 3)install coreboot on it + a distro
<GNUtoo> and you're done
<GNUtoo> no need to hack on it
<GNUtoo> I mean on coreboot
<kristianpaul> good deal
<GNUtoo> indeed
<GNUtoo> if you can find one in your area it's a good deal
<GNUtoo> else it become complicated to buy second hand stuff online etc...
<kristianpaul> i can but x40..
<kristianpaul> anyway..
phirsch has quit [Ping timeout: 248 seconds]
phirsch has joined #qi-hardware
<qi-bot> [commit] Werner Almesberger: components/: generate for connectors CONN_1 to CONN_40X2 (in gencon.lib) (master) http://qi-hw.com/p/kicad-libs/7864070
wej has quit [Ping timeout: 248 seconds]
GNUtoo has quit [Quit: Program received signal SIGSEGV, Segmentation fault.]
wej has joined #qi-hardware
<kristianpaul> wpwrak: seems your m1 patches not work well http://paste.debian.net/173758/
xwalk_ has quit [Quit: Leaving]
xwalk_ has joined #qi-hardware
paroneayea has quit [Read error: Connection reset by peer]
paroneayea has joined #qi-hardware
compcube has quit [Ping timeout: 260 seconds]
emeb has quit [Quit: Leaving.]
emeb has joined #qi-hardware
<wpwrak> they should work with rtems 5c51ba1333d96e2ada2c374ba22b551d179e6685
<wpwrak> maybe something has changed upstream since. that was two months ago
<kristianpaul> 1d179e6685, thats what i need it, thanks !
emeb has left #qi-hardware [#qi-hardware]
<kristianpaul> oh dear... http://paste.debian.net/173765/
* kristianpaul trying with 07896ad5d78af2f47e79c6829e3a57718d660e44
<wpwrak> the rtems-yaffs i have its cbe7492ee0e5a9bced8267d9c7ab2fd997299fda
rejon has joined #qi-hardware
jekhor has joined #qi-hardware
kristoffer has joined #qi-hardware
viric has quit [Quit: reiniciem]
viric has joined #qi-hardware
<viric> nice
<viric> how does GPL apply to verilog ?
<viric> All verilog synthesized to a single chip has to be GPL?
<lindi-> viric: what does it mean that "chip is GPL"?
<viric> And it can be connected only to other GPL chips? A LGPL verilog would allow connecting it to non-GPL chips
<viric> :)
<viric> lindi-: I also don't know. hehe
<viric> ah, I meant "verilog has to be GPL"
<viric> (synthesized to a single chip)
<viric> LGPL allows 'linking' to non-GPL pieces, but only if the LGPL pieces can be replaceable. Hence, a chip appart :)
Textmode has quit [Ping timeout: 255 seconds]
jurting has joined #qi-hardware
Textmode has joined #qi-hardware
viric has quit [Ping timeout: 244 seconds]
GNUtoo has joined #qi-hardware
wolfspraul has quit [Quit: Lost terminal]
xwalk_ has quit [Ping timeout: 248 seconds]
wolfspraul has joined #qi-hardware
jekhor has quit [Ping timeout: 244 seconds]
Aylax has joined #qi-hardware
* pabs3 didn't think copyright law applied to chips
Aylax has quit [Ping timeout: 252 seconds]
B_Lizzard has joined #qi-hardware
viric has joined #qi-hardware
viric has quit [Quit: tornem-hi]
Aylax has joined #qi-hardware
<roh> hm. gpl/lgpl.. maybe even agpl... i should ask the lawyers about that. thats a real good question
DocScrutinizer has joined #qi-hardware
DocScrutinizer has quit [Changing host]
DocScrutinizer has joined #qi-hardware
marcan has quit [Ping timeout: 250 seconds]
DocScrutinizer05 has quit [Ping timeout: 240 seconds]
DocScrutinizer06 has joined #qi-hardware
DocScrutinizer2 has quit [Ping timeout: 265 seconds]
marcan has joined #qi-hardware
Textmode has quit [Ping timeout: 255 seconds]
xwalk_ has joined #qi-hardware
viric has joined #qi-hardware
<viric> roh: I found my OOMK hangs relate to reiserfs. Having moved to ext4 it does not hang anymore, under OOMK conditions
<viric> roh: nevertheless, when I filled the same-size new ext4 fs with the files I had in the reiserfs, not only ext4 took far more disk...
<viric> but I had 92% of inode usage.
Aylax has quit [Ping timeout: 252 seconds]
panda|x201 has joined #qi-hardware
jekhor has joined #qi-hardware
Aylax has joined #qi-hardware
Aylax has quit [Client Quit]
Aylax has joined #qi-hardware
Aylax has quit [Client Quit]
phirsch has quit [Ping timeout: 245 seconds]
phirsch has joined #qi-hardware
jekhor has quit [Ping timeout: 244 seconds]
kristoffer has quit [Quit: This computer has gone to sleep]
kristoffer has joined #qi-hardware
<kristianpaul> wpwrak: it works now thanks a lot !
<wpwrak> was a pleasure to help :) and sorry for the inconvenience.
panda|x201 has quit [Ping timeout: 245 seconds]
jurting has quit [Ping timeout: 252 seconds]
<roh> viric: inode-count is set on format.
<qi-bot> [commit] Werner Almesberger: modules/pads-array.fpd: we need loop for pins and for packages, not just one (master) http://qi-hw.com/p/kicad-libs/20c9436
<qi-bot> [commit] Werner Almesberger: components/adxl32x.lib: Analog Devices ADXL321, ... accelerometers (master) http://qi-hw.com/p/kicad-libs/96c7eb3
<qi-bot> [commit] Werner Almesberger: modules/qfn.fpd: add experimental footprint for AD CP-16-5a* MQ_LFCSP_LQ (master) http://qi-hw.com/p/kicad-libs/e01b8d6
<roh> viric: you can easily make it have more inodes.
panda|x201 has joined #qi-hardware
<viric> yes, reformatting, I know
<viric> I used triple inodes (now ~33% usage) on the new format
<roh> viric: well.. you did that anyhow. usually if you do not run a ntpd on it one doesnt need extra many inodes
<viric> But I also noticed that for the very same files, ext4 needs 1,8GB *MORE* than reiserfs (on a 7,8GB disk. That's 23% of the disk)
<roh> you are sure you set reseved blocks the same?
<viric> ?
<viric> I've a tar. I unpack it to a reiserfs, or to an ext4. That's the difference in "df" free.
<roh> and not dialed around on bytes per inode or inode-size?
<viric> The default "mkfs.ext4" used 1,6GB more than reiserfs.
<viric> With triple inodes (500k vs 1500k) it uses 1,8GB more than reiserfs.
<roh> well... i do not have any clue what your distro uses ad defaults
<viric> my distro?
<viric> I run mkfs.ext4 /dev/blabla
<viric> why would the distro matter?
<roh> they all patch stuff/package different defaults
<viric> uh?
<viric> hm
<viric> I'll check the recipe
<viric> configureFlags = "--enable-elf-shlibs --disable-libuuid --disable-libblkid --disable-uuidd --disable-fsck";
<viric> That's the only detail out of "./configure; make; make install"
<roh> viric: i have a 116G filesystem here, which has 7684096 inodes. of that 30G are used (4 linux virtual machines) which is 419283 inodes.
<roh> so inode used count is direct proportional to space used in mbytes (atleast within 1% error)
<roh> ah. no. its 6% inodes used, to 28% diskspace used. sorry. checked the wrong table here.
<viric> well, the number of inodes depends a lot on the number of files you have
<viric> if you store videos, you'll have few inodes :)
<viric> their default guess does not match my usage, it seems
B_Lizzard has quit [Remote host closed the connection]
<viric> and for the disk space used... ext4 looks somehow optimised to big files. Small files take a lot, compare to reisersf (23% of the full fs)
<roh> viric: thats why one can adjust the settings. no heuristics can guess right in advance
<viric> do you have any suggestion of settings?
<viric> I'd be fine with 1500k inodes...
<viric> But I want more free space. I've no idea what to touch.
<viric> roh: I can paste you dumpe2fs
<roh> viric: how big is that fs in total?
<roh> half a million inodes seems low
<viric> roh: 8GB
<viric> (7,8GB, well.)
<roh> that seems ok.
<roh> what stuff do you put in there that you need so many small files?
<viric> OS files mostly
<viric> but as far as I understand, I can't make ext4 give me more free space for my use case.
<roh> viric: still weird. try finding out where you have 'many small files'
<viric> I know where they are... whether they are a lot or not, I can't tell
<viric> It's a matter of taste I imagine
<roh> viric: as shown above i have very few files per 'OS'
<roh> the 419283 inodes are 4 complete ubuntu server vms(12.04)
<viric> well, it's a development machine; I have all headers, libs, ...
<viric> not only runtime
<roh> ah. i see.
<roh> well.. then just tell it do use more inodes
<viric> in any case, I'm loosing 1,8GB that using reiserfs I'd have free
<viric> losing
<viric> pity
<viric> A hardcore dev would just fix reiserfs :)
<roh> i still dont get where those 1.8g should go. i dont have that here
<roh> well. yeah. the journal needs to be somewhere, but reiser needs that also, right?
<viric> roh: I've two loop devices of the same size, same tar unpacked to them. I run 'df', and shazam... 1,8G difference
<viric> yes, reiser has journal to
<viric> too
<viric> hum maybe I did not pass the hardlinks with tar... does tar pick hardlinks by default?
<viric> hm maybe it's that. I'll resolve the hardlinks
<roh> viric: reserved space?
<viric> I should have used --hard-dereference
<viric> Let's try.
compcube has joined #qi-hardware
compcube has quit [Changing host]
compcube has joined #qi-hardware
GNUtoo has quit [Remote host closed the connection]
Aylax has joined #qi-hardware
DocScrutinizer06 is now known as DocScrutinizer05
kuribas has joined #qi-hardware
panda|x201 has quit [Ping timeout: 245 seconds]
kuribas has quit [Read error: No route to host]
kuribas has joined #qi-hardware
panda|x201 has joined #qi-hardware
GNUtoo has joined #qi-hardware
GNUtoo has quit [Quit: Program received signal SIGSEGV, Segmentation fault.]
jurting has joined #qi-hardware
jekhor has joined #qi-hardware
Aylax has quit [Quit: Bye]
emeb has joined #qi-hardware
GNUtoo has joined #qi-hardware
kilae has joined #qi-hardware
wolfspraul has quit [Ping timeout: 244 seconds]
<DocScrutinizer05> viric: check for stuff hidden under mountpoints
<DocScrutinizer05> age old prank
wolfspraul has joined #qi-hardware
<DocScrutinizer05> also semantics of "used space" differs a lot, depending if you count and sum up real filelength, or you calculate space taken on storage - incl. sector overhead which is statistically 0.5 sectors/file
<DocScrutinizer05> plus inodes and whaztnot
<viric> DocScrutinizer05: I only look at 'df' free space
<viric> DocScrutinizer05: I mount one fs into ./r, the other into ./o;
compcube has quit [Ping timeout: 260 seconds]
<DocScrutinizer05> viric: ooh, I didn't mean mountpoint where the fs under test got mounted. Hidden files under a mountpoint count for the disk usage of the fs where the mountpoint dir is located, not for the mounted fs
<DocScrutinizer05> so aiui you mount a fs under ./o or ./r, and probably both have no mounts on them, so are unaffected by any hidden files
<viric> yes
<viric> in any case I look at 'df'
compcube has joined #qi-hardware
compcube has quit [Changing host]
compcube has joined #qi-hardware
<viric> I think that maybe the hardlinks explain the story... one fs has hardlinks, the other not
<DocScrutinizer05> df probably just looks for free blocks
<viric> but I don't know how to convey hardlinks from one side to the other.
<viric> tar --hard-dereference clearly fails
<viric> in fact when I used --hard-dereference, I had even less free space
<viric> AH!
<viric> because 'tar' by default respects hard links, and with --hard-reference I made it copy the contents...
<DocScrutinizer05> yep, sounds right
<viric> Weird. Then ext4 is really taking 23% of *additional* metadata compared to reiserfs
<viric> 23% of the total filesystem.
<viric> I've 1,8GB unavailable only because I use ext4 instead of reiserfs.
<DocScrutinizer05> hard to believe
<viric> do you want to test yourself? I could prepare a public tar. :)
<DocScrutinizer05> well, reiserfs afaik packs files, which means there's no wasted space at and of files (this average half sector)
<DocScrutinizer05> for a lot of files this can sum up
<DocScrutinizer05> s/at and/at end/
<viric> they have that 'tail' thing, yes
<viric> 400k files
kristianpaul has quit [Quit: leaving]
kristianpaul has joined #qi-hardware
kristianpaul has joined #qi-hardware
kilae has quit [Quit: ChatZilla 0.9.88.2 [Firefox 13.0/20120601045813]]
<viric> Does somebody know if UML works for anything other than x86?
<viric> (no arm and no mips, I imagine)
kristoffer has quit [Quit: Leaving]
Aylax has joined #qi-hardware
compcube has quit [Quit: Leaving]
zear has quit [Quit: bye]
kuribas has quit [Quit: ERC Version 5.3 (IRC client for Emacs)]
zear has joined #qi-hardware
jekhor has quit [Ping timeout: 252 seconds]
xiangfu has joined #qi-hardware
GNUtoo has quit [Quit: Program received signal SIGSEGV, Segmentation fault.]