01:45 <nicksydney> http://anonabox.com/home.html .. thoughts ?

02:21 <whitequark> it's ... misrepresented at best

02:21 <whitequark> there is a reason tor browser bundle exists. if you send all your usual cookies through tor, you are immediately identifying yourself

02:21 <whitequark> in a way, it makes things worse by giving you a false sense of security

02:45 <wpwrak> eintopf: there are no known cases of ebola in argentina so far, and i'd be a rather unlikely candidate for becoming the first one ;-)

02:47 <wpwrak> but it's the long columbus day weekend in the americas. well, columbus day for those of european heritage, "day of cultural diversity" (or such) for those who trace back their origin to natives

11:09 <eintopf> wpwrak: happy columbus day!

11:18 <SyntaxTerror> anyone around?

11:18 <DocScrutinizer05> about my quick and dirty approach to talk to PPSU (/dev/ttyUSB0): it has a downside of creating "-rw-r--r-- 1 root root 5 Oct 14 13:12 /dev/ttyUSB0" when the PPSU is not properly enumerated ;-)

11:21 <DocScrutinizer05> wondered why stuff suddenly fails, after I disconnected (and disassembled) the PPSU. Then I noticed this:

11:21 <DocScrutinizer05> saturn:~ # ll /dev/ttyUSB*

11:21 <DocScrutinizer05> -rw-r--r-- 1 root root 5 Oct 14 13:12 /dev/ttyUSB0

11:21 <DocScrutinizer05> crw-rw---- 1 root dialout 188, 1 Oct 14 13:12 /dev/ttyUSB1

11:24 <wpwrak> surprisingly, there doesn't even seem to be a redirect in bash that gives you write access without also implying O_CREAT. maybe i just didn't find it, or you have to use zsh or such ;-))

11:45 <DocScrutinizer05> wpwrak: might be related to permissions of parent dir. But maybe you can help me out how to check *programmaticaly* in shell script if a file is a character special device file?

11:46 <wpwrak> you can use "test". (man test / help test)

11:46 <DocScrutinizer05> ooh, and about create vs write: it's about >> and some parameter

11:46 <DocScrutinizer05> aaah test, that's been it, thanks

11:46 <wpwrak> but ... this still has a race condition: if the USB device disappears between test and >... access, you still get a new file

11:47 <DocScrutinizer05> sure

11:47 <wpwrak> and yes, you can prevent creation with permissions

11:48 <wpwrak> a bit fragile, though. but as a just-for-joerg-at-home solution, why not.

11:50 <DocScrutinizer05> parameter = noclobber

11:52 <wpwrak> noclobber should still create it if it doesn't exist

11:53 <DocScrutinizer05> err, I'm pretty sure it's meant to fail when file does exist, for >. and to fail when file does not exist, for >>

11:53 <DocScrutinizer05> at least I'm sure I've read this somewhere

11:54 <DocScrutinizer05> -C

11:54 <DocScrutinizer05> If set, bash does not overwrite an existing file with the >, >&, and <> redirection operators. This may be overridden when creating output files by using the redirection operator >| instead of >.

11:54 <DocScrutinizer05> isn't what I recal it been

11:54 <DocScrutinizer05> it's missing the >> aspect

11:57 <wpwrak> maybe write a C program that opens argv[1] without O_CREAT, then forks your shell script with the fd number as first arg ? then you can do your stuff in shell with a properly set up fd

11:58 <wpwrak> well, or exec the shell. no fork needed if you want to optimize

11:58 <wpwrak> (C) or any other real language. plenty of choices ;)

12:01 <DocScrutinizer05> meh

12:02 <DocScrutinizer05> I'm hardly motivated at all to check for type and existence of ttyUSB0

12:23 <wpwrak> all you want is get rid of the O_CREAT. well, you could also write a wrapper library that removes O_CREAT from calls that open something in /dev. that way, you don't need to change your application

12:35 <eintopf> wrapper library for systemcalls, I always search something like that to link other code to it

12:36 <eintopf> for example, unstable closed source software and some watchdog which restarts the unstable software

12:36 <wpwrak> LD_PRELOAD is your friend :)

12:36 <eintopf> wpwrak: yea, I know this, but for systemcalls? I want the normal behaviour

12:37 <eintopf> so only some call open_wrapper, afterwards then it should call open(2)

12:37 <eintopf> from libc

12:38 <eintopf> wpwrak: this should possible? It's like torsocks

12:38 <eintopf> torsocks is wrapper for socket, send, recv etc...

12:39 <eintopf> to make everything via tor, otherwise you need always applications with SOCKSv5 proxy support

12:39 <wpwrak> sure. there ought to be some tutorials on the net. it used to be "deep wizardry", but now it's pretty well-established hackery

12:39 <eintopf> and very important also wrapper for gethostbyname(2)

12:39 <eintopf> mhh

12:39 <eintopf> okay

12:40 <eintopf> gethostbyname isn't a systemcall, yea

12:40 <eintopf> that's something else, because readout also /etc/resolv.conf

12:40 <eintopf> I think :/

12:41 <eintopf> wpwrak: okay, maybe when I have time I will create a library where people could add easily code for that

12:41 <eintopf> libhack

