ChanServ changed the topic of #mlpack to: "mlpack: a fast, flexible machine learning library :: We don't always respond instantly, but we will respond; please be patient :: Logs at http://www.mlpack.org/irc/
ib07 has quit [Ping timeout: 240 seconds]
ib07 has joined #mlpack
kkc has joined #mlpack
< kkc>
hello everyone I am Kaushal Kumar , looking forward to contribute to this community.
kkc has quit [Quit: Connection closed]
ImQ009 has joined #mlpack
< AvikantSrivastav>
I am getting this message, after commenting some files in `src/mlpack/methods/ann/layer/CMakeLists.txt`
< AvikantSrivastav>
Is there any other way I can compile specific modules? or a solution to the above message
< AakashkaushikGit>
Hey seems like you have commented out/ deleted a component from cmake that you were using in `ann_layer_test.hpp`
< _slack_mlpack_U0>
Wait I'll attach cmakelist
< rcurtin>
I was hoping to review a bunch of PRs and work on mlpack today, but today is the day my hard drive has decided to announce that it is done working, so instead I have been spending it trying to move data to a different hard drive
< rcurtin>
not what I had hoped for my afternoon :(
< shrit[m]>
@ryan this is strange
< shrit[m]>
I had a similar issue yesterday
< rcurtin>
too much linking mlpack? :-D
< shrit[m]>
I deleted by error libcrypto.so.1.1 from my laptop
< shrit[m]>
And discovered that basically everything need it as dependency
< rcurtin>
oops...
< shrit[m]>
basically everything, package manger, non official package manger, make, sudo, and list goes on
< shrit[m]>
I tried to repaire it with live CD, but it did not work, even chroot did not work
< shrit[m]>
So my root file system on /dev/sda4 was dead,
< rcurtin>
:(
< shrit[m]>
I took me 8 hours to reinstall the system and have everything back, I am lucky it was only the laptop, which is only used for ssh
< shrit[m]>
lesson learned, we need to stop using libcrypto :)
< rcurtin>
:)
< rcurtin>
yeah, I am not sure how many hours this one will take me
< rcurtin>
the system seems to lock after transferring some amount of data, and even then the data transfer rate off the bad hard drive appears to be in the kb/s, not even MB/s
ImQ009 has quit [Quit: Leaving]
< shrit[m]>
I know how you feel, btw how do you know that hard drive is dying? I never experienced this kind of issues
< shrit[m]>
By the low rate of transfered data?
< rcurtin>
yeah, by that and also sometimes it just freezes up the system entirely
< rcurtin>
it's not giving me any information in dmesg, surprisingly, but it also clicks when I turn the system on :)
< zoq>
no error in the SMART report?
< rcurtin>
I can't keep the system online long enough :-D
< rcurtin>
yeah, anything important is backed up; I have not got /home regularly syncing across all my systems though
< shrit[m]>
Do you keep only one hard drive inside you system ?
< rcurtin>
no, there are multiple in it, but /home was only on one in this case
< rcurtin>
I have been running this as my main desktop since 2011, so it has gotten a little... crusty and strange :)
< rcurtin>
I think this is a good excuse to replace it and build a new one, even though only the hard drive is the issue :)
< shrit[m]>
Yeah, good service 9 years old with a decent amount of workload
< shrit[m]>
I think a good one will be the right thing to do for the next 10 years, now for the next 10 years SSD will take care of your data
< shrit[m]>
good new one
< rcurtin>
:)
< shrit[m]>
Also I find it strange that a lot of people like me in tech prefere old hardware rather than new one, I do not why, but I miss something in the classic old hardware that is nowhere to be found today, always guilty when buying new hardware :(