[00:24] <drab> I get the million <3
[00:24] <drab> it seems like if I disable predictable then the matching in udev is screwed up, don't have the time to debug why, but I can'tg et eth0 to become "lan"
[00:25] <drab> so if I make the names "predictable" again, and I will quote "predictable" to my death bed because it's the last thing those names are, the you can match with KERNEL="enp*"
[00:25] <drab> that seems to avoid the bridge device which wuoldn't match and therefore it all works in the end
[00:26] <drab> mega workaround but worth a million. at some point that systemd bug will make it through and it'll "just work" [tm]
[00:30] <OerHeks> drab, maybe this works, mask udev's rule file for the default policy: ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules >> https://www.shysecurity.com/post/20160510-Ubuntu%20Network%20Interfaces
[00:39] <drab> OerHeks: that post itself says that method doesn't :)
[00:39] <drab> anyway it's fixed per above
[00:39] <drab> I'm gonna go enjoy the million dollar :P
[00:40] <drab> certainly hard earned
[00:42] <OerHeks> oh
[02:07] <DirtyCajun> Do we have a stable kernel release that works with AM4 ?
[02:07] <DirtyCajun> Reading the release notes it looked like 4.10 was promising but i wanted some opinions
[02:08] <sarnold> DirtyCajun: I suspect most folks just use xeons. You may have better luck in #ubuntu
[02:10] <DirtyCajun> That is the pleb channel. i stay far away
[02:11] <sarnold> hehe
[02:11] <DirtyCajun> Xd
[02:11] <patdk-lap> I dunno why you don't ask in the kernel channel
[02:11] <sarnold> I just figured it'd be more likely a gamer would know..
[02:11] <DirtyCajun> Wat. its not for gaming
[02:11] <DirtyCajun> its a 16 thread proc. its for my plex 2u
[02:11] <patdk-lap> heh? not for gaming?
[02:11] <sarnold> oh? I thought this was the new amd cpu; the only other person who's mentioned it on irc is a gamer..
[02:11] <patdk-lap> dunno what an AM4 even is
[02:12] <patdk-lap> people use amd in servers?
[02:12] <DirtyCajun> absolutely
[02:12] <patdk-lap> never seen one, ever
[02:12] <DirtyCajun> wel.... i work at a datacenter
[02:12] <DirtyCajun> and it is in about 40% of our blades
[02:13] <patdk-lap> I have racks of servers, not a single amd
[02:13] <sarnold> well what do you know, an amd chip in a server ;) http://www.thinkmate.com/system/stx-nl-qe12-2210
[02:13] <patdk-lap> :)
[02:13] <patdk-lap> they are always horrible for my performance workload, due to the lack of ondie l2 cache that intel has
[02:13] <DirtyCajun> patdk-lap, check out the specs of the Ryzen
[02:13] <DirtyCajun> and the upcoming server grade chips
[02:14] <patdk-lap> ya, I'll wait for real benchmarks
[02:14] <drab> why is mdadm and preseeding such a pain to work with :(
[02:14] <patdk-lap> as the benchmarks so far, are not accurate
[02:14] <DirtyCajun> passmark has 50+
[02:14] <sarnold> in fairness it's insanely hard to do benchmarking well
[02:15] <patdk-lap> the last benchmk I saw of amd new cpu line was, in this specific memory workload test, we beat the crap out of intel
[02:15] <patdk-lap> due to having double the amount of memory channels
[02:15] <patdk-lap> ya, anyone can make something beat the crap out of something else in one area, I want to know about normal workloads :)
[02:17] <sarnold> gah
[02:17] <sarnold> so, cpubenchmark.net numbers on it look pretty good but I was curious about other specs.. and was looking for an ARK link. sigh. :)
[02:17] <patdk-lap> I guess for a in memory database, that might be ok, if the ondie cache is acceptable to actually run the sql server
[02:18] <patdk-lap> hehe
[02:18] <patdk-lap> I'll wait a year or two atleast
[02:19] <drab> how si there not an option to nuke everything with preseed? just nuke, *everything*, don't try to mount raids and be smart
[02:19] <patdk-lap> intel has pretty much deadended their cpu lines though
[02:19] <drab> have I missed it?
[02:19] <drab> I keep getting crap because some of the disks had raid stuff on it that apparently mdadm --zero-superblock hadn't cleaned and install fails
[02:19] <drab> and it seems non-sense since I don't care what's on the disks, I just want the whole thing to be wiped and reinstalled
[02:26] <sarnold> patdk-lap: what I could find on the amd website is sorely thin on specs, but it does say for the eight core model, 2 channels of ddr4, 768kb of l1, 4mb l2, 16mb l3; 95W
[02:26] <patdk-lap> seems light
[02:28] <patdk-lap> man, have to go all the way down to a e5-2620v4 to find an 8core intel
[02:28] <patdk-lap> 20mb cache
[02:29] <patdk-lap> not as bad as it used to be
[02:29] <sarnold> I've got a e5-2630v3, very similar specs; but four memory channels, 40 PCIe lanes (instead ofthe 24 that other news sites were reporting for the ryzen)
[02:29] <patdk-lap> 4 memory channels
[02:30] <sarnold> so says ark, hehe :)
[02:30] <patdk-lap> so says my m otherboard :)
[02:30] <patdk-lap> so it *might* be comparable
[02:31] <patdk-lap> have to see what pricing turns out to be
[02:31] <sarnold> cpubenchmark said it'd be a bit cheaper than my cpu
[02:31] <sarnold> if you had compute-bound tasks rather than memory bound tasks, the ryzen might be a good fit
[02:32] <patdk-lap> ya, most workloads are memory issues
[02:32] <patdk-lap> except stuff like encoding video
[02:32] <patdk-lap> I don't know why that isn't memory bound, as I would think it should be :)
[02:33] <sarnold> it's nice to know amd's in the game again
[02:33] <patdk-lap> intel did take themselves out of it
[02:33] <patdk-lap> been years since they made progress
[02:33] <patdk-lap> and now they basically admitted to giving up
[02:33] <sarnold> they haven't had any real need
[02:33] <patdk-lap> sure they have
[02:34] <patdk-lap> they have almost let arm overrun them
[02:34] <sarnold> back in early opteron days
[02:34] <sarnold> but it's been a decade
[02:34] <patdk-lap> intel is getting backed into a server cpu corner
[02:34] <patdk-lap> with this, more and more amd systems for desktops, maybe laptops
[02:35] <patdk-lap> but more and more laptops are going arm by being replaced with tablets and phones and stuff
[03:41] <fishcooker> how to duplicate a server using the same configuration ?
[07:55] <ybaumy> hi. what can cause something like the following. on vlan 1 iscsi connections work like a charm. on vlan 500 iscsi connections work like a charm. but on vlan 501 iscsi connection are really slow and its a lottery if they work at all
[07:56] <ybaumy> there are no dropped packets. no denies on the firewall
[07:56] <ybaumy> i dont find anything at all
[07:56] <ybaumy> just that its incredible slow
[07:57] <ybaumy> all 3 vlans are using the same physical connection
[07:58] <ybaumy> the VM that runs vlan 501 has no memory or cpu problems
[07:59] <ybaumy> they all run 16.04 latest patches
[08:42] <ybaumy> i found the problem
[08:43] <ybaumy> fyi there was proxy arp enabled on the firewall for vlan 501
[08:44] <ybaumy> i found that in tcpdump there were no arp requests
[11:42] <a8o> Know any tricks for saving shell history as you enter commands?  I keep getting connections lost/dropped and i loose my shell history unless i exit normall.
[11:46] <hateball> a8o: first hit on google is http://askubuntu.com/questions/67283/is-it-possible-to-make-writing-to-bash-history-immediate
[11:47] <hateball> if you keep dropping your connection you may want to consider using mosh
[11:47] <a8o> cool thanks.
[11:47] <a8o> I use mosh on some systems, but not all can have it.
[11:57] <hateball> a8o: true enough
[12:01] <TafThorne> Try using screen or tmux on the remote end.  Then your shell session will persist even if you loose ssh connection to the remote.
[12:01] <a8o> never heard of tmux.
[12:02] <a8o> i do use screen alot, but some terminal apps get all screwy when I use them in screen.  But I do use screen for stuff I need to run and watch now and then.
[12:03] <TafThorne> tmux is very similar to screen.  Their use to be use case differences between then but now days I think both can do pretty much everything the other can do.  screen is often already installed on systems (just because it was around first I think).
[12:04] <TafThorne> As long as you do not resize the terminal I usually find things behave OK inside screen.  I do not use tmux so I cannot vouch for it.
[12:05] <a8o> if anything it's fun to try something new.  Lately I've been using the fish shell.  Love that one
[15:22] <jamespage> coreycb: hello
[15:22] <jamespage> coreycb: https://launchpadlibrarian.net/311293238/buildlog_ubuntu-zesty-amd64.vmware-nsx_10.0.1~git20170317.bfa48c0-0ubuntu1~ubuntu17.04.1~ppa201703171404_BUILDING.txt.gz
[15:22] <jamespage> does that seem familiar to you - I can't get vmware-nsx to build in a PPA
[15:22] <jamespage> coreycb: builds fine locally/on a cloud instance using sbuild
[15:24] <coreycb> jamespage, haven't seen that before.  i wonder if the tests do any db setup that is getting missed for some reason.
[15:30] <coreycb> jamespage, i see run_tests.sh has an option to recreate the database
[15:30] <jamespage> coreycb: yeah not sure about that
[15:31] <jamespage> coreycb: afaict nothing ever gets re-created on disk
[15:31] <jamespage> created rather
[15:31] <jamespage> coreycb: I lied as well - it failed on my laptop
[15:31] <coreycb> jamespage, oh..
[15:37] <drab> anybody here using ansible by any change and has it working with a preseeded install against the in-target chroot?
[15:59] <jamespage> coreycb: hmm
[15:59] <jamespage> coreycb: I might have it identified
[15:59] <jamespage> coreycb: why do we have a patch to make unit tests use an on-disk sqlite db?
[16:00] <coreycb> jamespage, is that in vmware-nsx?
[16:00] <jamespage> coreycb: no in neutron
[16:00] <jamespage> coreycb: disabling it to see if that helps
[16:01] <coreycb> jamespage, ok, not sure i'll take a look at it though
[16:36] <station> can ubuntu core be used on an intel pc with 4 Etherports as an gateway/rooter … firewall
[16:49] <drab> station: I'm doing that
[16:49] <drab> actually just getting through the bonding part on a second machine to get a "4gbit" link
[16:50] <drab> oh nm, you said core, assumed -server since this is -server, nm
[16:53] <station> drab: what did you use to set it up? is it a bad idea to alsow host like security cam directly on the rooter?
[16:54] <station> im new to server ....
[16:55] <drab> station: if by router you mean your internet modem, it's ok ime as long as you don't open it up and set up, say, port forwarding
[16:59] <station> drab: so i could set open sense / pfsense on one "roooter PC" and a separate server
[17:01] <drab> <troll level raised to yellow>
[17:01] <drab> station: what are you trying to achieve? I'm having troubles to understand what you're asking for
[17:02] <drab> are you trying to build a firewall for your home?
[17:05] <station> drab: im still learning about server the 4 port pc will replace a slow rooter and I have to get internet access to nextcloud  rocketchat …
[17:09] <station> was hoping to get them both on one device with ubuntu core but …
[17:20] <drab> nacc: you might know, is there any ML I can post to about say preseed questions? ubuntu-server seems to be development list only and not for support requests
[17:20] <drab> but I don't see any other place/ML where -server ppl are hanging out to ask a question
[17:25] <nacc> drab: you can ask here
[17:26] <nacc> drab: you can ask on -server too, you might just get redirected around a bit; i wonder if ubuntu-users is the right place
[17:30] <drab> nacc: I doubt -users deal a lot with preseed, feels like asking in ubuntu-desktop :P
[17:30] <drab> but maybe I'm wrong, not on -users
[17:30] <nacc> drab: what's your question?
[17:31] <drab> nacc: if you don't think -server ppl are going to hate me for the rest of my life for posting support requests to a -devel list then I'll try that
[17:31] <drab> I have two preseed problems
[17:31] <drab> both on -server and -desktop actually, altho latetr may be a bug in ubiquity installer
[17:31] <drab> so on -server, I can't figure out how to get preseed to ignore everything on the drive
[17:32] <drab> if I try to re-pxe a sytem that had raid on it, initrd I think will autostart the md device
[17:32] <drab> by the time parted kicks in the drives are in use and everything fails because there's no root device
[17:32] <nacc> pxe doesn't depend on a physical device being present for root
[17:33] <drab> I have to manually get a shell, mdmad --zero-superblock, stop the mdadm device, and then dd zeros for good measure
[17:33] <drab> sure, talking about preseed
[17:33] <drab> I can't basically reinstall a system automatically as it stands
[17:33] <drab> if the disks had stuff on it
[17:33] <nacc> while not having done this with raid, i've reinstalled many systems in the past that were already installed
[17:34] <nacc> drab: does it only happen with raid?
[17:34] <drab> even if they had a previous install, parted stops and asks me to confirm which device I wanna use and stuff
[17:34] <drab> nope, with a single disk too, same issue
[17:34] <nacc> drab: then you're not telling preseed enough
[17:34] <nacc> partman-lvm/device_remove_lvm boolean true
[17:34] <drab> I'm sure, I just can't figure out what I'm missing
[17:34] <nacc> partman-lvm/confirm boolean true
[17:34] <drab> lemme dpaste it
[17:35] <drab> http://dpaste.com/30B43FQ
[17:35] <drab> nacc: I have all of those already
[17:35] <drab> that's a grep partman srv1604.seed
[17:37] <nacc> drab: can you pastebin your whoel preseed?
[17:38] <nacc> drab: iirc, what you have is sufficient for everything to get wiped by the installer and if it's still prompting you for a selection, then something else is wrong
[17:40] <nacc> drab: and please be precise as to where it stops, becasuse "asks me to confirm wich device ... and stuff" doesn't help me undersatnd where the preseed is stopping
[17:40] <nacc> drab: ideally screenshots, i think
[17:44] <drab> nacc: ok, I'll get to that, gimme a few, thank you
[17:45] <drab> I should have a windows VM on vbox to repro this so that I can get actual sshots instead of blurry pics with my phone
[17:48] <nacc> drab: in the meawhile, can you pastebin your entire preseed?
[17:49] <drab> nacc: k, that I can certainly do right away, sec
[17:58] <drab> nacc: ok this has everything , line from pxelinux that I start the install with + srv1604.seed + the partman diff with the raid1 version
[17:58] <drab> http://dpaste.com/27KH6SP
[17:59] <drab> thank you for taking the time to look
[18:03] <nacc> drab: do you have multiple physical disks?
[18:07] <drab> nacc: in the server using the raid-1, yes, in the testbox using the simple one, no, just one ssd
[18:07] <nacc> drab: in the latter case, does it help to specify
[18:07] <nacc> d-i partman-auto/disk string /dev/sda
[18:08] <drab> ok, I'll add and try with that and see if it helps
[18:09] <drab> there is the equivalent of that in the raid1 already tho, and I still get errors due to raid being mounted, but that might be a diff issue
[18:09] <nacc> drab: right i think it is
[18:09] <nacc> drab: hence why i want to see where preseed stops :)
[18:09] <drab> ok
[18:10] <drab> I'm still working on getting a VM going, it's a bit of a multitasking morning with a few more interruptions than usual, appreciate your patience
[18:10] <nacc> drab: np, i might need to step away for a bit to run some errands/lunch
[18:11] <drab> no worries at all, thank you for your help
[18:12] <drab> btw I just figured out another neat trick this morning, just in case anybody cares...
[18:12] <drab> to do end-to-end ansible installs
[18:12] <drab> or anything else really, would be the same with chef, if you wanted to trigger a push and need ssh
[18:13] <drab> the late-command can install ssh in /target and then you can just start it and it'll work just fine so than you can ssh in/push stuff to it and make all the changes before rebooting
[18:14] <drab> plus put in the bios boot from hd first, second network, so now I can WOL machines at night, dd a few bits to the disk to remove the mbr, reboot, and it'll go into pxe, install and then ansible it
[18:14] <drab> poor man ipmi :)
[20:05] <rgb-one> Hey
[20:05] <rgb-one> any osTicket users here?
[20:09] <tarpman> oh wow. been years since I heard that name..
[20:09] <tarpman> rgb-one: not any more, and boy am I grateful for that!
[20:10] <rgb-one> tarpman, hehe why do ya say that?
[20:24] <drab> tarpman: is there a better alternative? I've been looking for a simple ticketing system for ppl to report problems, but didn't find much
[20:37] <rgb-one> drab, I found a list on reddit
[20:41] <tarpman> drab: I moved to request tracker
[20:42] <drab> rgb-one: link? I saw a whole bunch, but they are all way too complicated or kinda broken
[20:42] <tarpman> rgb-one: embarrassing... it's long enough ago that I'm actually having trouble remembering specifics
[20:44] <rgb-one> some free ones, Request Tracker and OTRS
[20:44] <rgb-one> https://www.reddit.com/r/sysadmin/comments/na2r0/to_my_fellow_helpdesk_operators_what_trouble/
[20:46] <rgb-one> Free ticketing systems: https://www.reddit.com/r/sysadmin/comments/2pp8op/free_ticketing_systems/
[20:51] <drab> rgb-one: if you go through that list it basically seems to come down to the usual 2 tho, OTRS and RT
[20:51] <drab> everything else isn't free (despite the topic, see Jira) or is the usual hosted web thingie
[20:51] <rgb-one> do you use either of those?
[20:51] <drab> I have in the past
[20:52] <drab> and they are too complicated for where I'm at now
[20:52] <rgb-one> Oh
[20:52] <drab> I almost just need a form with a listing at the back
[20:52] <drab> a mini django site would do I reckon
[20:52] <drab> even just sending me an email would work... I could do that to start actually
[20:53] <drab> I almost implemented it as a google form... I just need a few questions/guided step for ppl to report problem
[20:53] <drab> so that they don't write "my internet is broken"
[20:53] <drab> and it turns out they were at home... not joking
[20:54] <drab> I don't need multi user, report generating ITIL TLA MSG BLAH BLAH super duper flashy mobile first
[20:54] <drab> :P
[20:54] <drab> but it seems I'm a minority so there's no such thing
[21:05] <rgb-one> I see
[21:11] <drab> nacc: this was my other problem btw, a bug still open since 2011... https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/713385
[21:11] <drab> still working on those sshots
[21:12] <drab> I have the same prob as the initial guy, server with a quadport nic
[21:13] <nacc> drab: and they don't report link up even though they have link?
[21:17] <drab> the problem is with the "predictable" names, in some cases the "first" port is not the one I have pxe set up on
[21:18] <drab> I understand the theory about predictable naming, but honestly I never had an issue with eth* stuff coming out of order and I could reliably say to pick, say eth4 for pxe
[21:18] <nacc> drab: and do you pass BOOTIF= down?
[21:19] <drab> so I used ifnames=0 to go back to that, which worked and could reliably pxeboot stuff, but that broke everything when I started working with the new VM server and need to preconfigure bridges
[21:19] <drab> have not used BOOTIF=, but I passed netcfg/choose_interface=eth0 if it means the same thing
[21:20] <nacc> well, if you use BOOTIF= netcfg/choose_interface=auto should work
[21:20] <nacc> fi you don't use BOOTIF=, then yes, you might need to specify the network interface
[22:14] <nacc> drab: if you don't use your recipes (but use 'atomic' or something) does it work?
[22:15] <drab> nacc: I did some more tests... it works with auto, but it doesn't do what I'd like it to do. basically, for whatever reason, what by the rear panel are port 3 and 4 come up "earlier" with systemd and are named enp129XXXX Vs the other two enp4XXX
[22:16] <drab> so I guess they are selected first and stuff gets installed/set up with the wrong interface
[22:16] <nacc> strange
[22:17] <drab> the "funny" thing is, if I disable predict interafces with ifnames=0
[22:17] <drab> then the enp4XXX gets eth0 etc
[22:17] <drab> so eth0-3 match the panel layout
[22:17] <drab> and I get preseeding etc on eth0 which is what I want
[22:18] <drab> but like I said if I do that then I get other problems when I get to setting up the bridge
[22:19] <drab> at this point I'm inclined to give up and work around it with ansible
[22:20] <drab> as long as the install works with predictable names, when the box comes back I can reconfigure it
[22:21] <drab> the thing that makes even less sense is that the dhcp server is set to tftp *only* on that first interface, the others don't
[22:22] <drab> so it pxeboot from iface1, then when installer stuff it loaded order is rearranged by systemd or whatever
[22:22] <drab> it dhcp out on iface3, gets an ip and continues the installation from there
[22:23] <drab> I guess a good fix would be to have the installer to use the same iface it pxebooted on, but it might not know what that is
[22:24] <drab> nacc: I'll test with atomic
[22:29] <drab> nacc: nope, same error, no root file system defined
[22:31] <leetskeet> hello all, recently setup server 16.04 and I have an issue where after a reboot, I have to complete a local login before SSH with key login will work
[22:32] <leetskeet> ran systemctl enable ssh and still same issue
[22:39] <leetskeet> anybody around
[22:58] <drab> ok so I found the error...
[22:59] <drab> nacc: ubiquity: error ddf1 wrong # of devices in RAID set "ddf1_kvm5" on /dev/sda
[22:59] <drab> I've no idea why I get that
[22:59] <drab> there's no raid on that disk, it's an old windows disk, or maybe windows was installed with fakeraid and that did something to it...
[23:08] <JMichaelX> did a release upgrade a few weeks ago on home server, from 14.04 to 16.04, and just noticed that installation is using kernel 3.13.0-110-generic
[23:09] <JMichaelX> desktop on 16.04 is using kernel 4.4.0-66-generic. is there a reason for this difference?
[23:10] <genii> You haven't done a dist-upgrade
[23:10] <drab> JMichaelX: 16.04 server uses 4.4.65 too, prolly just missing a dist-upgrade
[23:13] <sarnold> JMichaelX: how did you do the upgrade?


