[00:50] <soulseeker> hey paul98 how's thinhs going with you
[01:08] <soulseeker> I was working on installing ubuntu and encountered some problems booting.
[01:23] <soulseeker> it was interesting to find out that the pivot_root did not work which suggest ubuntu boots se other wayv
[02:13] <soulseeker> funny how pivot_root does not work
[02:14] <soulseeker> I checked it over again and it reads invalid argument for a standard invocation
[04:00] <soulseeker> paul98 talk to me
[04:00] <soulseeker> paul98 have you heard of a roman ring wormhole
[04:02] <soulseeker> suppose you want to send a message through time
[04:02] <soulseeker> say past or future past seems easier
[04:03] <soulseeker> say you have a journling filesystem
[04:03] <soulseeker> and want to commenicAte to somebody using the file system
[04:04] <soulseeker> and write synchfonicity in the fesystem
[04:05] <soulseeker> that iz earth right
[04:05] <soulseeker> sulposed unintentional jfs
[04:12] <soulseeker> by the way paul98 I have some company information that didnt take on #frenode
[04:13] <soulseeker> if you desire to look it over , only ask
[04:27] <soulseeker> hey unshackled!
[04:27] <soulseeker> welcome
[04:27] <soulseeker> the spirits which go through humanity
[04:28] <soulseeker> the different social structures
[04:28] <soulseeker> how to do away with archaic forms
[04:28] <soulseeker> shackles is an example
[04:28] <soulseeker> archaic satanic ritual of binding or bondage of human bodies
[04:29] <soulseeker> mammonic deemon
[04:32] <soulseeker> these forms of deemon worsgip remain in the filesystem long after they need to be removed
[04:32] <soulseeker> thats mostly what the police do
[04:33] <soulseeker> but now advancing towards worse torture
[04:33] <soulseeker> with electric guns
[05:00] <lotuspsychje> soulseeker: can you stop that please, this is the ubuntu server support channel not a satanistic chat
[05:12] <cpaelzer> ahasenack: for your clamav rebuild on a sync - I had the smae question a while ago, you chose correct
[05:13] <cpaelzer> in my case the base version was even more odd (I don't remember details), but the TL;DR was more or less "... as long as your new versions does not contain ubuntu it will be auto-synced still"
[10:02] <geodb27> People : hi ! I'm trying to write a kickstart file to automate the installation process of my ubuntu18.04.2-servers. I'm having troubles to write the partitionning. The instructions in the ks.cfg are not recognized. From what I remember, it worked fine with 16.04 version. Are there some notes about writing such a kickstart other than  https://wiki.dinfadom.com/index.php/Kickstart_-_Ubuntu_18.04_LTS ?
[10:04] <geodb27> So far, here is my ks.cfg file : https://pastebin.com/Fni4ga5d
[10:23] <frickler> geodb27: not sure whether you are seeing the same issue, but in order to deploy 18.04 with the same setup I was using for 16.04 I have to use the network installer iso from http://cdimage.ubuntu.com/netboot/18.04/ instead of the new server-install iso
[10:57] <geodb27> Thanks for your answer and help frickler. As a matter of fact, I've fallen on a page (https://opstuff.blog/2018/10/16/ubuntu-18-04-unattended-setup/) that seems to point that the prefered way is to use a preseed file.
[12:37] <zzlatev> Hey guys, can I make a mirror of my ubuntu-server and use it to another machine?
[12:46] <RoyK> zzlatev: yes, but it's generally not a good idea since UUID will be the same etc
[12:47] <RoyK> zzlatev: better setup the new machine with ansible or something else for automation and use those rules to setup the next machine automatically
[12:52] <zzlatev> hmm
[12:52] <zzlatev> OK
[13:12] <blackflow> UUIDs can be changed tho
[13:14] <blackflow> teward: ping, btw, that was a client-side issue, Firefox on Bionic, in certain situations I can't isolate, has issues with http2 streams.
[13:54] <catbadger> hi
[14:25] <ixil> hello, I'm trying to setup bionic(server) in lxc/lxd but can't work out how to make it use dhcp - I've been trying w/ netplan
[14:26] <teward> blackflow: sounds like  Firefox then needs a bug filed against it
[14:26] <teward> blackflow:  if FFox is using some buggy HTTP/2 implementations that'd explain things
[14:26] <teward> or if you have addons enabled that break things :P
[14:27] <teward> ixil: out of the box, if you deploy an LXD Bionic image it'll be set to DHCP for IPv4
[14:27] <teward> `lxc launch ubuntu:bionic foobar` defaults in itself to a DHCP'd netplan, it requires that you have DHCP on the default network bridge/segment the container is dropped onto though
[14:28] <ixil> teward: that's what I thought - possibly my host(an archlinux box) is misconfigured?
[14:28] <teward> possibly, but you'd want to go to #lxcontainers for support with the LXD config on your arch box
[14:28] <ixil> teward: well I use the default `lxdbr0` that `lxd init` brought up
[14:29] <teward> ixil: *points to the #lxcontainers channel*
[14:29] <ixil> teward: bit quite over there but I can give it another go, but even still manually configuring through `ip` seems to work, so for netplan itself I'm not sure what I'm doing wrong
[14:30] <teward> (we don't support arch here ;) )
[14:30] <teward> ixil: probably not necessarily a netplan problem.
[14:30] <teward> esp. if `netplan apply` doesn't complain about network config being wrong
[14:30] <ixil> teward: I suspect I have teh netplan config syntax wrong
[14:31] <teward> pastebin your netplan config then
[14:33] <ixil> http://ix.io/1HUl
[14:35] <teward> ixil: any chance you have a /etc/netplan/50-cloud-init.yaml at all?  You might want to refer to that to the 'proper format'
[14:36] <teward> usually I suggest to configure the devices directly rather than using a match clause
[14:38] <ixil> teward: so I used the cloud-init as a template, but left it in /etc/netplan
[14:38] <ixil> http://ix.io/1HUm <- top is `ip a` on the bionic machine, and bottom my host's relevant links
[14:40] <ixil> I'm new with netplan, but I've just been doing a `sudo netplan apply; sudo netplan try;` followed by checking `ip addr`
[14:41] <ixil> the point of the match was the interface gets called eth1@ifXX by lxc, is that something I should look to change?
[14:52] <teward> ixil: you can be fairly certain that those interface names 'won't change' - those're locked in usually on the config level of the VM from my testing.
[14:52] <teward> so you don't really need the *match* where you can just specify the individual devices
[14:55] <ixil> teward: I just `lxc restart ...` the container, and the interfaces are now eth@if107 :/
[14:57] <teward> :|
[14:57] <albert23> shouldn't filename 10-custom.conf be 10-custom.yaml?
[14:57] <teward> ixil: ^ that
[14:57] <teward> make sure it's a .yaml file
[14:57] <teward> then try and apply it.
[14:57] <teward> i have to head into a meeting...
[14:59] <ixil> albert23: you're my hero
[15:01] <cyphermox> ixil: no need to do apply and then try, it's the same thing
[15:01] <ixil> now the config at least shows up under /run/systemd/network/ but it doesn't seem to be correct
[15:01] <cyphermox> do one or the other
[15:02] <ixil> cyphermox: ah thanks, I thought it might be, but thought to err on the side of caution
[15:02] <cyphermox> "try" is just a fancy "apply" with a timer to attempt to revert if you don't respond within the timeout
[15:03] <cyphermox> revert often works, but not for all kinds of setups
[15:03] <ixil> ahh well there's no point in doing try, as I can't really check anyway as I have no secondary console to check from the container side
[15:20] <cyphermox> well, that's the thing
[15:20] <cyphermox> if you run that in screen you can reconnect (or you won't lose the connection at all)
[17:14] <blackflow> teward: biggest problem is I can't isolate what in FF causes this. I tried --safe-mode, and the problem doesn't appear there. It doe appear if I run normal mode but disable the two extensions I use. It does appear if I run a fresh new profile. It doesn't appear on every page load. There's no consistency ot point out the issue.
[17:15] <teward> blackflow: i'd file a bug with firefox then either way
[17:15] <blackflow> teward: I'm not sure if it is, or if it's something specific to my setup. I asked someone her yesterday to try my test page, from Bionic ,and they saw nothing.
[17:16] <blackflow> no problem I mean.
[17:16] <blackflow> someone *here
[18:12] <jdr> Any issues with running bind, apache, and postfix all on the same server?
[18:16] <sarnold> should be fine
[18:19] <teward> just make sure to harden them all properly
[18:20] <teward> and not leave yourself open to vulnerabilities heh
[18:21] <sdeziel> postfix + a recursive caching server is rather common/best practice
[18:22] <teward> yep
[18:23] <jdr> Gotcha. Thanks.
[18:25] <leftyfb> Is the 127.0.1.1 entry in /etc/hosts for server important? It looks like it's just a debian/ubuntu thing for some gnome applications that don't like not being able to resolve your hostname to an ip if you don't have a local DNS server on the network.
[18:26] <leftyfb> The reason I ask is because "dnsdomainname" fails to work if that entry exists without a FQDN which from what I can tell, DHCP is not able to populate
[20:07] <ahasenack> leftyfb: did you get that entry in /etc/hosts by default after an install?
[20:08] <leftyfb> ahasenack: yes. I checked with a fresh server install. It's just 127.0.1.1 <hostname> # no FQDN
[20:09] <ahasenack> 18.04 or what?
[20:09] <leftyfb> if the entry exists at all, it looks for FQDN there, if none is found, there is no result in looking it up. If there's no entry, it looks up via DNS
[20:09] <ahasenack> using the new installer, or the old one?
[20:09] <ahasenack> afaik that's a cloud-init parameter that the installer may be passing to it, or not passing, and some default is assumed
[20:10] <leftyfb> ahasenack: 16.04. I know 18.04 has a separate issue with /etc/host since I reported the bug :)
[20:10] <ahasenack> aha
[20:10] <ahasenack> well, 16.04 is definitely the old installer, I don't recall what it was doing back then
[20:10] <ahasenack> I like my machines to work without having to add that entry
[20:11] <leftyfb> right
[20:11] <leftyfb> which is why I'm asking if the entry is necessary in a server environment. I don't think it is
[20:12] <leftyfb> because it certainly breaks local FQDN lookup
[20:15] <leftyfb> ahasenack: I'm betting the classic installer for 18.04 will have the same issue
[20:15] <ahasenack> I really don't remember
[20:15] <ahasenack> my laptop has it, but it's a desktop