Boston Linux Installfest LXIII
When: Saturday March 18, 2017, from 9:00 am to 5:00 pm
Where: MIT Building E-51, Room 061
2 Amherst St, Cambridge
Plenty of free parking in the parking lot in front of E-51.
http://mitiq.mit.edu/mitiq/directions_%20parkinge51.htm
What you need to bring: Your computer, monitor, power strips and your
Linux distributions. We do have copies of some distributions.
In general we have expertise with most distros, but if you need special
expertise, please email the BLU discussion list in advance. Today, most
distros are using Live images that you can try out and then install.
This can be copied to DVDs or USB sticks.There are a number of USB
creators, such as UNetbootin (https://unetbootin.github.io/). Both
Fedora and Ubuntu have a USB creator built in.
COST: It's free! However, we DO have expenses, and contributions are
welcome. Please consider contributing $25 per machine.
Our volunteers will help you to install Linux on your own system. While
Linux runs on most systems, some systems do have configurations and
hardware that may not be supported. Please consult the following web
pages for hardware compatibility. While we prefer you to bring your own
distros, our volunteers will normally have
Linux Howto Pages: http://tldp.org/HOWTO/HOWTO-INDEX/howtos.html
Linux Frequently Asked Questions: http://tldp.org/docs.html#faq
Additionally, there are forums and listservs for most distros.
Generally our volunteers have sets of the latest Fedora, SuSE and
Ubuntu distributions:
* Fedora - https://getfedora.org/ (Fedora 25 Live DVD/USB)
* Ubuntu - http://www.ubuntu.com ( 16.04.2 LTS DVD/USB or 16.10)
* other distros can be downloaded at the Installfest
We generally have them on local drives and can burn CDs/DVDs and
USBs.Since there are many variants of these distros, we advise you to
bring an empty USB stick with sufficient memory to hold one of the
distros. Live images require about 1.5GB. I usually have some USBs
prepared.
We usually have both a Wired and Wireless network available.
The preferred wireless SSID at MIT is "MIT". In addition John does set
up a local wifi.
In addition, you can run Linux on your Windows PC through a virtual
machine manager, such as Virtualbox. You can install this in your
Windows machine and run Linux as a guest OS, or install it in your Linux
machine and run Windows as a guest. VirtualBox 5.1.10
(http://www.virtualbox.org.) is free and is available for Linux, Windows
10, Windows 8, Windows 7, Windows XP and Windows Vista. Additionally,
there are also some VMWare clients that are also free for Windows.
Lunch is generously sponsored by Bluefin Technical Services, John Ross
and Ron Thibeau
Please refer to the BLU website (http://www.blu.org) for further
information and directions. Parking is free and available in front of
the building on Amherst St. Enter the building, and take the elevator to
your left down 1 floor. Room 061 is opposite the elevator.
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix user group
http://www.blu.org
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Home | Calendar | Mail Lists | Video | Maps & Directions | Installfests | Keysignings | Meeting Notes | About BLU
Wednesday, March 8, 2017
Boston Linux Meeting, Wednesday, March 15, 2017 - BLU Quick Hits: IoT comms using LoraWAN. Also Layer 1 - 3 security with ProtonMail
When: March 15, 2017 7PM (6:30PM for Q&A)
Topic: BLU Quick Hits: IoT comms using LoraWAN. Also Layer 1 - 3
security with ProtonMail
Moderators: Kurt Keville, V. Alex Brennen
Location: MIT Building E-51, Room 325
Summary:
Updates on several local community projects
Abstract:
Details to follow later
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
Note: The Hayward St. lot has been closed affecting the MIT-E51 lot.
They have opened up another lot on Hayward Street that was usually
restricted.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Topic: BLU Quick Hits: IoT comms using LoraWAN. Also Layer 1 - 3
security with ProtonMail
Moderators: Kurt Keville, V. Alex Brennen
Location: MIT Building E-51, Room 325
Summary:
Updates on several local community projects
Abstract:
Details to follow later
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
Note: The Hayward St. lot has been closed affecting the MIT-E51 lot.
They have opened up another lot on Hayward Street that was usually
restricted.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Tuesday, February 14, 2017
Boston Linux Meeting reminder moderator change, tomorrow, Wednesday, February 15, 2017 - Linux Backups
When: February 15, 2017 7PM (6:30PM for Q&A)
Topic: Linux Backups
Moderator: BLU Staff
Location: MIT Building E-51, Room 325
Note: Room change - next door to previous room.
Summary:
Managing Encrypted Linux Backups
Abstract:
Three tiny tutorials: rsync, duplicity, and boxbackup. Demonstrations:
pros and cons, tips and tricks. Discussion, Case studies / audience
participation.
performance
media
security
backup disasters (if anyone is brave enough to share)
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
Note: The Hayward St. lot has been closed affecting the MIT-E51 lot.
They have opened up another lot on Hayward Street that was usually
restricted.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Topic: Linux Backups
Moderator: BLU Staff
Location: MIT Building E-51, Room 325
Note: Room change - next door to previous room.
Summary:
Managing Encrypted Linux Backups
Abstract:
Three tiny tutorials: rsync, duplicity, and boxbackup. Demonstrations:
pros and cons, tips and tricks. Discussion, Case studies / audience
participation.
performance
media
security
backup disasters (if anyone is brave enough to share)
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
Note: The Hayward St. lot has been closed affecting the MIT-E51 lot.
They have opened up another lot on Hayward Street that was usually
restricted.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Boston Linux Meeting reminder, tomorrow, Wednesday, February 15, 2017 - Linux Backups
When: February 15, 2017 7PM (6:30PM for Q&A)
Topic: Linux Backups
Moderator: Brian DeLacey
Location: MIT Building E-51, Room 325
Note: Room change - next door to previous room.
Summary:
Managing Encrypted Linux Backups
Abstract:
Three tiny tutorials: rsync, duplicity, and boxbackup. Demonstrations:
pros and cons, tips and tricks. Discussion, Case studies / audience
participation.
performance
media
security
backup disasters (if anyone is brave enough to share)
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
Note: The Hayward St. lot has been closed affecting the MIT-E51 lot.
They have opened up another lot on Hayward Street that was usually
restricted.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Topic: Linux Backups
Moderator: Brian DeLacey
Location: MIT Building E-51, Room 325
Note: Room change - next door to previous room.
Summary:
Managing Encrypted Linux Backups
Abstract:
Three tiny tutorials: rsync, duplicity, and boxbackup. Demonstrations:
pros and cons, tips and tricks. Discussion, Case studies / audience
participation.
performance
media
security
backup disasters (if anyone is brave enough to share)
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
Note: The Hayward St. lot has been closed affecting the MIT-E51 lot.
They have opened up another lot on Hayward Street that was usually
restricted.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Thursday, February 9, 2017
Boston Linux Meeting Wednesday, February 15, 2017 - Linux Backups
When: February 15, 2017 7PM (6:30PM for Q&A)
Topic: Linux Backups
Moderator: Brian DeLacey
Location: MIT Building E-51, Room 325
Note: Room change - next door to previous room.
Summary:
Managing Encrypted Linux Backups
Abstract:
Three tiny tutorials: rsync, duplicity, and boxbackup. Demonstrations:
pros and cons, tips and tricks. Discussion, Case studies / audience
participation.
performance
media
security
backup disasters (if anyone is brave enough to share)
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
Note: The Hayward St. lot has been closed affecting the MIT-E51 lot.
They have opened up another lot on Hayward Street that was usually
restricted.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Topic: Linux Backups
Moderator: Brian DeLacey
Location: MIT Building E-51, Room 325
Note: Room change - next door to previous room.
Summary:
Managing Encrypted Linux Backups
Abstract:
Three tiny tutorials: rsync, duplicity, and boxbackup. Demonstrations:
pros and cons, tips and tricks. Discussion, Case studies / audience
participation.
performance
media
security
backup disasters (if anyone is brave enough to share)
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
Note: The Hayward St. lot has been closed affecting the MIT-E51 lot.
They have opened up another lot on Hayward Street that was usually
restricted.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Tuesday, January 17, 2017
Boston Linux Meeting reminder, tomorrow, Wednesday, January 18, 2017 - Red Hat OCID and Container Security
When: January 18, 2017 7PM (6:30PM for Q&A)
Topic: Red Hat OCID and Container Security
Moderator: Daniel J Walsh , Lead SELinux Engineer , Red Hat Software
Location: MIT Building E-51, Room 315
Summary:
Red Hat's new OCID container system, an alternative to Docker
Abstract:
OCID (CRI-O) is a container runtime to be used with the Kubernetes
Kublet. Specifically, it implements the Kubelet Container Runtime
Interface (CRI) using OCI conformant runtimes. The goal of the OCID is
to optimize running of containers in production, via Kubernetes and
OpenShift.
At a high level, we expect the scope of OCID:
Support multiple image formats including the existing Docker image format
Support for multiple means to download images including trust & image
verification
Container image management (managing image layers, overlay filesystems, etc)
Container process lifecycle management
Monitoring and logging required to satisfy the CRI
Resource isolation as required by the CRI
Second part of the talk will cover Container Security. We will cover all
parts of container security from the importance of the kernel, to where
you should run your containers, container separation and what you should
run inside
Red Hat's OCID is a Docker Alternative, But Not a Fork :
http://containerjournal.com/2016/10/04/red-hats-ocid-docker-alternative-not-fork/
Running production applications in containers: Introducing OCID :
https://www.redhat.com/en/about/blog/running-production-applications-containers-introducing-ocid
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Topic: Red Hat OCID and Container Security
Moderator: Daniel J Walsh , Lead SELinux Engineer , Red Hat Software
Location: MIT Building E-51, Room 315
Summary:
Red Hat's new OCID container system, an alternative to Docker
Abstract:
OCID (CRI-O) is a container runtime to be used with the Kubernetes
Kublet. Specifically, it implements the Kubelet Container Runtime
Interface (CRI) using OCI conformant runtimes. The goal of the OCID is
to optimize running of containers in production, via Kubernetes and
OpenShift.
At a high level, we expect the scope of OCID:
Support multiple image formats including the existing Docker image format
Support for multiple means to download images including trust & image
verification
Container image management (managing image layers, overlay filesystems, etc)
Container process lifecycle management
Monitoring and logging required to satisfy the CRI
Resource isolation as required by the CRI
Second part of the talk will cover Container Security. We will cover all
parts of container security from the importance of the kernel, to where
you should run your containers, container separation and what you should
run inside
Red Hat's OCID is a Docker Alternative, But Not a Fork :
http://containerjournal.com/2016/10/04/red-hats-ocid-docker-alternative-not-fork/
Running production applications in containers: Introducing OCID :
https://www.redhat.com/en/about/blog/running-production-applications-containers-introducing-ocid
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Wednesday, January 11, 2017
Boston Linux Meeting Wednesday, January 18, 2017 - Red Hat OCID and Container Security
When: January 18, 2017 7PM (6:30PM for Q&A)
Topic: Red Hat OCID and Container Security
Moderator: Daniel J Walsh , Lead SELinux Engineer , Red Hat Software
Location: MIT Building E-51, Room 315
Summary:
Red Hat's new OCID container system, an alternative to Docker
Abstract:
OCID (CRI-O) is a container runtime to be used with the Kubernetes
Kublet. Specifically, it implements the Kubelet Container Runtime
Interface (CRI) using OCI conformant runtimes. The goal of the OCID is
to optimize running of containers in production, via Kubernetes and
OpenShift.
At a high level, we expect the scope of OCID:
Support multiple image formats including the existing Docker image format
Support for multiple means to download images including trust & image
verification
Container image management (managing image layers, overlay filesystems, etc)
Container process lifecycle management
Monitoring and logging required to satisfy the CRI
Resource isolation as required by the CRI
Second part of the talk will cover Container Security. We will cover all
parts of container security from the importance of the kernel, to where
you should run your containers, container separation and what you should
run inside
Red Hat's OCID is a Docker Alternative, But Not a Fork :
http://containerjournal.com/2016/10/04/red-hats-ocid-docker-alternative-not-fork/
Running production applications in containers: Introducing OCID :
https://www.redhat.com/en/about/blog/running-production-applications-containers-introducing-ocid
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Topic: Red Hat OCID and Container Security
Moderator: Daniel J Walsh , Lead SELinux Engineer , Red Hat Software
Location: MIT Building E-51, Room 315
Summary:
Red Hat's new OCID container system, an alternative to Docker
Abstract:
OCID (CRI-O) is a container runtime to be used with the Kubernetes
Kublet. Specifically, it implements the Kubelet Container Runtime
Interface (CRI) using OCI conformant runtimes. The goal of the OCID is
to optimize running of containers in production, via Kubernetes and
OpenShift.
At a high level, we expect the scope of OCID:
Support multiple image formats including the existing Docker image format
Support for multiple means to download images including trust & image
verification
Container image management (managing image layers, overlay filesystems, etc)
Container process lifecycle management
Monitoring and logging required to satisfy the CRI
Resource isolation as required by the CRI
Second part of the talk will cover Container Security. We will cover all
parts of container security from the importance of the kernel, to where
you should run your containers, container separation and what you should
run inside
Red Hat's OCID is a Docker Alternative, But Not a Fork :
http://containerjournal.com/2016/10/04/red-hats-ocid-docker-alternative-not-fork/
Running production applications in containers: Introducing OCID :
https://www.redhat.com/en/about/blog/running-production-applications-containers-introducing-ocid
For further information and directions please consult the BLU Web site
http://www.blu.org
Please note that there is usually plenty of free parking in the E-51
parking lot at 2 Amherst St, or directly on Amherst St.
After the meeting we will adjourn to the official after meeting meeting
location at The Cambridge Brewing Company
http://www.cambridgebrewingcompany.com/
--
Jerry Feldman <gaf@blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66 C0AF 7CEA 30FC 3BC1 EB90
_______________________________________________
Announce mailing list
Announce@blu.org
http://lists.blu.org/mailman/listinfo/announce
Subscribe to:
Posts (Atom)