Introducing Freebsd in New Environment the Good, the Bad and the Ugly

Introducing Freebsd in New Environment the Good, the Bad and the Ugly

Introducing FreeBSD in new environment The good, the bad and the ugly Baptiste Daroussin [email protected] BSDCan 2018 Ottawa June 9th, 2018 Disclaimer: subjective french point of view BSDCan 2018 Introducing FreeBSD in new environment 2 of 21 I No more a student since 2003 I Working mostly in France and Africa I Only one job really ocially FreeBSD related Who am I? I FreeBSD user since 1998 (thanks to FreeBSD on the desktop!) I FreeBSD committer since 2010 I portmgr since 2011 I core since 2014 I Contributing mostly in my free time BSDCan 2018 Introducing FreeBSD in new environment 3 of 21 Who am I? I FreeBSD user since 1998 (thanks to FreeBSD on the desktop!) I FreeBSD committer since 2010 I portmgr since 2011 I core since 2014 I Contributing mostly in my free time I No more a student since 2003 I Working mostly in France and Africa I Only one job really ocially FreeBSD related BSDCan 2018 Introducing FreeBSD in new environment 3 of 21 I Old school sysadmin usage I Appliances usage I Modern devops usage I Diskless Targets BSDCan 2018 Introducing FreeBSD in new environment 4 of 21 I Appliances usage I Modern devops usage I Diskless Targets I Old school sysadmin usage BSDCan 2018 Introducing FreeBSD in new environment 4 of 21 I Modern devops usage I Diskless Targets I Old school sysadmin usage I Appliances usage BSDCan 2018 Introducing FreeBSD in new environment 4 of 21 I Diskless Targets I Old school sysadmin usage I Appliances usage I Modern devops usage BSDCan 2018 Introducing FreeBSD in new environment 4 of 21 Targets I Old school sysadmin usage I Appliances usage I Modern devops usage I Diskless BSDCan 2018 Introducing FreeBSD in new environment 4 of 21 I sysadmins: I before: "Who is the vendor?" I now: "Never heard of that Linux distro?" I developers I PCI DSS auditors Audience BSDCan 2018 Introducing FreeBSD in new environment 5 of 21 I before: "Who is the vendor?" I now: "Never heard of that Linux distro?" I developers I PCI DSS auditors Audience I sysadmins: BSDCan 2018 Introducing FreeBSD in new environment 5 of 21 I developers I PCI DSS auditors Audience I sysadmins: I before: "Who is the vendor?" I now: "Never heard of that Linux distro?" BSDCan 2018 Introducing FreeBSD in new environment 5 of 21 I PCI DSS auditors Audience I sysadmins: I before: "Who is the vendor?" I now: "Never heard of that Linux distro?" I developers BSDCan 2018 Introducing FreeBSD in new environment 5 of 21 Audience I sysadmins: I before: "Who is the vendor?" I now: "Never heard of that Linux distro?" I developers I PCI DSS auditors BSDCan 2018 Introducing FreeBSD in new environment 5 of 21 I BSD is for real hardcode sysadmins I BSD is hard to use I BSD is a source only OS I one true BSD I There must be a reason for $feature not exist Myths BSDCan 2018 Introducing FreeBSD in new environment 6 of 21 I BSD is hard to use I BSD is a source only OS I one true BSD I There must be a reason for $feature not exist Myths I BSD is for real hardcode sysadmins BSDCan 2018 Introducing FreeBSD in new environment 6 of 21 I BSD is a source only OS I one true BSD I There must be a reason for $feature not exist Myths I BSD is for real hardcode sysadmins I BSD is hard to use BSDCan 2018 Introducing FreeBSD in new environment 6 of 21 I one true BSD I There must be a reason for $feature not exist Myths I BSD is for real hardcode sysadmins I BSD is hard to use I BSD is a source only OS BSDCan 2018 Introducing FreeBSD in new environment 6 of 21 I There must be a reason for $feature not exist Myths I BSD is for real hardcode sysadmins I BSD is hard to use I BSD is a source only OS I one true BSD BSDCan 2018 Introducing FreeBSD in new environment 6 of 21 Myths I BSD is for real hardcode sysadmins I BSD is hard to use I BSD is a source only OS I one true BSD I There must be a reason for $feature not exist BSDCan 2018 Introducing FreeBSD in new environment 6 of 21 I Never impose I Do not convert I Be accessible I Be reactive Methodology BSDCan 2018 Introducing FreeBSD in new environment 7 of 21 I Do not convert I Be accessible I Be reactive Methodology I Never impose BSDCan 2018 Introducing FreeBSD in new environment 7 of 21 I Be accessible I Be reactive Methodology I Never impose I Do not convert BSDCan 2018 Introducing FreeBSD in new environment 7 of 21 I Be reactive Methodology I Never impose I Do not convert I Be accessible BSDCan 2018 Introducing FreeBSD in new environment 7 of 21 Methodology I Never impose I Do not convert I Be accessible I Be reactive BSDCan 2018 Introducing FreeBSD in new environment 7 of 21 I NetASQ Stormshield I pfSense I FreeNAS I Niksun I Juniper I Isilon Always a FreeBSD machine somewhere BSDCan 2018 Introducing FreeBSD in new environment 8 of 21 I pfSense I FreeNAS I Niksun I Juniper I Isilon Always a FreeBSD machine somewhere I NetASQ Stormshield BSDCan 2018 Introducing FreeBSD in new environment 8 of 21 I FreeNAS I Niksun I Juniper I Isilon Always a FreeBSD machine somewhere I NetASQ Stormshield I pfSense BSDCan 2018 Introducing FreeBSD in new environment 8 of 21 I Niksun I Juniper I Isilon Always a FreeBSD machine somewhere I NetASQ Stormshield I pfSense I FreeNAS BSDCan 2018 Introducing FreeBSD in new environment 8 of 21 I Juniper I Isilon Always a FreeBSD machine somewhere I NetASQ Stormshield I pfSense I FreeNAS I Niksun BSDCan 2018 Introducing FreeBSD in new environment 8 of 21 I Isilon Always a FreeBSD machine somewhere I NetASQ Stormshield I pfSense I FreeNAS I Niksun I Juniper BSDCan 2018 Introducing FreeBSD in new environment 8 of 21 Always a FreeBSD machine somewhere I NetASQ Stormshield I pfSense I FreeNAS I Niksun I Juniper I Isilon BSDCan 2018 Introducing FreeBSD in new environment 8 of 21 I First: mangle I how do I install logrotate? I how do I install rsyslog? I Second: learn I oh, newsyslog is nice I hey your syslog does that? Users: wants to feel at home BSDCan 2018 Introducing FreeBSD in new environment 9 of 21 I how do I install logrotate? I how do I install rsyslog? I Second: learn I oh, newsyslog is nice I hey your syslog does that? Users: wants to feel at home I First: mangle BSDCan 2018 Introducing FreeBSD in new environment 9 of 21 I Second: learn I oh, newsyslog is nice I hey your syslog does that? Users: wants to feel at home I First: mangle I how do I install logrotate? I how do I install rsyslog? BSDCan 2018 Introducing FreeBSD in new environment 9 of 21 I oh, newsyslog is nice I hey your syslog does that? Users: wants to feel at home I First: mangle I how do I install logrotate? I how do I install rsyslog? I Second: learn BSDCan 2018 Introducing FreeBSD in new environment 9 of 21 Users: wants to feel at home I First: mangle I how do I install logrotate? I how do I install rsyslog? I Second: learn I oh, newsyslog is nice I hey your syslog does that? BSDCan 2018 Introducing FreeBSD in new environment 9 of 21 I long ago: I the good: easily customisable I the bad: hard to reproduce a setup I the bad: hard to maintain a repo I the ugly: hard to automate I the ugly: binary maintenance close to impossible I nowadays: I the good: easy to create/maintain a repo I the good: simple and straight forward command line interface I the good: easy I the good: up to date packages I the bad: no LTS repo I the bad: multi repository support Package management BSDCan 2018 Introducing FreeBSD in new environment 10 of 21 I the bad: hard to reproduce a setup I the bad: hard to maintain a repo I the ugly: hard to automate I the ugly: binary maintenance close to impossible I nowadays: I the good: easy to create/maintain a repo I the good: simple and straight forward command line interface I the good: easy I the good: up to date packages I the bad: no LTS repo I the bad: multi repository support Package management I long ago: I the good: easily customisable BSDCan 2018 Introducing FreeBSD in new environment 10 of 21 I the ugly: hard to automate I the ugly: binary maintenance close to impossible I nowadays: I the good: easy to create/maintain a repo I the good: simple and straight forward command line interface I the good: easy I the good: up to date packages I the bad: no LTS repo I the bad: multi repository support Package management I long ago: I the good: easily customisable I the bad: hard to reproduce a setup I the bad: hard to maintain a repo BSDCan 2018 Introducing FreeBSD in new environment 10 of 21 I nowadays: I the good: easy to create/maintain a repo I the good: simple and straight forward command line interface I the good: easy I the good: up to date packages I the bad: no LTS repo I the bad: multi repository support Package management I long ago: I the good: easily customisable I the bad: hard to reproduce a setup I the bad: hard to maintain a repo I the ugly: hard to automate I the ugly: binary maintenance close to impossible BSDCan 2018 Introducing FreeBSD in new environment 10 of 21 I the bad: no LTS repo I the bad: multi repository support Package management I long ago: I the good: easily customisable I the bad: hard to reproduce a setup I the bad: hard to maintain a repo I the ugly: hard to automate I the ugly: binary maintenance close to impossible I nowadays: I the good: easy to create/maintain a repo I the good: simple and straight forward command line interface I the good: easy I the good: up to date packages BSDCan 2018 Introducing FreeBSD in new environment 10 of 21 Package management I long ago: I the good: easily customisable I the bad: hard to reproduce a setup I the bad: hard to maintain a repo I the ugly: hard to automate I the ugly: binary maintenance close to impossible I nowadays: I the good: easy

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    84 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us