--- Log opened Sat May 12 00:00:16 2018 --- Day changed Sat May 12 2018 00:00 < Two_Dogs> its all linux in the end 00:00 < bls> huh? 00:01 < Two_Dogs> besides, if i ask apple they gonna tell me to buy some expensive thing i dont need/want 00:01 < Two_Dogs> or is ios more bsd like 00:01 < Two_Dogs> ? 00:01 < bls> iOS is BSD based 00:01 < Two_Dogs> ok 00:02 < aaro> mawk: in c you do "int mysocket = socket (...); how you call a netlink one? 00:02 < bls> and just barely 00:02 < Two_Dogs> i have looked at the analytics dump for some process on the thing, seems very linux'ish 00:03 < quul> aaro: using AF_NETLINK instead of AF_INET of AF_UNIX 00:03 < bls> they're both based on classic unix designs 00:03 < quul> s/of/or/ 00:04 < aaro> oh ok, same socket call just different family, thanks quul 00:06 < mawk> yes aaro 00:06 < mawk> but you don't use recv() but recvmsg() 00:07 < mawk> it allows you to receive a number of well delimited messages instead of a chunk of data 00:08 < mawk> and there is a set of macros to manipulate the data, because there are some alignment constraints 00:09 < mawk> aaro: for instance here's my boilerplate code for receiving events related to interface addresses, policy routing and the routing table: http://paste.suut.in/xBagRyR5.cpp 00:09 < mawk> I use some slightly higher level lib to create and manipulate my netlink socket but it's all the same, the open2 call is like socket(), etc 00:13 * aaro nods 00:41 < CuriousMind> Hi, can someone guide me in installing an iso image via command line? I don't know what I am doing 00:43 < CuriousMind> What I am trying to install is CentOS. I went to this website: http://dallas.tx.mirror.xygenhosting.com/CentOS/6.9/isos/x86_64/ , copied the URL, then did `curl http://dallas.tx.mirror.xygenhosting.com/CentOS/6.9/isos/x86_64/` and I started seeing a bunch of alien characters and stuff 00:43 < koala_man> haha 00:43 < xamithan> Why you curl a URL 00:43 < xamithan> er ISO 00:43 < xamithan> define "installing" too 00:44 < CuriousMind> xamithan: I thought that's what you are suppose to do? 00:44 < koala_man> CuriousMind: you want to download an iso and put it on a usb drive from the command line? installing from it is a separate step 00:44 < xamithan> I wget them 00:44 < CuriousMind> I'm trying to get CentOS on my virtual machine 00:44 < koala_man> ah 00:44 < xamithan> wget will download it, then just select the iso in your VM software 00:44 < koala_man> CuriousMind: curl -O url to save to file instead of writing to screen 00:45 < CuriousMind> xamithan: That's the command wget, not curl 00:45 < xamithan> Well curl will work too if you use the syntax koala said 00:45 < koala_man> 'wget url' and 'curl -O url' do the same thing 00:45 < CuriousMind> I see. Ok I am going to try now, thanks guys 00:46 < xamithan> I tried to cat an ISO one day. I thought I found the matrix 00:47 < CuriousMind> xamithan: lol yeah that was what I was seeing, the matrix 00:48 < koala_man> it's not necessarily insane. head -c 1000 file.iso is one way to check if it's usb bootable without 'file' and such available 00:50 < CuriousMind> Question, why is it when I did `curl ` it didn't just download normal? 00:50 < dannylee> hacking pool and chess are my favorite games... 8-) 00:50 < koala_man> CuriousMind: it downloaded normally for curl, whose default output is screen instead of file 00:50 < dannylee> its another great weekend 00:50 < uplime> curl -so disc.iso "$isourl" 00:50 < uplime> maybe -sSo 00:51 < CuriousMind> koala_man: I don't understand 00:52 < xamithan> He said it DID download, but it downloaded straight to your terminal instead of the filesystem 00:52 < koala_man> CuriousMind: it downloaded the file and showed it to you. it's not curls fault you don't know how to read iso9660 00:52 < CuriousMind> I'm a student by the way so I don't understand any of this lol. I just know that the curl is a tool that helps transfer data and you guys showing me a bunch of commands with options 00:53 < koala_man> CuriousMind: try 'curl wttr.in/dublin' for something that's more human readable than a .iso file 00:53 < CuriousMind> xamithan: Ok I understand that, thank you. It downloaded to my terminal instead of to the filesystem. Interesting, elaborate please? 00:53 < uplime> it didn't download to the terminal 00:53 < uplime> curl downloaded it, and spit its contents to the terminal 00:53 < uplime> which is its default behavior if you don't provide a file 00:53 < xamithan> semantics 00:53 < uplime> its an important difference 00:53 < uplime> for understanding what curl is doing 00:53 < koala_man> CuriousMind: you know how if you do 'echo foo' it shows 'foo' on screen? curl did the same but with a .iso file 00:54 < CuriousMind> koala_man: yes I see 00:55 < koala_man> it's very useful in scripts. for example, curl yoururl | tee /dev/sdd /dev/sde > /dev/sdf would have downloaded the file and written it to three separate USB devices at once without needing to store the file on disk first 00:56 < CuriousMind> koala_man: I see 00:58 < CuriousMind> Ok so curl downloaded the contents of the iso to my terminal, but not to a file. So curl indeed do what it was suppose to do which is to transfer data from server to me, but it was my mistake not to add an option to specify where contents should be stored in my system. Am I correct? 00:58 < koala_man> right 00:59 < CuriousMind> Ok that makes sense as to why people do curl