[06:38] <LetoThe2nd> 'morning!
[06:39] <LetoThe2nd> whats the current recommended way fo cross-building packages, especially kernel?
[06:39] <LetoThe2nd> is xdeb still alive?
[06:41] <scientes> LetoThe2nd, xdeb is dead
[06:42] <scientes> LetoThe2nd, https://wiki.ubuntu.com/MultiarchCross
[06:42] <scientes> LetoThe2nd, also this http://gsoc.sitedethib.com/posts/apt-get_install_gcc-4.7-arm-linux-gnueabihf/
[06:42] <scientes> LetoThe2nd, oh if you just want to cross-build the kernel that is easy with upstream or just from a git  using make deb-pkg
[06:43] <scientes> just set the cross-compiler prefix, and run config, and make with ARCH=arm
[06:43] <scientes> and install gcc-arm-linux-gnueabi[hf]
[06:43] <scientes> which is in ubuntu an emdebian
[06:43] <scientes> *and
[06:43] <LetoThe2nd> scientes: does make-kpkg shonour the ARCH envirnoment variable?
[06:45] <scientes> make deb-pkg
[06:45] <scientes> please use that
[06:46] <scientes> LetoThe2nd, you will know if you arch variable isn't set right, cause you will get alot of configuration questions that dont apply to arm
[06:46] <scientes> (if you have set up your .config right in the first place)
[06:46] <LetoThe2nd> scientes: ok, will check that out. thanks!
[06:48] <scientes> the ubuntu kernel packages have configs in them to start you out if you need that
[06:48] <scientes> but really you need something for your board
[06:49] <LetoThe2nd> i've got a known good kernel config i'm using for rt tests :) for a start compiling on the panda was fine, but it starts to get boring ;)
[06:55] <scientes> yeah you just set the cross compiler prefix variable
[06:55] <scientes> and you can even set arch in your .config
[06:56] <scientes> but i just run it with ARCH=arm make uImage
[06:56] <scientes> and gcc-arm-linux-gnueabihf in ubuntu or emdebian has all you need to cross-compile it
[07:42] <ogra_> LetoThe2nd, http://marcin.juszkiewicz.com.pl/2012/03/26/ubuntu-12-04-precise-and-cross-compilation-of-arm-kernels/
[07:43] <LetoThe2nd> ogra_: ah, the usual suspects strike again
[07:43] <ogra_> :)
[07:43] <LetoThe2nd> ogra_: but does that apply to vanilla kernels also?
[07:43] <ogra_> CROSS_COMPILE=arm-linux-gnueabi- make uImage
[07:44] <ogra_> :)
[07:44] <LetoThe2nd> gnah.
[07:44] <ogra_> oh, might be gnueabihf nowadays
[07:44] <LetoThe2nd> it is.
[07:45] <LetoThe2nd> i mean, isn't there a compact way to cross-build vanilla kernels into a deb?
[07:45] <ogra_> ah, i think they ship a way upstream but never used it
[07:46] <ogra_> if its really vaniall mainline you wan, there is a kernel team PPA that has daily builds iirc
[07:47] <ogra_> http://kernel.ubuntu.com/~kernel-ppa/mainline/
[07:47] <LetoThe2nd> ogra_: hard to use if you want to apply rt patches and spidev enablement...
[07:47] <ogra_> that should be mainline just with the ubuntu packaging bits added
[07:47] <ogra_> ah, k
[07:48] <ogra_> CROSS_COMPILE=arm-linux-gnueabihf- make deb-pkg
[07:49] <ogra_> try that one
[07:49] <ogra_> i think thats the makefile target upstream ships for debs
[07:49] <LetoThe2nd> yes, ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- make deb-pkg
[07:49] <LetoThe2nd> probably.
[07:49] <LetoThe2nd> will let you know once i've copied everything over.
[07:50] <ogra_> it wont be "proper" but at least it uses the package system
[07:50] <LetoThe2nd> will lack "properness" in terms of?
[07:50] <LetoThe2nd> so far i've just used make-kpkg on the target itself
[07:51] <ogra_> dunno, but there must be a reason our kernel team takes the effort to do our own packaging ;)
[07:52] <LetoThe2nd> possibly yes.
[07:52]  * ogra_ shakes his head about amazon spam ...
[07:52] <LetoThe2nd> ogra_: pretty amazons?
[07:53] <ogra_> based on my recent buyings they offer me "blah" ...
[07:53] <ogra_> i just bought "blah" why would i be intrested to buy that again  ?
[07:53] <ogra_> probably from a different manufacturer than i just bought it from ... butu still, where is the logic in that
[09:51] <_Lucretia_> to build opengl, is there a deb with the headers in?
[09:52] <ogra_> opengl ... on arm ?!?
[09:53] <_Lucretia_> well, gles
[09:53] <ogra_> there are mesa headers for it, yes
[09:53] <_Lucretia_> there are mesa packages
[09:53] <_Lucretia_> right, so just install that?
[09:53] <ogra_> yes
[09:53] <_Lucretia_> it won't overwrite any gl acceleration libs - not that i can find them
[09:54] <alf__> _Lucretia_: What platform are you using?
[09:54] <_Lucretia_> pandaboard es
[09:54] <_Lucretia_> using armhf
[09:54] <_Lucretia_> have installed the sgx drivers
[09:55] <alf__> _Lucretia_: libgles2-omap4-sgx-dev (I don't remember the exact name) has the headers files you need
[09:55] <_Lucretia_> no such package
[09:56] <_Lucretia_> is it another repo i have to activate?
[09:56] <ogra_> alf__, why wouldnt mesa work ? thats what we use for package builds afaik
[09:56] <alf__> ogra_: I think that installing the mesa -dev packages would uninstall sgx
[09:57] <_Lucretia_> that's what I was thinking - also, it would be sw rendering
[09:57] <_Lucretia_> I need hw
[09:57] <ogra_> oh, that could be (no idea about the deps here, i didnt look) the resulting binaries should work just fine built against mesa though
[09:58] <ogra_> else everything we build packaged for gles wouldnt work ;)
[09:59] <alf__> ogra_: Sure, they would work fine, but the development cycle would be horrendous (I 've been there ;)
[10:00] <_Lucretia_> alf__: I don't have that package in apt - where do I get it?
[10:03] <alf__> _Lucretia_: Let me check...
[10:03] <_Lucretia_> thanks
[10:04]  * _Lucretia_ doesn't have universe active in the repo
[10:07] <alf__> _Lucretia_: do you have pvr-omap4-dev?
[10:08] <_Lucretia_> yup
[10:08] <_Lucretia_> in there?
[10:08] <_Lucretia_> oh they're hidden away
[10:09] <ogra_> https://launchpad.net/ubuntu/precise/+source/pvr-omap4/<IP_ADDRESS>.1.21-0ubuntu1 ...
[10:09] <_Lucretia_> thanks
[10:09] <ogra_> but if you used the PPA you should rather get the -dev package from there
[10:09] <ogra_> i doubt the version matches whats in the ubuntu archive
[10:10] <ogra_> (the above is whats in the archive in "restricted")
[10:11] <_Lucretia_> aye
[10:11] <_Lucretia_> i know
[10:11] <_Lucretia_> thanks
[10:11] <_Lucretia_> trying to build an app, seems to want the GL stuff as well
[10:13] <_Lucretia_> ok they can be installed side by side
[10:14] <alf__> _Lucretia_: btw, the correct name is libgles2-sgx-omap4-dev, can you install that?
[10:14] <_Lucretia_> alf__: no
[10:14] <_Lucretia_> not in my apt
[10:15] <alf__> ogra_: Do you know where ^^ is? Universe maybe?
[10:15] <_Lucretia_> i can turn on universe
[10:15] <ogra_> alf__, see the LP page ;) its in restricted
[10:16] <ogra_> (which is enabled by default ... as well as universe and multiverse usually)
[10:16] <alf__> ogra_: but pvr-omap4 source doesn't seem to produce libgles2-sgx-omap4*
[10:17] <ogra_> pvr-omap4-dev_<IP_ADDRESS>.1.21-0ubuntu1_armhf.deb
[10:17] <ogra_> might be that rsalveti named it differently ?
[10:18] <_Lucretia_> this is my sources http://pastebin.com/0b41Xi6T
[10:18] <alf__> I think that pvr-omap4* just contain the files, and libgles2/gles1/egl-sgx-* enable these using alternatives (or something like that)
[10:20] <ogra_> _Lucretia_, looks fine
[10:20] <ogra_> alf__, well, if that package is really needed we should get it in if it isnt ... but i think we should wait for rsalveti to explain
[10:21] <alf__> ogra_: agreed
[10:23] <_Lucretia_> ogra_: ok
[10:24] <_Lucretia_> so does the alternatives work for selecting mesa/pvr?
[10:24] <alf__> _Lucretia_: Can you please run 'apt-cache madison libgles2-sgx-omap4' , so we can get a hint where the libgles2-sgx packages are.
[10:25] <alf__> _Lucretia_: assuming you have libgles2-sgx-omap4 (but not -dev)
[10:25] <_Lucretia_> libgles2-sgx-omap4 <- I don't have that
[10:26] <alf__> _Lucretia_: ok
[10:26] <_Lucretia_> I have pvr-omap4-dev
[10:28] <_Lucretia_> my version of ubu is precise
[10:31] <alf__> _Lucretia_: ok, so to be clear, what happens when you try to build an app that requires gles2?
[10:31] <_Lucretia_> i haven't actually tried that yet
[10:31] <_Lucretia_> what i have tried is something that's a bit of an abomination
[10:31] <_Lucretia_> in that it still requires GL/* stuff
[10:31] <_Lucretia_> its wierd
[10:32] <_Lucretia_> but uses only the gles subset - it's a binding to it from Ada
[10:32] <_Lucretia_> tbh, it doesn't build and i'm gonna get onto the person who wrote it
[10:33] <alf__> _Lucretia_: As ogra_ mentioned before you can experiment with mesa gles1/gles2 first (e.g. on a normal desktop), and when it builds you can continue on the panda.
[10:35] <_Lucretia_> ok, so it's possible to do that by using the alternatives then?
[10:37] <alf__> _Lucretia_: You can install all of gl/gles1/gles2 at the same time
[10:37] <alf__> _Lucretia_: no need for alternatives for that
[10:38] <_Lucretia_> yes i have done
[10:38] <_Lucretia_> but i have to select which version i'm using then?
[10:38]  * _Lucretia_ is just a bit unsure how all this fits together
[10:39] <alf__> _Lucretia_: no, there are different libraries (libGL,libGLESv2...) and header file locations. It's the app's job to select what it want to use and build using that.
[10:41] <alf__> ogra_: Checking  the pvr-omap4 packages a bit more it seems they are able to work standalone. Two issues I am seeing: 1. no pkg-config files 2. They don't "Provide" libegl,libgles2 etc, I am not sure what's going on with that.
[10:42] <ogra_> yeah, thus lets wait for rsalveti, i'm sure he tested them ...
[10:43] <_Lucretia_> ta
[10:56]  * ogra_ arghs over Bug 1032535
[10:56] <ubot2> Launchpad bug 1032535 in grub2 "installArchives() failed: Setting up linux-image-3.2.0-26-generic (3.2.0-26.41) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms 3.2.0-26-generic /boot/vmlinuz-3.2.0-26-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.2.0-26-generic /boot/vmlinuz-3.2.0-26-generic update-initra
[10:56] <ogra_> wow, i'm impressed the bot can handle the description
[10:58] <LetoThe2nd> ... better than being compressed by the bot
[10:58] <ogra_> heh
[11:26] <LetoThe2nd> my panda fails to mount a nfs share, it just gets stuck forever at the mount command. mounting the share from the desktop box works, nevertheless. any ideas where to start debugging?
[12:28] <ogra_> is no_root_squash set ? (usual suspect)
[12:29] <LetoThe2nd> ogra_: sure. its not for RFS anyways.
[12:29] <ogra_> hmm
[12:30] <LetoThe2nd> only thing a bit unusual is that the exported directory is a symplink in the end. but that used to be fine for a long time, even for RFS. and its still when i mount on the desktop
[12:31] <ogra_> do you have the nfs-common stuff installed ?
[12:31] <LetoThe2nd> yes.
[12:32] <ogra_> stgraber, any ideas ? ^^^
[12:32]  * ogra_ hasnt actually used nfs in years
[12:32] <LetoThe2nd> does nfs-mounting produce any logging somewhere?
[12:32] <ogra_> syslog i would guess
[12:33] <LetoThe2nd> i can start over with a backup of the fresh install, but it'll take quite some time to copy the image back.
[12:33] <ogra_> nah, better debug it
[12:34] <ogra_> lsmod shows nfs i suppose (and /proc/filesystems)
[12:36] <LetoThe2nd> check. /proc/filesystems{nfs,nfs4,nfsd} are marked with nodev, though
[12:36] <ogra_> are you using v4 actually ?
[12:36]  * ogra_ isnt sure if you dont need nfs4-acl-tools then
[12:37] <LetoThe2nd> not actively decided for v4
[12:45] <LetoThe2nd> the exports declaration is also classically v3
[12:46] <ogra_> weird
[12:46] <LetoThe2nd> /srv/panda<IP_ADDRESS>/24(rw,sync,no_root_squash,no_subtree_check)
[12:46] <LetoThe2nd> yeah
[12:46] <LetoThe2nd> hm. IIRC i've had a lockout earlier when using another NFS mount
[12:46] <LetoThe2nd> lockup
[12:47] <ogra_> tried async ?
[12:47] <LetoThe2nd> just done. no effect.
[12:48] <ogra_> pinging the ip of the server works ?
[12:48] <LetoThe2nd> yep.
[12:48] <ogra_> (and i assume the spaces in your fstab line above were just eaten by the paste)
[12:49] <ogra_> err /etc/exports line
[12:49] <LetoThe2nd> ogra_: correct assumptions. irssi ate my tabs.
[12:50] <ogra_> well, smells like a bug but without any data in dmesg or syslog its hard to nail down
[12:51] <LetoThe2nd> dmesg is dead silent
[12:51] <ogra_> no mount errors in syslog ?
[12:53] <LetoThe2nd> also dead silent
[12:53] <ogra_> very weird
[12:53] <LetoThe2nd> i think i'll start over with the backupped image.
[12:53] <LetoThe2nd> if it still appears then, it really is a hard bug.
[12:53] <ogra_> well, we need at least some datapoints
[12:58] <LetoThe2nd> hard to find.
[13:07] <stgraber> LetoThe2nd: is it just a problem at boot time? as in, if you add "nobootwait" in the fstab and try to mount post-boot, does it work?
[13:08] <BV1AL> which kernel module can enable OTG as 'host mode' ? so I can set it to load first in 'uInitrd'
[13:10] <LetoThe2nd> stgraber: only talking about post-boot, its a share i want to use for data transfer
[13:25] <ogra_> BV1AL, http://omappedia.org/wiki/Ubuntu_on_OMAP_FAQ#USB_OTG_port_on_PandaBoard_does_not_as_host_under_Ubuntu
[13:25] <_Lucretia_> back
[13:38] <BV1AL> ogra_: thanks
[13:38] <BV1AL> it seems ubuntu has poor support for these devices  :(
[13:41] <ogra_> feel free to help out with patches :)
[13:42] <BV1AL> I mean they release those 'pre-build' images for us to download, but it's unable to run
[13:42] <ogra_> ??
[13:42] <ogra_> they get tested pretty heavily before being released
[13:43] <LetoThe2nd> ogra_: i guess its the usual "we didn't you guess in advance what i need personally and implement it exactly that way"-bashing.
[13:43] <LetoThe2nd> s/we/why/
[13:43] <BV1AL> the ubuntu pre-build images just don't support OTG as host mode, so I cannot connect keyb/mouse to work on it
[13:44] <ogra_> connect to the normal USB?
[13:44] <ogra_> as i said, feel free to file a bug and submit a patch that fixes it
[13:44] <BV1AL> the Blaze has only a OTG to connect USB devices
[13:44] <ogra_> a blaze isnt a pandaboard
[13:45] <BV1AL> i knew
[13:45] <ogra_> if you have a blaze you should also have a contract with TI ... they provide ubuntu images adjusted for blazes
[13:46] <BV1AL> so it's a proprietary developed image ?
[13:46] <ogra_> no, its the same image with adjustments for the blaze
[13:47] <ogra_> i.e. a different kernel that has OTG enabled i suppose
[13:47] <ogra_> ask your TI representative ;)
[13:47] <BV1AL> this mean I have to find my contract, then ask TI for the image to download ?
[13:47] <ogra_> i guess so
[13:48] <BV1AL> ok, thanks
[13:48] <ogra_> the panda image works on the blaze but is definitely not optimized in any way for it
[13:49] <BV1AL> I thought I can find a kernel module and put in 'uInitrd' to force it load first during bootup and enable OTG.
[13:50] <ogra_> well, apparently not witzh the pandaboard kernel
[13:56] <alf__> rsalveti: Hi! Are there any libgl*-sgx-omap4 packages for precise armhf (not linaro)? I can only find pvr-omap4*
[14:51] <LetoThe2nd> ogra_: after reverting to backup, mount works fine. hmh.
[15:19] <ogra_> LetoThe2nd, cosmic rays
[15:22] <LetoThe2nd> ogra_: either that, or lack of metal mp3s on the nfs share.
[15:23] <ogra_> hah
[16:55] <prpplague> just fyi, there is an omap5 pandaboard wishlist thread up on the mailing list - feel free to post complaints as well - https://groups.google.com/forum/#!topic/pandaboard/mQxpEEDM6Ww
[16:59] <GrueMaster> Sata, 1Gb ethernet, 2G mem, 802.11n come to mind.?
[16:59] <infinity> Bazillions of gigs of RAM!
[16:59] <infinity> But you already have my feedback. ;)
[17:00] <GrueMaster> Sounds like someone wants to rebuild OOo.
[17:00] <infinity> prpplague: Please don't ditch the DB9 serial port, unless you ship the Panda5 with a header->DB9 ribbon, so I don't have to source one.
[17:01] <prpplague> please add to the thread if you have time
[17:03] <ogra_> 2G mem ?
[17:03]  * ogra_ just wants DRAM sockets !
[17:03] <ogra_> with no limits !
[17:06] <infinity> prpplague: Responded.
[17:06] <prpplague> infinity: thanks
[17:09] <rsalveti> alf__: the pvr-omap4 replaces the others
[17:09] <rsalveti> alf__: because it uses alternatives
[17:10] <rsalveti> ogra_: LetoThe2nd ^
[17:10] <rsalveti> so we don't have the libgl* packages anymore
[17:10] <prpplague> rsalveti: your feedback would greatly appreciated as well
[17:11] <rsalveti> prpplague: oh, cool, will check
[17:11] <ogra_> rsalveti, thats what i thought, thanks for confirming
[17:37] <ppisati> prpplague: any ETA for this board?
[17:38]  * prpplague can't make any statements on that
[17:38] <prpplague> ppisati: but any info you post on the list would be extremely helpfu;
[17:38] <prpplague> helpful
[17:38] <prpplague> brb need food
[17:38] <ppisati> prpplague: i don't have any info, i want info :)
[17:38]  * ogra_ is in line with maens on the rs232 :)
[17:39] <ppisati> prpplague: ram sockets, sats and pci-e
[17:39] <ppisati> prpplague: that would be perfect
[17:39] <ogra_> prpplague, and after spending two days to work around the USB powering (which is there for no good reason really) please done make it power through any mini USB ports
[17:40] <ogra_> oh, and no microSD ...
[17:40] <ogra_> i hate using adapters
[18:00] <prpplague> ogra_: i did not understand your statement about usb powering
[18:00] <ogra_> prpplague, you didnt read my blogpost then :)
[18:00] <prpplague> ogra_: url?
[18:00] <ogra_> http://ograblog.wordpress.com/2012/08/06/the-bamboo-feeder-automating-continuous-arm-image-tests/
[18:01] <ogra_> the mini USB doesnt give enough current to run the board unless you roll a custom embedded kernel anyway ...  i would just drop that "feature" in the new board
[18:02] <ogra_> it made a lot of sense on the beagle ... but the more power you require the less useful it is
[18:04] <prpplague> ogra_: yes that is why we recommend the dual usb cable, similar to whats used on external HD's and cdroms
[18:04] <prpplague> ogra_: but i am not understanding your "power cycle" issue
[18:04] <ogra_> prpplague, the boards are sitting in a rack you cant really access ... the power supplies are connected to a web controlled power strip
[18:05] <ogra_> if i power off the PSU, the boards stay on
[18:05] <ogra_> pulling their power from mini usb
[18:05] <prpplague> ogra_: they shouldn't be as long as you have the barrel jack inserted
[18:05] <ogra_> well, they are
[18:06] <prpplague> ogra_: even when the barrel jack is inserted?
[18:06] <ogra_> well, the web controlled power strip has no robot arm attached, so yes :)
[18:06] <prpplague> ogra_: well i didn't know if you were powering the board via the expansion header or via one of the other power points
[18:06] <prpplague> ogra_: 4430 or 4460?
[18:07] <ogra_> all of them
[18:07] <ogra_> from EA1 to ES B1
[18:07] <ogra_> i havent found a model that would power off in this setup
[18:07] <prpplague> ogra_: i suspect there is something in your setup that i do not understand, because i regularly test panda for this specific condition
[18:08] <ogra_> there is nothing to understand, use the std PSU and a usb->miniUSB cable
[18:08] <prpplague> ogra_: i wish you had checked with me sooner on this
[18:08] <prpplague> ogra_: yea thats how we test it
[18:08] <ogra_> prpplague, i only discovered it during this project last weeks monday
[18:09] <ogra_> but i can always reproduce, even with my pandas at home
[18:09] <ogra_> as long as mini usb is attached they recieve power
[18:09] <ogra_> no matter if i pull the barrel connector or the wall plug
[18:09] <ogra_> anyway, i worked around i, works fine now :)
[18:10] <ogra_> s/i/it/
[18:10] <prpplague> ogra_: yea that bothers me, because we specifically test for that
[18:10] <ogra_> if its actually supposed to have a switch through the barrel connector i'll happily test an EA board of omap5 if you have one :)
[18:10] <prpplague> ogra_: i just tested two boards here, neither show that issue
[18:10] <ogra_> funny
[18:11] <prpplague> ogra_: the board is specifically designed to not allow that to happen
[18:11] <prpplague> ogra_: no mods done to your boards?
[18:11] <ogra_> well, what should i say
[18:12] <ogra_> nope, they came freshly out of the boxes or out of bubblewrap ....
[18:12] <prpplague> ogra_: interesting
[18:12] <ogra_> we have several different models there
[18:12] <prpplague> ogra_: i'll grab some off the assembly line for testing
[18:12] <ogra_> i kept the EA1 though
[18:13] <ogra_> (doesnt make sense to test on such old HW)
[18:13] <prpplague> now EA1 boards might have an issue
[18:14] <ogra_> well, thats why i kept it out of the loop ;)
[18:14] <ogra_> the others are all ES
[18:14] <ogra_> different versions though (dont ask me which, i remember an A1 and a B1, all that are in now have black PCBs)
[18:15] <prpplague> ogra_: i'll rerun a bunch of tests to see if can replicate the issue
[18:15] <ogra_> it works fine as it is now and i wont be able to tear it apart anymore
[18:15] <ogra_> (beond me being 4000 miles away from it)
[18:15] <prpplague> but i need to know why you were having that problem
[18:16] <ogra_> i'll try to replicate it her tomorrow with the boards i brought back
[18:20] <prpplague> ogra_: interesting
[18:21] <prpplague> ogra_: i just tested A1-A4 of pandaboard
[18:21] <prpplague> ogra_: all work properly
[18:21] <ogra_> and let me guess, you dont get the issue
[18:21] <ogra_> fun
[18:21] <prpplague> ogra_: i am wondering if all of yours were made by either circuitco or svtronics
[18:22] <ogra_> how would i tell ?
[18:22] <ogra_> (apart from not having the boxes anymore or any physical access)
[18:23] <ogra_> as i said, i can test tomorrow ... now GF calls and she will slay me if dinner gets cold ...
[18:23] <prpplague> ogra_: no worries
[18:23] <prpplague> ogra_: i suspect there has been an incorrect placement of a resistor on your boards
[18:23] <ogra_> oh, i'm not worried, the setup works fine :)
[18:23] <ogra_> and i really enjoyed doing the hw hack ...
[18:24] <ogra_> nobody was injured, result was good ;)
[18:26] <prpplague> ogra_: hehe, yea, just worries me
[18:26] <prpplague> ogra_: i'll dig around to find out if we have a BoM issue
[19:40] <GrueMaster> ogra_: My pandarack at home had the power going to the barrel connector.  I had a single AT power supply connected through a serial controlled relay.  I also had all mini-usb connectors plugged into a powered hub which was connected to my serial console server.  I used this setup to test the configuration for the build rack that davidm built, and continue to use it now (although for SETI work).
[19:41] <GrueMaster> And I have several different rev boards, from EA1 to ES B1.
[19:55] <ojn> GrueMaster, did you use udev to keep the machines at a stable console device number, or did you not care that they could get renumbered on reboots?
[19:55] <ojn> that's my current pain point with usb-to-serial controllers as console server
[19:59] <GrueMaster> ojn: for my serial console setup, I have an 8-port PCI serial interface.  Always enumerates from com4-com11 and each 9-pin end is numbered.
[19:59] <GrueMaster> I didin't use the mini-usb.  OTG was too unstable between kernel rev's.
[20:00] <GrueMaster> I used mini-usb as one of the two boot methods, mainly to pull a preinstalled or netboot image to SD.
[20:02] <GrueMaster> I had too many issues with usb-serial cables.  1 per system is fine, 2+ becomes a headache.  I even have a 4-port usb-serial cable, but even it re-enumerates each port randomly.
[20:08] <ojn> yeah. having udev handle numbering of ttyUSB* the same way ethernet interfaces are handled wouldn't be a bad idea, renaming them to new numbers and keeping them stable. :)
[20:08] <ojn> seems quite doable, just never got high enough on the todo list
[20:11] <infinity> ojn: It's not even remotely doable with most USB->Serial dongles, actually.
[20:11] <infinity> ojn: Most have no unique identifier.
[20:11] <infinity> (Unless you intentionally buy several different brands)
[20:12] <scientes> just look at all the insanity in gpsd cause gps devices actually look like serial dongles
[20:12] <scientes> and gpsd has to bind to all of them and figure out if they are gps devices
[20:13]  * infinity vomits a little.
[20:13] <ojn> infinity, hmm, i was pretty sure the ones I looked at had serial numbers. Grmbl.
[20:13] <infinity> I thought I escaped modems 20 years ago.
[20:13] <infinity> Apparently not.
[20:13] <infinity> ojn: None of mine do.
[20:14] <infinity> ojn: And GrueMaster's squid-like one with several dongles had no way to uniquely identify the tentacles.
[20:14] <ojn> awesome
[20:15] <infinity> It makes perfect sense, really.
[20:15] <infinity> USB->serial dongles are a high-marging, low-cost part that have no REASON for someone to burn a unique ID into each one, so why would the manufacturers bother?
[20:16] <infinity> The tiny subset of their customers that might care (ie: us) really aren't enough to worry about.
[20:16] <infinity> s/marging/margin/
[20:16] <GrueMaster> Yea, my "squid" cable was esentially a hub in the center with 4 individual serial chips (pl2303 iirc) on the ends.
[20:17] <GrueMaster> If they had serial numbers in the usb device info, udev would be a no-brainer.
[20:18] <GrueMaster> But I have now experienced a worse condition.  Here in my new job, I have to suffer with Windows 7.  I have two different brands of serial usb cables, neither of which have the driver cd's.  They both work in Linux w/o issues.  Windows doesn't recognise them at all.
[20:19] <stgraber> VM + usb passthrough? :)
[20:19] <GrueMaster> stgraber: ???
[20:20] <GrueMaster> Straight Windows.  Sadly, I have had to revert to running Linux in a VM.  Only way to do decent coding.
[20:20] <GrueMaster> (and ensure my boss doesn't powercycle my Linux dev system...again.
[20:22] <stgraber> GrueMaster: You could run a VM on Windows using the USB passthrough feature of vmware/virtualbox to forward to the Ubuntu VM, then if the software is Windows-speciifc, run it in wine ;)
[20:22] <stgraber> then no more serial driver problem
[20:22] <stgraber> (though probably a whole lot of other problems)
[20:23] <GrueMaster> The Windows software has a slew of incompatibilities with Wine.  Doesn't even like to run in a Windows VM (I tried).
[20:23] <GrueMaster> The different programs I have to deal with are...interesting at best.
[20:23] <infinity> stgraber: That's just disgusting. :P
[20:24] <stgraber> infinity: well, the alternative being to write a proper universal usb serial driver for Windows, I think I prefer to use a VM and wine ;)
[20:24] <GrueMaster> Meh.  I've done worse things (like running a dos envirounment in a vm under an emulator.
[20:24] <infinity> I suspect said proper driver might already exist, and the "driver disks" are nothing more than .inf files.
[20:25] <GrueMaster> True.  But without that inf file, you're hosed.
[20:25] <infinity> Surely, the Internets can provide.
[20:25] <GrueMaster> And since there are no markings on said cable, no way to look up the vendor.
[20:25] <infinity> Or you can yank the USB IDs from Linux and write an INF file. :P
[20:26] <GrueMaster> I looked, but all I could find were malware sites with "We can identify what drivers you need" crapware.
[20:26] <GrueMaster> Still need the dll for the actual serial chip.  MOStech, iirc.
[20:26] <GrueMaster> In the end, I threw the cable in the trash and went across the street to buy two new Trendnet cables.
[20:27] <GrueMaster> At my salary rate, it was cheaper to get new cables.


[00:25] <cjwatson> srwalter: I can have a look in the morning if nobody gets there first.  Maybe file a ticket on https://answers.launchpad.net/launchpad/+addquestion to remind us?
[00:26] <cjwatson> (can't look at logs from where I am at the moment)
[00:34] <wgrant> srwalter: You're right that it's being rejected with no indication of the error, but I see from earlier uploads that you had some weird files in the .changes. How are you building the package? Can you upload it somewhere else so we can download it and see what might be wrong?
[00:45] <teward> cjwatson: wgrant: do you know when the daily/weekly/regular CVE DB updates are integrated into LP?  Just curious the frequency of it
[00:46] <wgrant> teward: The import runs daily.
[00:46] <teward> ack
[00:49] <teward> ah i see the CVE extractor from comments has pulled in the CVEs I was looking to see, and the system'll autoupdate the CVEs with actual descriptions later.  Good.  :D
[02:29] <srwalter> wgrant: I think that launchpad doesn't like debian/source/format being set to "3.0 (git)"  that's why that .bundle file (or maybe it's named .git?) was uploaded
[02:34] <wgrant> srwalter: Right, no widely used archive management software supports 3.0 (git)
[02:34] <wgrant> (it has major copyright compliance issues, along with bloat)
[02:35] <tsimonq2> That's a thing?
[02:36] <sarnold> I've never seen one in the wild, anyway
[02:36] <tsimonq2> How would you even do that? :)
[02:36] <srwalter> Ah, didn't realize that.  I just didn't want to deal with patches in my git repo :)
[02:36] <tsimonq2> Sorry for dogpiling on you srwalter, it just piqued my curiosity.
[02:37] <srwalter> no problem :)  I don't remember what I googled for, but I came across that somehow and seemed like it did what I wanted
[02:46] <wgrant> srwalter: I believe there are tools around to translate a git repo into a nice 3.0 (quilt) source package, but I'm not familiar with specifics.
[16:45] <ricotz> cjwatson, hi :), I think the PPA publisher is stuck again
[16:45] <cjwatson> ricotz: I unstuck it a little while ago but it has a backlog
[16:46] <cjwatson> It is working though
[16:46] <ricotz> cjwatson, I see, thanks!


[00:23] <DJOmnifrog>  o/ o, o/ o, o/
[00:27]  * cyberanger wonders if DJOmnifrog's hand is tired yet
[00:40] <DJOmnifrog> nevar!
[01:48] <DJOmnifrog> SHAKE SHAKE SHAKE!


[04:45] <cpaelzer> good morning
[06:14] <lordievader> Good morning
[06:21] <cpaelzer> hi lordievader
[06:22] <lordievader> Hey cpaelzer, how are you doing?
[06:22] <cpaelzer> great, I hope you as well?
[06:22] <lordievader> Yes, doing good :)
[06:38] <boritek> hello. why is it not possible to istall Ubuntu Server 18.04.1 in Virtualbox?
[06:40] <cpaelzer> boritek: it should work, what exactly is breaking for you?
[06:46] <boritek> well i have tried a simpler method now, it seems to work if installing it via virtualbox cdrom
[06:46] <boritek> it does not work though via network pxe booting
[06:46] <boritek> and pxe booting is also broken on its own, but I was able to make it boot via some APPEND kernel parameter
[07:24] <lordievader> Does it kernel panic or something with PXE?
[11:21] <CheckmateX> Hi can i add message to a blocked ip on .htaccess file ?
[11:26] <ahasenack> CheckmateX: I don't know, sorry
[11:27] <blackflow> CheckmateX: what do you mean "add message"?
[11:28] <CheckmateX> Specified message like go away and not forbidden html message
[11:28] <blackflow> well you can have a custom 403 page, yes, see "ErrorDocument" directive
[11:29] <blackflow> not sure if you can vary them per IP. You could with nginx, but I don't know if apache has the ability
[11:29] <blackflow> unless you use PHP for the 403 page and do the IP-based magick there
[11:31] <CheckmateX> blackflow echo will not work ?
[11:32] <CheckmateX> Order Deny,Allow
[11:32] <CheckmateX>  echo '<h1> blocked </h1>'
[11:33] <blackflow> from .htaccess? no
[11:34] <CheckmateX> yes
[11:34] <CheckmateX> not work echo with me
[11:34] <blackflow> so why don't you use a custom 403 page?
[11:35] <CheckmateX> because i want it easy just echo message from htaccess
[11:35] <blackflow> CheckmateX: you'll have to write a module for that then.
[11:38] <CheckmateX> blackflow ok i will try the 403 way
[11:40] <CheckmateX> blackflow should i add the path of the file or not .?
[11:40] <CheckmateX> ErrorDocument 403 /var/www/html/test.php
[11:42] <blackflow> CheckmateX: you know what? your echo question got me looking into whether there already are modules and it appears you can actaully specify a custom message with ErrorDocument itself.     ErrorDocument 403 "Go away, or something!"
[11:42] <blackflow> otherwise the path is an URL that's processed as such.
[11:43] <CheckmateX> blackflow i've added the option but not working !!
[11:46] <blackflow> CheckmateX: not sure what you've added, but you can consult the documentation, see what you did wrong:  https://httpd.apache.org/docs/2.4/mod/core.html#errordocument
[12:24] <CheckmateX> blackflow
[12:25] <CheckmateX> i've blocked the ip but its still on the var/logs
[12:26] <CheckmateX> i still received high request on the logs from that ip
[12:29] <CheckmateX> now i need to stop logs from that ip :/
[12:29] <lordievader> You've blocked the ip? How? Apache's 403 is not a block.
[12:30] <lordievader> To block connection from that source you need to instruct your firewall to drop or reject the traffic from there.
[12:36] <CheckmateX> lordievader you mean the option i do if htaccess deny ip not working ?
[12:37] <lordievader> Yes. That denies them to see the actual content (which could lower cpu load, not having to run php code for example), but apache still serves them something (the 403 page).
[12:37] <blackflow> CheckmateX: if you have high traffic from an IP and block it anyway with deny from, then yes dropping the traffic at the firewall level is your best choice, but then they won't see your message
[12:37] <blackflow> CheckmateX: or put nginx in front of apache
[12:37] <CheckmateX> lordievader you're right i checked the ufw status  Status: inactive
[12:38] <CheckmateX> how thats possible inactive!!
[12:38] <CheckmateX> anything wrong ?
[12:39] <blackflow> sounds like you didn't configure it. it's not enabled by default, it can't read your mind.
[12:41] <CheckmateX> blackflow i've enable it right now its ok but i can see the logs from that ip
[12:42] <blackflow> CheckmateX: then you didn't configure it
[12:44] <CheckmateX> its already configured i just enable it right now
[12:44] <CheckmateX> status [ 1] Anywhere                   DENY IN
[12:44] <CheckmateX> its say the ip denyed and i still receive var/logs
[12:45] <blackflow> CheckmateX: I'm guessing because it's allowing established and related flows. it should deny new connections from that IP
[12:45] <CheckmateX> ive denyed all connection sudo ufw deny from
[12:45] <CheckmateX> i'm using cloudflare by the way
[12:47] <blackflow> CheckmateX: then it won't work as you think it would. if you use CF then the src IP is cloudeflare's
[12:49] <CheckmateX> blackflow yeah cloudflare was blocked that ip i cannot see any logs now
[12:56] <rbasak> ahasenack: opinion on bug 1770532 please?
[12:56] <rbasak> Looks like Debian haven't patched either, but I haven't looked thoroughly
[12:57] <ahasenack> I don't know how this works, I was hoping upstream would do something
[12:58] <ahasenack> can we use the mailing list thread as basis to accept the change?
[12:58] <rbasak> Yes. We don't need upstream acknowledgement. We strongly prefer to, but it's not a hard requirement.
[12:58] <rbasak> But patching ourselves alone is a judgement call because then we're on the hook to maintain it.
[12:59] <rbasak> Which can be difficult in the future if upstream does something that will cause us to change user behaviour if we drop our patch, for example.
[12:59] <CheckmateX> blackflow shit even with cloudflare i still see that ip on the firewall of cloudflare
[12:59] <ahasenack> rbasak: yes, I know nothing about DKIM and the perl code in amavisd-new
[13:00] <blackflow> CheckmateX: well then that's CF's problem, not Ubuntu, right? :)
[13:00] <rbasak> ahasenack: yeah that's the hard part :-/
[13:00] <ahasenack> rbasak: maybe if #is uses it they could take a look? I doubt they use it, though
[13:00] <ahasenack> and it's in main :/
[13:01] <blackflow> what's amavis doing dkim signing anyway?
[13:01] <ahasenack> if upsream is gone, is that basis for demoting amavisd-new?
[13:01] <ahasenack> blackflow: maybe checking?
[13:01] <ahasenack> ah no, it says signing
[13:01] <rbasak> It's definitely a basis for questioning its continued presence in main.
[13:01] <CheckmateX> blaclflow it was blocked by i still see logs even with cloudflare
[13:02] <sdeziel> ahasenack: I use amavisd-new for both signing and checking
[13:02] <blackflow> CheckmateX: check which IP you're blocking. with CF in the equation, the src IP on the packets, and those logged by apache -- if you use cloudflare mod or something other trusting and logging x-forwarded-for -- will be different.
[13:02] <sdeziel> ahasenack: on Trusty though :(
[13:03] <blackflow> amavis upstream gone, that's not good. it's the only viable middleware for post-content filtering with different sub-daemons.
[13:03] <ahasenack> sdeziel: so you just need to upgrade to xenial, then bionic, and then tell us if the patch in the bug works? :)
[13:03] <blackflow> s/post-content/post-queue/
[13:03] <CheckmateX> i think i will try the option of CF i'm under attack
[13:04] <CheckmateX> blackflow the problem on the logs cannot stop that ip on the logs keep saving
[13:04] <rbasak> ahasenack: well, one of the reporters/patch authors has already told us that the patch works :)
[13:04] <sdeziel> ahasenack: will get there eventually but I wanted to confirm it does both signing and verifying
[13:04] <blackflow> CheckmateX: well like I said, with CF the IPs are different
[13:05] <rbasak> sdeziel: apparently it doesn't do DKIM signing :-P
[13:05] <blackflow> CheckmateX: so be sure to understand what is logged exactly and what you're blocking. Are you blocking CF or end user, and do you have x-forwarded-for or something other logged, rather than packet src IP.
[13:09] <sdeziel> rbasak: that's a bad regression... renders amavisd-new almost useless for us
[13:09] <CheckmateX> yes i have a search.php page they use some POST codes to search fast
[13:10] <CheckmateX> i' think i will go with google captcha if they search fast 10 time request to enter the captcha
[13:10] <CheckmateX> disturbing me
[13:11] <rbasak> sdeziel: it'd be great to get some of your help in fixing this in Bionic. I think part of the issue here is that most of us aren't familiar with amavisd-new in the detail we think we need :-/
[13:12] <ahasenack> rbasak: we could start with a debian bug
[13:12] <rbasak> ahasenack: sure. But I'm reluctant to block on a reply since we've been handed an apparently working patch.
[13:13] <ahasenack> we could accept it, but be more rigorous with the testing period
[13:13] <ahasenack> require two people to confirm it's working and has no regressions
[13:13] <ahasenack> thinking in terms of the sru
[13:13] <CheckmateX> blackflow i dont know what to do i want keep the search as easy way possible
[13:13] <sdeziel> ahasenack: I just added https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882324 to the bug
[13:13] <ahasenack> sdeziel: is that the same issue?
[13:14] <ahasenack> ah
[13:14] <sdeziel> yes
[13:14] <ahasenack> rbasak: fedora seems to be using it
[13:15] <rbasak> Exactly the same patch?
[13:15] <rbasak> I was under the impression that there were three available :-/
[13:15] <ahasenack> didn't check. There seem to be two versions
[13:17] <CheckmateX> blackflow untile now one option work with CF "i'm under attack" option
[13:23] <rbasak> rharper: may I have some help triaging bug 1761573 please? Is this the same issue or a new one?
[13:41] <Ussat> has the update path from 16.X --> 18.X been enabled ?
[13:51] <ahasenack> I think not, I had to use -d earlier today
[13:51] <ahasenack> Ussat: ^
[13:52] <boxrick> Any reason this doesn't work? 'mount --bind /dev/null /tmp/null' ---- mount: mount point /tmp/null does not exist
[13:54] <Ussat> OK, thanks
[13:54] <Ussat> Not in a huge hurry, and I did use -d earlier last week and was fine
[13:54] <ahasenack> boxrick: /dev/null is not a directory. You can create another null in /tmp if you want, no need to bind mount it
[13:55] <boxrick> mknod isn't available in this case since its an unpriviledged container
[13:55] <boxrick> I was trying to find an alternative.
[13:55] <ahasenack> you can try cp -a /dev/null /tmp
[13:55] <ahasenack> but if /tmp doesn't allow devices, you will get a permission denied error
[13:56] <sdeziel> boxrick: did you "touch /tmp/null" first?
[13:57] <boxrick> Nope
[13:57] <boxrick> Oh that was easy
[13:58] <boxrick> I thought I tried that before, clearly not
[14:00] <boxrick> Thanks sdeziel
[14:00] <sdeziel> np
[14:03] <ahasenack> cpaelzer: have you seen this in ppc64el builds?
[14:03] <ahasenack> cc1plus: error: unrecognized command line option ‘-Wno-deprecated-register’ [-Werror]
[14:11] <rharper> rbasak: sure
[14:13]  * ahasenack scratches head
[14:13] <ahasenack> ubuntu@cosmic-squid4:~$ g++ hello.cpp -o hello -Wno-deprecated-register
[14:13] <ahasenack> ubuntu@cosmic-squid4:~$ echo $?
[14:13] <ahasenack> 0
[14:13] <ahasenack> I guess I have to try on a real ppc64el
[14:17] <cpaelzer> ahasenack: not seen yet
[14:18] <cpaelzer> ahasenack: do you have access or should I try quickly?
[14:18] <ahasenack> I have
[14:18] <cpaelzer> ok
[14:18] <ahasenack> it's super odd, previous lines in the build show that flag being used and working, then all of a sudden it fails. make -j is being used, but just -j4, and many many other g++ lines worked
[14:18] <ahasenack> will know in a minute
[14:23] <ahasenack> trying an actual build, since g++ in the command line worked just fine compiling a hello-world.cpp sample
[14:25] <cpaelzer> ahasenack: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-4-06-compile-errors-on-Ubuntu-12-04-td4676098.html
[14:25] <cpaelzer> but your compiler should be rather new
[14:25] <ahasenack> yeah :)
[14:25] <ahasenack> it's also a known issue in the faq, but for old compilers
[14:25] <ahasenack> and it built on all other arches, except ppc64el
[14:26] <ahasenack> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3351/+packages
[14:27] <ahasenack> reproduced
[14:28] <ahasenack> waaaat
[14:29] <ahasenack> I think the problem is something else, the message is just misleading
[14:40] <cpaelzer> ahasenack: you reproduced it
[14:41] <cpaelzer> including the "working at first and then later breaking" ?
[14:41] <ahasenack> yes in the build
[14:41] <ahasenack> but if I copy the command line, and run again, it works
[14:41] <cpaelzer> can you sneak in an env call
[14:41] <cpaelzer> so you see what is set for the compiler?
[14:41] <ahasenack> I think the real error trigger is a bit up in the logs, where it complains about a variable that may be used uninitialized
[14:42] <ahasenack> maybe
[14:42] <ahasenack> trying a build without the parallelism enabled now
[14:42] <ahasenack> but it could really be just a different code path taken in the ppc64el arch, as I don't see what warning in the non-ppc builds
[14:42] <ahasenack> i'm talking about this one:
[14:43] <ahasenack> https://pastebin.ubuntu.com/p/HNC2Z2Yk9F/ <-- the tval warning that is being treated as an error
[14:46] <ahasenack> https://pastebin.ubuntu.com/p/JDVw8zFt6T/ I can probably fix that by just initializing tval with NULL, as parseTimeLine(&tval,...) stores a value there anyway
[17:03] <ahasenack> cpaelzer: rbasak: man
[17:03] <ahasenack> -O2/-O3 is the difference
[17:04] <ahasenack> https://gist.github.com/panlinux/4716e167c2e06612b28be4b9f8f2b52b just adding -O3 or -O2 at the end of that command line, which overrides any previous -On
[17:04] <ahasenack> first one, with -O2, worked
[17:04] <ahasenack> second one, huge error
[17:05] <ahasenack> -O3 seems to be enabling some -W options
[17:05] <ahasenack> the manpage doesn't mention that next to -O3
[17:22] <hallyn> stgraber: is landscape suppsoed to be integrated with snappy?
[17:23] <stgraber> hallyn: I don't believe there's any snap support in Landscape at this point, some kind of integration between Landscape and the snap enterprise proxy would be nice though
[17:24] <hallyn> wtf is "the snap enterprise proxy" :)
[17:24] <hallyn> forget i asked :)
[17:24] <hallyn> thanks.  so you'd recommend that casual users of landscape slowly migrate back to unattended-upgrades or ansible or something?
[17:28] <stgraber> Landscape is still good to manage your debs, apply updates, ... with snaps it doesn't get quite that much control and unless you're running an enterprise proxy, nothing really has that much control
[17:28] <stgraber> I suppose it could at least support installing and removing snaps, not sure if that's on the roadmap at this point
[17:28] <stgraber> dpb1 might know (I'd have pinged simpoir but he's not in this channel)
[17:35] <dpb1> hallyn: snappy integration will be coming in landscape but is still just in the planning stages, nothing official to announce.
[17:36] <hallyn> dpb1: "coming" as in "perhaps during 2018", or coming as in "we'll put it in plan one day for sure" ?
[17:36] <hallyn> fwiw the only reason i care about snaps is for lxd :)
[17:36] <hallyn> and i don't really want bleeding edge there usually so no urgency even there.  i'm just curious.
[17:39] <dpb1> hallyn: 'tracks' are really the thing you have there, which stgraber knows about.
[17:39] <dpb1> hallyn: and.  the enterprise snap proxy, but it's a commercial offering (as will be the landscape thing).
[17:39] <dpb1> tl;dr: fine-grained control of update frequency and pinning to specific revision numbers is an enterprise feature.
[17:40] <dpb1> hallyn: as for when it will be coming in landscape -- I don't know.
[17:42] <hallyn> thanks dpb1 :)
[18:03] <Delvien> Not sure if this is the right place to ask this... Im running xfs formating on an NVME drive, and when I do an xfs_repair /dev/nvme1n1 I get "Phase 1 - find and verify superblock...
[18:03] <Delvien> bad primary superblock - bad magic number !!!
[18:05] <tomreyn> and your question about this is?
[18:06] <Delvien> How to fix it? Or tell if the drive is bad?
[18:06] <ahasenack> Delvien: shouldn't the device be something like /dev/nvme1n1p1?
[18:06] <ahasenack> with a "pN" at the end, indicating the partition?
[18:07] <ahasenack> Delvien: for example, this is what I have: https://pastebin.ubuntu.com/p/Wy5rbpysHm/
[18:08] <Delvien> I have two nvme on board with this mobo
[18:08] <ahasenack> so?
[18:08] <Delvien> so thats what they were assigned as.
[18:08] <ahasenack> nvme0 and nvme1
[18:08] <ahasenack> n1 is the namespace
[18:08] <ahasenack> and p1 is first partition
[18:08] <ahasenack> and so on
[18:09] <ahasenack> nvme1n1 is the equivalent of a "full disk", like sda
[18:09] <ahasenack> nvme1n1p1 would be sda1 in this example
[18:09] <ahasenack> and so on
[18:11] <Delvien> alright, so
[18:11] <Delvien> xfs_repair /dev/nvme1n1p1  spits out the same thing.
[18:11] <ahasenack> did you format /dev/nvme1n1p1?
[18:11] <Delvien> yes
[18:11] <ahasenack> you have to use the same name for format and verification
[18:12] <RoyK> Delvien: pastebin output of lsblk, please
[18:14] <sarnold> is there a reason why you have seven partitions on tht devcie?
[18:14] <ahasenack> me?
[18:15] <sarnold> ahasenack: oh :) hah
[18:15] <Delvien> Seems formatting a 6th time did the trick.. Holy craperoni
[18:16] <sarnold> ahasenack: actualy now I am kind of curious :) what do you do with seven partitions on an nvme? :)
[18:16] <ahasenack> windows is still there, then I have /boot, /boot/efi, swap and one for linux (crypt)
[18:16] <sarnold> aha!
[18:17] <sarnold> I've got slog on one partition and l2arc on a second partition, and even that feels a bit silly (I should probably just remove the slog, I don't think it ever gets any use)
[18:17] <ahasenack> I did an experiment in another laptop and there I can actually have /boot encrypted (no uefi boot there)
[18:17] <ahasenack> but grub takes about 30s to unlock the luks key
[18:17] <ahasenack> oh, and /boot is on zfs as well
[18:18] <ahasenack> I didn't want to try that on this laptop just yet. That one is my testbed
[18:18] <ahasenack> this one isn't :)
[18:18] <sarnold> ooh /boot on zfs?
[18:18] <sarnold> nice
[18:18] <sarnold> I'm too lazy to even try
[18:18] <ahasenack> it spews out some warnings about unknown compression algorithms and such, but works in the end
[19:38] <tomreyn> teward: i'm a happy user of your ZNC PPA. is there a chance you'll do new builds to handle the CVEs discussed in https://wiki.znc.in/ChangeLog/1.7.1 - or do you have no motivating factor there on your own currently?
[19:51] <tomreyn> sorry, i didnt realize you have a bug tracker for those. :)
[21:03] <jonfatino> anyone know how to launch ubuntu installer over ssh (in a livecd)
[21:03] <jonfatino> like setup or install.bla   with kickstart.conf
[21:03] <jonfatino> and no I don't want to netboot and pass kernel parms.
[21:06] <tomreyn> jonfatino: i haven't done it for a long time, but you should be able to start the alterantive server installer , wait until it's booted to the installer, then press escape and find an option for ssh there.
[21:07] <tomreyn> there may also be a kernel option for this you can pass. the only way to fully automate bringing up the ssh server would be with a preseed file or netboot, i guess.
[21:08] <tomreyn> also please dont cross post
[23:04] <arooni> so my ssh user doesnt always have access to ls directories like /etc/letsencrypt/live ;; how can i do a one off ls in this case
[23:07] <sarnold> if you can't execute ls for some reason but you do have a shell, you can use 'echo *' kind of thing to see files and directories, if the read and execute permissions on the directory allow you
[23:07] <sarnold> try echo /etc/letsencrypt/live/*