[04:31] <radix> does SteveA generally disappear for the weekends?
[04:32] <LarstiQ> radix: I haven't really paid attention to that
[04:32] <Burgundavia> radix, likely, as he is paid to work on lp
[04:34] <radix> right :)
[08:20] <LarstiQ> oeh!
[08:20] <LarstiQ> someone implemented subscribed bugs in the web interface!
[09:05] <lifeless> stub: ping
[09:05] <stub> lifeless: pong
[09:05] <lifeless> i just nuked 3 corrupt jobs
[09:06] <lifeless> you have sftp://chinstraphome/warthogs
[09:06] <lifeless> and variations thereupon
[09:06] <stub> 2 corrupt jobs, and I just fixed bzr-submit-merge on the wiki so others don't have the same problem
[09:06] <lifeless> thanks
[09:06] <lifeless> whats your x-push-data file contents ?
[09:07] <stub> chinstrap:/home/warthogs/archives/stub/dists/devel/
[09:07] <stub> There seemed to be a missing '/' in bzr-submit-merge.
[09:07] <lifeless> hmm
[09:07] <lifeless> copied and pasted from my working one
[09:07] <lifeless> ah-oops
[09:41] <sivang> moins all
[01:14] <shawarma> Hi! Is there  any way to view the complete list of specifications?
[01:39] <Hieronymus> hello
[01:40] <Hieronymus> How come the French translation page in Rosetta lists more packages than the Dutch one?
[01:40] <Hieronymus> https://launchpad.net/distros/ubuntu/dapper/+lang/fr and https://launchpad.net/distros/ubuntu/dapper/+lang/nl
[06:21] <LarstiQ> hmm, I don't see a distinction between Serbian in Cyrillic and Latin anywhere
[07:50] <\sh> guys, is it possible to have the support tracker tool on launchpad to work as well for teams, like an "RFP" tracker for MOTU?
[07:51] <\sh> let's say, I select the "MOTU" team, and file a support ticket for having "shiny-software-5.0" packaged for universe?
[07:51] <sivang> \sh: does the moto have something like that currently?
[07:51] <\sh> sivang: well...a wiki page
[07:52] <\sh> UniverseCandidates..which is for this purpose a but degenerated...we thought about using RT but if there is something like a support tracker in LP...why not using this
[07:52] <\sh> s/but/bit/
[07:52] <sivang> \sh: if it supports the notion of group assignments of requests and has sufficient enough emailing interface , ofcourse
[07:53] <\sh> sivang: yes..but https://launchpad.net/people/motu/+tickets doesn't show up anything to create a ticket :)
[07:54] <shawarma> Hi! Is there  any way to view the complete list of specifications?
[07:55] <sivang> \sh: hmm, maybe we need it to be a "motu" product? :)
[07:55] <\sh> shawarma: all approved, or actually all?
[07:55] <shawarma> \sh: either.
[07:55] <sivang> \sh: seems issues are only registered against a product, not a team
[07:55] <\sh> shawarma: https://launchpad.net/distros/ubuntu/+specs
[07:55] <shawarma> \sh: I'd really like to take a look at all the Ubuntu Server specs to see if there's anything I can work on, but I can only view the 10 newest.
[07:55] <\sh> sivang: jepp...product or distro
[07:56] <\sh> shawarma: see the url
[07:56] <sivang> \sh: We need to ask Bjorn about that then
[07:56] <shawarma> \sh: How on earth did you find that?
[07:56] <\sh> shawarma: well..I used it when I was in the reviewing team during UBZ :)
[07:56] <shawarma> \sh:I've been clicking everywhere, but never been able to find anything but the 10 most recently added.
[07:57] <shawarma> \sh: Well, thank you!
[07:57] <\sh> shawarma: to see even the assignees https://launchpad.net/distros/ubuntu/+specstable
[07:58] <\sh> shawarma: you're welcome..even when i'm totally clueless...as I had to read a couple of minutes ago ;)
[08:01] <bercik> hey
[08:01] <bercik> when I get e-mail with activation?:p
[08:01] <BjornT_> \sh: so, basically you'd want it to be possible to open a ticket on a team, that's not necessarily associated with a product or distribution?
[08:02] <sivang> BjornT_: you're here? :-)
[08:02] <\sh> BjornT_: that's what I thought about...well..thinking of MOTU it belongs to distro ubuntu ... but is in need of this feature :)
[08:02] <bercik> when I get e-mail with activation?:p sorry for my englisch ;p
[08:02] <BjornT_> sivang: of course :)
[08:02] <bercik> english ;p
[08:05] <BjornT_> \sh: yeah, although i would guess that if someone request support to MOTU, it's always about ubuntu. the same is probably true for most teams.
[08:06] <\sh> BjornT_: yes, right, but this is special..it's a type of debians "RFP" or "ITP"
[08:06] <\sh> process
[08:06] <sivang> BjornT_: why does it make a difference? I would think that being able to open a ticket against a team would be possible without having to associate it with a distro product
[08:06] <\sh> so to have a package to hit ubuntu, it needs to go to universe first...
[08:09] <LarstiQ> bercik: it was immediate for me
[08:11] <BjornT_> \sh: i'll have to think about it will fit into the changes to the support tracker that will happen. could you file a bug about it (or better, create a spec ;), so i won't forget it?
[08:12] <\sh> BjornT_: sure...but not today..let me do it tomorrow :)
[08:12] <BjornT_> \sh: sure, thanks :)
[08:12] <\sh> BjornT_: spec to launchpad product? or ubuntu?
[08:12] <BjornT_> \sh: launchpad
[08:13] <\sh> BjornT_: k...you'll get your spec :)
[08:18] <sivang> BjornT_: are you also working on the spe tracker?
[08:18] <BjornT_> sivang: well, it does make a difference some difference, as how to implement it. my point was that you probably don't need to have the possibility to associate with both a product/distribution and a team, which makes it somewhat easier.
[08:19] <sivang> BjornT_: I had the same though :) we could be following ticket against ---->team---[assoc. with $DISTRO] .
[08:19] <BjornT_> sivang: i hope not :) actually, i'm probably going to be the one implementing email notifications for it.
[08:20] <sivang> BjornT_: email interface for the spec tracker you mean?
[08:20] <BjornT_> yeah
[08:21] <BjornT_> https://wiki.launchpad.canonical.com/SpecTrackerEmailInterface
[08:21] <BjornT_> (it's only a rough braindump so far, though)
[08:22] <sivang> anyway, re: tickets against team, those tickets could be indirectly assoc. with a distro through the team assoc itself. Does that sound sane?
[08:24] <sivang> BjornT_: hmm, I need to make some time and help you out with that rough braindump. maybe add some ideas etc..
[08:24] <BjornT_> sivang: yeah, that sounds sane.
[08:24] <BjornT_> sivang: that would be really great
[08:28] <sivang> BjornT_: I had some ideas back then, maybe I can refine and use my spare moments tomorrow at work to add them. Also, do you know if you could inherit email interface of support/malone trackers and just change syntax and semantics?
[08:29] <\sh> sivang: why?
[08:29] <sivang> \sh: what why? :)
[08:29] <\sh> Also, do you know if you could inherit email interface of support/malone trackers and just change syntax and semantics?
[08:30] <\sh> the syntax can stay like it is...the status fields has to be changed :)
[08:31] <sivang> \sh: ah, that's actually waht I meant. but to allow greater flexiabilty (ouch, here is that word again) you might want to have better extended semantics for support tickets that a bug tracker might not support or expose
[08:32] <sivang> not support/expose by design, that is
[08:32] <\sh> sivang: well...actually a support ticket is a subview of a bug ticket..everything what a support ticket can have, could be filed even in a bug ticket...
[08:33] <\sh> sivang: IMHO !! :)
[08:34] <sivang> :-)
[08:34] <\sh> .oO(I have no clue!)
[08:34] <\sh> I should trademark this statement
[08:34] <BjornT_> sivang: yeah, the support email interface will probably be similar to malone's.
[08:34] <sivang> \sh: LOLO
[08:35] <\sh> BjornT_: but get rid of the gpg signed email for filing bugs/support tickets...
[08:35] <ajmitch> \sh: you sound like bddebian
[08:36] <sivang> but, thinking in general terms, what about things like price quotes per ticket, departments invovled, status (which is basically different from a bug status) etc..
[08:36] <LarstiQ> ajmitch: what, about trademarking? :)
[08:36] <sivang> as I see it, a support ticket might sometime have more data over a bug -
[08:36] <ajmitch> LarstiQ: no, the 'I have no clue' thing
[08:36] <\sh> BjornT_: or think a bit more complicated: if it's a gpg signed mail, which identifies user X which is in team A and is able to change the status and some other stuff for the bug/support ticket, then allow him to do it...if there is no gpg signed mail, drop all action keywords
[08:36] <LarstiQ> ajmitch: yeah, that is what I mean
[08:37] <BjornT_> \sh: i'll see what i can do. it requires some discussion, but i think it should be possible to file a bug without having a gpg key.
[08:38] <\sh> BjornT_: well..the possibilty must be given, to send always a gpg signed mail to create a special report with action keywords in it, to file it directly to a special assignee or set a status != new
[08:38] <\sh> anyways back to my merges :)
[08:38] <\sh> which i'm doing without a clue ,)
[08:40] <sivang> a bug should ideally be a technical description of a technical system specific problem. While a support ticket need not always result in a bug.
[08:41] <sivang> \sh: why do you keep saying you have no clue? you seem to have more clue then everybody else. The fact I don't say I have no clue doesn't make me less clueless
[08:41] <BjornT_> \sh: yeah, something like that. when i have time i will bring it up with the others for discussion.
[08:41] <\sh> sivang: read ubuntu-devel ml...then u know why :)
[08:42] <sivang> \sh: I wish I could :-( pitti's server has been hacked and we need to wait for monday so the server farm compnay will restore a backup :...-(
[08:43] <\sh> sivang: say this again? hacked? pittis server?
[08:43] <sivang> err ops /me runs
[08:43] <sivang> actually that was a lie
[08:43] <\sh> didn't he install the latest security patches?
[08:43] <sivang> :)
[08:43] <\sh> hehe...I'll tease him with this :)
[08:43] <sivang> well, it was mostly a DoS
[08:43] <sivang> \sh: please don't, I don';t know if I was supposed to tell about it :)
[08:43] <\sh> sivang: I know how it feels to be hacked
[08:43] <\sh> sivang: well..it's logged now :)
[08:44] <\sh> but do not worry
[08:44] <sivang> \sh: I really don't understand what people have to be hacking with piware.de, such a wonderful server with a wonderful name
[08:44] <\sh> sivang: hackers don't do this..these are scriptkiddies
[08:44] <sivang> yes
[08:44] <sivang> that is why I said crackers :-)
[08:44] <ajmitch> sivang: you just announced it on a publically logged channel :P
[08:45] <sivang> erm
[08:45] <\sh> not even crackers...crackers are cracking copy protection
[08:45] <\sh> or phreaking..
[08:47] <sivang> (and logs)


