[08:56] <tdr112> morning all
[08:56] <ebel> yo
[08:56] <tdr112> what is the best why to find a file , just grep the whole disk
[08:57] <ebel> find
[08:57] <ebel> there's a command for it.
[08:57] <ebel> that'll find files (& directories) based on the name, location, size etc. Do you need to search inside a file or just the name/path/etc?
[08:58] <tdr112> ah that is better
[08:58] <tdr112> thanks ebel
[09:01] <tdr112> much much much quicker
[09:04] <ebel> were you grepping "grep /dev/sda1" ? :P
[09:14] <tdr112> na even worse grep /*
[09:14] <tdr112> bad mistake , it was even looking in /proc
[09:15] <tdr112> only had it going for a minute and said to myself this cant be right
[09:15] <ebel> hehehe
[09:15] <ebel> "find /" will do similar
[09:15] <ebel> but you can add in "-x" or something to restrict it to only one device
[09:16] <tdr112> but not open the files :)
[09:16] <ebel> lots of unix commands that do recursiveness often have an option to only stay on one device.
[09:16] <ebel> I was backing up a server once and copying all the files. I wondered if it was a good idea to do it with /proc (or /dev) or something
[09:17] <ebel> and someone pointed out that /dev/kmem (?) is the contents of the RAM of the machine, and that it would not be wise to restore that to an existing system :P
[09:17] <tdr112> you dont need /proc
[09:17] <ebel> You can look into the files with the -exec argument to find
[09:18] <ebel> or pipe through xargs, parrellel, etc.
[09:18] <tdr112> it is a virtual file system
[09:19] <ebel> yep
[09:21] <airurando> morning
[09:29] <tdr112> hey airurando
[09:29] <airurando> hi tdr112
[09:29] <airurando> long time no see
[09:29] <airurando> you all set for electric picnic?
[09:32] <tdr112> nope , i hope to get my tent and all that this weekend if i dont have to work
[09:35]  * airurando won't be able to make the early part of the release party on 15 oct 11 due to work :(
[09:36] <airurando> shift has gone from 4 to 3 people and that weekend one of the girls is getting married with the other going to the wedding.
[09:37] <airurando> Some other poor sod has to be drafted in to help me so no point in even asking for time off.
[09:42] <ebel> We've got the OK from TOG for a global jam there
[09:42] <ebel> So there'll be a Dublin venue for the Ubuntu Global Jam, in TOG
[09:59] <tdr112> airurando: we will have to get back onto the galway lads again about bug jam , as i think i stole them for the hackerspace at electric picnic
[10:01] <airurando> tdr112 no I think it is ok
[10:02] <airurando> a few of them were at the monthly meeting on the 17th and they said they were going ahed with it.
[10:02] <airurando> they put it up on their calendar of events so I generated the loco dir listing based on that
[10:03] <airurando> charles-091labs said he was going to electric picnic with you but some other members stepped up to the plate (fair play to them)
[10:04] <tdr112> yep but i only got them to come to ep the other night ,
[10:13] <airurando> tdr112 I don't follow. what is ep?
[10:13] <ebel> electric picnic
[10:14] <airurando> thanks ebel
[10:15] <ebel> some hackerspace people are going to do demos and stuff (right?)
[10:15] <airurando> tdr112 are you sure they are all going?
[10:15] <airurando> that is not the way it was portrayed at the monthly meeting
[10:16] <airurando> tdr112 could you clarify this as we'll have to pull the Galway one down from the loco dir if it is not going ahead
[10:16] <tdr112> airurando: i have talk to them since the monthly meeting , 3 out of the 4 are going , i will email them now to confirm they are going ahead
[10:17] <airurando> thanks
[10:18] <airurando> it is still listed on their upcoming events
[14:53] <tdr112> any one know how to go from unix time to real time
[14:53] <ebel> date
[14:54] <tdr112> i have a time in millseconds
[14:54] <tdr112> since 1970
[14:54] <tdr112> i want its real time
[14:55] <ebel> with @
[14:55] <ebel> e.g. date -d "@1234567890"
[14:55] <ebel> date -d SOMETHING will parse and print the date represented by SOMETHING
[14:56] <ebel> (pedantically unix time is only approximately the number of seconds since 1st jan 1970, it doesn't include leap seconds)
[14:56] <ebel> probably not relevant for you, but remember sometimes unix time can go backwards.
[14:57] <ebel> (when a leap second occurs the unix time might go forwards then backwards to make all the sums add up)
[14:57] <tdr112> so i have this 13143700177851471228928
[14:58] <tdr112> i want it in normal time
[14:58] <tdr112> date -d "@13143700177851471228928"
[14:59] <tdr112> now working
[15:01] <tdr112> ah ok its not linux its a java problem , my * was in int when it should be long
[15:04] <ebel> you divide by 1,000,000 to get from nanosec to seconds?
[15:04] <ebel> sorry, 1,000 to get from millisec
[15:05] <ebel> might wanna double check the source for your numbers. see if the specs say "unix time" or "milliseconds since 00:00 1st jan 1970", cause there could be a difference due to leap seconds.
[15:06] <ebel> (if there is a spec ;) )
[15:06] <ebel> (very much depends on how accurate you want/need it to be)