[00:32] jancoow: on 16.04, systemctl is part of systemd. you should defintely have it available as root. if not, it suggests that your upgrade did not work out well. [00:34] there are counter measures against hdd failures. one of them is RAID with a mirroring confiuguration - that's pretty easy if you can afford another disk. the other is to do backups, and do them properly and reliably, which you need to do either way. [00:56] I replaced my serve casing [00:56] i've 7hhd's in greyhole configuration [00:57] the only not redunant disk, the os drive, broke during the move... [00:57] the sata connectors littarly broke from the pcb and now th drive isn't spinning anymore [00:57] Last backup is from 2 months ago.. [01:17] there shouldn't really be anything important on the OS drive, right? [01:18] drab: the best documentation of the difference of hash and bitmap might be the source code [01:18] drab: chances are you probably want one of the hash versions [06:18] is it possible to run the early preseed script and modify the /etc/mke2fs.conf? [06:19] or is there another way to set ext4 options in preseed? [08:36] Good morning. [09:19] mornin [13:21] hi [13:21] is there a way to get normal network interface names back in 16.04? [13:22] at them moment they're all stuff like enp39asdfasdfblahblahblah and they change on every boot [13:22] gordonjcp: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [13:23] They shouldn't change every boot... [13:23] okay, why are they called "predictable" when they're essentially random [13:23] They are named based on where the bios says they are. [13:23] o_O [13:23] the bios has no idea what a network interface is [13:24] It does know where the device is. [13:24] In short, read the link I gave you. [13:24] I'm reading it [13:25] it seems like a pretty pointless change, which only makes things more difficult for users [13:26] In my opinion it makes more sense than the old way. [13:26] randomly assigning names to interfaces, based on when systemd gets around to looking at them? [13:27] The point is that it is not random. [13:27] okay, but it's not stable [13:27] It is. [13:27] it changes on every boot [13:27] Those ethX names werent. "Oh hey a new interface in the same location, lets give it a new name. [13:27] " [13:28] Anyhow, these are just opinions. [13:28] is there a way to get rid of systemd in 16.04? [13:28] or if there isn't, is there a way to force it to work *exactly* like sysvinit [13:29] right now it doesn't seem to run init scripts in any predictable order [13:29] "oh hey, I can't see one of the network interfaces. Never mind, I'll just start up dnsmasq on it, then I'll bring up the xl2tpd tunnel, oh hell everything on fire now" [13:33] I guess that's a no [13:33] so Ubuntu Server isn't actually intended for use on servers, then? [13:34] or is there something fundamental I'm not getting about this [14:46] sarnold: yeah I got some answers in #netfilter, turns out it's mostly a choice based on types and features [14:46] looking closer it indeed makes sense for example bitmap:ip expects a range to be specified upon creation, something I hadn't noticed at first [14:48] I would imagine bitmap to be much faster, as no hasing needed [14:49] more geared for matching against local network [15:18] patdk-lap: that's a good point, I hadn't thoguht of it, thank you [15:51] Hi [15:52] How do I upgrade my 12.04-LTS server to 16.04 LOTS [15:52] *LTS [15:58] I just didnt that for a system. worked great, and I was doing it over ssh [16:00] oh, wait. I think it was 14.04. nm === JanC is now known as Guest86017 === JanC_ is now known as JanC [17:34] is it possible to rsnapshop backup to a windows/ntfs share? I would think not since it relies on hard links.. no? [18:50] Hey all. I am having a bit of trouble with vim. I have several lines in the script that are formated mm-dd-yyyy like 01-01-2017, 01-08-2017 etc. how can I delete them all in one shot? I have tried g/^0?-*/d but that does not seem to work. [18:51] And now that I think about it I will have like 10, 11 and 12 so even using ^0?-* wouldn't work anyway. === ashleyd is now known as ashd [20:11] Hi there. How to change this service into the new systemctl ? http://pastebin.com/8cnuJzZG [21:22] Hi! I'm trying to set up some backup scripts and I noticed that the backup user don't have write access to its home directory (/var/backups) What's the reasoning behind this? What's the preferred workaround (my specific problem right now is that gpg can't create the .gnupg directory) [21:23] heh? [21:23] backup user? [21:23] there is no backup user unless you created one [21:24] and /var/backups isn't exactly something you want to backup, as it's outdated infomation, why it's called backups [21:25] patdk-lap: I don't want to backup the contents of /var/backups, I want somewhere for my backup user to write metadata :) [21:26] patdk-lap: are you 100% sure there's not a backup user by default? cause I have no memory of creating one and a 'random' person in #ubuntu had the exact same settings as me in his /etc/passwd [21:26] backup:x:34:34:backup:/var/backups:/usr/sbin/nologin [21:27] hmm, I do have a backups user on this system [21:30] I could of course create a "backups2" user with its own home directory that I control, but it feels a bit silly. I don't want to change the current user without knowing why it's setup the way it is. [21:30] In case I break something [21:35] backupgs "sigh" [21:42] It looks to be a heritage from debian, they appearantly have an open bug from 2001 about it...