**** BEGIN LOGGING AT Sat May 28 02:59:58 2016 May 28 08:10:12 ZeekHuge: you actually here, or your client just decided to rejoin? May 28 08:11:16 * Wormo looks at clock, decides the latter May 28 08:25:46 Hey Wormo May 28 08:25:49 I am here .. May 28 08:25:56 oh hi May 28 08:26:00 hey :) May 28 08:26:30 so I took a look & you're right, pru_rproc got added not long after the GSOC baseline May 28 08:26:43 in 4.4.9, I think May 28 08:27:34 so it should be fine to pull it into your 4.4.8 tree as a patch May 28 08:27:48 I got the 4.4.11-ti-r28 and it has pru_rproc in it May 28 08:28:17 so just cp it into 4.4.8 ? May 28 08:29:05 simple as that might work May 28 08:29:33 if not, should be a small number of git commits that you could grab as patches May 28 08:30:17 from the TI tree where RCN got it from (might have seen reference to the TI tree in one of his commits, not sure...) May 28 08:49:31 Hi anybody there? May 28 08:49:44 does anybody know how to boot a newly build uImage on beaglebone black? May 28 08:56:12 you want to netboot it over tftp, put it on SD card, or what? May 28 08:56:59 kiran4399 ^^ May 28 08:57:40 I just build a 4.4 kernel.. I need to put into my beaglebone black which is having debian 14.04 May 28 08:57:45 3.14 kernel. May 28 08:57:57 I mean it has 3.14 kernel on it already.. May 28 09:00:16 Wormo: ^^ May 28 09:04:59 it probably has the 3.14 internal storage, emmc right? May 28 09:05:46 in which case it's a nice thing to do a new image on sd card, keeping the older working install on emmc May 28 09:10:18 Worm: yeah.. May 28 09:10:45 Wormo: I am sorry.. it has 4.1.17.. May 28 09:10:48 not 3.14 May 28 09:11:55 same idea though, I still recommend keeping your working emmc pristine and flashing an SD card with rootfs and your new kernel + modules May 28 09:13:02 Wormo: Is'nt there any procedure to just transfer the uImage file from the host machine and start booting from it? May 28 09:13:06 kiran4399: you can also follow https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-ARMCrossCompiler:GCC May 28 09:13:13 or http://wiki.beyondlogic.org/index.php/BeagleBoneBlack_Building_Kernel May 28 09:13:51 you can tftp boot if if you want, but you'd need to install the modules first into the rootfs May 28 09:14:20 tftp boot is good when you're testing out a lot of kernels May 28 09:15:03 it's not hard to put tftp server on your host May 28 09:30:50 ZeekHuge: That link which you sent.. did you try it yourself? Is it working for ubuntu 14.04? May 28 09:32:51 Wormo: seems like a huge process. I actually need to test the kernel which I built.. I don't think I should do it each and everytime right? May 28 09:34:32 no i didn’t try it. but i think it should. May 28 09:34:50 Wormo: What if I write the new 4.4 image and flash BBB?? If I make some modifications on the 4.4 kernel and build it.. in this case can I just transfer the uImage file? May 28 09:34:55 ZeekHuge: ^^ May 28 09:36:24 kiran4399: which project are you doing again? one where you will be testing a lot of kernels or no? May 28 09:36:49 api support for beaglebone black.. May 28 09:36:59 Wormo: I need to test the pru kernel driver for beaglebone black 4.4 May 28 09:37:19 ok plenty of kernels, I'd say it's worth setting up to boot tftp May 28 09:37:32 it's fast iteration once you got it set up May 28 09:38:09 I looked a lot of websites.. not working.. can you get me a proper link if you have successfully tried for debian image? May 28 09:38:10 Wormo: ^^ May 28 09:39:18 I'll look for one w/out nfs since that's probably not as useful as the tftp for you May 28 09:39:57 http://elinux.org/Building_BBB_Kernel#Transferring_the_image_to_the_BBB_via_TFTP May 28 09:40:20 hm too old, no dtb file May 28 09:57:30 ok about to put a quickstart up on pastebin, not found one I liked May 28 09:58:55 http://paste.debian.net/plain/710830 May 28 09:59:23 it's time to get sleep, hopefully it's understandable May 28 09:59:44 gnight May 28 11:08:25 Does anybody know how to bringup u-boot command line? May 28 15:36:24 kiran4399: you're running ubuntu on your beaglebone? May 28 15:50:38 alexhiam: yeah.. ubuntu May 28 15:53:32 kiran4399: the ubuntu images are out of the control of bb.org and could have differences in the filesystem, it's better to use the bb.org Debian images May 28 15:54:44 kiran4399: you should be starting with the "Jessie for BeagleBone" image here: http://beagleboard.org/latest-images May 28 15:55:09 alexhiam: Alright.. so do you want me to flash the emmc with this: bone-debian-8.4-lxqt-4gb-armhf-2016-05-01-4gb.img May 28 15:55:30 kiran4399: I'd recommend flashing it to an sd card and just booting off that May 28 15:55:41 OK.. May 28 15:55:49 alexhiam: advantage? May 28 15:56:09 kiran4399: that way it's easier to load kernel images you build right onto it, plus you can have a couple sd cards going with different images and swap between May 28 15:56:50 kiran4399: you can also do your building with this: https://github.com/RobertCNelson/bb-kernel May 28 15:57:10 alexhiam: just tell me one thing.. when I get the uimage.. should I use the bb-kernel or the image-builder? May 28 15:57:12 clone that and checkout am33x-v4.4 May 28 15:58:28 with bb-kernel you can use the tools/install_kernel.sh script to install the new kernel on your sd card May 28 15:58:50 which is a lot quicker than building and flashing a new image, and you don't lose your data May 28 16:01:32 that's just the way I've done bb kernel dev May 28 16:05:32 alexhiam: Alright.. I am on it.. I got all the kernel drivers of the pheripherals.. I am testing the pru kernel driver for linux 4.4 May 28 16:05:45 alexhiam: did you try it before?? May 28 16:06:14 alexhiam: can you give me some guidelines.. because these 2 weeks.. I think that is the main one.. May 28 16:06:32 kiran4399: awesome. Did I try the 4.4 PRU stuff? I only just fired up 4.4 the other day, haven't really tried much on it... May 28 16:07:06 kiran4399: did you end up adding any new drivers? May 28 16:07:20 bm180.c May 28 16:07:35 alexhiam: I still have to configure mpu9150.. May 28 16:07:53 because the cape uses mpu9150 May 28 16:08:59 alexhiam: ^^ May 28 16:09:45 right. Well the new driver, once it's tested and working, can be submitted to the ml as a patch May 28 16:09:54 yeah.. am on it.. May 28 16:10:01 kiran4399: do you know how to generate a patch? May 28 16:10:12 alexhiam: yeah... using git diff May 28 16:10:18 cool May 28 16:14:04 alexhiam: I've got a doubt.. May 28 16:14:52 kiran4399: didn't we figure out that there's a driver that works for all the MPU parts? May 28 16:15:58 kiran4399: what's your doubt? May 28 16:17:55 alexhiam: I have the uImage file.. How should I use the bb-kernel? May 28 16:19:13 kiran4399: oh.. you might need to rebuild with the bb-kernel repo May 28 16:19:30 once you've added your changes to that it'll be a lot easier going forward May 28 16:20:01 alexhiam: so should I give the entire kernel source code or the patch as input to bb-kernel? May 28 16:22:41 kiran4399: been a while since I've done this, I need to dig up my notes.... May 28 16:25:53 kiran4399: ok, so you want to clone bb-kernel, checkout the 4.4 branch and run build_kernel.sh May 28 16:26:36 then you make your additions in the KERNEL/ directory that gets created and run tools/rebuild.sh May 28 16:26:58 then you can do tools/install_kernel.sh to test, and once an update is confirmed working you create the patch May 28 16:27:54 alexhiam: ok.. so there is no way to input uimage file? May 28 16:28:34 and it's probably best to checkout a new branch in the KERNEL/ dir after the first build for each change, which will make patching easier I think May 28 16:28:50 kiran4399: I'm sure there is, but I don't know it May 28 16:29:18 kiran4399: I gotta run for a bit, is that enough to keep you going for now? May 28 16:29:38 alexhiam: guidelines for pru kernel driver? May 28 16:29:59 alexhiam: I mean if the 4.4 pruss failes.. then what should I do? May 28 16:30:26 kiran4399: you could always use 4.1 May 28 16:30:48 kiran4399: is it not working? May 28 16:30:49 alexhiam: but i think jkridner told we must use 4.4 May 28 16:31:00 alexhiam: I did not test it yet.. May 28 16:31:50 kiran4399: well, I wouldn't worry about it, a lot of the projects are using the PRU so it's bound to get sorted out, and you don't need it right away May 28 16:32:20 alexhiam: so what do you want me to do RIGHT now?? May 28 16:32:44 alexhiam: sort out the pru issue.. or build kernel modules for beaglebone blue? May 28 16:33:27 kiran4399: so next step I'd say is get set up working with the bb-kernel repo, and once you have a Debian 8.4 image running with a kernel you built you can start working on adapting the Strawson APIs to use the new kernel drivers May 28 16:34:04 kiran4399: you can't move forward until the kernel drivers are there, so that's definitely the first step May 28 16:34:27 alexhiam: you definitely want me working on the 4.4 image right? May 28 16:34:59 alexhiam: or 4.1? May 28 16:35:14 kiran4399: I'd say use 4.4 for now. If you end up running into a problem with it we can fall back to 4.1 May 28 16:36:21 kiran4399: I'll be AFK for a while, but I'll keep my irc client open so feel free to keep me updated and ask questions in here and I'll catch up when I return May 28 16:36:33 alexhiam: one last thing.. once I build the kernel for blue.. May 28 16:37:10 alexhiam: you want me to use the bb-kernel script and load the new kernel on the sd card and boot the beaglebone black from the sd card right? May 28 16:38:05 kiran4399: yeah, that's easiest May 28 16:38:21 so first flash that Debian 8.4 image to the sd card May 28 16:40:03 debian 8.4? May 28 16:40:07 alexhiam: ^^ May 28 17:09:12 test May 28 17:53:40 kiran4399: this one: https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz May 28 17:53:50 that comes with 4.4 iirc May 28 18:04:32 hey alexhiam! I am having some problems with booting up the BBB that the org sent me. I am assuming that it contains Angstron already. May 28 18:05:21 alexhiam, But when I am connecting it via usb to my laptop,it isn't connecting.It doesn't show up when I do lsusb May 28 18:06:24 I installed mkudevrule.sh. Could you help me out? May 28 18:09:23 alexhiam, I think the only possible reason is that it doen't have the linux distribution on it. However, the led corresponding to flash storage does light up sometimes. May 28 18:09:54 mdp ^^ May 28 18:20:31 chanakya_vc: why arent you just installing the latest kernel image onto it ? May 28 18:21:29 I was just testing whether I can access it or not. After all angstron is supposed to work,Zeekhuge May 28 18:22:54 ZeekHuge, And then I don't have a micro SD card slot on my laptop.I will have to wait till Monday to go to my lab and get microsd-usb May 28 18:22:59 that is right, but if its not working and if you dont have a way to hook it up to a display using hdmi screen, you should probably just install new kernel image and then check it. it will just take about 30-40 minutes May 28 18:23:41 ZeekHuge, They have a card reader. I don't know of any other way May 28 18:23:53 ZeekHuge, You are using Jessie right? May 28 18:24:08 yep. iot as i dont need UI May 28 18:24:42 ZeekHuge, I will use the same.Even I don't need UI May 28 18:25:17 ZeekHuge, But what I don't understand is that it should atleast show up as a usb connected device right? May 28 18:25:33 cool ! though that has been removed and now, the 4.4.9 kernel image is being given at http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot_iot May 28 18:26:27 chanakya_vc: it should. May 28 18:26:35 Hi Wormo ! May 28 18:26:45 Hey ZeekHuge how's it going now? May 28 18:26:46 I have got the patches ready, May 28 18:26:53 nice work May 28 18:27:02 for 4.4.8-ti-r22 May 28 18:27:10 and they are working completely fine May 28 18:27:31 I have built the pru_rproc and pruss drivers May 28 18:28:01 you can push the patch + your doc on how to get the source set up to actually use it May 28 18:28:47 I take it the changes were minimal enough that you can still load against the 4.4.8-t-r22 kernel? May 28 18:29:04 or will you need to update the kernel too May 28 18:31:45 chanakya_vc: FYI they ship with Debian these days May 28 18:32:10 either with 3.8 or 4.1 I'd guess May 28 18:32:32 alexhiam, Ohh didn't know that.I think I will install the latest kernel image and then try May 28 18:32:53 chanakya_vc: yeah, that's the way to go May 28 18:33:31 alexhiam, There has no been changes in the mkudevrule file right.The one I have installed right now is about 6-8 months old May 28 18:34:00 I mean does it depend on the kernel you are running on the bbb? May 28 18:34:37 shouldn't be, it's just about the USB VID and PID May 28 18:34:52 did you try browsing to 192.168.7.2? May 28 18:35:03 Yes not connecting May 28 18:35:08 alexhiam, ^^ May 28 18:35:23 do you have a usb to serial converter? May 28 18:35:46 I guess the latest kernel image is the way to go.Any suggestions for a software to burn stuff to sd card? May 28 18:35:53 Not at the moment May 28 18:35:56 chanakya_vc: dd May 28 18:36:47 just "dd if=path/to/kernel/image of=/path/to/sd/card bs=1M" and wait May 28 18:36:47 It's in my lab .I can get it on Monday.Do you want me to serial debug.See if it boots up on the console? May 28 18:36:57 I've always used xzcat + dd, though I just tried out http://www.etcher.io/ and it worked nicely May 28 18:37:21 chanakya_vc: that'll be the next step if the new image doesn't boot May 28 18:37:24 chanakya_vc: NOTE=be careful with the path to sd card thing. May 28 18:37:27 and be *really* careful about getting the right device file May 28 18:37:39 Wormo: ? May 28 18:37:44 yeah what you just said May 28 18:37:56 ZeekHuge, Okay. sudo apt-get dd? :P May 28 18:38:06 chanakya_vc: nope May 28 18:38:11 its already there. May 28 18:38:14 etcher.io is a plus there, it doesn't let you select hard disks May 28 18:38:19 right May 28 18:38:48 Wormo: what about loading against 4.4.8-ti-r22 ? that you were saying ? May 28 18:38:59 What does bs=1M mean in that command? May 28 18:39:04 ZeekHuge, ^^ May 28 18:39:05 block size May 28 18:39:13 how much to copy at a time May 28 18:39:14 the modules you built got loaded on BBB already or are you still testing that May 28 18:39:27 testing it May 28 18:39:40 chanakya_vc: if you have any doubt about dd just use etcher.io ;) May 28 18:39:44 and one question regarding that May 28 18:39:50 it's one of the more dangerous commands May 28 18:39:53 Okay..alexhiam any reason we chose only 1M(== 1Megabyte?) May 28 18:40:08 go ahead ZeekHuge May 28 18:40:24 Wormo: how can i know the right sequence to load the modules ? is it in modules.order ? May 28 18:41:05 chanakya_vc: it's a trade off. The know the optimal block size would involve a lot of math depending on your OS, architecture, buses, etc. May 28 18:41:16 1MB is a nice round number May 28 18:41:25 you don't actually need to look at that order, modprobe should do it right, if it doesn't that's something to fix May 28 18:41:34 I believe etcher.io does some optimizing in that regard May 28 18:42:10 alexhiam, Yes I was just looking at etcher.io .Looks better to me ;) May 28 18:42:21 Wormo: okay, got it. May 28 18:42:42 so just modprobes on the modules you want to use, their dependencies should load in the proper order May 28 18:43:27 chanakya_vc: certainly the safe way. Plus it uses AppImage, which is pretty neato May 28 18:43:48 alexhiam, I am downloading it now.Is it gui? May 28 18:43:54 yeah May 28 18:43:56 Actually, i was using modprobe but it was saying "not found". I then tried loading it using its full path . and that worked. To load it without using full path, i'll have to add it into the alias name file right ? May 28 18:44:15 Wormo: ^ May 28 18:44:21 alexhiam, Okay I will use that.Thanks for your help! May 28 18:44:23 ZeekHuge means you neededt to run 'depmod -a' May 28 18:44:35 ZeekHuge,Wormo Thanks May 28 18:45:00 chanakya_vc: and if you continue to have issues connecting it might be worth asking in #beagle as well May 28 18:45:31 it collects together the info for installed modules in the files modprobe uses May 28 18:45:43 it = depmod May 28 18:47:13 Okay I will do that alexhiam . Let me ask right now.I have never asked on the #beagle. Infact beagle-gsoc is the only channel I have ever talked on :P May 28 18:58:55 Wormo: i tried loading pruss, and it gave Exec error, and the dmesg was like: May 28 18:58:56 pruss: no symbol version for module_layout May 28 18:59:11 then tried modprobe -f pruss May 28 18:59:24 dmesg : May 28 18:59:25 pruss: module_layout: kernel tainted. May 28 18:59:25 [31699.929168] Disabling lock debugging due to kernel taint May 28 18:59:33 rebooting now . May 28 18:59:59 remember those warnings during the build? if you don't get the version info into the modules then that's what happens May 28 19:00:30 so will have to build complete kernel atleast once May 28 19:00:46 well that's the easy way to do it May 28 19:01:08 right ? May 28 19:01:13 I think there's a specific make rule that can be called, but don't remember it May 28 19:01:23 its related to that .symvers warning ? May 28 19:01:30 yess May 28 19:01:37 module prepare ? May 28 19:01:38 that's what the warning is about May 28 19:02:01 modules_prepare might be the one May 28 19:02:19 if the warning goes away after running it, you'll know May 28 19:02:20 what about make module only ? will that work ? May 28 19:03:00 nope "make module", is not working either . May 28 19:03:34 I normally run the full kernel then modules, and this is why May 28 19:03:51 here I found the discussion in kernel docs May 28 19:03:55 https://www.kernel.org/doc/Documentation/kbuild/modules.txt May 28 19:04:00 " May 28 19:04:00 NOTE: "modules_prepare" will not build Module.symvers even if May 28 19:04:00 CONFIG_MODVERSIONS is set; therefore, a full kernel build needs to be May 28 19:04:02 " May 28 19:04:24 oops cut off "executed to make module versioning work." May 28 19:08:00 this is a good detail to put in your notes about building, yes? May 28 19:10:03 yes sure :) May 28 19:13:34 chanakya_vc: that probably failed because of the old key May 28 19:16:05 try ssh-keygen -R 192.168.7.2 -f /home/username/.ssh/known_hosts May 28 19:16:07 chanakya_vc: ^^ May 28 19:32:52 ZeekHuge,alexhiam, You know I was wondering in the command ssh 192.168.7.2 -1 root, what does the -1 stand for? May 28 19:33:14 I saw it on the adafruit website May 28 19:33:27 it to force the protocol May 28 19:33:36 ssh protocol 1, not a good thing normally May 28 19:33:51 shows an obsolete server May 28 19:33:52 I just use it without that "ssh root@192.168.7.2" May 28 19:51:48 Wormo, alexhiam ZeekHuge Got disconnected.Logs are not showing the conversation.Anything I missed about ssh protocol 1 May 28 19:52:07 ? May 28 19:52:29 * chanakya_vc needs to get his net plan changed May 28 19:52:58 just that -1 should not be needed, sign of an obsolete server if it won't take protocol 2 May 28 19:52:59 logs are showing everything that was said here : http://logs.nslu2-linux.org/livelogs/beagle-gsoc.txt May 28 19:53:59 yes you probably didn't miss anythingn May 28 19:54:56 ZeekHuge, I was accessing this:http://logs.nslu2-linux.org/livelogs/beagle-gsoc/ and wondering where the log for today had gone :P May 28 19:55:11 My mistake May 28 19:57:15 the channel topic is pointing to the archives rather than current log, so it's no wonder that's were you looked May 28 19:57:21 where May 28 19:59:54 Wormo, Yes that's what I did. Only jkridner can change that right? May 28 20:00:14 I ought to be more careful before raising false alarms :P May 28 20:03:46 https://en.wikipedia.org/wiki/Secure_Shell#SSH-1 May 28 20:03:47 [WIKIPEDIA] Secure Shell#SSH-1 | "Secure Shell, or SSH, is a cryptographic (encrypted) network protocol operating at layer 7 of the OSI Model to allow remote login and other network services to operate securely over an unsecured network.SSH provides a secure channel over an unsecured network in a client-server architecture, connecting..." May 28 20:04:03 Since SSH-1 has inherent design flaws which make it vulnerable, it is now generally considered obsolete and should be avoided by explicitly disabling fallback to SSH-1 May 28 20:04:52 apparently gcl-bot doesn't follow to the right anchor in a page May 28 20:07:26 gcl-bot has some problems... May 28 20:07:36 gcl-bot: .weather May 28 20:07:36 AttributeError: 'NoneType' object has no attribute 'get' (file "/usr/local/lib/python2.7/dist-packages/sopel/modules/weather.py", line 144, in weather) May 28 20:07:39 :| May 28 20:07:59 perhaps I'll fix it some day... May 28 20:08:06 Wormo,alexhiam Back to same problem.It won't let me change the keygen May 28 20:08:24 run it 10 times :) May 28 20:08:28 change the keygen? May 28 20:08:29 # Host 192.168.7.2 found: line 28 type ECDSA May 28 20:08:30 /home/vc/.ssh/known_hosts is not a valid known_hosts file. May 28 20:08:31 Not replacing existing known_hosts file because of errors May 28 20:09:07 `mv ~/.ssh/known_hosts ~/.ssh/known_hosts.bak` and start over? May 28 20:09:09 just move aside your known hosts May 28 20:10:49 yes success! Thanks alexhiam Wormo May 28 20:11:53 Got to brush up my skills on ssh.So what you did was just rename the file ? May 28 20:11:59 yes May 28 20:12:09 mv = move May 28 20:12:33 Yes Wormo but w/o dest folder it is just renaming it May 28 20:12:35 ? May 28 20:12:46 yes May 28 20:13:03 So .bak was the only problem? May 28 20:13:14 Like my previous one was not .bak May 28 20:13:20 Wormo, ^^ May 28 20:13:25 .bak is just getting the existing file out of the way May 28 20:13:48 known_hosts is a generated file, will get regenerated by ssh over time May 28 20:14:22 The authenticity of host 'whatever' can't be established May 28 20:14:35 ECDSA key fingerprint is $something. May 28 20:14:40 Are you sure you want to continue connecting (yes/no)? May 28 20:14:47 ... May 28 20:15:04 each time you say 'yes' it adds an entry to known_hosts May 28 20:15:06 Ohh so Wormo this file was present in my system from previous ssh attempts and so the new ssh attempts could not write over it or what? May 28 20:15:49 new ssh attempts expect the previously seen host keys to stay the same May 28 20:16:12 it's a security measure for when you're connecting to internet May 28 20:16:55 Ohh wormo.ssh seems fascianting.Got to read up on it! May 28 20:17:00 you run ssh to your server in the cloud, how do you know you're not being redirected by bad guys to a different server inbetween? May 28 20:17:10 look up "man in the middle" May 28 20:17:34 yes I was reading an article about it on coding security.com May 28 20:18:21 if you keep reinstalling a target, then its key will keep getting clobbered, so ssh won't know it's really the same bbb May 28 20:19:00 Wormo, So each time I connnect a new BBB to my comp,this problem will occur right? May 28 20:19:03 it does the right thing by warning you, but you can set up .ssh/config file to tell it not to worry about changing keys on a particular ssh server May 28 20:19:51 Because the keys will change for the same ssh server right? May 28 20:20:15 if you don't reinstall the rootfs, it shouldn't keep changing keys May 28 20:20:35 it really should just be first attempt after a reinstall May 28 20:21:12 however some of us do lots of reinstalls on a target, in which case we can disable that check for certain ip May 28 20:21:20 pruss: disagrees about version of symbol rproc_put May 28 20:21:21 [ 213.202492] pruss: Unknown symbol rproc_put (err -22) May 28 20:21:21 [ 444.814782] pruss: disagrees about version of symbol rproc_put May 28 20:21:21 [ 444.814843] pruss: Unknown symbol rproc_put (err -22) May 28 20:21:30 i am still getting this :( May 28 20:21:52 ZeekHuge: that's module versioning doing its job May 28 20:22:12 yes, but this time I built the complete kernel. May 28 20:22:34 it tells me that there were enough changes to add the pruss driver that it will not work with the exact prebuilt kernel May 28 20:22:44 should i copy the kernel onto bb and build the remoteproc module on it ? May 28 20:22:45 that was a different warning see? May 28 20:22:54 Okay Wormo! Got it.When I will install the new kernel,rootfs will change right? May 28 20:23:24 alexhiam, I would love to work on the bot. Any chance I could help you out? May 28 20:23:27 chanakya_vc: you don't have to change the whole rootfs for that May 28 20:23:54 ZeekHuge: do you see the difference in complaint, though the end result is still that it won't load? May 28 20:24:24 Okay got to read up a bit on rootfs Wormo .All I know as of know is that it is the filesystem that is loaded before all others get loaded May 28 20:25:20 alexhiam, Perhaps after GSOC.Do tell me please : ) May 28 20:25:46 chanakya_vc: I think he has it on github, so you'll be welcome to take a look May 28 20:27:00 also when I said changing the rootfs, I meant doing the dd / etcher.io thing to blow away the whole rootfs by writing the new one May 28 20:28:02 I don't mean just writing files unrelated to /etc/ssh/ area, that won't kill your ssh host keys (they are stored under /etc/ssh) May 28 20:28:32 Wormo, Yes I was wondering about that only,when I am upgrading using the sd card,the entire kernel gets written over again or only certain parts are upgraded? May 28 20:28:58 if you do the dd/etcher thing everything gets overwritten May 28 20:30:18 you can also just write a new kernel file while the filesystem is mounted May 28 20:30:35 Wormo, Okay got you.So if I don't write over ssh area,host keys won't go. But if upgrade using sd card,all is going to be overwritten. May 28 20:30:45 yes May 28 20:30:56 using those methods I mean May 28 20:31:17 you could also take that sd card and mount the filesystem, to write specific files May 28 20:31:45 Wormo, Okay so only upgrade certain parts of the kernel right? May 28 20:31:52 When you do that? May 28 20:32:33 um you replace the whole kernel if you're building new kernels to test May 28 20:33:02 maybe I misunderstood the question May 28 20:34:12 full-image upgrades replace absolutely all software on the SD, and that's what you do with dd May 28 20:34:28 Wormo, What I meant was that when you are said that you could mount the filesystem to an sd card to only write certain files to a host having a kernel,you would only change certain files right? May 28 20:34:39 in the host kernel? May 28 20:34:55 In that case I am assuming the rootfs won't go? May 28 20:35:20 the normal terminology is there is one kernel file, which you can replace as a single file May 28 20:35:40 Okay got that! May 28 20:36:12 in a sense modules are additional "kernel pieces" but that's not how it is said May 28 20:36:31 "I'm replacing my kernel" = single file that boots May 28 20:36:43 "I'm replacing my modules" = directory of module files May 28 20:37:34 Wormo, alexhiam Would love to work on the bot(anything related to ML,NN,NLP).I have been working a bit on python and hopefully I will reach a stage by the end of summers where I can help : ) May 28 20:37:45 Wormo, So that's what insmod does right? May 28 20:38:06 Load new module May 28 20:38:29 yes it merges a new module into the running kernel code May 28 20:38:33 Okay you mean replace the code of the module itself with a new piece of code May 28 20:38:51 And then maybe insmod it May 28 20:38:59 yes, after removing the old May 28 20:39:01 rmmod May 28 20:39:07 Okay May 28 20:40:02 Thanks Wormo for giving so much time.I know it is holiday weekend in US. May 28 20:40:16 yw May 28 20:40:26 And yet all mentors are here clearing our doubts May 28 20:40:27 :P May 28 20:41:55 I wouldn't touch the computer if I had such a long weekend during college time :P May 28 20:42:08 Wormo, ^6 May 28 20:42:11 *^ May 28 20:58:32 Wormo, http://kernelnewbies.org/RootFileSystem May 28 20:59:07 Wormo, Here what little I could understand that at the end everything is called by the init system. May 28 21:00:15 So if I was moving from ubuntu 14.04 to 16,i'd be shifting from upstart to systemd. So in this case I guess I would have to a fresh install May 28 21:00:28 yes kernel brings up the hardware, then looks for an init executable inside root filesystem, and init is responsible for running everything else May 28 21:00:38 no you don't need fresh install in that case May 28 21:01:33 because, there is a difference between messing with the 'init' process already loaded into memory, and changing init files that will be loaded on next boot May 28 21:02:02 and ubuntu in fact made it possible to upgrade from 14.04 to 16.04 without too much trouble normally May 28 21:02:31 though I wish I had not upgraded mine, for a very specific regression May 28 21:03:26 it has to do with the brand of video card I use, and the fact that I normally use my ubuntu partition for running games... May 28 21:04:09 You run games on Ubuntu? :P May 28 21:04:15 Wormo, ^^ May 28 21:04:16 if you're not running Steam with AMD cards, then 16.04 upgrade should be just fine May 28 21:04:29 I have gentoo hardened on the other partition May 28 21:05:23 Wormo, I thought no games existed for Ubuntu(except cs).That's why I still keep windows May 28 21:05:24 'hardened' means high security and is probably not going to mix well with running games May 28 21:05:35 oh no Way May 28 21:05:59 there are a ton of games for linux on Steam May 28 21:06:21 just not 100% so people who want to play one specific set of games can be out of luck May 28 21:06:50 Wormo, I have also wanting to upgrade it .But I become very lazy when I think of all the s/w I would have to install again. May 28 21:07:00 I do not have a copy of windows in my house, that includes a steam box instead of an xbox May 28 21:07:30 chanakya_vc: gcl-bot? it's just an instance of sopel https://github.com/sopel-irc/sopel May 28 21:07:45 And I am not even sure whether all of them would be compatible with 16. May 28 21:07:53 alexhiam, I will check it out May 28 21:08:35 chanakya_vc: maybe upgrade after your project is complete, 14.04 will still be supported a while May 28 21:08:36 chanakya_vc: plus a bridge to the gitter API that I threw together quickly May 28 21:10:26 alexhiam, So in layman's language it just gives you functions that you can use to code up a bot in python? May 28 21:11:42 chanakya_vc: well, it is a bot, and it gives you an API to add modules to it May 28 21:11:58 alexhiam, I thought it simply used the HTML parser to get info from the net May 28 21:12:21 Like the library that exists in python(just started with it) May 28 21:12:39 it's an irc client and bot engine May 28 21:12:46 type 'gcl-bot: .commands' May 28 21:13:14 gcl-bot: Rootfilesysytem May 28 21:13:22 wait i got the syntax wrong May 28 21:13:42 lol May 28 21:14:10 gcl-bot: .Rootfilesystem May 28 21:14:25 Okay now what I do wrong alexhiam? May 28 21:14:26 gcl-bot: .commands May 28 21:14:27 Wormo: I'm sending you a list of my commands in a private message! May 28 21:14:33 it was literal :) May 28 21:14:40 ohh May 28 21:14:43 :P May 28 21:15:03