[00:03] <rockstar> mwhudson, just sent mine to you.
[00:26] <rockstar> mwhudson, https://code.edge.launchpad.net/~rockstar/launchpad/assert-needs-upgraded/+merge/14125
[01:17] <mwhudson> review pls: https://code.edge.launchpad.net/~mwhudson/launchpad/dont-oops-sftp-unlink-directory-bug-372506/+merge/14127
[01:34] <rockstar> mwhudson, r=me - I actually wanted to fix that bug.
[02:11] <mwhudson> rockstar: oh!
[02:11] <rockstar> mwhudson, ?
[02:12] <mwhudson> rockstar: sorry for toe-stepping
[02:12] <mwhudson> rockstar: it took me too long to fix it, i kept seeing TransportError and reading TransportNotPossible :/
[02:12] <rockstar> mwhudson, no, it was pie in the sky wanting.  I was thinking "you know, I could fix this rather simple bug, and maybe learn some more about codehosting while I'm at it."
[02:12] <rockstar> mwhudson, one of my big concerns is that I don't know enough about codehosting.
[02:12] <mwhudson> rockstar: oh ok
[02:13] <mwhudson> rockstar: fair enough
[02:13] <rockstar> Although really, the upgrade_branches stuff has started curing that.
[02:13] <rockstar> Now I know I just want you to fix it all.
[02:13] <rockstar> :)
[02:13] <mwhudson> :)
[02:14] <mwhudson> rockstar: i know very little about js in launchpad, so maybe we're even
[02:14] <rockstar> mwhudson, yea, I can take that tradeoff.
[12:26] <noodles775> al-maisan: did you start abentley's branch? if not, I'll start it now.
[12:26] <al-maisan> noodles775: please do.
[12:45] <jtv> noodles775: thanks for the review btw
[12:46] <noodles775> np.
[12:46] <noodles775> jtv: why was it that your original conf for the test_runner didn't work?
[12:46] <noodles775> al-maisan or anyone else, MP here if you have time: https://code.launchpad.net/~michael.nelson/launchpad/copy-binaries-timeout/+merge/14157
[12:46] <jtv> noodles775: it worked, but I'm documenting the procedure for oops-enabling a script, and this turned out to be the "slightly cleaner" way.  I wanted to validate my documentation.
[12:47] <noodles775> jtv: but why is the test_runner using the development conf?
[12:47] <al-maisan> noodles775: please give me a bit of time and I'll get to it.
[12:47] <noodles775> (or is that just the way it is)?
[12:47] <noodles775> al-maisan: no rush... someone else might get to it too :)
[12:48] <jtv> noodles775: it inherits that config as a base, apparently because there's a lot of overlap.
[12:48] <noodles775> jtv: ah - ok, that makes sense then.
[12:49] <jtv> noodles775: btw, excuse me if my advertising is too aggressive, but if you know anything about this, please take a moment to review https://dev.launchpad.net/LoggingOopses
[12:49] <noodles775> :)
[12:50] <noodles775> jtv: thanks for documenting that! It'll make it much easier for the next person... I haven't had to add an oops yet.
[12:51] <jtv> noodles775: I'll bet there's a script running somewhere that you _could_ do it for and that _should_ be logging oopses.  :-)
[12:51] <noodles775> jtv: without a doubt.
[12:59] <abentley> noodles775: You're a star.  I'm around if you have any questions.
[13:00] <noodles775> abentley: Thanks.
[13:03] <BjornT_> jtv: i was looking at your lp:~jtv/launchpad/bug-463097. where are oops recorded when you run the script itself?
[13:06] <jtv> BjornT_: from memory, /var/tmp/poimport.test
[13:06] <jtv> BjornT_: though maybe I didn't fully understand your question... the script itself as opposed to what?
[13:07] <noodles775> jtv: when the real script runs - as opposed to running the tests - you mention in your MP that the configuration for production will be in a separate branch (or something to that effect)?
[13:08] <BjornT_> jtv: as opposed to the test runs. i would have thought that we wanted separate dirs for this, like we usually have
[13:08] <BjornT_> jtv: for example 'make run' produces oopses in /var/tmp/lperr, while 'make check' produces oopses in /var/tmp/lperr.test
[13:08] <jtv> noodles775: the config for production goes into lp-production-configs, not devel/db-devel etc.
[13:09] <BjornT_> jtv: why does poimport need to be different?
[13:09] <jtv> BjornT_: existing practice is mixed, and I haven't found any documentation.
[13:09] <jtv> BjornT_: in fact, you may be just the person to make a ruling on this, right now.  :-)
[13:13] <noodles775> abentley: do you think we'll eventually need an option to modify the prerequisite branch? or just create a new one?
[13:14] <noodles775> abentley: also, I wonder whether the +resubmit page should mention the prerequisite too? What do you think?
[13:14] <abentley> noodles775: I think we won't need to modify the prerequisite branch often.  We don't provide a way to modify the target branch, and I was following that.
[13:14] <noodles775> yep, makes sense.
[13:14] <BjornT_> jtv: i think it makes sense to have separate dirs. the test suite does produce oopses, so it would be nice being able to keep the normal oops dir empty for manual testing.
[13:15] <abentley> noodles775: I think we could mention the prerequisite branch on +resubmit.  I did test that it works.
[13:15] <noodles775> abentley: ok, great. r=me (code/ui*).
[13:16] <abentley> noodles775: So are you asking me to change the resubmit text?
[13:17] <noodles775> abentley: not necessarily, I was just asking you whether you thought it would be worthwhile - up to you.
[13:17] <noodles775> (details in the mp reply coming :) ).
[13:18] <abentley> noodles775: Cool.
[13:20] <jtv> BjornT_: I don't feel particularly strongly about it; I use file timestamps to sort out the "manual" oopses from the "test" ones and I don't like having too many directories in /var/tmp, but I can see your point as well.
[13:34] <abentley> noodles775: We plan to use prerequisite branches for more than just calculating the diff-- we'll also be using it when landing merge proposals.  E.g. if the prerequisite branch hasn't been approved or merged, we might prompt for confirmation before landing the subsequent merge proposal.
[13:35] <noodles775> abentley: nice!
[13:36] <noodles775> abentley: I guess I was just trying to think like someone who's not aware of any of that. I create an MP which has a previous branch included - and all I know is that I'd like the diff to not include those changes. Hmm...
[13:36] <abentley> noodles775: So that's why the text is broader than just being about diffs.
[13:38] <noodles775> abentley: do you think it would be too explicit to say "A branch that should be merged before this one. The changes in this prerequisite branch will not be displayed on the merge proposal."
[13:38] <noodles775> s/explicit/verbose
[13:39] <abentley> noodles775: Wouldn't you want to say "...will not be displayed in the diff"?
[13:40] <noodles775> abentley: yes, that's clearer.
[13:41] <abentley> noodles775: But it still is a bit long.  I wonder if we should provide it as inline help?
[13:41] <noodles775> abentley: one other tiny thing, I don't think that should be a capital 'B' for 'Branch' in that description.
[13:41] <abentley> noodles775: Sure.
[13:41] <noodles775> abentley: yeah, it would be quite long. inline help is a great option.
[13:42] <abentley> noodles775: But is it possible with autogenerated forms?
[13:42] <noodles775> as you could also mention there the other affects later on.
[13:42] <noodles775> hm, not sure, but I'd assume so?
[13:42]  * noodles775 checks out of interest.
[13:43] <abentley> noodles775: Because I think it's normally done with a specially-formatted link...
[13:46] <noodles775> abentley: if that is the case, maybe leave it for the moment.
[13:46] <noodles775> (or use the long description - up to you.)
[13:54] <abentley> noodles775: Here's an incremental diff: http://pastebin.ubuntu.com/304310/
[13:55] <noodles775> abentley: great, thanks.
[13:55] <noodles775> abentley: one small thing: s/and target/target in branchmergeproposal-resubmit.pt?
[13:56] <abentley> noodles775: I actually just did s/and target,/target/
[13:56] <noodles775> yep, I was about to mention the comma :) Excellent, r=me.
[13:57] <abentley> noodles775: Cool.
[14:00] <abentley> noodles775: I plan to add a command to bzr-pipeline to create a branch merge proposal, including the prerequisite branch.
[14:01] <noodles775> abentley: great! I'll be looking forward to that :)
[14:01] <noodles775> abentley: btw, I noticed the other day that I had to keep r130 of pipeline, as otherwise it was requiring a later version of bzrlib?
[14:03] <abentley> noodles775:  lp:bzr-pipeline/stable is compatible with the stable bzr series (2.0.x) and lp:bzr-pipeline is the devel branch.
[14:03] <noodles775> abentley: ah great - I'll switch to that, thanks.
[14:03] <abentley> noodles775: np
[14:08] <leonardr> noodles775, for your queue: https://code.edge.launchpad.net/~leonardr/launchpadlib/trusted-workflow-tests/+merge/14167
[14:09] <noodles775> leonardr: I'll jump on it soon :)
[14:16] <maxb> I would like to append the following one-liner to the queue: https://code.edge.launchpad.net/~maxb/launchpad/remove-stray-ref-to-sourcecode-lazr-js2/+merge/14168
[14:31] <al-maisan> noodles775: I am looking at your branch.
[14:31]  * al-maisan needs a review as well: https://code.edge.launchpad.net/~al-maisan/launchpad/relsets-463195/+merge/14169
[14:37] <noodles775> Thanks al-maisan !
[14:43] <noodles775> al-maisan: i'm going to finish reviewing now, I've pushed leonardrs back into the queue as I didn't get to start it.
[14:43] <al-maisan> noodles775: no problem
[18:07] <abentley> rockstar: Did you get my request to review https://code.edge.launchpad.net/~abentley/launchpad/prerequisite-ui/+merge/14110 ?
[18:20] <rockstar> abentley, I did.  I'm on the phone with jam, but I plan on looking at it right after that.
[18:35] <rockstar> abentley, wasn't this going to land against db-devel?  I'm okay with reviewing against devel, just checking though.
[18:36] <abentley> rockstar: Yes, it is.  That's why I think eventually we'll want to support changing merge proposal target branches.
[18:36] <rockstar> abentley, ack.
[18:37] <rockstar> abentley, ui=me
[18:38] <abentley> rockstar-afk: thanks.


