[00:38] <infinity> houkouonchi-work: It's the linux-image postinst that's meant to twiddle them.
[00:38] <houkouonchi-work> infinity: well if you check my pastebin it doesn't appear to be doing it or do you have to do something special when making the linux-image .deb to get it to do that?
[00:38] <infinity> houkouonchi-work: Well, the distro packages are clearly working, since your links point to -31- and -30- for current and old.
[00:39] <infinity> houkouonchi-work: So, I'd assume your postinst is different from ours.
[00:39] <infinity> houkouonchi-work: At which point, I can't say how yours is different, cause I haven't seen it.
[00:40] <infinity> diff -u /var/lib/dpkg/info/linux-image-{3.5.0-31-highbank.postinst,3.9.0-ceph-b5b09be3-highbank} should be enlightening.
[00:40] <infinity> houkouonchi-work: If you're producing yours with make-kpkg, rather than using our kernel packaging, it will probably be quite different.
[00:41] <houkouonchi-work> well when you build a debian with make 'deb-pkg' do you need to specify something special to get it to do the the symlinks?
[00:41] <infinity> See above, we don't use make-kpkg, we build our kernels as proper Debian source packages (from the 'linux' source package), so the method is quite different.
[00:43] <houkouonchi-work> big differences ok so its part of the postinstall script of the .deb hmm
[00:43] <houkouonchi-work> http://pastebin.com/raw.php?i=HwMs9Qr1
[00:43] <infinity> You want a unified diff (-u), if you want that to be readable...
[00:43] <houkouonchi-work> really the post install of the one i built is pretty much nothing
[00:44] <infinity> Oh, but true, the make-kpkg one is mostly empty these days, it would seem.
[00:44] <houkouonchi-work> yeah its pretty much non-existent
[00:44] <infinity> So, it would seem there might need to be a hook script to do the symlink twiddling in the new world order.
[00:45] <houkouonchi-work> http://pastebin.com/raw.php?i=HVBtbRWg <-- inline one not that its saying much
[00:45] <infinity> (Or, use the Ubuntu packaging for your kernels instead, if your goal is just to add some patches to the highbank kernel...)
[00:45] <houkouonchi-work> well its more like build kernels using newer ceph-client stuff
[00:45] <houkouonchi-work> not really just a matter of patches
[00:48] <houkouonchi-work> Do you think stealing the post install script off the ubuntu one is likely to work with a different one. It looks pretty generic so a quick look over it by me looks like it would probably work?
[00:49] <infinity> Possibly.
[00:49] <infinity> Though seems like overkill if all you want is the symlink twiddling.
[00:49] <houkouonchi-work> i guess my $version is being specified in the file though... Yeah I guess I am just trying to figure out the best way to automate this
[00:50] <houkouonchi-work> these kernel packages are all automated and the installation/testing is automated too the problem is if that symlink isnt correct when the machine is rebooted u-boot isnt loading the kernel
[00:50] <houkouonchi-work> even though it says its flashing with it during the installation of the package...
[00:51] <houkouonchi-work> might be easier if we just create the symlink in our code-base that does the testing after it does the install rather than doing it with the post install of the .deb I just wasnt sure what handled that stuff. Not super familiar with the .deb packaging system
[00:51] <infinity> Well, there is no "flashing" to do with flash-kernel on highbank, that's a bit of a lie.
[00:51] <houkouonchi-work> Thanks for the help
[00:51] <houkouonchi-work> infinity: then it makes sense why it didnt boot the kernel =)
[00:53] <houkouonchi-work> cant wait for these newer arm hardware. Even with like 10+ nodes and distcc it takes a long time to build stuff on them heh
[00:53] <infinity> So, Debian's kernel postinsts are also still the massive long Perl postinst.
[00:53] <infinity> I wonder why make-kpkg's is so anaemic.
[00:54] <infinity> Waaait, so is the one in make-kpkg.
[00:55] <infinity> houkouonchi-work: How are you building these kernel packages?
[00:55] <infinity> houkouonchi-work: Are you using "make-kpkg" from the "kernel-package" package?
[00:55] <infinity> houkouonchi-work: Cause that should provide you with something with the complex/useful postinst.
[01:27] <houkouonchi-work> infinity: its kernels from git doing make debb-pkg
[07:22] <tharvey_home> where did ubuntu core for 11.10 go?  I see lots of references to http://cdimage.ubuntu.com/ubuntu-core/releases/11.10 yet it doesn't exist (removed as 11.10 is no longer supported?)
[07:23] <infinity> tharvey_home: 11.10 is EOL and gone, yeah.  Use 12.04.
[07:24] <tharvey_home> so is core just another rootfs like server, desktop, cloud are?  is core the only one that supports arm?
[07:25] <infinity> core is just a minimal rootfs with pretty much nothing installed but essential packages and apt.
[07:25] <infinity> We also have full installer images for some platforms (like omap4/Panda), but not many.
[07:25] <tharvey_home> would you call 'server' and 'desktop' a rootfs too then?
[07:25] <infinity> And netboot installer images for things like highbank and armadaxp.
[07:25] <infinity> server and desktop are installers, not rootfses.
[07:27] <tharvey_home> where are the installer images and how would I go about creating one for a different board?
[07:28] <infinity> http://cdimage.ubuntu.com/netboot/ for netboot images, http://cdimage.ubuntu.com/releases/12.04/release/ for some installer images.  Creating one for a specific board isn't trivial, and not something I'd try to explain at 1:30am.
[07:29] <infinity> This is all very much a hacker's game right now, still.  It's not easy to give simple "this is how you do it" instructions for booting a board we don't support.
[07:30] <infinity> But that's slowly changing with generic multiplatform kernels.
[07:30] <infinity> Slowly.
[07:31] <tharvey_home> well, I know how to 'boot' my board with say the core rootfs, I'm just not clear what the 'installer image' does for me - perhaps make it easier for someone to repeat my process less manually?
[07:32] <infinity> tharvey_home: Possibly that, yeah.  But it's certainly not a necessity for people to have shiny installers, if you can give people simple instructions on booting and jamming a kernel/config into ubuntu-core.
[07:34] <tharvey_home> looking at some of the installer images - I see they are just the bins needed like the bootloader, and kernel, boot scripts and then the .img* files are ie usd images you would dd to the usd?
[07:35] <infinity> tharvey_home: The .img files are DDable to SD, yeah.
[07:36] <infinity> tharvey_home: And for some platforms (androidish platforms, like ac100 or nexus devices), we provide a bootimg to stuff in the boot partition.
[07:36] <tharvey_home> so the images presume a specific sized uSD for example?
[07:36] <infinity> tharvey_home: The old preinstalled images we used in 12.04 actually just auto-resize to fill the card on first boot.
[07:37] <infinity> tharvey_home: The images we did for 12.10 and later use the same installer as x86 desktop images and expect to install FROM the card to an external storage device (like a USB hard drive).
[07:39] <tharvey_home> ah... neat.  Is there someplace I can see the installer script that does the auto-resize for the 12-04 images and the script that does the installing for 12.10?
[07:40] <infinity> The "script" that does the installing for 12.10 is ubiquity.  It's the full desktop installer.
[07:40] <infinity> The auto-resizing magic in 12.04 is in the jasper-initramfs package.
[07:42] <tharvey_home> and what is used to 'build' the img file (what dictates the packages and actually installed them to a rootfs)?
[07:43] <infinity> tharvey_home: That's a combination of live-build/livecd-rootfs, and the finishing touches are cdimage.  That's the part(s) of the process that I hinted at being pretty complex and not something for a 1:30am conversation. :)
[07:44] <tharvey_home> infinity, no worries - thanks for the explanation
[09:04] <LetoThe2nd> for the record_ he/she is banned in #pandaboard now
[09:45] <hrw> who?
[09:45] <hrw> morphis?
[09:48] <LetoThe2nd> yes.
[14:42] <brykt> Hi.
[14:43] <brykt> I have installed ubuntu for ARM on a beaglebone black. Should it be possible to login to the BBB via ssh  when it has booted. I am able to ping the BBB, but when I try the ssh into it i get: ssh: connect to host 192.168.1.70 port 22: No route to host
[14:43] <maxinux> yes you should be able to
[14:44] <maxinux> can the bbb ssh into itself?
[14:45] <brykt> I tried using "ubuntu" and "root" as users but still no luck.
[14:45] <brykt> How do you mean ssh into itself?
[14:45] <maxinux> ssh from it to it :)
[14:46] <brykt> I dont have any acces to temrinal. My mointor does not work with the mini-HDMI output.
[14:47] <ogra_> well, did you set up the network and did you install ssh ?
[14:47] <hrw> ogra_: I just had to ask the same ;D
[14:47] <ogra_> we dont offer any official images for the beagles anymore, best is to talk to the person who created that image
[14:48] <maxinux> are you using the armhf image brykt?
[14:48] <brykt> I flashed the eMMC by booting up from the mini SD-card....
[14:48] <brykt> I dont know how to set it up.
[14:48] <maxinux> so you got the image from armhf.com?
[14:48] <brykt> I used the image from this page:
[14:48] <brykt> http://elinux.org/BeagleBoardUbuntu#eMMC:_BeagleBone_Black
[14:48] <ogra_> well, find the person who created it
[14:49] <maxinux> ive not used that image
[14:49] <maxinux> i use www.armhf.com/index.php/boards/beaglebone-black/ loaded on an SD card
[14:50] <maxinux> though it can be loaded onto the mmc if you want
[14:50] <brykt> ok, great. I will try that one...
[14:51] <maxinux> note that it does not support fbdev out of th ebox
[14:51] <maxinux> oh no screen
[14:51] <maxinux> you dont care
[14:52] <maxinux> that image will bring up eth0 automatically via dhcp on first boot  and has ssh going .. and supports all the wifi cards ive thrown at it... but i also reloaded a new kernel on it shortly thereafter... 3.8 > 3.2
[14:52] <maxinux> though i suppose i could give you my  kernel and modules if you need it
[14:53] <brykt> ah, ok. Will keep that in mind if I ever want to connect a screen.
[14:53] <hrw> maxinux: iirc beaglebone black had 3.8 kernel out of the box
[14:53] <maxinux> hrw:  angstrom comes with, but ubuntu does not
[14:54] <hrw> maxinux: person which created image to blame then
[14:54] <maxinux> im not complaining
[14:54] <maxinux> i simply cross recompiled my kernel
[14:54] <hrw> ;)
[14:54] <maxinux> i jokingly recompiled on the bbb also
[14:54] <maxinux> a few -6 hours later it was starting on modules
[14:56] <brykt> You loaded Angstrom  3.2 from 3.8?
[14:56] <maxinux> ? no
[14:56] <maxinux> ubuntu arm image from armhf.com ships with kernel 3.2
[14:56] <maxinux> i compiled 3.8.13 and loaded it on my bbb
[14:58] <brykt> ah. ok... I'll get back to you if I cannot get the stuff I need the BBB for to work. Maybe 3.8.13 will solve it...
[22:46] <T3CHKOMMIE> hello everyone.
[22:46] <T3CHKOMMIE> I was wondering if I could get some pointers on imaging an SDcard with Ubuntu Server Arm...
[22:47] <T3CHKOMMIE> I have a BeagleBone Black, and I have tried the documentation several times, but still cant get it to post.
[22:47] <T3CHKOMMIE> does anyone know of a good method to getting the image on an SD card?
[23:52] <mijk> hi
[23:53] <maxinux> hi.