[00:49] <kaosine> ok is there any way to reinstall server? I had set it up last night on a old dell and it was working fine for a few hours then nothing. I rebooted it at one point only to have it go black screen after BIOs
[00:49] <kaosine> I've tried rescueing it with the install media I used the first time but I can't figure it out to do that.....
[02:46] <QoQOoO> Hello dose anyone meet locale-gen steal ram problem?
[02:46] <QoQOoO> We use chef-client to provision out machine, but today we found when we execute "locale-gen en_US en_US.UTF-8" command, the command hang and steal many of memory
[03:13] <patdk-lap> yes, running a command that takes a lot of ram, will use a lot of ram
[05:19] <stanford_ai> I'm looking for a GENIUS to work with us on the most promising drone AI company. Do you know any geniuses here?
[05:45] <stanford_ai> is anyone here familiar with ROS/robotics on linux? computer vision, AI, drones, manufacturing, electronics, industrial design, awesomeness, video-making, marketing, lean startup, design-thinking, ethnography, graphic design, or anything related?
[07:58] <cpaelzer> stanford_ai: if your list is meant && and not || you are looking for excessive self-esteem instead of a person right :-) ?
[07:59] <stanford_ai> lol
[08:38] <lordievader> Good morning.
[09:24] <Village> Good time,
[09:25] <Village> libreadline5-dev packege not in apt-get base, what alternative?
[09:25] <Village> E: Package 'libreadline5-dev' has no installation candidate
[09:27] <OerHeks> !info libreadline
[09:27] <OerHeks> !find libreadline
[09:27] <OerHeks> !find libreadline-dev
[09:27] <OerHeks> libreadline-dev (source: readline): GNU readline and history libraries, development files. In component main, is optional. Version 7.0-0ubuntu2 (yakkety)
[09:28] <OerHeks> seems we are at 7 now, Village
[09:28] <Village> i see, OerHeks, Thank You
[09:29] <lordievader> !info libreadline7-dev
[09:31] <OerHeks> strange, ey?
[09:32] <OerHeks> that points to libreadline-dev itself
[09:32] <OerHeks> at least info libreadline7-dbg is available.
[09:34] <Village> yes i will try libreadline-dev
[09:34] <Village> one people recomendet it from all packager
[09:34] <Village> packages*
[10:31] <jamespage> coreycb, morning
[10:31] <coreycb> jamespage, morning!
[14:42] <rbasak> nacc: o/ for when you get in, any chance you have some time to spare with me on letsencrypt/certbot please?
[15:09] <massprog> hello I want to use of python instead of php in vps what shoud i do?
[16:52] <nacc> rbasak: sure
[17:23] <kaosine> "That is our last such motherboard and I'm not sure if it is ready to ship. Just checking, do you need the exact model or something similar?" *sigh*
[17:24] <kaosine> whoops
[17:24] <kaosine> wrong channel
[18:00] <xpistos> Hey all. I am trying to write a simple bash script that will call a few other scripts. Those scripts have input prompts with default values. I just want the scripts to accept all the defaults. How can I do that? They are not all yes, but some are locations and a few are yeses?
[18:01] <xpistos> Is there some arguement I can pass into the ./scriptname/sh that will accept the defaults
[18:02] <nacc> xpistos: is there a default value that will cause the scripts to work automatically?
[18:02] <nacc> xpistos: you may want to look at the `yes` utility
[18:03] <xpistos> nacc: they defaults are always different, but the user only needs to hit enter to accept whatever the defaults are. sometimes they are "/opt/program/folder" and other times they are "yes"
[18:04] <nacc> hrm, `yes '' | /other/script` may work then
[18:04] <nacc> not sure if yes can take an empty string or not
[18:04] <xpistos> let me look into it
[18:04] <nacc> xpistos: alternatively, you can use expect for it
[18:07] <xpistos> nacc: I am trying to use "-d default" as an argument to one of the complicate scripts now.
[18:08] <nacc> xpistos: -d as a flag to what?
[18:09] <xpistos> ./vmware.pl -d default
[18:09] <nacc> xpistos: oh ok, i'd have no idea about that
[20:59] <rbasak> nacc: got time now, or in half an hour?
[21:00] <nacc> rbasak: now is fine
[21:00] <rbasak> Two minutes and I'll start a hangout.
[21:00] <nacc> k
[21:51] <axisys> server rebooted and only showing memtest+ in the grub.. need help to fix the grub..
[21:52] <axisys> I tried to boot from live CD and mounted the /dev/md1 into /mnt and then grub-install --root-directory=/mnt /dev/sda and then same for /dev/sdb and then reboot.. still showing only memtest+ in the grub
[21:53] <axisys> # mdadm --assemble --scan
[21:53] <axisys> mdadm: /dev/md1 has been started with 2 drives.
[21:53] <axisys> # mount /dev/md1 /mnt
[21:54] <axisys> and then the rest
[21:55] <axisys> looks like there are more steps
[21:55] <axisys> http://howtoubuntu.org/how-to-repair-restore-reinstall-grub-2-with-a-ubuntu-live-cd
[21:55] <axisys> all these are needed?
[21:56] <axisys> I did not run the update-grub
[21:56] <axisys> is that needed after the grub-install?
[21:57] <axisys> right now I am at grub> prompt
[21:57] <axisys> is there something I can do from here to fix it?
[22:06] <axisys> looks like someone removed the kernel
[22:06] <axisys> nice!
[22:08] <compdoc> you dont need a kernel
[22:08] <patdk-lap> kernel is just deadbeat software
[22:09] <patdk-lap> you need to boot fomr a live cd
[22:09] <compdoc> fake programming
[22:09] <patdk-lap> and run update-grub
[22:09] <patdk-lap> and make sure it locates something to boot
[22:11] <axisys> so do the chroot first and then update-grub ?
[22:11] <axisys> patdk-lap: ^
[22:12] <patdk-lap> mount root, do your bind mounts, chroot into it, then run that yes
[22:12] <axisys> patdk-lap: like this url http://howtoubuntu.org/how-to-repair-restore-reinstall-grub-2-with-a-ubuntu-live-cd .. it is doing a lot more
[22:13] <patdk-lap> no, it's doing exactly what I said
[22:13] <axisys> patdk-lap: possible to send me a cheatsheet/link?
[22:13] <patdk-lap> you just posted one
[22:13] <axisys> or a pastebin?
[22:14] <axisys> patdk-lap: ah ok.. I did not have bind in it
[22:14] <patdk-lap> heh?
[22:14] <patdk-lap> why would you need bind?
[22:14] <axisys> i meant bind mounts
[22:14] <patdk-lap> hmm, they are on that page you just posted
[22:14] <axisys> patdk-lap: ah ok.. got it.. thank you
[22:15] <axisys> heading back to the lab
[22:32] <axisys> patdk-lap: if I chroot to /mnt update-grub fails since the OS probably has older version? OS is 14.04 and live cd is 16.04
[22:32] <axisys> how do I run update-grub with root dir as /mnt ?
[22:33] <patdk-lap> by following the instructions on that url you posted
[22:33] <patdk-lap> that is the holw point of all those commands
[22:34] <axisys> patdk-lap: that one did not bind /usr
[22:34] <patdk-lap> if you have more than a single mount, you will have to mount them all
[22:35] <patdk-lap> nothing will be specific to your exact install
[22:35] <patdk-lap> you need to mount everything you normally need, /, /boot, /usr, /var, ...
[22:35] <patdk-lap> before you do the bind mounts
[22:35] <patdk-lap> so mount xxxx /mnt
[22:36] <patdk-lap> mount xxxx /mnt/usr
[22:36] <patdk-lap> mount xxxx /mnt/boot
[22:36] <patdk-lap> then your binds, mount --bind ....
[22:36] <axisys> ah..
[22:37] <axisys> grub-install worked from livecd since I can point to /mnt as root dir
[22:37] <axisys> may be I could use update-grub of livecd if I can point to /mnt as root dir
[22:38] <axisys> how do I read the disks fstab?
[22:38] <axisys> mount / to /mnt ?
[22:40] <axisys> ignore that question
[22:40] <axisys>  /mnt is root .. doh
[22:41] <axisys> so /mnt/etc/fstab does not have anything but / and swap
[22:41] <axisys> root@ubuntu:/mnt/usr/sbin# ls -al update-grub
[22:41] <axisys> -rwxr-xr-x 1 root root 64 Mar 15  2016 update-grub
[22:41] <axisys> root@ubuntu:~# chroot /mnt
[22:42] <axisys> root@ubuntu:/# update-grub
[22:42] <axisys> /usr/sbin/grub-probe: error while loading shared libraries: libdevmapper.so.1.02.1: cannot open shared object file: No such file or directory
[22:42] <patdk-lap> didn't mount everything you needed?
[22:42] <axisys> only / and swap needed per fstab
[22:43] <axisys> and they are mounted
[22:43] <patdk-lap> no idea why that is missing
[22:43] <axisys> http://dpaste.com/347CS45
[22:44] <patdk-lap> ok, that is confusing as crap
[22:44] <patdk-lap> your mounted it inside itself like 4 times?
[22:44] <patdk-lap> confusing
[22:44] <axisys> sorry I was following his url where he did that
[22:44] <patdk-lap> he didn't do chroot /mnt >1 time
[22:45] <patdk-lap> I don't think I should see grub-install or update-grubs cause those would be in a new shell
[22:46] <patdk-lap> I think you should reboot and try again
[22:46] <patdk-lap> mdadm assemble
[22:46] <axisys> ok
[22:46] <patdk-lap> mount /dev/md1 /mnt
[22:46] <patdk-lap> then start the bind mounts, chroot, grub stuff
[22:46] <axisys> rebooting now
[22:47] <axisys> hmm I have exit after each chroot
[22:47] <axisys> did not know in history
[22:50] <axisys> bind mounts is line 7 thru 10 .. correct? since I dont have any special partitions?
[22:50] <patdk-lap> yes, no need for 6
[22:52] <axisys> installing mdadm on livecd
[22:54] <axisys> all 4 binding done..
[22:55] <axisys> grub-install --root-directory=/mnt /dev/sda will work.. or should I  do chroot and run it without root dir option?
[22:56] <axisys> and same for /dev/sdb
[22:57] <axisys> with chroot /mnt, grub-install does not work
[22:57] <axisys> program not found
[22:57] <patdk-lap> why did you do that?
[22:57] <patdk-lap> you should follow the url, not modify and insert other things
[22:57] <axisys> ok exited out of chroot
[22:57] <patdk-lap> why?
[22:58] <patdk-lap> you must be in the chroot
[22:58] <patdk-lap> what does, grub-install /dev/sda, say?
[22:58] <patdk-lap> exiting out will NOT fix your issue
[22:58] <patdk-lap> it just means your issue is much worse than just grub
[22:58] <axisys> http://dpaste.com/3GBSR0F
[22:59] <patdk-lap> ok, ignore that for now
[22:59] <patdk-lap> what about update-grub
[23:00] <patdk-lap> and what does, dpkg -l | grep grub, say?
[23:00] <axisys> http://dpaste.com/1EY73JK
[23:00] <patdk-lap> ok, so grub doesn't appear to be installed at all, or you didn't mount stuff right somehow
[23:00] <axisys> http://dpaste.com/18XJX5H
[23:01] <patdk-lap> that says grub was uninstalled
[23:01] <patdk-lap> is networking setup on this live boot?
[23:01] <axisys> yes
[23:01] <patdk-lap> apt-get install grub-pc then
[23:02] <axisys> just so you know, I am still on chrooted env
[23:02] <patdk-lap> as you should be, I never said to exit
[23:02] <patdk-lap> we aren't attempting to fix the live install :)
[23:03] <axisys> http://dpaste.com/305X210
[23:03] <patdk-lap> so networking was not setup and working
[23:03] <patdk-lap> exit out and get networking setup
[23:03] <patdk-lap> oh wait, you probably just need to get resolv.conf fixed up in the chroot
[23:04] <sarnold> or /etc/hosts the thing
[23:04] <patdk-lap> ya, add us.archive.ubuntu.com to /etc/hosts in the chroot
[23:05] <sarnold> 91.189.91.26 and 91.189.91.23
[23:06] <axisys> that is fixed with hosts file.. thanks guys! but apt still has issue
[23:06] <axisys> http://dpaste.com/0N2KK6Q
[23:06] <patdk-lap> apt-get update
[23:07] <patdk-lap> then attempt again
[23:07] <patdk-lap> your local apt cache must be way out of date
[23:07] <patdk-lap> atleast I don't remember grub being updated recently
[23:08] <axisys> ok.. updating it.. need security.ubuntu.com also
[23:08] <sarnold> the same two should work
[23:09] <sarnold> (there's way more but .. meh. you just need this up and running, right? :)
[23:09] <axisys> sarnold: right :-)
[23:09] <patdk-lap> sarnold, I finally upgraded all my letsencrypt stuff to dehydrated :)
[23:09] <patdk-lap> life is so much nicer now
[23:09] <sarnold> patdk-lap: I hadn't heard of that yet..
[23:10] <patdk-lap> it's very simple
[23:10] <sarnold> I like simple
[23:10] <patdk-lap> but has nice hook calls, so I have it hooking to generate my pinning, tlsa records, and cert rotation
[23:11] <patdk-lap> so much more reliable than certbot
[23:11] <patdk-lap> hadn't done it yet, cause certbot was *working*
[23:11] <axisys> apt-get install grub-pc is success.
[23:11] <patdk-lap> but it died on me horrible 2 weeks ago, just found the time to fix it, before they expired in 2 more weeks
[23:11] <patdk-lap> :)
[23:11] <axisys> root@ubuntu:/# update-grub
[23:11] <axisys> Generating grub configuration file ...
[23:11] <axisys> grub-probe: error: disk `md1' not found.
[23:11] <patdk-lap> now to do grub-install and update-grub
[23:12] <patdk-lap> odd
[23:12] <patdk-lap> mdadm installed?
[23:12] <axisys> nawp :-)
[23:12] <patdk-lap> I wonder what happened to uninstall all this stuff
[23:12] <patdk-lap> dpkg -l | grep ^rc
[23:13] <patdk-lap> best review what got removed :)
[23:13] <axisys> previous sysadmin is in a "shock" when I asked
[23:13] <axisys> mdadm installed now
[23:13] <patdk-lap> mdadm by itself I don't think should have caused that error
[23:13] <axisys> --assemble --scan ?
[23:13] <patdk-lap> no
[23:13] <axisys> ok
[23:14] <patdk-lap> outside the chroot counts for that
[23:14] <patdk-lap> cause of the bind mounts
[23:14] <patdk-lap> why I suspect something else
[23:14] <patdk-lap> but I just have no idea yet, what
[23:14] <axisys> root@ubuntu:/# grub-install /dev/sda
[23:14] <axisys> Installing for i386-pc platform.
[23:14] <axisys> Installation finished. No error reported.
[23:14] <patdk-lap> ah, so it must have wanted mdadm
[23:14] <patdk-lap> for some reason
[23:15] <axisys> root@ubuntu:/# grub-install /dev/sdb
[23:15] <axisys> Installing for i386-pc platform.
[23:15] <axisys> Installation finished. No error reported.
[23:15] <patdk-lap> I would update initrd files
[23:15] <patdk-lap> lets review that dpkg -l | grep ^rc, though
[23:15] <axisys>  /boot has almost nothing
[23:15] <patdk-lap> if all this stuff got removed, and it's missing from initramfs too, it won't boot even if we fix grub
[23:15] <axisys> root@ubuntu:/boot# ls
[23:15] <axisys> grub  memtest86+.bin  memtest86+.elf  memtest86+_multiboot.bin
[23:15] <patdk-lap> so no kernels either
[23:15] <patdk-lap> ok, no need to fix initramfs then
[23:16] <sarnold> man what happened to this poor system?
[23:16] <axisys> patdk-lap: like I mentioned earlier..
[23:16] <patdk-lap> are we sure we dont' need to mount /boot?
[23:16] <patdk-lap> from somewhere?
[23:16] <axisys> sarnold: previous mediocore sysadmin's blessing
[23:17] <patdk-lap> what does blkid show?
[23:17] <patdk-lap> I just want to be very careful we aren't *fixing* the wrong thing
[23:17] <axisys> http://dpaste.com/1Y3CCHX
[23:17] <patdk-lap> ya, a second raid
[23:18] <patdk-lap> likely swap you said?
[23:18] <patdk-lap> is swap another md?
[23:18] <axisys> patdk-lap: yes md0
[23:18] <patdk-lap> ok
[23:19] <axisys> # swap was on /dev/md0 during installation
[23:19] <axisys> UUID=859bf518-f6bd-4d27-ae13-6c895b40a857 none            swap    sw              0       0
[23:19] <patdk-lap> guess this stuff did get wiped
[23:19] <patdk-lap> lets get that dpkg listing
[23:19] <axisys> with the grep?
[23:19] <patdk-lap> ya
[23:19] <patdk-lap> grep ^rc
[23:19] <patdk-lap> it will show a bunch of stuffwe don't care about
[23:20] <patdk-lap> but lets see what else is missing that will cause boot failures
[23:22] <axisys> its looooong output.. hard to catch from console
[23:22] <axisys> I will try
[23:23] <axisys> 229  packages
[23:23] <patdk-lap> ok, try this
[23:24] <axisys> dpkg -l | grep ^rc > /tmp/out
[23:24] <patdk-lap> dpkg -l | grep ^rc | grep -v linux
[23:24] <axisys> wc -l /tmp/out
[23:24] <axisys> 229 /tmp/out
[23:24] <patdk-lap> or, grep -v linux /tmp/out
[23:24] <axisys> 200
[23:24] <patdk-lap> heh
[23:25] <patdk-lap> exit the chroot, and try using pastbinit
[23:26] <axisys> http://paste.ubuntu.com/24061714/
[23:27] <patdk-lap> that doesn't look good
[23:27] <patdk-lap> what does this machine do? when it *works*
[23:29] <patdk-lap> actually, a lot of that seems to be from a 12.04 -> 14.04 upgrade
[23:29] <axisys> its a xymon server.. monitors
[23:29] <axisys> right..
[23:29] <axisys> I think they broke during their upgrade
[23:30] <patdk-lap> dpkg -l | grep xymon
[23:30] <patdk-lap> that shows an ii  xymon line right?
[23:30] <patdk-lap> version 4.3.7 it should be
[23:30] <axisys> line 200
[23:30] <patdk-lap> no, that is an rc line, not ii
[23:30] <axisys> ah
[23:31] <axisys> root@ubuntu:/# dpkg -l | grep xymon
[23:31] <axisys> rc  xymon                                      4.3.0~beta2.dfsg-5                              amd64        monitoring system for systems, networks and applications
[23:31] <patdk-lap> so xymon isn't installed anymore either
[23:31] <axisys> xymon is compiled most likely
[23:31] <patdk-lap> hmm, ok, but lets check this
[23:32] <patdk-lap> is there anything in /etc/apt/sources.list.d
[23:32] <axisys> # ls
[23:32] <axisys> percona.list		    snabb-downtimed-lucid.list.distUpgrade
[23:32] <axisys> percona.list.distUpgrade    zabbix.list
[23:32] <axisys> snabb-downtimed-lucid.list  zabbix.list.distUpgrade
[23:32] <patdk-lap> ok, that is probably what did it
[23:33] <axisys> its odd I could update /etc/hosts but not /etc/resolv.conf
[23:33] <patdk-lap> well, /etc/resolv.conf is a symlink normally these days
[23:33] <patdk-lap> so it's attempting to update the missing file it points to
[23:33] <axisys> /etc/resolv.conf -> ../run/resolvconf/resolv.conf
[23:33] <patdk-lap> ya, you need to create that file
[23:34] <patdk-lap> and directory likely also
[23:34] <marahin> Hey. I'm running Rails on rbenv/rvm (unsure right now), nginx, php5-fpm (wordpress sites), nodejs, go and some virtualization through virt-manager on my Ubuntu 14.04 server.
[23:34] <axisys> resolv working now
[23:35] <marahin> I'm thinking about dist-upgrading. How destructive can it be? I'm a complete newbie, not a experienced admin.
[23:35] <patdk-lap> axisys, try this
[23:36] <pmatulis> marahin, i wouldn't call upgrading "destructive"
[23:36] <patdk-lap> apt-get install ubuntu-minimal
[23:36] <marahin> pmatulis by "destructive" I mean: what might stop working on a machine that runs basic web stuff + teamspeak? :)
[23:36] <pmatulis> marahin, have you installed any software outside the official ubuntu arhives?
[23:36] <patdk-lap> marahin, nothing
[23:36] <axisys> patdk-lap: done
[23:36] <marahin> pmatulis: as far as I can reach with my memory: none that I use currently.
[23:36] <patdk-lap> the only time an upgrade or dist-upgrade would break something is, a software update that needs a config file change
[23:37] <patdk-lap> unlikely, but happens sometimes
[23:37] <marahin> well, maybe phpmyadmin?
[23:37] <marahin> allright, you convinced me! :-)
[23:37] <patdk-lap> axisys, ok, and what is the count on that dpkg -l | grep ^rc | wc -l
[23:37] <marahin> "#yolo"
[23:37] <pmatulis> marahin, do make backups of your data however
[23:37] <axisys> patdk-lap: 226
[23:37] <marahin> pmatulis I can always rescueboot with another image on it.
[23:37] <patdk-lap> the same?
[23:37] <axisys> patdk-lap: nawp
[23:37] <patdk-lap> down by 3 :(
[23:38] <axisys> is it.. ah.. oh yeah there was a grep -v
[23:38] <patdk-lap> how about
[23:38] <patdk-lap> dpkg -l | grep ureadahead
[23:38] <axisys> ii
[23:38] <patdk-lap> good
[23:39] <axisys> 0.100.0-16
[23:39] <patdk-lap> so lets get you a kernel
[23:39] <axisys> patdk-lap: please!!
[23:39] <axisys> :-)
[23:39] <patdk-lap> this a physical machine?
[23:39] <axisys> patdk-lap: yes
[23:40] <patdk-lap> apt-get install linux-generic
[23:40] <patdk-lap> maybe also, apt-get install linux-firmware
[23:41] <axisys> getting it still...
[23:42] <patdk-lap> ya, it will take a little bit
[23:42] <marahin> Pardon me, but: what about do-release-upgrade? Can this mess things up?
[23:42] <axisys> patdk-lap: so far so good :-)
[23:42] <patdk-lap> marahin, that WILL cause you issues
[23:43] <patdk-lap> do-release-upgrade will cause breakage
[23:43] <patdk-lap> sometimes minimal, sometimes major, it depends on the software you use
[23:43] <patdk-lap> cause that will do major upgrades
[23:43] <marahin> uh-huh.
[23:43] <marahin> I see.
[23:43] <marahin> well I guess I'll pass. I am going to swap the machines anyways soon, and then contenerize/isolate by virtualization the services
[23:43] <marahin> patdk-lap thank you!
[23:44] <axisys> patdk-lap: ok installed linux-generic and linux-firmware
[23:44] <patdk-lap> update-grub
[23:44] <axisys> sweet.. looks good
[23:44] <sarnold> marahin: apache drastically changed authentication and authorization configuration between 2.2 and 2.4; if you've got any apache in your stack, take a look at their docs first
[23:44] <patdk-lap> ok, dunoo what else to fix now
[23:44] <patdk-lap> have to reboot and test it :)
[23:44] <patdk-lap> see what works and what doesn't
[23:44] <axisys> patdk-lap: crossing my fingers..
[23:45] <marahin> sarnold nah I'll pass do-release-upgrade; I'm going to swap the physical machine anyways. And I'm using NGINX :)
[23:45] <patdk-lap> marahin, it mainly comes into play in how many files you have edited, configuration changes you have made
[23:45] <axisys> can I eject from here? or do I need to go back to the lab and eject manually?
[23:45] <patdk-lap> the less you do, the *easier* do-release-upgrade is
[23:45] <axisys> patdk-lap: ^
[23:45] <patdk-lap> axisys, exit the chroot
[23:45] <patdk-lap> and just type in reboot
[23:46] <axisys> hopefully it wont boot from cdrom
[23:46] <axisys> Please remove the installation medium, then press ENTER:
[23:46] <patdk-lap> it likely will, unless you remove it
[23:46] <sarnold> try 'eject' first
[23:46] <axisys> ah.. cd usually gets kicked out by now
[23:46] <patdk-lap> I always just remove it while at the bios screen
[23:46] <sarnold> maybe the tray will suck it back in ..
[23:47] <axisys> sarnold: ok.. I will try from downstairs then
[23:51] <patdk-lap> must locate sugar
[23:51] <axisys> took the cd out.. oh yeah I need some sugar too
[23:52] <axisys> rebooting with a kernel.. eehaa!
[23:52] <axisys> doing fsck
[23:52] <sarnold> where's those girl scouts need more cookies
[23:52] <axisys> lol
[23:53] <axisys> we have potbelly here
[23:53] <sarnold> oh yeah. I just polished off a wreck.
[23:53] <axisys> their cookies are really good.. and probably not healthy
[23:59] <patdk-lap> out of sugar here :(
[23:59] <patdk-lap> found italian ice though