[01:22] <NwS> OMG that bezels on the Ubuntu tablet -.-"
[01:22] <NwS> those*
[01:22] <NwS> or that bezel w.e
[01:23] <NwS> Why can't BQ create something prettier? fml
[08:40] <yellabs-r2> hello and , goodmorming
[08:41] <yellabs-r2> yesterday we talked about the video stutter on Bq E5 ubuntu edition with ubuntu OTA-9
[08:42] <yellabs-r2> i tried some other sites with video , and on some its the same issue ( stutter )
[08:42] <yellabs-r2> now as i was thinking about it, could it be that maybe its stuttering on buffering ?
[08:43] <yellabs-r2> and when it would buffer ( or read ahead ) a bit more , it would be solved ?
[08:43] <yellabs-r2> what do you think ?
[08:58]  * yellabs-r2 background
[10:12] <vs__> hello everybody. i have a question. can connect ubuntu phone to linux mint cinnamon 17.3?
[16:38] <CheeryLee> J
[16:39] <CheeryLee> Is anybody here?
[16:49] <CheeryLee> Can you help me with porting?
[16:57] <peat-psuwit> CheeryLee: What's your problem? Ask your question right away.
[16:59] <CheeryLee>  I built the image for my tablet, but I don't know how to flash it
[17:01] <CheeryLee> Rootstock-ng doesn't work for me.
[17:02] <peat-psuwit> CheeryLee: What's wrong?
[17:04] <CheeryLee> It copies the files of the image in /cache. But after rebooting these files disappear.
[17:06] <CheeryLee> I did everything as written in porting article (besides AppArmor).
[17:21] <peat-psuwit> CheeryLee: What does you mean "disappear"? Did you flash boot and recovery partition?
[17:28] <CheeryLee> Sure. Before flashing system.img and Ubuntu tarball I flashed boot.img and recovery.img
[17:28] <CheeryLee> Recovery works fine.
[17:31] <peat-psuwit> CheeryLee: What do you mean "disappear", anyway? Like, how do you know that they disappear?
[17:33] <CheeryLee_> Oh, disconnect
[17:34] <peat-psuwit> CheeryLee_: What do you mean "disappear", anyway? Like, how do you know that they disappear?
[17:34] <CheeryLee_> So, when rootstock-ng finishes it's operations, I reboot the tablet. After it I got cycle reboot.
[17:35] <CheeryLee_> Through TWRP I can view the root folder
[17:36] <peat-psuwit> CheeryLee_: Hey hey hey, you shouldn't have TWRP. Flash "Ubuntu" recovery.
[17:36] <CheeryLee_> I was convinced that android folder doesn't create in root.
[17:37] <CheeryLee_> No, I use TWRP for file management
[17:38] <peat-psuwit> CheeryLee_: I think there's no problem with rootstock-touch-ng
[17:38] <CheeryLee_> Even if I use ubuntu recovery, the situation will not change
[17:39] <CheeryLee_> I have no /android folder in root.
[17:39] <peat-psuwit> CheeryLee_: Anyway, when you get a bootloop (that's the word), do you get Ubuntu word with 5 dots on the purple background?
[17:40] <CheeryLee_> No. I get Samsung logo. Nothing else.
[17:41] <CheeryLee_> It seems that the kernel does not see the ramdisk.
[17:42] <peat-psuwit> CheeryLee_: Create bootloop, go to recovery (Don't let phone power off), then run "cat /proc/last_kmsg" in recovery (any recovery will do).
[17:42] <CheeryLee_> Hmm. How can I turn to recovery without rebooting?
[17:43] <CheeryLee_> ADB doesn't work
[17:43] <peat-psuwit> CheeryLee_: Press recovery combo keys when the phone reboots.
[17:46] <CheeryLee_> I I have done it many times, but last_kmsg is absent
[17:46] <CheeryLee_> I have no it
[17:47] <CheeryLee_> Maybe my kernel doesn't want to be flashed? :D
[17:47] <peat-psuwit> CheeryLee_: I don't think so. Let me think....
[17:49] <mariogrip> is the wiki down or is it just me?
[17:50] <CheeryLee> No. It works fine
[17:51] <mariogrip> humm, that's weird. it works with firefox...
[17:51] <mariogrip> not in chrome
[17:53] <CheeryLee> Hmm. I just tried the wiki in my Chrome and it works. Try to clean your cache.
[17:54] <peat-psuwit> CheeryLee: What does your bootloop look like? Samsung logo appears, briefly disappear, then re-appear, all without your intervention. Is that right?
[17:54] <CheeryLee> Yes, it is
[17:55] <peat-psuwit> CheeryLee: BTW, what's your tablet's model?
[17:56] <CheeryLee> Galaxy Note 10.1 N8000
[17:59] <peat-psuwit> CheeryLee: When bootloop happen, try pressing only volume up and not pressing power button.
[18:00] <CheeryLee> OK, i'm going to try now. Don't go leave please
[18:13] <peat-psuwit> CheeryLee: Does it works?
[18:13] <CheeryLee> Rootstock-ng now. Still waiting
[18:18] <CheeryLee> I completely forgot! When rootstock comes to 'adding android system image to installation' recovery blinking in second.
[18:19] <CheeryLee> And process doesn't finish.
[18:20] <peat-psuwit> CheeryLee: That's strange. Could you try again?
[18:21] <peat-psuwit> CheeryLee: What's on the terminal when it fails?
[18:21] <CheeryLee> 'adding android system image to installation'
[18:21] <peat-psuwit> CheeryLee: And it goes to prompt?
[18:22] <CheeryLee> Now I get that: 'Invalid sparse file format at header magi. Failed to read sparse file'
[18:23] <peat-psuwit> CheeryLee: run "file $OUT/system.img" and give me the result.
[18:24] <CheeryLee> Linux rev 1.0 ext4 filesystem data, UUID=7737b09a-291e-a752-a883-f5e38364b952, volume name "SYSTEM" (extents) (large files)
[18:29] <peat-psuwit> CheeryLee: I see now why rootstock-touch-install doesn't work. Finding the way to solve.
[18:39] <peat-psuwit> CheeryLee: Run "sed -i.bak 's#simg2img \$SYSIMG \$WORKDIR/system.img.raw#\0 || cp $SYSIMG $WORKDIR/system.img.raw#' rootstock-touch-install" in project-rootstock-ng directory
[18:40] <peat-psuwit> CheeryLee: Then try running rootstock-touch-install again
[18:48] <CheeryLee> Still this error
[18:49] <peat-psuwit> CheeryLee: Does the flashing continue?
[18:49] <CheeryLee> The flashing process ended but I got bootloop
[18:50] <peat-psuwit> CheeryLee: Then press volume up when bootloop happens
[18:50] <CheeryLee> Nothing happens when pressing
[18:50] <peat-psuwit> CheeryLee: Did you hold it?
[18:50] <CheeryLee> Sure
[18:56] <CheeryLee> Now I check /system folder. It's empty.
[18:56] <peat-psuwit> CheeryLee: That's correct. System files sits in /data/ubuntu.img
[18:57] <CheeryLee> Hmm... I have only /data/media.
[18:58] <peat-psuwit> CheeryLee: The partition is probably not mounted.
[18:58] <peat-psuwit> CheeryLee: Let's do some experiment. Run 'ls /dev/block/platform'
[18:59] <CheeryLee> I get dw_mmc and s3c-sdhci.2
[18:59] <CheeryLee> My partitions stores in /dev/block/platform/dw_mmc/by-name/
[19:00] <peat-psuwit> CheeryLee: OK, now 'ls /dev/block/platform/dw_mmc/by-name/boot'
[19:01] <CheeryLee> /dev/block/platform/dw_mmc/by-name/BOOT
[19:01] <CheeryLee> Thats what I get
[19:01] <peat-psuwit> 'dd if=/dev/zero of=/dev/block/platform/dw_mmc/by-name/BOOT bs=16 count=1'
[19:02] <CheeryLee> And?
[19:02] <peat-psuwit> CheeryLee: reboot, wishing to get fastboot mode
[19:03] <CheeryLee> My device doesn't support fastboot. Only Heimdall and Odin.
[19:03] <peat-psuwit> CheeryLee: Oh, how can I forget that?
[19:04] <CheeryLee> So, I need to reflash the kernel?
[19:05] <peat-psuwit> CheeryLee: I'm sorry. Re-flash boot.img
[19:05] <CheeryLee> Ok. It's done.
[19:07] <peat-psuwit> CheeryLee: I'm out of idea to help solving your problem. Sorry.
[19:09] <CheeryLee> It's sad. I had high hopes. :c
[19:10] <peat-psuwit> CheeryLee: BTW, do you have console=tty0 in your kernel cmdline?
[19:10] <CheeryLee> Yep.
[19:11] <CheeryLee> And when compilation finishes I get the kernel which has a many 0 bites files.
[19:21] <peat-psuwit> CheeryLee: What files?
[19:23] <CheeryLee> In initramfs.cpio.gz. In folder bin and sbin
[19:26] <peat-psuwit> CheeryLee: where?
[19:29] <CheeryLee> boot.img contaims initramfs.cpio.gz and zImage, right?
[19:29] <CheeryLee> contains*
[19:29] <peat-psuwit> CheeryLee: Right.
[19:30] <CheeryLee> So, in initramfs.cpio.gz. In folder bin and sbin
[19:31] <peat-psuwit> CheeryLee: Ok. Ther're probably symlinks to Busybox multi-call binary.
[19:32] <CheeryLee> Oh, sure. I did not take it into account
[19:34] <CheeryLee> How can I make sure that boot.img was flashed on my device?
[19:35] <CheeryLee> I think it doesn't want to flash.
[19:36] <peat-psuwit> CheeryLee: How do you flash it, BTW? In recovery?
[19:36] <CheeryLee> Through Heimdall
[19:37] <peat-psuwit> CheeryLee: Try 'md5sum /dev/block/platform/dw_mmc/by-name/BOOT' in recovery, and 'md5sum boot.img' on your computer.
[19:38] <CheeryLee> It's different
[19:39] <peat-psuwit> CheeryLee: Then try flashing in recovery
[19:40] <CheeryLee> Hmm, but i have IMG, not ZIP
[19:40] <CheeryLee> I need to create it myself?
[19:40] <peat-psuwit> CheeryLee: 'dd if=boot.img of=/dev/block/platform/dw_mmc/by-name/BOOT'
[19:41] <CheeryLee> Run on computer or adb shell?
[19:41] <peat-psuwit> CheeryLee: adb shell, in recovery
[19:43] <CheeryLee> No space left on device
[19:44] <CheeryLee> Thats what i wrote
[19:45] <CheeryLee> Kernel contains the files that take up space
[19:45] <peat-psuwit> CheeryLee: that's strange.
[19:46] <peat-psuwit> CheeryLee: I think boot partition maybe really have not enough space to hold boot image.
[19:47] <CheeryLee> How can I extend it?
[19:47] <peat-psuwit> CheeryLee: Maybe hiemdal can help. But I really don't know.
[19:52] <CheeryLee> That's strange. I just extracted initramfs.cpio.gz and got 7.2 MBytes.
[19:54] <CheeryLee> So, when i delete symlinks, the size decreases.
[19:59] <peat-psuwit> CheeryLee: I have to go now. See you again next time.
[20:00] <CheeryLee> Thanks for your reply! I will try to extend my boot partition.
[20:37] <taiebot> Eh eh looks like the Mx5 pro will be a reality \o/ look what as landed 3 days ago online https://github.com/meizuosc/m576
[20:57] <matv1> taiebot well spotted!
[21:05] <tathhu> :o
[21:05] <tathhu> damn