IRC log for #elinux on 20121106

01:11.05*** join/#elinux djerome (~djerome@ip68-2-20-108.ph.ph.cox.net)
02:05.02*** join/#elinux ccxCZ (~ccxCZ@156.200.broadband11.iol.cz)
02:47.32*** join/#elinux ccxCZ (~ccxCZ@156.200.broadband11.iol.cz)
04:05.49*** join/#elinux blupp (~blupp@dslb-188-099-240-178.pools.arcor-ip.net)
04:45.00*** join/#elinux _Lucretia_ (~munkee@pdpc/supporter/active/lucretia)
08:18.30*** join/#elinux suy (~modpow@236.Red-83-57-248.dynamicIP.rima-tde.net)
09:27.01*** join/#elinux isbric (~isbric@c-5e5be255.020-12-6875761.cust.bredbandsbolaget.se)
09:37.58*** join/#elinux jackmitchell (~Thunderbi@195.171.99.130)
09:50.20*** join/#elinux isbric (~isbric@c-5e5be255.020-12-6875761.cust.bredbandsbolaget.se)
09:51.02*** join/#elinux isbric_ (~isbric@c-5e5be255.020-12-6875761.cust.bredbandsbolaget.se)
09:51.39*** join/#elinux isbric (~isbric@c-5e5be255.020-12-6875761.cust.bredbandsbolaget.se)
11:17.27*** join/#elinux gustavoz (~gustavoz@host187.190-139-30.telecom.net.ar)
11:58.21*** join/#elinux cbrake (~cbrake@oh-69-34-21-229.sta.embarqhsd.net)
12:30.46*** join/#elinux phantoxeD (~destroy@a95-92-89-24.cpe.netcabo.pt)
12:32.55*** join/#elinux codefire (51531411@gateway/web/freenode/ip.81.83.20.17)
12:33.06codefirehi all
12:33.30codefirei am new here
12:34.27codefireis it the right place to get help about using JFFS2 with summary on embedded system ?
12:37.22wmatcodefire: always just ask your question. If someone can answer, they will. This applies to all channels.
12:37.40codefireok
12:37.53codefiredo you recommand to use the distribution list instead?
12:38.10codefire*the mailing list
12:38.47wmatI recommend just asking, whichever medium you choose
12:39.11wmatmailing lists do allow for more thorough answers though
14:01.33*** join/#elinux isbric (~isbric@c-5e5be255.020-12-6875761.cust.bredbandsbolaget.se)
14:47.06*** join/#elinux gustavoz (~gustavoz@host187.190-139-30.telecom.net.ar)
15:30.22*** join/#elinux GPSFan (~kenm@64.92.145.112)
16:06.23*** join/#elinux bob_ (461c221f@gateway/web/freenode/ip.70.28.34.31)
16:06.31bob_Hi
16:07.19*** join/#elinux TimRiker (TimRiker@bzflag/projectlead/TimRiker)
16:07.19*** mode/#elinux [+o TimRiker] by ChanServ
16:57.06*** join/#elinux GPSFan (~kenm@64.92.145.112)
17:01.54wmatbob_: hello
17:01.57*** join/#elinux cr-ver (~craver@e180086211.adsl.alicedsl.de)
17:05.01bob_Is it possible to change time_t to a 64 bit integer in order to avoid the year 2038 bug?
17:17.36Russbob_, buy a 64 bit machine
18:16.15bob_thanks, I already have one, but my problem is with an embedded system
18:23.07Russyou can use the bionic time64.h
18:34.22bob_I will look into that, thanks. But is it really a system-wide solution or only a solution for programs compiled to use time64.h instead of time.h?
18:46.32Russyou'd have to modify programs
18:46.49Russpart of the problem is that even if you change time_t in userspace, all the kernel interfaces still use a 32 bit time_t
18:47.18Russperhaps it'd be better to back up and instead of asking for a specific solution, talk about the problem you are trying to solve
18:48.13bob_well I have an embedded system which must be able to run for at least something like 60 years
18:49.48bob_there will be many logs produced
18:50.12bob_I don't really need dates before 1970 so maybe switching to an unsigned time_t would be an option
19:00.22bob_unsigned 32 bits seems to do the job. Time continue after 2038
19:01.01Russif you are running 32-bit, you'd have to audit everything
19:01.05Russso many things use time_t
19:01.41bob_yeah. But I didn't make any changes to the kernel. Should I?
19:03.17Russwell all the apis are 32-bit time_t
19:40.01*** join/#elinux ccole (~cole@coledd.com)
22:09.44*** part/#elinux pytey (~pytey@howler.blatero.com)
22:49.51*** join/#elinux dijenerate (~dijenerat@173.225.251.175)
23:59.43*** join/#elinux ccxCZ (~ccxCZ@156.200.broadband11.iol.cz)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.