12:41 <wpwrak> LD_PRELOAD is not limited to syscalls

12:41 <eintopf> yep

12:41 <eintopf> I know, at my university I compiled a second rootfs in $HOME/local

12:42 <eintopf> because the pool environment is stupid

12:42 <eintopf> they install libs and not dev debian packets

12:42 <eintopf> and also, there was no autoconf and automake

12:43 <eintopf> and then I make a:

12:43 <eintopf> export LD_LIBRARY_PATH="$HOME/local/lib:$LD_LIBRARY_PATH"

12:43 <eintopf> also for PKG_CONFIG_PATH

12:44 <eintopf> and everything else

12:44 <eintopf> my co-students want's always to know I can install new software on university pc's...

12:44 <eintopf> but I told their "You don't wanna know that"

12:44 <eintopf> because after system upgrade... I can recompile everything

12:45 <eintopf> but I laugh always, because no autotools are installed

12:45 <eintopf> I think the most people do java eclipse programming ;)

12:46 <eintopf> so they don't need autotools (Oh yea I remember you name it autocrap)

12:47 <eintopf> wpwrak: fvwm uses autocrap :P

12:47 <eintopf> everything uses autocrap

12:47 <eintopf> but the most weird buildsystem is the gcc buildsystem, never understand it

12:47 <DocScrutinizer05> ((<wpwrak> all you want is get rid of the O_CREAT)) I hardly could care

12:48 <DocScrutinizer05> I first check if ttyUSB is of right type, then I open it for *reading* which will fail if the file doesn't exist

12:49 <DocScrutinizer05> ( cat /dev/ttyUSB& )

12:58 <DocScrutinizer05> only then I'll open it for writing

13:00 <DocScrutinizer05> what annoys me much more is root permissions needed

13:01 <DocScrutinizer05> though prolly I should add user to dialout group

13:10 <DocScrutinizer05> actually I probably should do a find /sys -path '*cp210x*ttyUSB*'

13:11 <DocScrutinizer05> the damn thing doesn't give away any hint that it's a PSU

13:13 <DocScrutinizer05> they simply added the USB<->RS232 on a separate PCB. Standard, in no way customized. And powered by USB even when PSU is unpowered

13:14 <DocScrutinizer05> that's why I never noticed before about the funny side effects of creating ttyUSB0 by my own script

13:14 <DocScrutinizer05> the device file only vanishes when unplugging USB

13:16 <DocScrutinizer05> http://privatepaste.com/462c28c138

13:19 <DocScrutinizer05> you actually need to tell system: "I'm going to plug in a PPSU, please consider next cp210x showing up on USB as Voltcraft PPS-161005!"

13:20 <DocScrutinizer05> s/161/16/

13:20 <qi-bot> DocScrutinizer05 meant: "you actually need to tell system: "I'm going to plug in a PPSU, please consider next cp210x showing up on USB as Voltcraft PPS-16005!""

13:22 <DocScrutinizer05> how would I rename a /dev/ttyUSB to some other more specific name?

13:23 <DocScrutinizer05> a symlink won't help since it doesn't notice when the ttyUSB vanishes

13:23 <mth> udev rule?

13:23 <DocScrutinizer05> prolly, yep. But I dunno how to rename in such rule

13:24 <DocScrutinizer05> wait, udev creates the device, to start with, right?

13:26 <mth> yes

13:26 <DocScrutinizer05> also it's a tad nasty for a udev rule to go "interactive", i.e. wait answer (or check previously given command) of user, to declare next cp210x as PPSU

13:26 <mth> udev does have a SYMLINK option, I presume it also cleans up the link at unplug then

13:26 <DocScrutinizer05> ummm, makes sense

13:29 <DocScrutinizer05> o/

13:42 <kyak> in case someone missed the global notice: http://bit.ly/1z78rgQ

13:50 <kyak> very interesting is how this shit got into their servers in the first place

15:03 <SyntaxTerror> Still looking to chat to someone about putting together a Tizen dev board for us with a specific screen & capacitive touch input size. Get in touch if you know someone, we have budget!

15:03 <SyntaxTerror> DM or email me at: anthony@make-us-proud.com

15:04 <arhuaco> kyak: That's what I was looking for. No mention of it.

17:29 <astr> SyntaxTerror, custom boards are easy with eoma-68, the the hard expencive bit the soc is taken care of so you can make a simple & cheep custom board with the lcd and touch driver and power supply on it that fits around the screen size you want and the eoma-68 card see rhombus-tech.net browse the sitemap and add your self to the mailing list and ask on there. while the website needs updating the project is moving forward

17:30 <astr> and any money(orders) would help speed things up

17:31 <astr> I belive some work has already been done with tizen on the a20 card

17:35 <SyntaxTerror> @astr: thanks for the info! That looks like a neat bit of kit

17:36 <astr> SyntaxTerror, crowdfunding is planing around nov~

18:05 <DocScrutinizer05> arhuaco: [2014-10-14 Tue 19:02:40] <DocScrutinizer05> http://bit.ly/1z78rgQ is there any info available to mere mortals yet on how this crap crept in? [2014-10-14 Tue 19:02:55] <mist> No more information is available

20:15 <arhuaco> DocScrutinizer05: In the last comment they say they do not know. Weird...