[00:00] <TAFB> okies, here it goes :)
[00:00] <sarnold> I suspect these are choices from your vps provider
[00:00] <tarpman> eh, hoster-provided images tend to be pretty bad...
[00:00] <tarpman> about the same as OEM-provided windows images, from my perspective :)
[00:00] <sarnold> ouch man that's a low blow :)
[00:00] <tarpman> :D
[00:00] <TAFB> says it's removing 6 apache packages
[00:01] <patdk-lap> heh, first packages I purge are os-prober and mlocate
[00:01] <TAFB> is os-prober the thing that keeps deleteing my ffmpeg?!?
[00:01] <sarnold> patdk-lap: oh is os-prober ther thing that craps all over dmesg? :)
[00:01] <patdk-lap> well, craps all over grub
[00:02] <patdk-lap> it totally screwed something up
[00:02] <patdk-lap> think it was my glusterfs testing
[00:02] <TAFB> http://167.114.135.106/
[00:02] <TAFB> holy crap, works!
[00:03] <TAFB> now just need to get php working :(
[00:04] <TAFB> sudo add-apt-repository ppa:ondrej/php5-5.6
[00:06] <TAFB> Ok, wtf?? When I go "apt-get install php5" it says "The following NEW packages will be installed:   apache2 apache2-bin apache2-data apache2-utils"
[00:06] <TAFB> why would I want apache with php??! :(
[00:07] <patdk-lap> cause the default is mod-php
[00:07] <patdk-lap> install like, php5-fpm
[00:07] <patdk-lap> as that is what nginx really wants
[00:07] <TAFB> ahhh, nice :)
[00:08] <TAFB> PHP 5.6.20-1+deb.sury.org~trusty+1 (cli)
[00:08] <TAFB> new enuff?
[00:09] <patdk-lap> na
[00:10] <patdk-lap> should install php 7
[00:10] <TAFB> damn, how could I make it do that? :(
[00:10] <patdk-lap> no idea :)
[00:10] <patdk-lap> but not sure how much stuff supports php 7
[00:10] <patdk-lap> not much stuff I use atleast does
[00:10] <TAFB> my script will, it's super simple
[00:11] <sarnold> i'd skip php7 not everything supports it yet
[00:11] <sarnold> if this were a long-lived server it might be worth investigating but if it's getting torn down again tomorrow afternoon what's the point? :)
[00:11] <TAFB> i thought I could upgrade to 16.04?!
[00:12] <sarnold> it'll probably be a pain in the ass to upgrade to 16.04 with all those extra ppas installed
[00:12] <sarnold> you'd want to purge them first
[00:12] <TAFB> lol :(
[00:12] <TAFB> ok, so stick with PHP 5.6.20-1+deb.sury.org~trusty+1 (cli) then?!
[00:12] <sarnold> sure
[00:13] <TAFB> okies. re-installing :)
[00:21]  * patdk-lap wonders how well 16.04 has been testing on a 2.6 kernel :)
[00:21] <sarnold> probably "none at all" given systemd's list of requirements
[00:25] <TAFB> i enabled php-fpm in default.conf and added index.php to the nginx.conf, I just get "an error occured" now :( http://167.114.135.106/
[00:25] <TAFB> default.conf: http://pastie.org/10806168
[00:25] <TAFB> nginx.conf: http://pastie.org/10806169
[00:26] <sarnold> error logs?
[00:28] <TAFB> 2016/04/20 20:27:39 [error] 28277#28277: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 104.158.123.204, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "167.114.135.106"
[00:29] <sarnold> alright that's good progress, is fpm listening on 127.0.0.1:9000?
[00:29] <TAFB> sarnold: how do I tell that?
[00:29] <sarnold> netstat -tlnp | grep 9000
[00:30] <TAFB> ^^ empty
[00:30] <sarnold> try netstat -alnp | grep fpm -- see where it -is- listening, if it's running..
[00:31] <TAFB> http://pastie.org/10806173
[00:31] <sarnold> TAFB: nice, uncomment the unix:/... socket line and fix the path to match, and restart nginx
[00:33] <TAFB> how do I tell where the path to php is?
[00:34] <TAFB> unix:/var/run/php-fpm/php-fpm.sock failed (2: No such file or directory)
[00:34] <patdk-lap> php-fpm pool config
[00:34] <sarnold> TAFB: it's line 2 of http://pastie.org/10806173
[00:35] <TAFB> nice. getting closer: unix:/var/run/php5-fpm.sock failed (13: Permission denied)
[00:39] <sarnold> TAFB: check ls -l /var/run/php5-fpm.sock -- what group owns that file? you can probably tell nginx to run with that group
[00:39] <TAFB> srw-rw---- 1 www-data www-data 0 Apr 20 20:23 /var/run/php5-fpm.sock
[00:39] <patdk-lap> easier to just modify php to have it set correctly
[00:40] <patdk-lap> edit the file in /etc/php5-fpm.d/www.conf likely
[00:40] <sarnold> hunh i'm surprised that failed
[00:41] <TAFB> this one? /etc/php5/fpm/php-fpm.conf?
[00:41] <patdk-lap> no
[00:41] <patdk-lap> /etc/php5/fpm/pool.d/*.conf
[00:42] <patdk-lap> I've been in rhel land too long lately
[00:42] <TAFB> listen.owner = www-data
[00:45] <TAFB> it says to make sure execute permission on that user on the file?
[00:47] <sarnold> on the directories that contain the file?
[00:47] <TAFB> not sure, just searching google for "permission denied php"
[00:48] <sarnold> oh don't do that, that'll lead to nutters who solve everything with chmod 777 rather than understand the problem at hand :)
[00:48] <TAFB> also read to uncomment "listen.mode = 0660" in the www.conf
[00:49] <patdk-lap> 777 solves everything
[00:49] <patdk-lap> it also invites *guests* to help solve things
[00:50] <TAFB> uncommenting "listen.mode = 0660" didn't fix the permission problem
[00:54] <patdk-lap> apparmor?
[00:54] <patdk-lap> type in, dmesg
[00:54] <TAFB> dmesg said nothing
[00:55] <patdk-lap> what user is nginx running as?
[00:55] <TAFB> how do I check that?
[00:55] <sarnold> I'd check with ps auxw | grep nginx
[00:56] <TAFB> http://pastie.org/10806183
[00:56] <sarnold> full detailswould be in /proc/<pid>/status but ps auxw should show user ..
[00:58] <patdk-lap> why is it running as nginx? :)
[00:58] <patdk-lap> change php to run as nginx
[00:58] <TAFB> no clue, just apt-get installed it :)
[00:59] <sarnold> changing the nginx configuration to use "user nginx www-data" ought to work too
[00:59] <patdk-lap> well, in that same php file
[00:59] <patdk-lap> just change the user/group listen-user/group lines
[00:59] <patdk-lap> sarnold, assuming he has a www-data user
[00:59] <patdk-lap> he isn't using the ubuntu package
[00:59] <patdk-lap> it might not exist
[00:59] <sarnold> patdk-lap: he does, it owns the socket :)
[00:59] <patdk-lap> ok, hope it doesn't screw nginx finding it's own modules or someting :)
[01:00] <TAFB> k. done. change all www-data to nginx, now getting this: *11 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 104.158.123.204, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "167.114.135.106"
[01:01] <sarnold> great now you're just stuck with php problems :D
[01:01] <TAFB> http://167.114.135.106/
[01:03] <patdk-lap> or nginx -> php problems
[01:03] <TAFB> i tell you it's like this every time for me :(
[01:06] <TAFB> someone needs to write install script for php. check what program is on port 80, check what user it's running as, self config, check permissions, set up nginx.conf, etc. etc. :(
[01:12] <TAFB> "You need to ensure you have +x on all of the directories in the path leading to the site's root - so /home, /home/noisepages and /home/noisepages/www
[01:12] <TAFB> checking
[01:13] <TAFB> all had +x already :(
=== chuck__ is now known as zul
[01:17] <TAFB> looks like something wrong with this line: "fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;"
[01:19] <TAFB> "NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini"?
[01:21] <TAFB> was set to 1, restarting php and trying
[01:21] <TAFB> changed the error a bit: 2016/04/20 21:20:55 [error] 28635#28635: *4 FastCGI sent in stderr: "Unable to open primary script: /etc/nginx/html/index.php (No such file or directory)" while reading response header from upstream, client: 104.158.123.204, server: localhost, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "167.114.135.106"
[01:22] <TAFB> the path is completely wrong
[01:22] <TAFB> that .php is in /usr/share/nginx/html :(
[01:23] <TAFB> how do I point it to the right place?
[01:59] <TAFB> IT WORKS using the default.conf from here: http://pastebin.com/Y2CaqNeZ
[02:00] <sarnold> \o/
[02:01] <TAFB> ok, now to enable directly listing and install h5ai!
[02:05] <Emmanuel_Chanel> Hello! I'm going to upgrade my Ubuntu Server from 14.04 LTS to 16.04 LTS when it's released. It's not released yet?
[02:06] <sarnold> Emmanuel_Chanel: it should be released tomorrow
[02:07] <Emmanuel_Chanel> On UTC, it's today. On JST, too. So I wondered.
[02:07] <Emmanuel_Chanel> sarnold: thx for answering me.
[02:08] <sarnold> Emmanuel_Chanel: ah then "later today" :) hehehe
[02:18] <patdk-lap> ya, something around 8pm or so your time
=== profall_ is now known as profall
=== j^2_ is now known as j^2
[06:27] <cliffer> is there a dovecot line needed in /etc/postfix/master.cf on using postfix iwth dovecot? i cant find any mention in the docs
[06:28] <qman__> if you want dovecot sasl auth, you need several
[06:29] <qman__> oh, in main.cf, not master.cf
[06:29] <cliffer> a line starting with dovecot
[06:29] <qman__> I can check if mine has one
[06:30] <qman__> no, mine doesn't have one
[06:33] <cliffer> i get the following errors related to dovecot: "qmgr: warning: connect to transport private/dovecot: No such file or directory" and "systemd: dovecot.service: PID file /var/run/dovecot/master.pid not readable (yet?) after start: No such file or directory"
[06:33] <cliffer> is it right that "ls /var/run/dovecot/master.pid  -al" is owned by root?
[06:36] <cliffer> qman__: thx btw :)
[06:37] <qman__> my master.pid is root.root
[06:37] <qman__> and the first error appears to be related to the unix socket location
[06:38] <qman__> make sure postfix and dovecot have the same thing specified
[06:38] <qman__> and that the directory exists
[06:38] <qman__> mine's /var/spool/postfix/private/auth
[06:39] <qman__> postfix's config line only uses private/auth, the rest is implied for it, but dovecot uses the whole path
[06:41] <cliffer> both correctly set, dir exists and is owned by postfix:postfix
[06:42] <cliffer> but private /var/spool/postfix/private/dovecot does not exists
[06:42] <qman__> ok, dovecot might not be starting correctly then, it should be creating it
[06:43] <qman__> I'm not exactly an expert on it, just what I ran into making mine work
[06:46] <cliffer> dovestart is started, the onyl message in the logs is the missing master.pid
[06:53] <contumax> hi, any experience with Cannot make directory '/var/run/screen': Permission denied ?
[06:54] <SierraKomodo> contumax: What exactly are you doing that's bringing up that error?
[06:54] <contumax> trying to run screen
[06:54] <contumax> ubuntu 14.04 server
[06:55] <contumax> furthermore this issue started with another one at same time
[06:55] <contumax> there is no tty after boot, just black screen, but I'm able to ssh to the server
[07:23] <lynxman> aah exciting LTS release day :)
=== athairus is now known as afkthairus
[09:08] <Dieselhonky> anyone feeling helpful and polite?
[09:09] <cpaelzer> Dieselhonky: sure - feelings are easy - BEING helpful and polite is the hard part
[09:10] <Dieselhonky> just asked for help in the #ubuntu support channel and those guys tore me apart and werent helpful.  they just talked crap to me.
[09:10] <Dieselhonky> ok so here is my question
[09:12] <Dieselhonky> The unetbootin website says that you can make a bootable USB instance on the main hard drive to boot from.  I dont have a USB stick and only have external hard drives over 250GB.  i want to install ubuntu.  tried to do it that way and it didnt work.
[09:13] <Dieselhonky> i dodnt want to dual boot.  i want windows gone.
[09:14] <rbasak> External USB drives are basically identical to USB sticks as far as the system is concerned. So whatever instructions you follow, when you see "USB stick" just think "my external USB drive" instead.
[09:15] <cpaelzer> rbasak: exactly
[09:15] <Dieselhonky> correct.  but my computer will not allow me to format any of my external HDD devices to FAT32.  thats the issue there
[09:15] <Dieselhonky> says they are too big
[09:15] <cpaelzer> Dieselhonky: and be careful - unetbootin is about creating an install media onto e.g. an usb stick / or disk in your case
[09:16] <cpaelzer> Dieselhonky: that is what the other channel tried to refer to I think
[09:16] <cpaelzer> Dieselhonky: so this won't "install" Ubuntu on it - instead it would convert your USB drive so you are able to install FROM it
[09:16] <cpaelzer> wasn't there wubi or so in the past
[09:16] <Dieselhonky> ok.  so no linux until i can oer a live CD.
[09:16] <rbasak> I don't really know how Windows does it. In principle there is no need to create a filesystem on your "USB stick" first. Perhaps that's a requirement on Windows though, I don't know.
[09:16] <Dieselhonky> cpaelzer exactly thats what i want to do
[09:17] <Dieselhonky> wubi only installs a dual boot as far as i know
[09:18] <cpaelzer> Dieselhonky: well the windows would be sad being wiped away while running :-) so yes probably only dual boot
[09:19] <Dieselhonky> haha.  windows needs to be sad
[09:19] <cpaelzer> I look for alternatives, ... do you have a smartphone with some space around ?
[09:19] <Dieselhonky> i am in the process of converting all of my pc's.  just starting with a laptop to see how it goes.
[09:20] <Dieselhonky> cpaelzer, yes i do have a smartphone with free space
[09:20] <cpaelzer> second please, I need to find how that app was called ...
[09:21] <cpaelzer> Dieselhonky: could you check if this would be an option for you https://www.maketecheasier.com/install-linux-distro-from-android/
[09:21] <cpaelzer> Dieselhonky: I neverused it but a friend of mine recommended it once
[09:21] <hateball> DriveDroid works, if you have android
[09:22] <hateball> for booting ISOs, that is
[09:22] <cpaelzer> hateball: that is what I just linked - glad you agree
[09:22]  * hateball hopes he read the above conversation right
[09:22] <Dieselhonky> hateball, cpaelzer, awesome!!! finally an option.  you guys rock.  Let me go check it out
[09:22] <hateball> cpaelzer: :)
[09:22] <Dieselhonky> thanks for going eazy on a noob.
[09:23] <cpaelzer> Dieselhonky: don't hurt yourself, even in the other channel they didn't really go that bad - they even started to call each other back to reason
[09:23] <cpaelzer> Dieselhonky: good luck with this approach
[09:24] <cpaelzer> Dieselhonky: in IT there is always more you don't know than what you know - so everyone or nowone is a noob :-)
[09:25] <Dieselhonky> thanks man.
[10:41] <Dieselhonky> cant abtain root on my android :(  i must be Tech-Tarded
=== guampa_ is now known as guampa
=== icey_ is now known as icey
=== chuck__ is now known as zul
[12:29] <lynxman> zul: hey hey
[12:33] <zul> lynxman: whats up
[12:35] <lynxman> zul: waiting for the release so I can build AMIs out of it ;)
[12:36] <zul> lynxman: nifty....
[12:36] <lynxman> zul: you know me :)
[13:55] <sts> hi. anyone knows where i can find the current ubuntu package source for the zfs systemd service files?
[13:55] <TJ-> sts: for which release?
[13:56] <sts> 16.04
[13:57] <TJ-> !info zfsutils-linux | sts
[13:57] <ubottu> sts: Package zfsutils-linux does not exist in wily
[13:57] <TJ-> ahhh!
[13:57] <sts> :)
[13:59] <TJ-> sts it's there, zfsutils-linux "/lib/systemd/system/zfs-mount.service" and friends
[13:59] <TJ-> !info zfsutils-linux  xenial | sts
[13:59] <ubottu> sts: zfsutils-linux (source: zfs-linux): Native OpenZFS management utilities for Linux. In component universe, is extra. Version 0.6.5.6-0ubuntu8 (xenial), package size 277 kB, installed size 721 kB
[13:59] <sts> got it!
[14:00] <TJ-> I forgot the bot still thinks 15.10 is the current release
[14:01] <rbasak> Well, it is :)
[14:02] <lynxman> rbasak: as of this hour :D
[14:03] <TJ-> nah, its 6 months old... far too old in the Internet age :)
[14:04] <jrwren> ancient!
[14:10] <lynxman> almost EOL
=== afkthairus is now known as athairus
[16:43] <randymarsh9> does richard stallman get along with linus
[16:43] <nacc> randymarsh9: #offtopic.
[16:43] <randymarsh9> nacc: sry i'm on my lunch break
[16:45] <randymarsh9> what is the topic anyway
[17:01] <nacc> randymarsh9: type /topic
=== mukhbiir is now known as neoark
=== ChanServ changed the topic of #ubuntu-server to: Ubuntu Server discussion and support | For general (not server specific) support, try #ubuntu | IRC Guidelines: https://wiki.ubuntu.com/IrcGuidelines | https://wiki.ubuntu.com/ServerTeam/GettingInvolved | Docs and resources: https://help.ubuntu.com/14.04/serverguide/ | 16.04 will become an upgrade path on July 21st when 16.04.1 is released
=== ChanServ changed the topic of #ubuntu-server to: Ubuntu Server discussion and support | For general (not server specific) support, try #ubuntu | IRC Guidelines: https://wiki.ubuntu.com/IrcGuidelines | https://wiki.ubuntu.com/ServerTeam/GettingInvolved | Docs and resources: https://help.ubuntu.com/14.04/serverguide/ | 14.04 to 16.04 will be offered on July 21st when 16.04.1 is released
=== InfoTest1 is now known as InfoTest
=== skipyyty is now known as caliculk
=== jml_ is now known as jml
=== InfoTest1 is now known as InfoTest
=== daker_ is now known as daker
=== Pici` is now known as Pici
=== j^2_ is now known as j^2
=== pleia2_ is now known as pleia2
=== andol_ is now known as andol
=== temmi_hoo_ is now known as temmi_hoo
[17:26] <RoyK> hm... can I install ubuntu 16.04 on a zfs root?
[17:27] <patdk-wk_> maybe?
[17:27] <Odd_Bloke> RoyK: I don't believe that's supported.
[17:27] <patdk-wk_> I see grub has zfs and *wonders zfscrypt
[17:27] <Odd_Bloke> But I'm not 100% sure.
[17:28] <nacc> i think it's not supported, but some folks have done it (meaning it's possible)
[17:31] <RoyK> lemme try...
[17:31] <nacc> RoyK: there is this, as well, fwiw: https://github.com/zfsonlinux/pkg-zfs/wiki/HOWTO-install-Ubuntu-to-a-Native-ZFS-Root-Filesystem
[17:32] <nacc> i think the installer natively doesn't allow it, but i'm not sure
[17:32] <RoyK> yeah, found that
[17:32] <RoyK> no, the installer doesn't seem to have zfs
[17:32]  * patdk-wk_ is just using zfs-on-linux for datastore currently
[17:33] <nacc> RoyK: it's meant mostly for datastore for containers, aiui (in 16.04)
[17:34] <RoyK> I know, but then, I've worked with zfs for six years or so and have seen the nice things about having on the root as well as for data
[17:34] <nacc> your experience is, ultimately != Ubuntu supporting it :)
[17:34] <nacc> RoyK: but I think it's a known thing (no root support)
[17:34] <jcastro> yeah, would have been a nice-to-have
[17:35] <RoyK> Plan A: Setup a normal system, add a disk, setup an zfs rpool on it, rsync everything, install grub, reboot
[17:36] <RoyK> or perhaps not... setting the mountpoint for the pool will be tricky
[17:36] <nacc> RoyK: and note, though, you immediately become unsupported
[17:37] <patdk-wk_> I find it strange, rpool name is limited to only using rpool
[17:37] <patdk-wk_> I commonly rename it, to support upgrading/moving my rpool
=== madwizar1 is now known as madwizard
[17:37] <RoyK> nacc: what do I care? It's a VM for testing - I use debian in production (lvm/ext4 root with zfs datastore)
[17:37] <nacc> RoyK: just a note :)
[17:38] <RoyK> nacc: I'm quite aware of that, thanks ;)
[17:38] <RoyK> the 'support' in ubuntu (without paying) is rather on the slack side anyway
[17:39] <nacc> *cough*, /me puts RoyK on the ignore list :)
[17:39] <nacc> i mean, technically, the above *is* support :)
[17:39] <devster31> hi, I'm trying to make a directory owned by someuser:somegroup that behaves in such a way that every new file or directory created inside has rw permission for the group regardless of the user who creates it and is owned by somegroup, how can I do it?
=== funkyHat_ is now known as funkyHat
[18:01] <jalt> Hi, #maas was not helpful so trying my luck here: anyone using MAAS knows how does it manage its (rack controller) networks? It currently sees both NICs but only setup the first one (DHCP), so I want to know if manually enabling the 2nd one on /etc/network/interfaces is the right thing to do.
[18:03] <nacc> devster31: you probably want to look into the setgid and setuid bits
[18:03] <nacc> iirc
[18:04] <sdeziel> devster31: chmod g+s the dir and make if group owned by the group you want to be set on every files under it
[18:28] <saftblandarn> Can someone tell me a easy way to upload files from my (windows) computer to my ubuntuserver? LIke when I want to change my /var/www/html?
[18:29] <jalt> winscp
[18:29] <saftblandarn> okey, cool
[18:30] <saftblandarn> or can I do it with directly with putty?
[18:32] <jalt> not putty per se, but you can use pscp (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)
[18:36] <devster31> sdeziel: I already have them set g+s, but when I create a new folder it's created with the correct group but not the correct permissions
[18:37] <devster31> meaning a user:group owned folder with 2775 permissions contains a second folder with 2755 permissions
[18:37] <sdeziel> devster31: the permissions are derived from your user's umask
[18:37] <devster31> and I can't enforce them with acl or something?
[18:38] <sdeziel> devster31: ACLs could do this IIRC but if you tune the umask you should get the perms you want
[18:38] <saftblandarn> jalt, thanks!
[18:40] <JanC> FileZilla also supports SFTP, and there are Explorer (the file browser) plugins that implement sftp
[18:40] <devster31> and I should change umask in login.defs,  /etc/pam.d/common-session or user profiles?
[18:41] <sdeziel> devster31: I would suggest to try manually first and see if that gives what you want
[18:45] <sdeziel> devster31: then /etc/login.defs seems to be the place now :)
[18:52] <devster31> thanks
[18:53] <sdeziel> np
[18:57] <jalt> For 16.04 is there any supported way to reload the whole /etc/network/interfaces short of rebooting?
[18:58] <sarnold> jalt: try ifdown -a ; ifup -a  ?
[19:00] <jalt> nope, that is the same as ip link set <devname> up and does not load ip (or any other configuration really)
[19:01] <jalt> For reference: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015
[19:01] <ubottu> Launchpad bug 1301015 in ifupdown (Ubuntu) "Networking does not restart" [High,Confirmed]
[19:05] <sarnold> jalt: that bug is a dumping ground; there's nearly nothing useful in it except  the advice to use (ifdown -a ; ifup -a) & -- which seems like better advice than my ifdown -a ; if up -a -- if there's something wrong with it, please file a bug
[19:06] <jalt> actually the bug is about the removal of a useful feature "Networking does not restart ", as per title.
[19:06] <sarnold> yes, I myself filed a bug somewhere along the way when "service network restart" destroyed my desktop environment
[19:07] <sarnold> that's when I learned that ifup and ifdown were the way to restart networking services
[19:07] <jalt> i'd blame your DE then ;)
[19:07] <sarnold> if those don't work, please file a bug.
[19:07] <sarnold> oh I did. and still do. :)
[19:07] <jalt> they are a way to restart an interface, but not to reload the full networking stack
[19:07] <jalt> i.e., you cannot change ips, cannot create bonds, etc.
=== Isla_de_Muerte is now known as NwS
[19:08] <jalt> that is not a bug, because ifupdown and ip set link are not supposed to do all that
[19:12] <jalt> so I rebooted (and it worked to load the new interfaces conf) but tty1 font color is now orange-ish!? any idea why that happened?
[19:12] <randymarsh9> so ubuntu server supports zfs now
[19:12] <randymarsh9> ?
[19:13] <sarnold> randymarsh9: yes
[19:13] <jalt> you may want to read the whole ZoL docs to confirm what features are supported, but in short, yes.
[19:13] <sarnold> jalt: wiggle the vga cable? that was the cause last time I saw something like that
[19:14] <jalt> for desktop use you should be careful if you want to boot out of it, dual boot with win and/or efi, or full drive encryption.
[19:14] <jalt> sarnold, i'm using DVI, the cable did not move and the other TTYs are normal :)
[19:16] <sarnold> jalt: dang :)
[19:21] <jalt> restarting again fixed it....
[19:21] <sarnold> o_O
[19:29] <dasjoe> Hah oh wow, 16.04 got released today
[19:30] <dasjoe> I thought we had one week left
[19:35] <patdk-wk_> I have only upgraded 1 server so far
[19:35] <patdk-wk_> others still running beta :)
=== zopsi_ is now known as zopsi
=== Assailant is now known as a12345
=== a12345 is now known as Assailant
=== njalk_ is now known as njalk
[21:25] <Emmanuel_Chanel> Hello! I'm trying to upgrade my Ubuntu 14.04 LTS. "sudo do-release-upgrade" says "No new release found"
[21:25] <Emmanuel_Chanel> Shall I wait for a few days?
[21:26] <dasjoe> For around 3 months, the upgrade will be made available around July 21st
[21:26] <Emmanuel_Chanel> hi
[21:34] <Emmanuel_Chanel> ok.
[21:43] <patdk-lap> upgrades from 14.04 aren't supported till 16.04.1 comes out
[22:16] <Delemas> Anyone know if 16.04 still supports upstart like 15.10 did?
[22:20] <Delemas> The answer is yes.
[22:20] <JanC> 16.04 uses systemd as its (default) init system though
[22:21] <Delemas> Agreed.
[22:21] <Delemas> I was trying to figure out if upstart alone would cause do-release-upgrade to fail. It seems it shouldn't.
[22:22] <JanC> it didn't break upgrades on earlier versions  :)
[22:22] <JanC> and 15.10 used systemd too
[22:22] <Delemas> I've had bad luck with do-release-upgrade lately... Did with 15.10 too...
[22:23] <Delemas> One of them was a btrfs corruption though so that's not do-release-upgrade's fault.
=== Guest49657 is now known as karstensrage