https://wiki.hackrva.org/api.php?action=feedcontributions&user=Dfire&feedformat=atomHackRVA - User contributions [en]2024-03-29T10:30:38ZUser contributionsMediaWiki 1.38.7https://wiki.hackrva.org/index.php?title=Terms_and_Conditions&diff=2810Terms and Conditions2021-07-11T18:04:55Z<p>Dfire: /* Non-Members and Guests in the Makerspace */</p>
<hr />
<div> WARNING! THIS PAGE IS A LIVING DOCUMENT. NOT ALL AREAS ARE COVERED, BUT MOST ARE - CHECK WITH ANOTHER MEMBER IF THERE ARE ANY QUESTIONS.<br />
<font size=8>HackRVA Terms and Conditions</font><br />
<br />
=Membership=<br />
==Becoming a HackRVA Member==<br />
Go here to join - [http://www.hackrva.org/blog/membership/ Membership Signup]<br />
<br />
==Being an Active Member==<br />
* Paying dues makes someone a member of hackrva.<br />
* The stopping of paying dues stops membership.<br />
* We ask that members contribute to the hackrva community as their time and talents allow. This is a community, not a service.<br />
* The new members area has more info on this - [https://wiki.hackrva.org/index.php/New_Members]<br />
<br />
==Billing==<br />
* All members are billed monthly starting on the day that they sign up and the same day on each subsequent month going forward.<br />
* All billing is handled via PayPal Subscription. <br />
* We don't use cash billing. Any cash given to us will be happily accepted as a donation, but we only use PayPal for memberships. We know this may not be ideal for some people but in order to stay solvent we've found recurring billing is the best way.<br />
<br />
==Changing Membership Level==<br />
* Membership levels are defined [[Membership Levels|here]]<br />
* Email us at info@hackrva.org at least 2 weeks prior to the next billing date<br />
* Please try and keep this limited to 1-2 times per year.<br />
<br />
==Cancelling Membership==<br />
Please consider continuing to support us, even if you are not using the space now. <br />
Remember that we are all keeping the makerspace alive and thriving in our spare time. We're volunteers instead of a business so please keep that in mind.<br />
* To stop membership, go to PayPal and log into your account. Stop the automatic monthly payment: <br />
**Go to paypal.com, and log in. <br />
**In your account activity, click one of the payments to Hackrva Labs, Inc.<br />
**Click the link Manage Hackrva Labs, Inc payments.<br />
**Click Cancel.<br />
Your fob will then be deactivated. If you plan to rejoin later, hold on to your fob. It will be reactivated when you start paying.<br />
<br />
=Makerspace Guidelines=<br />
==Security==<br />
===Doors===<br />
* Be sure to lock the door if you are the last member to leave. We are working on making all 3 doors automatically lock. That also means you must be sure to keep your keys with you if you go outside!<br />
* Do not make copies of hackrva keys or RFID fobs.<br />
<br />
===Personal Belongings===<br />
* Personal belongings/equipment are left at your own risk. If you forgot something, post on Slack.<br />
<br />
===Non-Members and Guests in the Makerspace===<br />
* Don't bring anyone into the makerspace that you don't wholly trust.<br />
* You are responsible for the actions of your guest while they are at the makerspace.<br />
* Non-members are not allowed to use tools. This is a liability issue. You are responsible for damage they cause.<br />
<br />
==Housekeeping==<br />
* Do not leave any food. We must avoid a roach or mouse problem.<br />
* Return all tools and supplies to where they belong after you are done with them.<br />
* Turn off lights when you leave.<br />
* Do not leave small electronics on, especially things like soldering irons, etc.<br />
* Take out the trash and recycling when it is full.<br />
* Clean up after yourself. There is no staff. <br />
* Anything not in your storage box may be mistaken as donations. Larger projects and items should be labeled with a parking permit to avoid confusion.<br />
* Larger projects and items should not be left at the space without a parking permit. <br />
* Thumbs Up/Down rule on loud music and video. <br />
* Do not make changes or modifications to the building or facilities without clearing it with hack.rva leadership. This includes making holes in the walls larger than a screw hole. <br />
* Do not remove equipment from the space. (There is a project to create a lending library, so those tools are the exception.) Some other smaller tools (owned by hack.rva) may be allowed with permission from hackrva leadership on Slack, for hours, not days.<br />
* If a tool is broken or working improperly, put a Damaged/Broken ticket on it, and contact the [[HackRAT| '''HackRAT'''s]] on Slack so they can assess repairs needed.<br />
<br />
==Damages==<br />
* A member is responsible for any damage done to the space, equipment or other people's belongings done by them or their guests.<br />
<br />
==Parking Permits==<br />
We use a system of tags to mark materials and equipment. Blanks are on the counter in the main room, under the cabinets.<br />
**Parking Permit (green) This is what a member puts on projects or materials being left 'temporarily' meaning about 2 weeks. It must be filled out with contact information so the owner can be reached. It can be renewed, and as long as you are working on a project, that is generally not a problem.<br />
**Parking ticket (orange) Anyone who finds things left without a permit, or with a permit over a month old can put a Parking Ticket on it, and try to contact the owner.<br />
**Up for grabs (blue?) If the owner of the ticketed materials does not respond within 2 weeks, the material is either claimed by Hack.RVA, or tagged with an ''Up for Grabs'' ticket. Another member may claim the material. (This may sound extreme, but we have had large furniture sit for a year. We don't have the space.)<br />
**Broken or Damaged (red) For equipment or tools. Please explain what is wrong, and if possible, how it got that way. On Slack, report it on the appropriate channel so we can fix it. Post a picture of the model number and identifying info so we can easily order parts.<br />
<br />
==Consumable Supplies==<br />
We have some bits, blades, etc. for the tools, but if you want something specific, bring your own.<br />
We have a small budget to provide consumables to the space. We supply 'some':<br />
* 3d printer filament<br />
* Self-adhesive vinyl for the small vinyl cutter<br />
* Basic blades for the band saw, table saw<br />
* Sandpaper for belt sanders, etc.<br />
* Trash bags, paper towels, cleaning supplies<br />
<br />
If you have extra of something please consider donating. You can donate freely or if you'd like a receipt, go [[Terms and Conditions#Donating|here]].<br />
* Screws, Nails, Bolts are welcome<br />
* 3D Printer filament (especially if you plan to use a lot - it may be best to keep your own roll)<br />
* Stock pieces (wood, metal, plastic, etc.)<br />
<br />
We do not supply:<br />
* Cups<br />
* Coffee<br />
* Spoons, forks, knives<br />
<br />
==Events, Workshops, Meetings==<br />
* No. During COVID restrictions, we will not have any group activites.<br><br><br />
These rules will be active again some time in the future when we can return to normal:<br />
* The hackrva schedule is publicly available for all to know at http://www.hackrva.org/blog/calendar/<br />
* It is the members responsibility to be aware of the calendar.<br />
* Free-hack days have been established so that no events are allowed on those days in order to balance the needs of events, workshops, and meetings against individual members who need times to work with out restriction. check the calendar for Free-hack days. <br />
* Use of the any part or all of the space may be restricted because of an event, workshop, or meetings. This is at the discretion of the organizer.<br />
* Disruption of events, workshops, or meetings should be avoided. The organizer will decide what is disruptive and if that activity should stop. <br />
* If you're hosting something, please clean up any mess you make in the Meeting Room<br />
* If you leave something, the people who clean up after you reserve the right to claim and/or trash anything you leave<br />
<br />
==Guests==<br />
'''Due to COVID-19 restrictions guests are not currently allowed<br><br><br />
These rules will be active again some time in the future when we can return to normal:<br><br />
*''Members are responsible for their guests''<br><br />
*''Guests are not entitled to storage or access to equipment''<br><br />
*''Guests should be supervised at all times''<br><br />
*''Guests that cause disruption can be asked to leave at anytime''<br><br />
*''Guests are discouraged during schedule events and workshops unless they are there to participate in that specific event or workshop''<br />
<br />
==Photography==<br />
* Pictures will be taken at HackRVA and our events. This includes you, guests, and projects.<br />
* You're welcome to decline photos, but don't be offended if someone attempts to take one.<br />
* In general, don't post things to HackRVA Slack, Flickr, Facebook, or any other HackRVA thing that you don't want posted other places. <br />
* We don't do attribution on photos for our blogs or anywhere else unless specifically asked.<br />
* We will remove photos by request.<br />
<br />
==Minors==<br />
HackRVA Policy on Minors<br />
<br />
Kids are awesome! HackRVA sponsors many special events that focus on learning for a younger age group, such as Maker Camp and Maker Guild. We also realize the need for safety and clear guidelines regarding minors. We've created this policy to make HackRVA a stronger organization that caters to a diverse set of needs while keeping in mind the limitations of our organization.<br />
<br />
Our age guidelines are as follows:<br />
<br />
*Saturdays are typically adults only. The exception being a minor focused event held on Saturday, which would be in the description on the calender/meetup page.<br />
<br />
*Members should have no more than 2 minors with them at any time unless it is a minor designated event.<br />
<br />
*There should be no more than 5 minors at the space at a time unless it is a minor designated event.<br />
<br />
*0-5 years old - Wait until they're older to bring them to the space.<br />
<br />
*6-12 - Welcomed at special "kid-friendly" events only. Must be accompanied by a guardian at those events. The Tech-lab and wood shop are restricted for this age group.<br />
<br />
*13-14 - Welcome to the space anytime with direct adult supervision(except Saturdays). The Tech-lab and wood shop are restricted for this age group.<br />
<br />
*15-17 - Welcome to the space anytime with direct adult supervision(except Saturdays). The Tech-lab is available on a case by case basis with proper training and consistent guardian supervision.<br />
<br />
We've also created a guide for young makers in Richmond, see here: [[Young Makers]].<br />
<br />
Kid-Friendly Events General Use Tech-lab Saturdays<br />
(Makerguild) (w/ Guardian) (hackathons)<br />
(LEGO League, etc.) (except Saturdays) <br />
AGE <br />
0-5 NO NO NO NO <br />
6-12 YES NO NO NO<br />
13-14 YES YES NO NO<br />
15-17 YES YES case-by-case NO<br />
<br />
=Donating=<br />
We accept donations by credit/debit card or PayPal via a donation button on our website that links to [https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=84JTAZFP72MMC here]. We also accept donations by check in person. Checks must be made out to "HackRVA Labs"<br />
<br />
==Tools, Materials, In-Kind==<br />
At this time we are generally not accepting donations of equipment or materials. This is largely a space issue: the current space is pretty full. Financial contributions are always welcome. If you have something you think we really need for some reason, ask on Slack first. Also, you can offer it on the "UpForGrabs" channel on our Slack account ([[Online Chat Channel]]).<br />
<br />
If you have any questions, you can ask mailto://info@hackrva.org. And, if you coordinate a drop-off/pick-up exchange on the mailing list, please follow-up on it.<br />
<br />
==Membership for Donations==<br />
HackRVA doesn't trade membership for donations of tools or goods.<br />
<br />
=Safety=<br />
* Please get at least a little training on all wood shop tools. They may seem simple but they are powerful, and there are ways they can hurt you that you may not know.<br />
* If you need training, ask a person in the space or contact [[HackRAT| the HackRAT's]] on Slack and we'll coordinate a training opportunity.<br />
* Common Sense rules the day at the makerspace. <br />
* Please do not run with scissors, stick things in electrical sockets, or endanger anyone at any time<br />
* Safety is not just about you. You may be okay with the danger, but you must not endanger other members. <br />
<br />
===Proper Ventilation===<br />
* Please ensure you have proper ventilation when your project needs it. Work outside if fumes are dangerous.<br />
* Aerosol (spray) paint is not allowed inside the space. You can paint outside, but use a drop cloth so your over-spray does not hit walls or pavement. If the paint is warm, and the object is warm, you can paint in the cold and bring it inside to dry. <br />
* Filling the makerspace with fumes and smoke will not earn you friends or cool points.<br />
<br />
===First Aid===<br />
* There is a first aid kit in the makerspace for use when needed<br />
===Fire Extinguishers===<br />
* There are multiple fire extinguishers in the makerspace, one in each room, 2 in the wood shop. <br />
* Please be familiar with their locations for use when needed<br />
* Please be aware of the areas around the fire extinguishers (marked in red tape). Do NOT leave any objects or furniture within the tape.<br />
* There is a special CO2 extinguisher by the laser cutter. Use only this one for the laser cutter. Other types will destroy the machine.<br />
<br />
===Damages===<br />
* Members are responsible for their guest's damages as well as their own. Guest must not operate any tools or equipment.<br />
<br />
==Alcohol==<br />
===In the Makerspace===<br />
* We know many of us enjoy a cold beer while hanging out. As long as you're over 21, that's fine.<br />
* HackRVA doesn't (typically) pay for the beer.<br />
* Do not use dangerous tools when you are having a beer. Don't drink and drill! Or use any other power tools.<br />
<br />
===Intoxication===<br />
* Members reserve the right to ask anyone to leave who is intoxicated, high, or not in a fit state to be around heavy machinery.<br />
<br />
=FAQ-Like-Thing of Additional Information=<br />
<br />
FAQ:<br />
<br />
- I read the above, but, what are you exactly, whats going on?<br />
<br />
We're a [https://en.wikipedia.org/wiki/Hackerspace makerspace/hackerspace(wikipedia)]. Sometimes we're referred to as a gym for the brain, a clubhouse for nerds, a mad-scientist's lair, or a preeminent basement. We're essentially a space filled with tools, computers, and curious people interested in knowledge and hands-on experience. Members pay dues and that provides the money to keep the space going. We are run by volunteers who are also members. No one owns the space and everyone contributes as they are able to see it flourish. If you're interested in a hobby or subject of knowledge that is technology or "makery" related you will likely find comradery here and a place to work on projects.<br />
<br />
<br />
- Whats a good way to find out if HackRVA is a good fit for me?<br />
<br />
For now, we are not allowing group events. We have a few online meetings on MeetUp. Join our [http://www.meetup.com/HackRVA-Meetup/ HackRVA Meetup] group and watch for a workshop or event that interests you. Some are members only, and others are open to the public. Some are free, and some have a cost.<br />
You can contact us at info@hackrva.org for a tour.<br />
<br />
<br />
- What kinds of stuff are you mostly into?<br />
<br />
We are interested in all forms of making. Our members do computer related activities (code, networking, video games, digital creations), electronics, woodworking, metalworking, mechanical stuff, and adjacent nerdery. Tools, craft, code, engineering, science, and invention are at the forefront, but we also enjoy art, design,and all things fabricated and creative. For a complete-ish list, see the bottom of this page.<br />
<br />
<br />
- I don't know how to use these tools. Will someone teach me?<br />
<br />
Yes. We do this through workshops on a fairly regular basis, but more often we do it as a natural part of our community through one-on-one experiences. If you become a member, contribute to our organization, and are around enough to get to know people, someone will train you, show you, help you. Typically people get what they put in. Also, Saturdays are great day to learn tools - there are almost always knowledgeable people around willing to take 20 or 30 minutes to show you the basics. Watching YouTube videos, reading about our tools on our wiki, and being willing to try new things also help and show initiative. The wiki is a great source, although it can often use some updates.<br />
<br />
<br />
- I've never made anything before. Will I fit in?<br />
<br />
Yes and absolutely. Many of our most active members have never made anything before joining HackRVA. Some have since become maker addicts. You've been warned.<br />
<br />
<br />
- Where are you?<br />
<br />
Scott's Addition behind the Dairy bar at [https://www.google.com/maps/place/HackRVA+Labs,+Inc./@37.5708732,-77.4754977,17z/data=!4m6!1m3!3m2!1s0x89b11403aa442d61:0xe5b7ad02f80c107a!2sHackRVA+Labs,+Inc.!3m1!1s0x89b11403aa442d61:0xe5b7ad02f80c107a 1600 Roseneath Road - Suite E, Richmond, VA 23230]. That is our mailing address, but it takes you to the opposite side of the building. Set GPS for 3920 W. Moore, 23230 to find our door. Don't park in the lot at night without a parking pass. They will tow.<br />
<br />
<br />
-Do you have open hours for the public?<br />
<br />
No. Our members have keys and use the space at their discretion. No one works at HackRVA and we don't keep regular hours like a business. If you'd like to visit, contact us at info [at] hackrva.org and we can arrange for someone show you around.<br />
<br />
<br />
- Can I donate tools or materials to HackRVA?<br />
<br />
Generally, [http://www.hackrva.org/wiki/index.php?title=Terms_and_Conditions#Donating no]. We might like something, but we don't have unlimited space. But things like old computers and electronics are not useful enough to store. Contact us at info [at] hackrva.org if you think we would like a donation.<br />
<br />
- Can I teach a workshop?<br />
<br />
Yes - most workshops are presented by HackRVA members, but we love any opportunity to learn. HackRVA is as much a place to teach as it is to learn, improve skills, and make stuff. [http://www.hackrva.org/blog/contact/ Contact us] if you'd like to host a workshop. We can do it virtually. <br />
<br />
<br />
- What about kids?<br />
<br />
HackRVA is [http://www.hackrva.org/wiki/index.php?title=Terms_and_Conditions#Minors adult oriented.] We have hosted some kid-friendly events in the past, but we have many dangerous machines that we sometimes worry about the adults using them.<br />
<br />
<br />
- What are the rules of this land?<br />
<br />
[http://www.hackrva.org/wiki/index.php?title=Terms_and_Conditions Complete Details] - How being a member works.<br />
<br />
<br />
- Where do I go to learn lots of other things about HackRVA?<br />
<br />
Go to [http://www.hackrva.org/wiki/index.php?title=Main_Page our wiki] - its not always complete or up-to-date, but its where we huddle together to digitally organize the space. We've also littered the web with our offerings, most of which can be found by clicking through the links on the right side-bar of this website. For current events, follow us on [https://www.meetup.com/HackRVA-Meetup/ MeetUp]<br />
<br />
<br />
- Does HackRVA do projects for money for other people?<br />
<br />
No. We're not a prototyping business or service.<br />
<br />
<br />
- Can I invent and prototype something at HackRVA?<br />
<br />
Certainly. We do that all the time. Often members are just trying to solve a problem or fix something, but other times they invent something new. <br />
<br />
- I'm a professional 'X' looking for a workshop, is HackRVA for me?<br />
<br />
Possibly, but expectations should be managed. The place isn't always clean (depending on standards), things get moved a lot, tools break and don't get fixed until a member volunteers to fix them - stuff happens. HackRVA isn't a professional shop. We aspire to ever better tools and organization, but with over a hundred members, things are always changing. On the other hand, we love it when industrial designers, maker-pros, artisans, artists, and other professionals of the maker world join our space. We revel in your shared knowledge and skills. And there are typically enough tools here to make most things with some patience. It's not uncommon for our hardcore makers to keep a personal set of bits and blades around so they know it will work. Or even bring in their own tools.<br />
<br />
<br />
- Your space isn't giant and there's a lot of people. Do you get crowded?<br />
<br />
Typically, no. During the weekdays the space is usualy quiet. Some people come here for a co-working experience as they mash buttons on computers, using our high-speed WiFi. Weekday evenings are often quiet, though we do have regular events you should check on before coming. Saturday afternoons and evenings tend to be busy and and members sign up to reserve a tool or area. (Sign up for the morning to get the place to yourself). In general, we have enough room to do most projects, but we often have to get creative and some work is just best done outside, either because of scale or fumes or heat.</div>Dfirehttps://wiki.hackrva.org/index.php?title=Quarterly_Goal_Progress&diff=2368Quarterly Goal Progress2019-04-19T16:17:31Z<p>Dfire: /* Documents */</p>
<hr />
<div>This page will serve as a log to document progress toward our [[The HackRVA Quarterly Goal|quarterly goals]] <br />
It's important to report and celebrate our progress. <br />
=2019=<br />
==Q1 - Improve member on-boarding & new member experience==<br />
We had a late start to Q1, but we managed to get a lot done. Several new members have received orientation which helps them become better equipped to use the space and they now know where and how to find help when needed.<br />
<br />
===What did we accomplish?===<br />
#We had a planning session<br />
#We had a meetup where we executed several ideas<br />
#New Member On-boarding Process -- defined and documented<br />
#New Member Orientation Process -- orientation checklist made<br />
#Member Sign up Station (tablet on table under TV)<br />
#Name-Tags -- diy or low-tech paper<br />
#Purchased some safety equipment (e.g. hair ties, first aid kits, etc...)<br />
#Fixed automated Slack invite<br />
#Member Handbook/Welcome Packet -- kicked off/in progress<br />
<br />
===How did we celebrate?===<br />
A big part of this process is to report and celebrate progress.<br />
<br />
We signed up several members while we worked on the new on-boarding process and most importantly '''we had an awesome cookout.''' :)<br />
<br />
Overall, it has been a great success.<br />
Read more [https://www.hackrva.org/blog/2019/04/the-quarterly-goal-initiative/ here]<br />
<br />
==Q2 - Remodel Front Room and build framework for space sponsored group projects==<br />
In Q2 we plan on remodeling the front room to better declare that space. It is the face of HackRVA and typically the first thing people see when they walk in. We can do a lot to reduce clutter, improve storage, and make better use of the space. In addition to the remodel, we will have a team building an arcade cabinet as a way to bootstrap space sponsored group projects. <br />
<br />
===Documents===<br />
<br />
[https://docs.google.com/document/d/1rPHbfcFTewjhwVoVQGBwUQnHrn5ptzOGZ08VeOIOSkg/edit?usp=sharing 2019-Q2 Planning]<br />
<br />
[https://docs.google.com/document/d/1imq_9-dPCTdJD6__ugFaNtUiEOMvwRZ9e1Q5bb-WHBA/edit?usp=sharing Front Room Remodel BOM]<br />
<br />
[https://docs.google.com/spreadsheets/d/1hBQQDJYRVAH7vYnQDXLnaL13IKoUVRhqYooF4QoOvwI/edit Arcade Cabinet BOM]</div>Dfirehttps://wiki.hackrva.org/index.php?title=Quarterly_Goal_Progress&diff=2366Quarterly Goal Progress2019-04-13T17:00:55Z<p>Dfire: </p>
<hr />
<div>This page will serve as a log to document progress toward our [[The HackRVA Quarterly Goal|quarterly goals]] <br />
It's important to report and celebrate our progress. <br />
=2019=<br />
==Q1 - Improve member on-boarding & new member experience==<br />
We had a late start to Q1, but we managed to get a lot done. Several new members have received orientation which helps them become better equipped to use the space and they now know where and how to find help when needed.<br />
<br />
===What did we accomplish?===<br />
#We had a planning session<br />
#We had a meetup where we executed several ideas<br />
#New Member On-boarding Process -- defined and documented<br />
#New Member Orientation Process -- orientation checklist made<br />
#Member Sign up Station (tablet on table under TV)<br />
#Name-Tags -- diy or low-tech paper<br />
#Purchased some safety equipment (e.g. hair ties, first aid kits, etc...)<br />
#Fixed automated Slack invite<br />
#Member Handbook/Welcome Packet -- kicked off/in progress<br />
<br />
===How did we celebrate?===<br />
A big part of this process is to report and celebrate progress.<br />
<br />
We signed up several members while we worked on the new on-boarding process and most importantly '''we had an awesome cookout.''' :)<br />
<br />
Overall, it has been a great success.<br />
Read more [https://www.hackrva.org/blog/2019/04/the-quarterly-goal-initiative/ here]<br />
<br />
==Q2 - Remodel Front Room and build framework for space sponsored group projects==<br />
In Q2 we plan on remodeling the front room to better declare that space. It is the face of HackRVA and typically the first thing people see when they walk in. We can do a lot to reduce clutter, improve storage, and make better use of the space. In addition to the remodel, we will have a team building an arcade cabinet as a way to bootstrap space sponsored group projects. <br />
<br />
===Documents===<br />
<br />
[https://docs.google.com/document/d/1rPHbfcFTewjhwVoVQGBwUQnHrn5ptzOGZ08VeOIOSkg/edit?usp=sharing 2019-Q2 Planning]<br />
<br />
[https://docs.google.com/document/d/1imq_9-dPCTdJD6__ugFaNtUiEOMvwRZ9e1Q5bb-WHBA/edit?usp=sharing Front Room Remodel BOM]<br />
<br />
[https://docs.google.com/document/d/1k2LAgRHz_fUwKusS0QKmFSsKSVxHxHyID5OS1uCPQPA/edit?usp=sharing Arcade Cabinet BOM]</div>Dfirehttps://wiki.hackrva.org/index.php?title=Quarterly_Goal_Progress&diff=2365Quarterly Goal Progress2019-04-13T16:55:26Z<p>Dfire: </p>
<hr />
<div>This page will serve as a log to document progress toward our [[The HackRVA Quarterly Goal|quarterly goals]] <br />
It's important to report and celebrate our progress. <br />
=2019=<br />
==Q1 - Improve member on-boarding & new member experience==<br />
We had a late start to Q1, but we managed to get a lot done. Several new members have received orientation which helps them become better equipped to use the space and they now know where and how to find help when needed.<br />
<br />
===What did we accomplish?===<br />
#We had a planning session<br />
#We had a meetup where we executed several ideas<br />
#New Member On-boarding Process -- defined and documented<br />
#New Member Orientation Process -- orientation checklist made<br />
#Member Sign up Station (tablet on table under TV)<br />
#Name-Tags -- diy or low-tech paper<br />
#Purchased some safety equipment (e.g. hair ties, first aid kits, etc...)<br />
#Fixed automated Slack invite<br />
#Member Handbook/Welcome Packet -- kicked off/in progress<br />
<br />
===How did we celebrate?===<br />
A big part of this process is to report and celebrate progress.<br />
<br />
We signed up several members while we worked on the new on-boarding process and most importantly '''we had an awesome cookout.''' :)<br />
<br />
Overall, it has been a great success.<br />
<br />
==Q2 - Remodel Front Room and build framework for space sponsored group projects==<br />
<br />
===Documents===<br />
<br />
[https://docs.google.com/document/d/1rPHbfcFTewjhwVoVQGBwUQnHrn5ptzOGZ08VeOIOSkg/edit?usp=sharing 2019-Q2 Planning]<br />
<br />
[https://docs.google.com/document/d/1imq_9-dPCTdJD6__ugFaNtUiEOMvwRZ9e1Q5bb-WHBA/edit?usp=sharing Front Room Remodel BOM]<br />
<br />
[https://docs.google.com/document/d/1k2LAgRHz_fUwKusS0QKmFSsKSVxHxHyID5OS1uCPQPA/edit?usp=sharing Arcade Cabinet BOM]</div>Dfirehttps://wiki.hackrva.org/index.php?title=Quarterly_Goal_Progress&diff=2362Quarterly Goal Progress2019-04-02T21:43:21Z<p>Dfire: adding "how did we celebrate"</p>
<hr />
<div>This page will serve as a log to document progress toward our [[The HackRVA Quarterly Goal|quarterly goals]] <br />
It's important to report and celebrate our progress. <br />
=2019=<br />
==Q1 - Improve member on-boarding & new member experience==<br />
We had a late start to Q1, but we managed to get a lot done. Several new members have received orientation which helps them become better equipped to use the space and they now know where and how to find help when needed.<br />
<br />
===What did we accomplish?===<br />
#We had a planning session<br />
#We had a meetup where we executed several ideas<br />
#New Member On-boarding Process -- defined and documented<br />
#New Member Orientation Process -- orientation checklist made<br />
#Member Sign up Station (tablet on table under TV)<br />
#Name-Tags -- diy or low-tech paper<br />
#Purchased some safety equipment (e.g. hair ties, first aid kits, etc...)<br />
#Fixed automated Slack invite<br />
#Member Handbook/Welcome Packet -- kicked off/in progress<br />
<br />
===How did we celebrate?===<br />
A big part of this process is to report and celebrate progress.<br />
<br />
We signed up several members while we worked on the new on-boarding process and most importantly '''we had an awesome cookout.''' :)<br />
<br />
Overall, it has been a great success.</div>Dfirehttps://wiki.hackrva.org/index.php?title=On_boarding_members&diff=2361On boarding members2019-04-02T21:35:51Z<p>Dfire: </p>
<hr />
<div>This page documents the process to on board new members to all of the systems at HackRVA.<br />
<br />
[https://docs.google.com/document/d/1sGMCOwcHUd8IB6zGn3W0kjhnWGI3tUQ8NYqx_2_fDpQ/edit?usp=sharing Editable-Member Orientation Checklist]<br/><br />
[[Media:Member Orientation Checklist v0.0.1.pdf| Printable-Member Orientation Checklist]]<br/><br />
<br />
<br />
<br />
# Have the new member sign up on paypal at https://www.hackrva.org/blog/membership/<br />
# Have the new member read and sign the [[Media:HackrvaMembershipAgreement.pdf|hackrva membership agreement and liability waiver]]<br />
# Go to [http://10.200.200.11 the membership portal] ( you must be on the internal network)<br />
## Enter the email address that the new member used to sign up in paypal<br />
## If you see an error message that says something like <q>There are no recorded payments in the last month from <email></q> then either the new member did not successfully subscribe on paypal or they used another email address. have them review their paypal information and retry<br />
## You will then come to a screen where it asks for the rfid tag number:<br />
::::* Get the new member an rfid tag and grab the usb scanner from the drawer in the main room under the tv<br />
::::* Scan the tag with the scanner so it fills in the rfid field on the form (if you run into difficulty, you can enter this manually - the number is imprinted on the tag)<br />
::::* Once you submit the form the new member will receive a slack invite and will be able to use their rfid tag.<br />
::::* Test the rfid tag on the outer door to make sure the new member can gain access.</div>Dfirehttps://wiki.hackrva.org/index.php?title=The_HackRVA_Quarterly_Goal&diff=2360The HackRVA Quarterly Goal2019-03-28T16:13:25Z<p>Dfire: Created page with "=What is The Quarterly Goal= The quarterly goal initiative is a vehicle for enabling members to contribute to driving the space forward. We rally together to determine what t..."</p>
<hr />
<div>=What is The Quarterly Goal=<br />
The quarterly goal initiative is a vehicle for enabling members to contribute to driving the space forward.<br />
<br />
We rally together to determine what the major areas of improvement are and define a goal. Then we plan and execute changes that work toward that goal. <br />
<br />
==High Level==<br />
#Choose a goal<br />
#Brainstorm ideas that work toward that goal<br />
#Complete tasks that work toward that goal<br />
#Report and celebrate progress<br />
<br />
Join the conversation on the #BHAG slack channel.<br />
<br />
See [[Quarterly Goal Progress]]</div>Dfirehttps://wiki.hackrva.org/index.php?title=Quarterly_Goal_Progress&diff=2359Quarterly Goal Progress2019-03-28T16:13:00Z<p>Dfire: Created page with "This page will serve as a log to document progress toward our quarterly goals It's important to report and celebrate our progress. =2019= ==Q1..."</p>
<hr />
<div>This page will serve as a log to document progress toward our [[The HackRVA Quarterly Goal|quarterly goals]] <br />
It's important to report and celebrate our progress. <br />
=2019=<br />
==Q1 - Improve member on-boarding & new member experience==<br />
We had a late start to Q1, but we managed to get a lot done. Several new members have received orientation which helps them become better equipped to use the space and they now know where and how to find help when needed.<br />
<br />
===What did we accomplish?===<br />
#We had a planning session<br />
#We had a meetup where we executed several ideas<br />
#New Member On-boarding Process -- defined and documented<br />
#New Member Orientation Process -- orientation checklist made<br />
#Member Sign up Station (tablet on table under TV)<br />
#Name-Tags -- diy or low-tech paper<br />
#Purchased some safety equipment (e.g. hair ties, first aid kits, etc...)<br />
#Fixed automated Slack invite<br />
#Member Handbook/Welcome Packet -- kicked off/in progress<br />
<br />
===How did we celebrate?===<br />
tbd</div>Dfirehttps://wiki.hackrva.org/index.php?title=Getting_Involved&diff=2358Getting Involved2019-03-28T16:04:27Z<p>Dfire: </p>
<hr />
<div><br />
==The 3 Hour Rule==<br />
''If you have an idea about what might make the space better, it's best to discuss with several other members, but we do have an '''unofficial rule''' that we refer to as "the 3 hour rule"''<br />
<blockquote>It is generally acceptable to make a change to the space as long as it can be undone in 3hours or less (by you,) if it is deemed to be an undesirable change.</blockquote><br />
<br />
==Forming a Committee==<br />
<br />
You may notice a need or have a desire to change something at HackRVA. We have found that one effective way to make big changes is to form a committee. This committee will take it upon themselves to make informed decisions and plan how to execute changes. The committee will then report to the Monthly Membership meeting before enacting the changes. <br />
<br />
When large build outs or large HackRVA projects are presented to the monthly membership meeting. We should encourage a committee to be formed to plan and execute. This will reduce the planning that happens at membership meetings and allow for more than just one topic to be discussed at the meeting.<br />
<br />
===How To Form a Committee===<br />
*Attend a member meeting (last Wednesday of the month) or join the #leadership channel on slack<br />
**state your idea/plan and declare that you would like to form a committee to accomplish the goal,task,project, and/or change.<br />
**share with membership that the committee exists and what its goal/purpose is.<br />
*Start a Slack channel (This is optional, but can be a great way to communicate)<br />
*Schedule meetings to plan or discuss entirely on slack channel<br />
*Schedule time to execute plans<br />
<br />
Be sure to report progress back to the membership (either at a member meeting or the #leadership channel on slack)<br />
<br />
===Some examples of successful committees:===<br />
*Room swap - Swapping the woodshop with the techlab<br />
*Purchasing the laser<br />
*Planning for secondary clean space<br />
*Building arts and crafts area/cabinets & counter in main room<br />
*XCarve restore and station build out<br />
<br />
<br />
If you have further questions about how to start a committee join the #leadership channel on slack.<br />
<br />
==The Quarterly Goal Initiative==<br />
[[The HackRVA Quarterly Goal]] initiative (we sometimes call it BHAG -- i.e. Big hairy audacious goal) is a quarterly drive to make progress and enable people to contribute to the space. Join the conversation on our slack channel #BHAG.<br />
<br />
==Volunteering at HackRVA==<br />
See the tasks whiteboard in the space for tasks that need to be complete.<br />
Or email, infoAThackrva.org for more specific details.<br />
<br />
(note: we've tried several iterations of digital management systems - so far a whiteboard kicks their butt)<br />
<br />
If you are experienced with a tool or know how to fix it, consider joining the [[HackRAT| HackRAT program]]<br />
<br />
==Other Sweet Volunteer Activities==<br />
<br />
*Join the [[HackRAT| HackRAT Program]] (Repair And Train) to help keep tools running and train others on their use.<br />
*Lead a [https://docs.google.com/spreadsheet/ccc?key=0Akt_buuj3P2jdHJRQVZzU0RFTTJuSmtvU1A2alpPWVE&usp=drive_web#gid=0/ workshop] (contact us and we'll set you up with meetup and assist with lesson plans if needed)<br />
*Start a new event (again, contact us, and we'll give you the social media tools to advertise)<br />
*Improve the Wiki (just create an account, and start adding useful info)<br />
*Post a project to the maker blog (anyone at HackRVA can be a blogger, just ask and we'll give you access)<br />
*Research and recommend a purchase (add them to our acquisitions spreadsheet (link needed))<br />
*Socialize with new folks during open house (Thursday nights)<br />
*Attend monthly business/board meetings and help figure out the way forward at HackRVA (see the calender for dates)<br />
<br />
<br />
<br />
==Deprecated:==<br />
'''HackRVA KanBoard - Improving the Space One Virtual Sticky Note at a Time'''<br />
<br />
We use the [[HackRVA KanBoard]] to do tasks around HackRVA.<br />
<br />
It's a project management tool for groups to get things done. We use it for things like cleaning, fixing things, and all the rest.<br />
<br />
Learn the details here - [[HackRVA KanBoard]].<br />
<br />
==<br />
<br />
[https://docs.google.com/spreadsheets/d/1KxUA6yGkUhzf6KzMVsPl26S2-VB6mK7SANiT7UCuz_4/edit#gid=902108231 Volunteer Sign Up Sheet]<br />
(this is one of our attempts at getting more people involved and worked for awhile. it's being deprecated )</div>Dfirehttps://wiki.hackrva.org/index.php?title=Getting_Involved&diff=2357Getting Involved2019-03-28T13:57:52Z<p>Dfire: moving 3 hour rule to the top</p>
<hr />
<div><br />
==The 3 Hour Rule==<br />
''If you have an idea about what might make the space better, it's best to discuss with several other members, but we do have an '''unofficial rule''' that we refer to as "the 3 hour rule"''<br />
<blockquote>It is generally acceptable to make a change to the space as long as it can be undone in 3hours or less (by you,) if it is deemed to be an undesirable change.</blockquote><br />
<br />
==Forming a Committee==<br />
<br />
You may notice a need or have a desire to change something at HackRVA. We have found that one effective way to make big changes is to form a committee. This committee will take it upon themselves to make informed decisions and plan how to execute changes. The committee will then report to the Monthly Membership meeting before enacting the changes. <br />
<br />
When large build outs or large HackRVA projects are presented to the monthly membership meeting. We should encourage a committee to be formed to plan and execute. This will reduce the planning that happens at membership meetings and allow for more than just one topic to be discussed at the meeting.<br />
<br />
===How To Form a Committee===<br />
*Attend a member meeting (last Wednesday of the month) or join the #leadership channel on slack<br />
**state your idea/plan and declare that you would like to form a committee to accomplish the goal,task,project, and/or change.<br />
**share with membership that the committee exists and what its goal/purpose is.<br />
*Start a Slack channel (This is optional, but can be a great way to communicate)<br />
*Schedule meetings to plan or discuss entirely on slack channel<br />
*Schedule time to execute plans<br />
<br />
Be sure to report progress back to the membership (either at a member meeting or the #leadership channel on slack)<br />
<br />
===Some examples of successful committees:===<br />
*Room swap - Swapping the woodshop with the techlab<br />
*Purchasing the laser<br />
*Planning for secondary clean space<br />
*Building arts and crafts area/cabinets & counter in main room<br />
*XCarve restore and station build out<br />
<br />
<br />
If you have further questions about how to start a committee join the #leadership channel on slack.<br />
<br />
==Volunteering at HackRVA==<br />
See the tasks whiteboard in the space for tasks that need to be complete.<br />
Or email, infoAThackrva.org for more specific details.<br />
<br />
(note: we've tried several iterations of digital management systems - so far a whiteboard kicks their butt)<br />
<br />
If you are experienced with a tool or know how to fix it, consider joining the [[HackRAT| HackRAT program]]<br />
<br />
==Other Sweet Volunteer Activities==<br />
<br />
*Join the [[HackRAT| HackRAT Program]] (Repair And Train) to help keep tools running and train others on their use.<br />
*Lead a [https://docs.google.com/spreadsheet/ccc?key=0Akt_buuj3P2jdHJRQVZzU0RFTTJuSmtvU1A2alpPWVE&usp=drive_web#gid=0/ workshop] (contact us and we'll set you up with meetup and assist with lesson plans if needed)<br />
*Start a new event (again, contact us, and we'll give you the social media tools to advertise)<br />
*Improve the Wiki (just create an account, and start adding useful info)<br />
*Post a project to the maker blog (anyone at HackRVA can be a blogger, just ask and we'll give you access)<br />
*Research and recommend a purchase (add them to our acquisitions spreadsheet (link needed))<br />
*Socialize with new folks during open house (Thursday nights)<br />
*Attend monthly business/board meetings and help figure out the way forward at HackRVA (see the calender for dates)<br />
<br />
<br />
<br />
==Deprecated:==<br />
'''HackRVA KanBoard - Improving the Space One Virtual Sticky Note at a Time'''<br />
<br />
We use the [[HackRVA KanBoard]] to do tasks around HackRVA.<br />
<br />
It's a project management tool for groups to get things done. We use it for things like cleaning, fixing things, and all the rest.<br />
<br />
Learn the details here - [[HackRVA KanBoard]].<br />
<br />
==<br />
<br />
[https://docs.google.com/spreadsheets/d/1KxUA6yGkUhzf6KzMVsPl26S2-VB6mK7SANiT7UCuz_4/edit#gid=902108231 Volunteer Sign Up Sheet]<br />
(this is one of our attempts at getting more people involved and worked for awhile. it's being deprecated )</div>Dfirehttps://wiki.hackrva.org/index.php?title=Getting_Involved&diff=2356Getting Involved2019-03-27T19:38:55Z<p>Dfire: /* Forming a Committee */</p>
<hr />
<div>==Forming a Committee==<br />
<br />
You may notice a need or have a desire to change something at HackRVA. We have found that one effective way to make big changes is to form a committee. This committee will take it upon themselves to make informed decisions and plan how to execute changes. The committee will then report to the Monthly Membership meeting before enacting the changes. <br />
<br />
When large build outs or large HackRVA projects are presented to the monthly membership meeting. We should encourage a committee to be formed to plan and execute. This will reduce the planning that happens at membership meetings and allow for more than just one topic to be discussed at the meeting.<br />
<br />
===How To Form a Committee===<br />
*Attend a member meeting (last Wednesday of the month) or join the #leadership channel on slack<br />
**state your idea/plan and declare that you would like to form a committee to accomplish the goal,task,project, and/or change.<br />
**share with membership that the committee exists and what its goal/purpose is.<br />
*Start a Slack channel (This is optional, but can be a great way to communicate)<br />
*Schedule meetings to plan or discuss entirely on slack channel<br />
*Schedule time to execute plans<br />
<br />
Be sure to report progress back to the membership (either at a member meeting or the #leadership channel on slack)<br />
<br />
===Some examples of successful committees:===<br />
*Room swap - Swapping the woodshop with the techlab<br />
*Purchasing the laser<br />
*Planning for secondary clean space<br />
*Building arts and crafts area/cabinets & counter in main room<br />
*XCarve restore and station build out<br />
<br />
<br />
If you have further questions about how to start a committee join the #leadership channel on slack.<br />
<br />
==The 3 Hour Rule==<br />
''If you have an idea about what might make the space better, it's best to discuss with several other members, but we do have an '''unofficial rule''' that we refer to as "the 3 hour rule"''<br />
<blockquote>It is generally acceptable to make a change to the space as long as it can be undone in 3hours or less (by you,) if it is deemed to be an undesirable change.</blockquote><br />
<br />
==Volunteering at HackRVA==<br />
See the tasks whiteboard in the space for tasks that need to be complete.<br />
Or email, infoAThackrva.org for more specific details.<br />
<br />
(note: we've tried several iterations of digital management systems - so far a whiteboard kicks their butt)<br />
<br />
If you are experienced with a tool or know how to fix it, consider joining the [[HackRAT| HackRAT program]]<br />
<br />
==Other Sweet Volunteer Activities==<br />
<br />
*Join the [[HackRAT| HackRAT Program]] (Repair And Train) to help keep tools running and train others on their use.<br />
*Lead a [https://docs.google.com/spreadsheet/ccc?key=0Akt_buuj3P2jdHJRQVZzU0RFTTJuSmtvU1A2alpPWVE&usp=drive_web#gid=0/ workshop] (contact us and we'll set you up with meetup and assist with lesson plans if needed)<br />
*Start a new event (again, contact us, and we'll give you the social media tools to advertise)<br />
*Improve the Wiki (just create an account, and start adding useful info)<br />
*Post a project to the maker blog (anyone at HackRVA can be a blogger, just ask and we'll give you access)<br />
*Research and recommend a purchase (add them to our acquisitions spreadsheet (link needed))<br />
*Socialize with new folks during open house (Thursday nights)<br />
*Attend monthly business/board meetings and help figure out the way forward at HackRVA (see the calender for dates)<br />
<br />
<br />
<br />
==Deprecated:==<br />
'''HackRVA KanBoard - Improving the Space One Virtual Sticky Note at a Time'''<br />
<br />
We use the [[HackRVA KanBoard]] to do tasks around HackRVA.<br />
<br />
It's a project management tool for groups to get things done. We use it for things like cleaning, fixing things, and all the rest.<br />
<br />
Learn the details here - [[HackRVA KanBoard]].<br />
<br />
==<br />
<br />
[https://docs.google.com/spreadsheets/d/1KxUA6yGkUhzf6KzMVsPl26S2-VB6mK7SANiT7UCuz_4/edit#gid=902108231 Volunteer Sign Up Sheet]<br />
(this is one of our attempts at getting more people involved and worked for awhile. it's being deprecated )</div>Dfirehttps://wiki.hackrva.org/index.php?title=Main_Page&diff=2355Main Page2019-03-27T18:22:28Z<p>Dfire: </p>
<hr />
<div>'''Welcome to HackRVA!!!'''<br />
<br />
HackRVA is a makerspace/hackerspace in Richmond, VA started in 2008. We're a self-funded and volunteer run non-profit dedicated to the art of making things in a fun and positive community.<br />
<br />
===Membership===<br />
* [http://www.hackrva.org/blog/membership/ Becoming a member] (back to main website)<br />
* [[Terms and Conditions]] - Policies of the space. How to navigate the space. Other good information. A must read.<br />
* [[Membership Levels]]<br />
* [[Terms_and_Conditions#Minors | Minor Policy]] - Minors at HackRVA.<br />
* Membership Agreement ([[Media:HackrvaMembershipAgreement.pdf|pdf]])<br />
* [[On boarding members]]<br />
<br />
===Community===<br />
*[[Online Chat Channel|Online Chat]]<br />
*[[Getting Involved|Getting Involved]]<br />
*[[Groups]] ''Find out about different interest groups at HackRVA.''<br />
*[[Member Pages | Member Bio Pages]]<br />
<br />
Quicklinks:<br />
*[https://hackrva.slack.com/messages/general/files/F02J2VCFG/ HackRVA Slack Channel] ''Where we chat on the internet - See [[Online Chat Channel]] for signup details''<br />
*[https://docs.google.com/presentation/d/1tYKz7UslQnXTdiLRI4jf2oNNzsE9YmGumoNCzkIP4as/pub?start=true&loop=true&delayms=30000 Open House Presentation] See [[Open House Presentations|Previous Presentations]].<br />
<br />
===Processes===<br />
* [[Digital_design|Digital Design]] '': before you can make things you need to design them''<br />
*[[3D Printing]] '': thermoplastic and photoresin 3D printing are supported''<br />
*[[Vinyl_Cutter_-_Brother_Scan-N-Cut_2|Vinyl Cutting]] '': a large vinyl cutter with up to 130 cm roll, and a 12 x 12" Brother ScanNCut are available''<br />
*[[CNC_Mogul_Router|CNC Routing]] '': if you've got sheet goods that you want to route into anything from furniture to signs we have it''<br />
*[[Thunder_Laser|Laser Cutting]] '': we can laser cut and engrave certain plastics and woods up to 900 mm x 600 mm x 230 mm''<br />
*[[Small Electronics]] '': from soldering irons to microcontrollers, we can make things blink and buzz''<br />
*[[Wood working]] '': if your material can be described as a natural composite of cellulose fibers that are embedded in a matrix of lignin then we have tools for that.''<br />
*[[Metal Machining]] '': if you want to turn a sort of square block of metal into a more square block then you've come to the right place.''<br />
<br />
===Workshops, Projects, & Events===<br />
*[[Workshops]] ''A place for documenting our workshops and learning events.''<br />
*[[Projects]] ''A place to document HackRVA group projects''<br />
*[[Events]] ''Documentation on HackRVA events.''<br />
<br />
===Facilities & Equipment===<br />
*[[Safety]]<br />
*[[HackRAT | Training]]<br />
*[[:Category:Equipment|Equipment and Tools]] <br />
*[[Primary IT Infrastructure]]<br />
<br />
===Organization===<br />
''Monthly Meeting - see the calender on [http://www.hackrva.org/blog/ hackrva.org] for board meeting dates. All are welcome to attend meetings''<br />
*[https://docs.google.com/document/d/1nETQVMTBQwTFAJvq0DFy_h5jCGChjUBdLkkoxp3VlWA/ Organizational Meeting Notes] (Updated monthly)<br />
*[[Financial Reports]] (Updated 1/20/19)<br />
*[https://docs.google.com/spreadsheets/d/1nG9Tm0k9Fo_WKPZJ3ka_OO35FTjRAFH53dykjQj3U0o/edit?usp=sharing Budget Spreadsheet]<br />
<br />
''General Information''<br />
*[[Coordinators]]<br />
*[[Acquisitions]]<br />
*[[History]]<br />
*[[Email us at info@hackrva.org.]]<br />
*By-Laws for HackRVA Labs, Inc. ([[Media:HackRVALabsIncBylaws.pdf|pdf]]) ([[Media:HackRVALabsInc_Bylaws.pdf|newer formatting pdf]])<br />
<br />
''Leadership Tools''<br />
* Slack<br />
* Email distribution list<br />
* HackRVA.org email address<br />
* Membership app<br />
* Financial Reports and Budget spreadsheet<br />
<br />
===Donating & Co-Locating===<br />
*[[Terms and Conditions#Donating|Donating]] - How to donate money or goods.<br />
*[[Co-Locating]] - How to co-locate at HackRVA.<br />
<br />
===Other Stuff===<br />
''HackRVA''<br />
*[[HackRVA Media]] (Logos, Signs, Business Card graphics, etc)<br />
*[[HackRVA Forms]] (Reimbursement, Instructor Payment, Parking Permits, etc)<br />
*[[Facilities Floor Plan]]<br />
*[[HackRVA in The Media]]<br />
<br />
''Resources''<br />
*[[Hacker Resources|Maker Resources]]<br />
*[[Young Makers]] - A list of things/places in Richmond for makers under 18.<br />
*[[List of local tech groups]]<br />
*[[Maker Entertainment]]<br />
<br />
''Guest Liability Waiver''<br />
*[[Media:HackRVA Draft .01 Access Acknowledgement and Liability Release.docx]]<br/><br />
*[[Media:HackRVA Draft .01 Access Acknowledgement and Liability Release.pdf]]<br/><br />
<br />
===Wiki How-To===<br />
* [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Wiki Editing Cheatsheet]<br />
* [http://www.mediawiki.org/wiki/Manual:Configuration_settings Configuration settings list]<br />
* [http://www.mediawiki.org/wiki/Manual:FAQ MediaWiki FAQ]<br />
* [https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
* [[HackRVA style guide]]</div>Dfirehttps://wiki.hackrva.org/index.php?title=Getting_Involved&diff=2354Getting Involved2019-03-27T17:31:41Z<p>Dfire: </p>
<hr />
<div>==Forming a Committee==<br />
<br />
You may notice a need or have a desire to change something at HackRVA. We have found that one effective way to make big changes is to form a committee. This committee will take it upon themselves to make informed decisions and plan how to execute changes. The committee will then report to the Monthly Membership meeting before enacting the changes. <br />
<br />
When large build outs or large HackRVA projects are presented to the monthly membership meeting. We should encourage a committee to be formed to plan and execute. This will reduce the planning that happens at membership meetings and allow for more than just one topic to be discussed at the meeting.<br />
<br />
===Some examples of successful committees:===<br />
*Room swap - Swapping the woodshop with the techlab<br />
*Purchasing the laser<br />
*Planning for secondary clean space<br />
*Building arts and crafts area/cabinets & counter in main room<br />
*XCarve restore and station build out<br />
<br />
<br />
<br />
==The 3 Hour Rule==<br />
''If you have an idea about what might make the space better, it's best to discuss with several other members, but we do have an '''unofficial rule''' that we refer to as "the 3 hour rule"''<br />
<blockquote>It is generally acceptable to make a change to the space as long as it can be undone in 3hours or less (by you,) if it is deemed to be an undesirable change.</blockquote><br />
<br />
==Volunteering at HackRVA==<br />
See the tasks whiteboard in the space for tasks that need to be complete.<br />
Or email, infoAThackrva.org for more specific details.<br />
<br />
(note: we've tried several iterations of digital management systems - so far a whiteboard kicks their butt)<br />
<br />
If you are experienced with a tool or know how to fix it, consider joining the [[HackRAT| HackRAT program]]<br />
<br />
==Other Sweet Volunteer Activities==<br />
<br />
*Join the [[HackRAT| HackRAT Program]] (Repair And Train) to help keep tools running and train others on their use.<br />
*Lead a [https://docs.google.com/spreadsheet/ccc?key=0Akt_buuj3P2jdHJRQVZzU0RFTTJuSmtvU1A2alpPWVE&usp=drive_web#gid=0/ workshop] (contact us and we'll set you up with meetup and assist with lesson plans if needed)<br />
*Start a new event (again, contact us, and we'll give you the social media tools to advertise)<br />
*Improve the Wiki (just create an account, and start adding useful info)<br />
*Post a project to the maker blog (anyone at HackRVA can be a blogger, just ask and we'll give you access)<br />
*Research and recommend a purchase (add them to our acquisitions spreadsheet (link needed))<br />
*Socialize with new folks during open house (Thursday nights)<br />
*Attend monthly business/board meetings and help figure out the way forward at HackRVA (see the calender for dates)<br />
<br />
<br />
<br />
==Deprecated:==<br />
'''HackRVA KanBoard - Improving the Space One Virtual Sticky Note at a Time'''<br />
<br />
We use the [[HackRVA KanBoard]] to do tasks around HackRVA.<br />
<br />
It's a project management tool for groups to get things done. We use it for things like cleaning, fixing things, and all the rest.<br />
<br />
Learn the details here - [[HackRVA KanBoard]].<br />
<br />
==<br />
<br />
[https://docs.google.com/spreadsheets/d/1KxUA6yGkUhzf6KzMVsPl26S2-VB6mK7SANiT7UCuz_4/edit#gid=902108231 Volunteer Sign Up Sheet]<br />
(this is one of our attempts at getting more people involved and worked for awhile. it's being deprecated )</div>Dfirehttps://wiki.hackrva.org/index.php?title=File:Member_Orientation_Checklist_v0.0.1.pdf&diff=2353File:Member Orientation Checklist v0.0.1.pdf2019-03-09T19:10:17Z<p>Dfire: Dfire uploaded a new version of File:Member Orientation Checklist v0.0.1.pdf</p>
<hr />
<div>edit this form here: https://docs.google.com/document/d/1sGMCOwcHUd8IB6zGn3W0kjhnWGI3tUQ8NYqx_2_fDpQ/edit?usp=sharing</div>Dfirehttps://wiki.hackrva.org/index.php?title=File:Member_Orientation_Checklist_v0.0.1.pdf&diff=2352File:Member Orientation Checklist v0.0.1.pdf2019-03-09T19:09:13Z<p>Dfire: Dfire uploaded a new version of File:Member Orientation Checklist v0.0.1.pdf</p>
<hr />
<div>edit this form here: https://docs.google.com/document/d/1sGMCOwcHUd8IB6zGn3W0kjhnWGI3tUQ8NYqx_2_fDpQ/edit?usp=sharing</div>Dfirehttps://wiki.hackrva.org/index.php?title=File:Member_Orientation_Checklist_v0.0.1.pdf&diff=2351File:Member Orientation Checklist v0.0.1.pdf2019-03-09T18:48:32Z<p>Dfire: Dfire uploaded a new version of File:Member Orientation Checklist v0.0.1.pdf</p>
<hr />
<div>edit this form here: https://docs.google.com/document/d/1sGMCOwcHUd8IB6zGn3W0kjhnWGI3tUQ8NYqx_2_fDpQ/edit?usp=sharing</div>Dfirehttps://wiki.hackrva.org/index.php?title=HackRVA_Forms&diff=2350HackRVA Forms2019-03-09T18:23:46Z<p>Dfire: </p>
<hr />
<div>Forms should include a version number. <br/><br />
An Editable version of the form should be available online somewhere.<br/><br />
<br />
Place completed forms in the top right drawer (labeled FORMS) and notify Michael Lane.<br/><br />
[[File:FormsLocation.jpg]]<br />
<br />
[[Media:Member Orientation Checklist v0.0.1.pdf| Member Orientation Checklist v0.0.1]]<br/><br />
[[Media:HackRVA_Reimbursement_Form.pdf|Reimbursement Form]]<br/><br />
[[Media:HackRVA_Instructor_Payment_Form.pdf|Instructor Payment Form]]<br/><br />
[[Parking Permits]]<br/></div>Dfirehttps://wiki.hackrva.org/index.php?title=HackRVA_Forms&diff=2349HackRVA Forms2019-03-09T18:23:10Z<p>Dfire: </p>
<hr />
<div>Forms should include a version number<br />
An Editable version of the form should be available online somewhere.<br />
<br />
Place completed forms in the top right drawer (labeled FORMS) and notify Michael Lane.<br/><br />
[[File:FormsLocation.jpg]]<br />
<br />
[[Media:Member Orientation Checklist v0.0.1.pdf| Member Orientation Checklist v0.0.1]]<br/><br />
[[Media:HackRVA_Reimbursement_Form.pdf|Reimbursement Form]]<br/><br />
[[Media:HackRVA_Instructor_Payment_Form.pdf|Instructor Payment Form]]<br/><br />
[[Parking Permits]]<br/></div>Dfirehttps://wiki.hackrva.org/index.php?title=On_boarding_members&diff=2348On boarding members2019-03-09T18:22:12Z<p>Dfire: </p>
<hr />
<div>This page documents the process to on board new members to all of the systems at HackRVA.<br />
<br />
[https://docs.google.com/document/d/1sGMCOwcHUd8IB6zGn3W0kjhnWGI3tUQ8NYqx_2_fDpQ/edit?usp=sharing Editable-Member Orientation Checklist]<br/><br />
[[Media:Member Orientation Checklist v0.0.1.pdf| Printable-Member Orientation Checklist v0.0.1]]<br/><br />
<br />
<br />
<br />
# Have the new member sign up on paypal at https://www.hackrva.org/blog/membership/<br />
# Have the new member read and sign the [[Media:HackrvaMembershipAgreement.pdf|hackrva membership agreement and liability waiver]]<br />
# Go to [http://10.200.200.11 the membership portal] ( you must be on the internal network)<br />
## Enter the email address that the new member used to sign up in paypal<br />
## If you see an error message that says something like <q>There are no recorded payments in the last month from <email></q> then either the new member did not successfully subscribe on paypal or they used another email address. have them review their paypal information and retry<br />
## You will then come to a screen where it asks for the rfid tag number:<br />
::::* Get the new member an rfid tag and grab the usb scanner from the drawer in the main room under the tv<br />
::::* Scan the tag with the scanner so it fills in the rfid field on the form (if you run into difficulty, you can enter this manually - the number is imprinted on the tag)<br />
::::* Once you submit the form the new member will receive a slack invite and will be able to use their rfid tag.<br />
::::* Test the rfid tag on the outer door to make sure the new member can gain access.</div>Dfirehttps://wiki.hackrva.org/index.php?title=HackRVA_Forms&diff=2347HackRVA Forms2019-03-09T18:20:52Z<p>Dfire: </p>
<hr />
<div>Forms should include a version number <br />
<br />
Place completed forms in the top right drawer (labeled FORMS) and notify Michael Lane.<br/><br />
[[File:FormsLocation.jpg]]<br />
<br />
[[Media:Member Orientation Checklist v0.0.1.pdf| Member Orientation Checklist v0.0.1]]<br/><br />
[[Media:HackRVA_Reimbursement_Form.pdf|Reimbursement Form]]<br/><br />
[[Media:HackRVA_Instructor_Payment_Form.pdf|Instructor Payment Form]]<br/><br />
[[Parking Permits]]<br/></div>Dfirehttps://wiki.hackrva.org/index.php?title=File:Member_Orientation_Checklist_v0.0.1.pdf&diff=2346File:Member Orientation Checklist v0.0.1.pdf2019-03-09T18:17:47Z<p>Dfire: edit this form here: https://docs.google.com/document/d/1sGMCOwcHUd8IB6zGn3W0kjhnWGI3tUQ8NYqx_2_fDpQ/edit?usp=sharing</p>
<hr />
<div>edit this form here: https://docs.google.com/document/d/1sGMCOwcHUd8IB6zGn3W0kjhnWGI3tUQ8NYqx_2_fDpQ/edit?usp=sharing</div>Dfirehttps://wiki.hackrva.org/index.php?title=On_boarding_members&diff=2345On boarding members2019-03-09T17:41:09Z<p>Dfire: </p>
<hr />
<div>This page documents the process to on board new members to all of the systems at HackRVA.<br />
<br />
[https://docs.google.com/document/d/1sGMCOwcHUd8IB6zGn3W0kjhnWGI3tUQ8NYqx_2_fDpQ/edit?usp=sharing Member Orientation Checklist]<br />
<br />
# Have the new member sign up on paypal at https://www.hackrva.org/blog/membership/<br />
# Have the new member read and sign the [[Media:HackrvaMembershipAgreement.pdf|hackrva membership agreement and liability waiver]]<br />
# Go to [http://10.200.200.11 the membership portal] ( you must be on the internal network)<br />
## Enter the email address that the new member used to sign up in paypal<br />
## If you see an error message that says something like <q>There are no recorded payments in the last month from <email></q> then either the new member did not successfully subscribe on paypal or they used another email address. have them review their paypal information and retry<br />
## You will then come to a screen where it asks for the rfid tag number:<br />
::::* Get the new member an rfid tag and grab the usb scanner from the drawer in the main room under the tv<br />
::::* Scan the tag with the scanner so it fills in the rfid field on the form (if you run into difficulty, you can enter this manually - the number is imprinted on the tag)<br />
::::* Once you submit the form the new member will receive a slack invite and will be able to use their rfid tag.<br />
::::* Test the rfid tag on the outer door to make sure the new member can gain access.</div>Dfirehttps://wiki.hackrva.org/index.php?title=Old_Laser_Cutter&diff=2211Old Laser Cutter2018-06-30T16:47:03Z<p>Dfire: </p>
<hr />
<div>[[category:equipment]][[category:design]][[category:back room]]<br />
<br />
<br />
<span style="color:#00ff00; background:#808080"> <br />
'''We have a new Laser Cutter! check out [[Thunder Laser]] for info'''<br />
</span><br />
<br />
<br />
<br />
The Laser Cutter is a 40 watt CO2 laser located in the HackRVA Electronics Lab. It can cut materials such as wood and plastic (but nothing containing chlorine, such as PVC!). We use Mach3 control software. The [[2.x Laser Cutter]] page has details about the laser construction.<br />
<br />
Access to the Laser Cutter requires [[Laser Training]] from a qualified member. <br />
<br />
wear eye protection<br />
no incorrect materials with laser (PVC)<br />
<br />
===Material Sizes and Thicknesses===<br />
'''The maximum cutting area is 19 inches across and 10 inches deep.''' Smaller work pieces are easier to handle - getting under the cutting head without having to lower the bed a lot. If you are cutting, and not etching, a good material thickness for easy cutting would be 1/8 inch, or 3 mm. A maximum thickness is about 1/4 inch, or 6 mm, and may require multiple passes to cut completely through.<br />
<br />
===Laser Spot Size / Cut Width===<br />
The laser cuts a path through your material that is approximately '''0.23 mm''' wide if the laser is focused correctly for your material (see Step 11 of the Quick-Start guide that follows). This is similar to the cut made by a saw blade or a router bit. Another name for the width of the cut is the '''kerf'''. Most users don't need to bother about this as the cut-width is too small to have a noticeable effect on your work piece. <br />
<br />
However, if you are cutting very precise (or very small) shapes, you may want to factor in the kerf. Assume that 1/2 of that width (or 0.115 mm) will be removed from each side of your final work piece. You can either 1) enlarge your dimensions to include this amount or 2) use a "profiling" setup in CamBam and select the 0.23mm tool. CamBam will create a toolpath that accounts for the kerf width and maintains your original work piece dimensions.<br />
<br />
===Quick-Start guide for the Laser Cutter===<br />
Step 1: Turn on the computer connected to the laser (computer on first or they won’t talk).<br />
<br />
Step 3: Open Mach3 software on the computer.<br />
<br />
Step 4: Turn on the Laser Cutter by plugging in the GFI cord (looks like a short, yellow extension cord).<br />
<br />
Step 5: Plug in the ventilation fan (fan is on the nearby double-door).<br />
<br />
Step 6: "Home" the laser (so it knows where the laser head is).<br />
<br />
Step 7: Load your G-Code under “file->load g-code” in the top--bar menu. (See below for more information on generating the g-code for this.)<br />
<br />
Step 8: Use “tab” to bring up the virtual pendent (so you can jog/move the machine head)<br />
<br />
Step 9: Place your workpiece on the cutting bed, but don't knock into the laser head. Lower the cutting bed if you need more room.<br />
<br />
Step 10: Position the tool to your 0,0 point.<br />
<br />
Step 11: Raise or Lower the cutting bed such that the top of your workpiece is '''70 mm''' below the top of the laser carriage (the larger moving aluminum plate). An easy way to set the cutting bed height is to use the height gauge, which is the wooden paint stirrer with blue painters tape marking 70 mm. The distance used to be 71 mm, but we made more accurate measurements. Getting this pretty close to 70 mm is important in preventing fires (usually caused by an out-of-focus beam).<br />
<br />
Step 12: Zero-out all your coordinates inside Mach3. (the “ref coordinates” button on screen)<br />
<br />
Step 13: Set the laser power as needed.<br />
<br />
Step 14: Hit “Cycle-Start” button on computer screen in Mach3 to begin cutting routine.<br />
<br />
Step 15: Be ready to hit “stop” on screen, especially on first starting, in case something is wrong.<br />
<br />
===Laser Tips and Safety===<br />
====Using the Machine:====<br />
*Wear safety glasses. Stray laser beams are invisible and can blind you.<br />
*If your work-piece starts flaming, hit the big-red stop button on the front of the laser, then put out the fire. It will very likely go out once the laser is off, but open the lid and remove the workpiece to keep excessive smoke out of the system. In very extreme cases, there is a fire extinguisher, but using it would destroy the laser cutter. <br />
*Don’t put your hands in proximity of the laser head while it’s running. The machine might make a move you’re not expecting.<br />
*Watch the machine while it’s cutting. Be ready to turn it off in case something malfunctions.<br />
* If you have doubts about your G-Code, run the CNC in the air with the big, red Stop Button on the front of the laser pressed in. You can see the laser's path without damaging your work piece.<br />
*Be aware when adjusting the table height. You don’t want the laser nozzle to bang the work piece.<br />
*Wear safety glasses. Stray laser beams are invisible and can blind you. (Yes, it is important enough to repeat.)<br />
<br />
====Mach3 Software Tips====<br />
*If Mach3 isn’t responding, hit the “RESET” button. There’s a good chance it’s flashing at you.<br />
*If you need to start over on g-code, the “rewind” button takes the code to the start. The “Go Home” button takes the spindle to your original starting place.<br />
*There’s a virtual tool-path graphic in the top right corner of the screen. It can give you an idea of what’s going to happen when you hit start.<br />
*You can edit your g-code inside Mach3 if needed. This is a fast way to make adjustments.<br />
*You can increase/decrease the travel speed inside Mach3. If the machine is going too fast, you can slow it down there with the arrows.<br />
<br />
====G-Code Tips====<br />
*Use XXXX to guide you on setting parameters.<br />
*If your workpiece is charring or burning, use a lower power level or a faster feed speed.<br />
*If the laser doesn't cut completely through your workpiece, try multiple passes by running your gcode again. Click "Rewind" and start. Don't touch your workpiece or it won't line up.<br />
<br />
===Software for Making G-Code===<br />
The [[CNC Mogul Router]] page has a lot of information about making G-Code. However, the laser needs a few special modifications. The easiest way to get started is to use either CamBam or MakerCam.<br />
====CamBam====<br />
Start with a DXF file generated by your favorite CAD package. <br />
<br />
* Start CamBam and load your DXF file.<br />
<br />
* Select the "System" tab, expand the "Post Processors" drop down folder, then make "Laser-HackRVA" the default post-processor.<br />
<br />
[[File:CamBamInstructions1.PNG]]<br />
<br />
* Pick all the shapes you want to cut in your drawing by highlighting them.<br />
<br />
* Once they are selected, click the red/orange "engrave" button to do an engraving machine operation<br />
<br />
* Highlight the "Engrave1" machine operation just created in the "Machining" folder on the side-bar view. In the details below, click in the blank area to the right of "Style" paramater under "General" and a drop-down list will appear. Choose "laser" from the list. This is the only setting that needs adjustment, the rest is pre-populated from choosing the "Laser-HackRVA" post-processor in the earlier step.<br />
<br />
[[File:CamBamInstructions2.PNG]]<br />
<br />
* Now hover over and right-click the "Engrave1" machining operation you've been using, and select "Generate toolpaths". This will create a bunch of lines on top of your lines in the drawing where the laser will cut at.<br />
<br />
[[File:CamBamInstructions3.PNG]]<br />
<br />
* Finally do the same thing as in last step, but this time pick "Produce gcode". This will create a file that ends in file extension ".nc" which is the file Mach3 needs to run the laser.<br />
<br />
====MakerCam.com====<br />
[http://www.makercam.com/ MakerCam.com] is an in the browser vector drawing program and g-code generator.<br />
There is a tutorial and help button on the site.<br />
<br />
Make an SVG file using a drawing package like InkScape. Load your SVG file into makercam and use the following settings:<br />
<br />
-set z-clearance plane to 0.001 (temp)<br />
<br />
-set depth increment to 0.001 <br />
<br />
-set final depth to 0.001<br />
<br />
-set tool diameter to 0.001<br />
<br />
-the rest is normal<br />
<br />
* Use Laser - MakercamConverter.py on the desktop of the digital design PC. [[Media:Laser-MakercamConverter.py|Laser - MakercamConverter.py]]<br />
<br />
===Problems===<br />
For more help go to https://groups.google.com/forum/#!forum/hackratlasercutter and ask to join. <br />
<br />
===Additional Information===<br />
====Feeds and Speeds====<br />
Feed or Feed-Rate is how fast your tool moves across the works surface.<br />
The power level of the laser is controlled by the aluminum knob on the front, and shown by the analog meter on the front. It is limited to 20mA, but lower is better for the life of the tube. A slower feed with a lower power will get similar results.<br />
If you are not sure if the laser is cutting all the way though wood or other non-transparent material, look for the reflection in the bottom of the chamber. You will see the bright white of the cutting if it is all the way through.<br />
====CamBam and Mach3 Configuration Files====<br />
Both CamBam and Mach3 require configuration files to work properly with the laser cutter. CamBam uses these configuration files to properly generate gcode designed for the laser cutter. Mach3 uses a configuration file to configure the controls to match the lasers motors, limit switches, power controls, etc.<br />
If the configuration files need to be reinstalled, the master copies can be found on [https://github.com/AlanFord/laser-cutter github.com]<br />
<br />
===Remaining Tasks===<br />
* Rear electrical cover plate<br />
* Acquire CO2 or other non-destructive fire extinguisher<br />
* Install Z+ limit switch<br />
* Build and test PWM controller</div>Dfirehttps://wiki.hackrva.org/index.php?title=File:Hrva_2018_floor_plan.png&diff=2195File:Hrva 2018 floor plan.png2018-06-10T04:06:28Z<p>Dfire: </p>
<hr />
<div></div>Dfirehttps://wiki.hackrva.org/index.php?title=Getting_Involved&diff=2152Getting Involved2018-05-10T16:59:01Z<p>Dfire: </p>
<hr />
<div>'''''Volunteering at HackRVA'''''<br />
<br />
See the tasks whiteboard in the space for tasks that need to be complete.<br />
Or email, infoAThackrva.org for more specific details.<br />
<br />
(note: we've tried several iterations of digital management systems - so far a whiteboard kicks their butt)<br />
<br />
If you are experienced with a tool or know how to fix it, consider joining the [[HackRAT| HackRAT program]]<br />
<br />
<br />
'''Other Sweet Volunteer Activities'''<br />
<br />
*Join the [[HackRAT| HackRAT Program]] (Repair And Train) to help keep tools running and train others on their use.<br />
*Lead a [https://docs.google.com/spreadsheet/ccc?key=0Akt_buuj3P2jdHJRQVZzU0RFTTJuSmtvU1A2alpPWVE&usp=drive_web#gid=0/ workshop] (contact us and we'll set you up with meetup and assist with lesson plans if needed)<br />
*Start a new event (again, contact us, and we'll give you the social media tools to advertise)<br />
*Improve the Wiki (just create an account, and start adding useful info)<br />
*Post a project to the maker blog (anyone at HackRVA can be a blogger, just ask and we'll give you access)<br />
*Research and recommend a purchase (add them to our acquisitions spreadsheet (link needed))<br />
*Socialize with new folks during open house (Thursday nights)<br />
*Attend monthly business/board meetings and help figure out the way forward at HackRVA (see the calender for dates)<br />
<br />
<br />
<br />
'''The 3 Hour Rule'''<br />
''If you have an idea about what might make the space better, it's best to discuss with several other members, but we do have an '''unofficial rule''' that we refer to as "the 3 hour rule"''<br />
<blockquote>It is generally acceptable to make a change to the space as long as it can be undone in 3hours or less (by you,) if it is deemed to be an undesirable change.</blockquote><br />
<br />
<br />
'''Deprecated:'''<br />
<br />
'''HackRVA KanBoard - Improving the Space One Virtual Sticky Note at a Time'''<br />
<br />
We use the [[HackRVA KanBoard]] to do tasks around HackRVA.<br />
<br />
It's a project management tool for groups to get things done. We use it for things like cleaning, fixing things, and all the rest.<br />
<br />
Learn the details here - [[HackRVA KanBoard]].<br />
<br />
==<br />
<br />
[https://docs.google.com/spreadsheets/d/1KxUA6yGkUhzf6KzMVsPl26S2-VB6mK7SANiT7UCuz_4/edit#gid=902108231 Volunteer Sign Up Sheet]<br />
(this is one of our attempts at getting more people involved and worked for awhile. it's being deprecated )</div>Dfirehttps://wiki.hackrva.org/index.php?title=Getting_Involved&diff=2151Getting Involved2018-05-10T16:57:01Z<p>Dfire: </p>
<hr />
<div>'''''Volunteering at HackRVA'''''<br />
<br />
See the tasks whiteboard in the space for tasks that need to be complete.<br />
Or email, infoAThackrva.org for more specific details.<br />
<br />
(note: we've tried several iterations of digital management systems - so far a whiteboard kicks their butt)<br />
<br />
If you are experienced with a tool or know how to fix it, consider joining the [[HackRAT| HackRAT program]]<br />
<br />
<br />
'''Other Sweet Volunteer Activities'''<br />
<br />
*Join the [[HackRAT| HackRAT Program]] (Repair And Train) to help keep tools running and train others on their use.<br />
*Lead a [https://docs.google.com/spreadsheet/ccc?key=0Akt_buuj3P2jdHJRQVZzU0RFTTJuSmtvU1A2alpPWVE&usp=drive_web#gid=0/ workshop] (contact us and we'll set you up with meetup and assist with lesson plans if needed)<br />
*Start a new event (again, contact us, and we'll give you the social media tools to advertise)<br />
*Improve the Wiki (just create an account, and start adding useful info)<br />
*Post a project to the maker blog (anyone at HackRVA can be a blogger, just ask and we'll give you access)<br />
*Research and recommend a purchase (add them to our acquisitions spreadsheet (link needed))<br />
*Socialize with new folks during open house (Thursday nights)<br />
*Attend monthly business/board meetings and help figure out the way forward at HackRVA (see the calender for dates)<br />
<br />
<br />
<br />
'''The 3 Hour Rule'''<br />
''If you have an idea about what might make the space better, it's best to discuss with several other members, but we do have an unofficial rule that we refer to as "the 3 hour rule"''<br />
<blockquote>It is generally acceptable to make a change to the space as long as it can be undone in 3hours or less (by you,) if it is deemed to be an undesirable change.</blockquote><br />
<br />
<br />
'''Deprecated:'''<br />
<br />
'''HackRVA KanBoard - Improving the Space One Virtual Sticky Note at a Time'''<br />
<br />
We use the [[HackRVA KanBoard]] to do tasks around HackRVA.<br />
<br />
It's a project management tool for groups to get things done. We use it for things like cleaning, fixing things, and all the rest.<br />
<br />
Learn the details here - [[HackRVA KanBoard]].<br />
<br />
==<br />
<br />
[https://docs.google.com/spreadsheets/d/1KxUA6yGkUhzf6KzMVsPl26S2-VB6mK7SANiT7UCuz_4/edit#gid=902108231 Volunteer Sign Up Sheet]<br />
(this is one of our attempts at getting more people involved and worked for awhile. it's being deprecated )</div>Dfirehttps://wiki.hackrva.org/index.php?title=File:FDOCN10IVA4PZOU.jpg&diff=2058File:FDOCN10IVA4PZOU.jpg2018-01-21T20:43:37Z<p>Dfire: </p>
<hr />
<div></div>Dfirehttps://wiki.hackrva.org/index.php?title=Primary_IT_Infrastructure&diff=2054Primary IT Infrastructure2018-01-18T21:10:18Z<p>Dfire: </p>
<hr />
<div>Hack.rva provides community wifi and lan drops in all rooms, as well as a few in house hosted services. All traffic is monitored by a snorby server that checks for illegal torrents, bots and other malware.<br />
<br />
<br />
----<br />
<br />
<br />
[[File:serverrack.jpg]]<br />
<br />
<br />
----<br />
<blockquote><span style="color: red;">''Entire page needs to be updated''</span></blockquote><br />
<br />
----<br />
<br />
==About==<br />
-more info coming-<br />
<br />
<br />
----<br />
<br />
==Topology==<br />
<br />
A crude Network topology by John V.<br />
<br />
[[file:Net_diagram.png]]<br />
<br />
----<br />
==Network Appliances==<br />
<br />
*'''Modem''' - Motorola Surfboard 575186<br />
*'''Firewall''' - custom PFSense box<br />
*'''Switch''' - Netgear GS724T<br />
*'''Wifi AP''' - Ubiquity Unifi AP<br />
<br />
----<br />
==Networked Equipment==<br />
<br />
*'''[[Proxmox virtualization Node]]'''<br />
-An in house solution to keep the number of physical machines running various services down to a minimum. Rocking dual 12 thread Xeons and 48gb of ram, this thing provides all of our virtualzation needs. Runs Proxmox 4.4<br />
*'''Networked Attached Storage'''<br />
-The NAS was built out of spare parts donated by several members and has 4 1tb WD greens in a zfs raid 5.<br />
*'''[[Digital Design Workstation]]'''<br />
-Donated by Michael, the Digital Design station is rocking a q6600, 6gb of ddr2, and a Radeon HD 5770, this machine is the work horse for all of our design and manufacturing equipment. This including the CNC router, 3D printers and laser cutter.<br />
*'''Wall of monitors machine'''<br />
-What started off as a separate dev machine, The wall of monitors machine was Aaron's Idea because he wanted to sit in front of a machine that drove 9 screens running off of one tower.<br />
*'''TV PC'''<br />
A Raspberry Pi model B 1st gen, hooked to the large plasma screen display good for digital signage or just a secondary screen<br />
*'''Chromecast'''<br />
- simple streaming stick that stays plugged in the HDMI switch for broadcasting things wirelessly to the projector, Works best with the Chrome browser.<br />
<br />
----<br />
<br />
==Services==<br />
*'''LAN games'''<br />
-We host our own Minecraft Server @ minecraft.hackrva.org:25565<br />
<br />
-Saturday nights tends to turn into Age Of Emipres 3 lan gaming<br />
<br />
-Occasionally an Artemis game gets played though, not too often any more<br />
*'''Community storage'''<br />
-We have a 4tb NAS for community use, It holds a fair amount of various Operating system ISOs and other wise is a hub for hackrva related files<br />
*'''Virtualization'''<br />
We have a in house hypervisor machine for public use after training.<br />
*'''Cad software'''<br />
The digital design station is full to the brim with different CAD software, the main suite being Auto desk products<br />
<br />
==History==<br />
<br />
<br />
<blockquote><span style="color: red;">''This section needs to be updated''</span></blockquote><br />
<br />
<br />
The network at hackrva started out as a just a WRT54GL named "robot king" and a fall back AP named "robot queen". They had to be rebooted almost weekly due to the constant traffic and numerous DHCP problems. These devices ran out of address space very quickly.<br />
<br />
<br />
Thus a beefier network needed to be created. A more reliable network was created with enterprise grade gear and, in a lot of ways, this network became the model of what is currently in place.<br />
<br />
<br />
Many hands are involved in maintaining the network, running network cabling throughout the space and ensuring minimal downtime. <br />
The equipment at the space is there to be used. If you would like access to a VM or would like to contribute to the maintenance of the infrastructure, please email HackRATnetworkRats@googlegroups.com</div>Dfirehttps://wiki.hackrva.org/index.php?title=Primary_IT_Infrastructure&diff=1703Primary IT Infrastructure2016-12-01T14:45:19Z<p>Dfire: /* History */</p>
<hr />
<div>Hack.rva provides community wifi and lan drops in all rooms, as well as a few in house hosted services. All traffic is monitored by a snorby server that checks for illegal torrents, bots and other malware.<br />
<br />
<br />
----<br />
<br />
<br />
[[File:serverrack.jpg]]<br />
<br />
<br />
----<br />
<br />
==About==<br />
-more info coming-<br />
<br />
<br />
----<br />
<br />
==Topology==<br />
<br />
A crude Network topology by John V.<br />
<br />
[[file:Net_diagram.png]]<br />
<br />
----<br />
==Network Appliances==<br />
<br />
*'''Modem''' - Motorola Surfboard 575186<br />
*'''Firewall''' - custom PFSense box<br />
*'''Switch''' - Netgear GS724T<br />
*'''Wifi AP''' - Ubiquity Unifi AP<br />
<br />
----<br />
==Networked Equipment==<br />
<br />
*'''[[Proxmox virtualization Node]]'''<br />
-An in house solution to keep the number of physical machines running various services down to a minimum. Rocking dual 12 thread Xeons and 48gb of ram, this thing provides all of our virtualzation needs. Runs Proxmox 4.4<br />
*'''Networked Attached Storage'''<br />
-The NAS was built out of spare parts donated by several members and has 4 1tb WD greens in a zfs raid 5.<br />
*'''[[Digital Design Workstation]]'''<br />
-Donated by Michael, the Digital Design station is rocking a q6600, 6gb of ddr2, and a Radeon HD 5770, this machine is the work horse for all of our design and manufacturing equipment. This including the CNC router, 3D printers and laser cutter.<br />
*'''Wall of monitors machine'''<br />
-What started off as a separate dev machine, The wall of monitors machine was Aaron's Idea because he wanted to sit in front of a machine that drove 9 screens running off of one tower.<br />
*'''TV PC'''<br />
A Raspberry Pi model B 1st gen, hooked to the large plasma screen display good for digital signage or just a secondary screen<br />
*'''Chromecast'''<br />
- simple streaming stick that stays plugged in the HDMI switch for broadcasting things wirelessly to the projector, Works best with the Chrome browser.<br />
<br />
----<br />
<br />
==Services==<br />
*'''LAN games'''<br />
-We host our own Minecraft Server @ minecraft.hackrva.org:25565<br />
<br />
-Saturday nights tends to turn into Age Of Emipres 3 lan gaming<br />
<br />
-Occasionally an Artemis game gets played though, not too often any more<br />
*'''Community storage'''<br />
-We have a 4tb NAS for community use, It holds a fair amount of various Operating system ISOs and other wise is a hub for hackrva related files<br />
*'''Virtualization'''<br />
We have a in house hypervisor machine for public use after training.<br />
*'''Cad software'''<br />
The digital design station is full to the brim with different CAD software, the main suite being Auto desk products<br />
<br />
==History==<br />
<br />
<br />
<blockquote><span style="color: red;">''This section needs to be updated''</span></blockquote><br />
<br />
<br />
The network at hackrva started out as a just a WRT54GL named "robot king" and a fall back AP named "robot queen". They had to be rebooted almost weekly due to the constant traffic and numerous DHCP problems. These devices ran out of address space very quickly.<br />
<br />
<br />
Thus a beefier network needed to be created. A more reliable network was created with enterprise grade gear and, in a lot of ways, this network became the model of what is currently in place.<br />
<br />
<br />
Many hands are involved in maintaining the network, running network cabling throughout the space and ensuring minimal downtime. <br />
The equipment at the space is there to be used. If you would like access to a VM or would like to contribute to the maintenance of the infrastructure, please email HackRATnetworkRats@googlegroups.com</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1517Diving Into Bash2016-03-16T22:45:53Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
== Permissions == <br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
Change the permissions on your new directory and remove access to "Others." You can do this by running the following command:<br />
<br />
chmod 750 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxr-x--- 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User. The Group has read and execute. Others should have no access.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
== Creating a File == <br />
<br />
Let's make sure we are in ''myNewDirectory''.<br />
<br />
cd ~/myNewDirectory<br />
<br />
To create a new file we will use the [http://linux.die.net/man/1/touch touch] command.<br />
<br />
Create a new file and view the contents of that file with the [http://linux.die.net/man/1/cat concatenate ] command.<br />
<br />
touch newFile<br />
cat newFile<br />
<br />
The cat command should not return anything. This is because the file is empty. Try adding some content to the file.<br />
<br />
echo $'The ships hung in the sky in much the same way that bricks don\'t.\n\n\t ― Douglas Adams, The Hitchhiker\'s Guide to the Galaxy ' >> newFile<br />
cat newFile<br />
<br />
Excellent! We should now have text content in our newFile. <br />
<br />
== Text Editor ==<br />
In this step by step we will be introducing you to the command line text editor vim, however there are several other good options such as emacs and nano<br />
<br />
$vim newFile<br />
<br />
You should now be in the vim text editor. Here are some good vim commands for your to know<br />
<br />
a - insert text behind the cursor i - insert text ahead of the cursor<br />
<br />
k - move up j - move down l - move right h - move left<br />
<br />
n dd - remove “n” of lines from cursor n dw - remove “n” of words from cursor<br />
<br />
:q! - quit without making changes :wq - write quit<br />
<br />
x - delete character at cursor n p - paste “n” of times<br />
<br />
o - insert blank line under cursor yy - copy <br />
<br />
:w - write file :n - move to line “n”<br />
<br />
(esc key) leave insert mode<br />
<br />
Press the "A" key to get into insert mode and type the following into your text file:<br />
<br />
#!/bin/bash<br />
<br />
PS3='Choose one word: '<br />
<br />
#bash select<br />
select word in "linux" "bash" "scripting" "tutorial"<br />
do<br />
echo "The word you have selected is: $word"<br />
#Break, otherwise endless loop<br />
break<br />
done<br />
<br />
exit 0<br />
<br />
Now press the "esc" key and then type ":wq" and press "Enter". You should be back at the bash command prompt.<br />
<br />
You have just created you first bash script. Now lets change our file permissions and run it.<br />
<br />
$chmod 750 myscript<br />
<br />
$./myscript<br />
<br />
This should be your output<br />
<br />
1) linux<br />
2) bash<br />
3) scripting<br />
4) tutorial<br />
Choose one word: 4<br />
The word you have selected is: tutorial<br />
<br />
We are not going to get to get much into bash scripting here but this is a small example of what is possible from the command line in Linux<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
rmdir ~/myNewDirectory<br />
<br />
== External Links ==<br />
# [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI'']</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1516Diving Into Bash2016-03-16T22:40:07Z<p>Dfire: /* Creating a File */</p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
== Permissions == <br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
Change the permissions on your new directory and remove access to "Others." You can do this by running the following command:<br />
<br />
chmod 750 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxr-x--- 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User. The Group has read and execute. Others should have no access.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
== Creating a File == <br />
<br />
Let's make sure we are in ''myNewDirectory''.<br />
<br />
cd ~/myNewDirectory<br />
<br />
To create a new file we will use the [http://linux.die.net/man/1/touch touch] command.<br />
<br />
Create a new file and view the contents of that file with the [http://linux.die.net/man/1/cat concatenate ] command.<br />
<br />
touch newFile<br />
cat newFile<br />
<br />
The cat command should not return anything. This is because the file is empty. Try adding some content to the file.<br />
<br />
echo $'The ships hung in the sky in much the same way that bricks don\'t.\n\n\t ― Douglas Adams, The Hitchhiker\'s Guide to the Galaxy ' >> newFile<br />
cat newFile<br />
<br />
Excellent! We should now have text content in our newFile. <br />
<br />
== Text Editor ==<br />
In this step by step we will be introducing you to the command line text editor vim, however there are several other good options such as emacs and nano<br />
<br />
$vim newFile<br />
<br />
You should now be in the vim text editor. Here are some good vim commands for your to know<br />
<br />
a - insert text behind the cursor i - insert text ahead of the cursor<br />
<br />
k - move up j - move down l - move right h - move left<br />
<br />
n dd - remove “n” of lines from cursor n dw - remove “n” of words from cursor<br />
<br />
:q! - quit without making changes :wq - write quit<br />
<br />
x - delete character at cursor n p - paste “n” of times<br />
<br />
o - insert blank line under cursor yy - copy <br />
<br />
:w - write file :n - move to line “n”<br />
<br />
(esc key) leave insert mode<br />
<br />
Press the "A" key to get into insert mode and type the following into your text file:<br />
<br />
#!/bin/bash<br />
<br />
PS3='Choose one word: '<br />
<br />
#bash select<br />
select word in "linux" "bash" "scripting" "tutorial"<br />
do<br />
echo "The word you have selected is: $word"<br />
#Break, otherwise endless loop<br />
break<br />
done<br />
<br />
exit 0<br />
<br />
Now press the "esc" key and then type ":wq" and press "Enter". You should be back at the bash command prompt.<br />
<br />
You have just created you first bash script. Now lets change our file permissions and run it.<br />
<br />
$chmod 750 myscript<br />
<br />
$./myscript<br />
<br />
This should be your output<br />
<br />
1) linux<br />
2) bash<br />
3) scripting<br />
4) tutorial<br />
Choose one word: 4<br />
The word you have selected is: tutorial<br />
<br />
We are not going to get to get much into bash scripting here but this is a small example of what is possible from the command line in Linux<br />
<br />
<br />
<br />
<br />
<br />
+This is where we should probably talk about text editors.<br />
<br />
+This is where bash script should go<br />
<br />
<br />
<br />
rmdir ~/myNewDirectory<br />
<br />
== External Links ==<br />
# [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI'']</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1514Diving Into Bash2016-03-16T22:31:27Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
== Permissions == <br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
Change the permissions on your new directory and remove access to "Others." You can do this by running the following command:<br />
<br />
chmod 750 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxr-x--- 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User. The Group has read and execute. Others should have no access.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
== Creating a File == <br />
<br />
Let's make sure we are in ''myNewDirectory''.<br />
<br />
cd ~/myNewDirectory<br />
<br />
To create a new file we will use the [http://linux.die.net/man/1/touch touch] command.<br />
<br />
Create a new file and view the contents of that file with the [http://linux.die.net/man/1/cat concatenate ] command.<br />
<br />
touch newFile<br />
cat newFile<br />
<br />
The cat command should not return anything. This is because the file is empty. Try adding some content to the file.<br />
<br />
echo $'The ships hung in the sky in much the same way that bricks don\'t.\n\n\t ― Douglas Adams, The Hitchhiker\'s Guide to the Galaxy ' >> newFile<br />
cat newFile<br />
<br />
Excellent! We should now have text content in our newFile. <br />
<br />
In this step by step we will be introducing you to the command line text editor vim, however there are several other good options such as emacs and nano<br />
<br />
$vim newFile<br />
<br />
You should now be in the vim text editor. Here are some good vim commands for your to know<br />
<br />
a - insert text behind the cursor i - insert text ahead of the cursor<br />
<br />
k - move up j - move down l - move right h - move left<br />
<br />
n dd - remove “n” of lines from cursor n dw - remove “n” of words from cursor<br />
<br />
:q! - quit without making changes :wq - write quit<br />
<br />
x - delete character at cursor n p - paste “n” of times<br />
<br />
o - insert blank line under cursor yy - copy <br />
<br />
:w - write file :n - move to line “n”<br />
<br />
(esc key) leave insert mode<br />
<br />
+This is where we should probably talk about text editors.<br />
<br />
+This is where bash script should go<br />
<br />
<br />
<br />
rmdir ~/myNewDirectory<br />
<br />
== External Links ==<br />
# [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI'']</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1509Diving Into Bash2016-03-14T16:19:33Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
== Permissions == <br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
Change the permissions on your new directory and remove access to "Others." You can do this by running the following command:<br />
<br />
chmod 750 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxr-x--- 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User. The Group has read and execute. Others should have no access.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
== Creating a File == <br />
<br />
Let's make sure we are in ''myNewDirectory''.<br />
<br />
cd ~/myNewDirectory<br />
<br />
To create a new file we will use the [http://linux.die.net/man/1/touch touch] command.<br />
<br />
Create a new file and view the contents of that file with the [http://linux.die.net/man/1/cat concatenate ] command.<br />
<br />
touch newFile<br />
cat newFile<br />
<br />
The cat command should not return anything. This is because the file is empty. Try adding some content to the file.<br />
<br />
echo $'The ships hung in the sky in much the same way that bricks don\'t.\n\n\t ― Douglas Adams, The Hitchhiker\'s Guide to the Galaxy ' >> newFile<br />
cat newFile<br />
<br />
Excellent! We should now have text content in our newFile. <br />
<br />
<br />
+This is where we should probably talk about text editors.<br />
<br />
+This is where bash script should go<br />
<br />
<br />
<br />
rmdir ~/myNewDirectory<br />
<br />
== External Links ==<br />
# [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI'']</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1508Diving Into Bash2016-03-14T16:18:58Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
== Permissions == <br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
Change the permissions on your new directory and remove access to "Others." You can do this by running the following command:<br />
<br />
chmod 750 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxr-x--- 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User. The Group has read and execute. Others should have no access.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
== Creating a File == <br />
<br />
Let's make sure we are in ''myNewDirectory''.<br />
<br />
cd ~/myNewDirectory<br />
<br />
To create a new file we will use the [http://linux.die.net/man/1/touch touch] command.<br />
<br />
Create a new file and view the contents of that file with the [http://linux.die.net/man/1/cat concatenate ] command.<br />
<br />
touch newFile<br />
cat newFile<br />
<br />
The cat command should not return anything. This is because the file is empty. Try adding some content to the file.<br />
<br />
echo $'The ships hung in the sky in much the same way that bricks don\'t.\n\n\t ― Douglas Adams, The Hitchhiker\'s Guide to the Galaxy ' >> newFile<br />
cat newFile<br />
<br />
Excellent! We should now have a line of text in our newFile. <br />
<br />
<br />
+This is where we should probably talk about text editors.<br />
<br />
+This is where bash script should go<br />
<br />
<br />
<br />
rmdir ~/myNewDirectory<br />
<br />
== External Links ==<br />
# [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI'']</div>Dfirehttps://wiki.hackrva.org/index.php?title=Introduction_to_Linux(Linux_4_n00bs)&diff=1507Introduction to Linux(Linux 4 n00bs)2016-03-14T13:14:55Z<p>Dfire: </p>
<hr />
<div>'''SlideShow'''<br />
*[https://docs.google.com/presentation/d/1IAtkl9u0w84Q7L0SM7Vph3LjGWBV8Cdf19p5iqyZuHY/edit?usp=sharing Linux101]<br />
<br />
'''Step By Step'''<br />
* [[Diving Into Bash]]<br />
<br />
<br />
'''Getting Started''': <br />
* [[Getting Debian]] <br />
<br />
* [[Setting up your install media]]<br />
<br />
* [[Installing Debian]]<br />
<br />
* [[File System]]<br />
<br />
* [[Basic Commands]]<br />
<br />
* [[Package Manager]]<br />
<br />
* [[Text Editor]]<br />
<br />
<br />
<br />
<br />
* [[Challenges for After the Workshop]]<br />
<br />
''What is Linux and what are these "Distros"''<br />
<br />
Someone like John Vann should put some stuff here.</div>Dfirehttps://wiki.hackrva.org/index.php?title=Installing_Debian&diff=1506Installing Debian2016-03-14T13:14:12Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
'''Starting up the computer''':<br />
<br />
Place your imaged thumb drive or DVD in the computer intend to install Linux on<br />
<br />
"WARNING" This instruction is for a full hard disk install. If you wish to dual<br />
<br />
boot please reference the Debian official documentation.<br />
<br />
When turning on the computer your bios boot order may not be set to recognize the <br />
<br />
USB or DVD before the hard disk(or at all) and you may end up booting into an already <br />
<br />
installed operating system if this is not changed. When booting your computer may display<br />
<br />
a key to press to enter the BIOS menu or a boot menu. You can use the settings in <br />
<br />
either of these menus to change the boot order. If fast boot is enabled and you can <br />
<br />
not get this information from the display you may be able to press the delete key and <br />
<br />
get to the bios menu or you may have to consult your manufacturers manual for the appropriate<br />
<br />
key. Once the appropriate boot order is selected the computer will boot into the Debian<br />
<br />
installation menu. <br />
<br />
'''Installation''':<br />
<br />
''Language Selection''<br />
<br />
This is the first option you come to. For most people this will be American English<br />
<br />
''Setting a Hostname''<br />
<br />
This can be anything you want it to be. It is essentially the name of your computer<br />
<br />
''Enter a domain name''<br />
<br />
If on a private network this can also be whatever you want<br />
<br />
''Root Password''<br />
<br />
This password is for the root user (this user has all administrative rights to this machine<br />
<br />
and will not be what you are normally logged in as)<br />
<br />
''New User Real Name''<br />
<br />
This requests your real name but really it doesn't matter what you put<br />
<br />
''New User Name/Password''<br />
<br />
This is the username that you will normally log onto the computer with.<br />
<br />
''Time Zone''<br />
<br />
Select Eastern for EST<br />
<br />
''Paritioning(Guided-Use entire disk)''<br />
<br />
*select the hard disk which should be listed as /sda<br />
*select all files in one partition<br />
*select finish and write<br />
*"Write changes to disk" select yes<br />
<br />
at this point there will be a long pause while the file system is created and some files are copied<br />
<br />
''Scan another CD or DVD''<br />
<br />
Select No<br />
<br />
''Configuring Popularity Contest''<br />
<br />
This is essentially asking if you want to send data back to the developers. This is a personal decision<br />
<br />
I usually choose no<br />
<br />
''Select package to install''<br />
<br />
This is a personal preference based on what you want the machine to do. I almost always recommend at least SSHD.<br />
<br />
You can always install more packages later.<br />
<br />
*Now there will be a very very long pause while Debian is installed<br />
<br />
''Installing the boot loader''<br />
<br />
since we are not dual booting select yes to install Grub to the MBR(Master Boot Record)<br />
<br />
Choose the device /dev/sda (Your hard drive)<br />
<br />
''Installation complete''<br />
<br />
At this point you should take the installation media out of your machine and press continue.<br />
<br />
Your machine will reboot into your new operating system.</div>Dfirehttps://wiki.hackrva.org/index.php?title=Setting_up_your_install_media&diff=1505Setting up your install media2016-03-14T13:13:54Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
'''Create a bootable USB drive'''<br />
<br />
* Insert a blank USB drive into your computer.<br />
<br />
<br />
* To create a bootable USB drive the tool that I advocate using is the Universal USB Installer from www.pendrivelinux.com.<br />
Follow the above link for pendrive Linux and scroll half way down the page until you see the "Download UUI" link. Click on the download link and wait for the program to download.<br />
<br />
* When the download has completed double click on the executable.<br />
<br />
<br />
* When the license agreement screen appears read it and then click "I Agree" if you accept the license.<br />
<br />
* Creating the drive is fairly straight forward.<br />
<br />
* The first thing to do is choose your distribution of choice, in this case Linux Mint, from the dropdown list.<br />
<br />
* Click on the "Browse" button. Find the downloaded Debian ISO.<br />
<br />
<br />
* Select your chosen USB drive letter and make sure that the "We will format" option is checked.<br />
<br />
* At this point you can create the USB drive so that it persists data. This makes it possible to install software when using the live Linux Mint version and it will still be available the next time you boot from the USB drive.<br />
<br />
* Click "Create" to continue.<br />
<br />
<br />
<br />
* A summary screen will tell you what is about to happen.<br />
<br />
Basically your USB drive is about to be completely wiped and Linux Mint is about to be installed as a live image to it.<br />
<br />
If you are happy to continue click "Yes".<br />
<br />
<br />
* You will now see a progress bar showing how far through the process the installer is and how long it is expected to last.</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1504Diving Into Bash2016-03-14T13:09:31Z<p>Dfire: /* Creating a File */</p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
== Permissions == <br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
Change the permissions on your new directory and remove access to "Others." You can do this by running the following command:<br />
<br />
chmod 750 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxr-x--- 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User. The Group has read and execute. Others should have no access.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
== Creating a File == <br />
<br />
Let's make sure we are in ''myNewDirectory''.<br />
<br />
cd ~/myNewDirectory<br />
<br />
To create a new file we will use the [http://linux.die.net/man/1/touch touch] command.<br />
<br />
Create a new file and view the contents of that file with the [http://linux.die.net/man/1/cat concatenate ] command.<br />
<br />
touch newFile<br />
cat newFile<br />
<br />
The cat command should not return anything. This is because the file is empty. Try adding some content to the file.<br />
<br />
echo "The ships hung in the sky in much the same way that bricks don't." >> newFile<br />
cat newFile<br />
Excellent! We should now have a line of text in our newFile. <br />
<br />
<br />
+This is where we should probably talk about text editors.<br />
<br />
+This is where bash script should go<br />
<br />
<br />
<br />
rmdir ~/myNewDirectory<br />
<br />
== External Links ==<br />
# [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI'']</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1503Diving Into Bash2016-03-14T13:06:12Z<p>Dfire: /* Creating a File */</p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
== Permissions == <br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
Change the permissions on your new directory and remove access to "Others." You can do this by running the following command:<br />
<br />
chmod 750 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxr-x--- 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User. The Group has read and execute. Others should have no access.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
== Creating a File == <br />
<br />
Let's make sure we are in ''myNewDirectory''.<br />
<br />
cd ~/myNewDirectory<br />
<br />
To create a new file we will use the [http://linux.die.net/man/1/touch touch] command.<br />
<br />
Create a new file and view the contents of that file with the [http://linux.die.net/man/1/cat cat] command.<br />
<br />
touch newFile<br />
cat newFile<br />
<br />
The cat command should not return anything. This is because the file is empty. Try adding some content to the file.<br />
<br />
echo "The ships hung in the sky in much the same way that bricks don't." >> newFile<br />
cat newFile<br />
<br />
<br />
<br />
rmdir myNewDirectory<br />
<br />
== External Links ==<br />
# [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI'']</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1502Diving Into Bash2016-03-14T13:05:51Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
== Permissions == <br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
Change the permissions on your new directory and remove access to "Others." You can do this by running the following command:<br />
<br />
chmod 750 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxr-x--- 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User. The Group has read and execute. Others should have no access.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
== Creating a File == <br />
<br />
Let's make sure we are in myNewDirectory.<br />
<br />
cd ~/myNewDirectory<br />
<br />
To create a new file we will use the [http://linux.die.net/man/1/touch touch] command.<br />
<br />
Create a new file and view the contents of that file with the [http://linux.die.net/man/1/cat cat] command.<br />
<br />
touch newFile<br />
cat newFile<br />
<br />
The cat command should not return anything. This is because the file is empty. Try adding some content to the file.<br />
<br />
echo "The ships hung in the sky in much the same way that bricks don't." >> newFile<br />
cat newFile<br />
<br />
<br />
<br />
rmdir myNewDirectory<br />
<br />
== External Links ==<br />
# [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI'']</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1496Diving Into Bash2016-03-10T17:31:25Z<p>Dfire: /* Permissions */</p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
== Permissions == <br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
Change the permissions on your new directory and remove access to "Others." You can do this by running the following command:<br />
<br />
chmod 750 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxr-x--- 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User. The Group has read and execute. Others should have no access.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
<br />
<br />
<br />
<br />
rmdir myNewDirectory<br />
<br />
== External Links ==<br />
# linux.com : [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI''], Joe 'Zonker' Brockmeier</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1495Diving Into Bash2016-03-10T17:08:10Z<p>Dfire: /* Permissions */</p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
== Permissions == <br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
Change the permissions on your new directory and remove access to "Others." You can do this by running the following command:<br />
<br />
chmod 750 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxr-x--- 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User, the Group and Others.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
<br />
<br />
<br />
<br />
rmdir myNewDirectory<br />
<br />
== External Links ==<br />
# linux.com : [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI''], Joe 'Zonker' Brockmeier</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1494Diving Into Bash2016-03-10T16:57:47Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
== Permissions == <br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
For the sake of learning, let's throw security out the window. Change the permissions on your new directory to Allow All. You can do this by running the following command:<br />
<br />
chmod 777 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxrwxrwx 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User, the Group and Others.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
<br />
<br />
<br />
<br />
rmdir myNewDirectory<br />
<br />
== External Links ==<br />
# linux.com : [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI''], Joe 'Zonker' Brockmeier</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1493Diving Into Bash2016-03-10T16:57:06Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your [http://www.linfo.org/shell.html shell] open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
Exit it out of the man page and you should see the output of your last command<br />
<br />
'''drwxr-xr-x 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
The output is showing us the permissions, ownership, datestamp and Name of the directory.<br />
You can read more on permissions [http://www.linux.org/threads/file-permissions-chmod.4094/ here.]<br />
<br />
<br />
<br />
For the sake of learning, let's throw security out the window. Change the permissions on your new directory to Allow All. You can do this by running the following command:<br />
<br />
chmod 777 myNewDirectory<br />
ls -l<br />
<br />
<br />
You should now see something similar to this:<br />
<br />
'''drwxrwxrwx 2 linux101 linux101 4096 Mar 10 11:29 myNewDirectory'''<br />
<br />
Read, Write and Execute is enabled for the User, the Group and Others.<br />
<br />
<br />
<br />
[[File:LinuxPermissions.jpg]]<br />
<br />
<br />
<br />
<br />
<br />
<br />
rmdir myNewDirectory<br />
<br />
== External Links ==<br />
# linux.com : [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI''], Joe 'Zonker' Brockmeier</div>Dfirehttps://wiki.hackrva.org/index.php?title=File:LinuxPermissions.jpg&diff=1492File:LinuxPermissions.jpg2016-03-10T16:40:25Z<p>Dfire: </p>
<hr />
<div></div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1491Diving Into Bash2016-03-10T16:22:19Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your shell open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
cd /<br />
cd ~<br />
pwd<br />
ls -l<br />
<br />
chmod 777 myNewDirectory<br />
ls -l<br />
rmdir myNewDirectory<br />
<br />
== External Links ==<br />
# linux.com : [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI''], Joe 'Zonker' Brockmeier</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1490Diving Into Bash2016-03-10T16:21:59Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your shell open and ready for input.<br />
<br />
To find which directory you are in, type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
Now, let's make a new directory!<br />
<br />
Type the following command:<br />
mkdir myNewDirectory<br />
<br />
[http://linux.die.net/man/1/mkdir mkdir] stands for ''Make Directories''.<br />
<br />
<br />
<br />
If you type [http://linux.die.net/man/1/ls ls], you will see the directory you just created.<br />
<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
To navigate between directories, you will need to use the [http://linux.die.net/man/1/cd Change Directory] command. Take note of the output of pwd:<br />
<br />
cd myNewDirectory<br />
pwd<br />
cd ..<br />
pwd<br />
cd /<br />
pwd<br />
cd /home/linux101<br />
pwd<br />
ls -l<br />
<br />
Notice that we've added a parameter to the end of the ls command. Passing parameters to a command can allow you to make that function behave differently. <br />
<br />
If you compare the difference between ls and ls -l , you will see that ls -l gives you a more detailed view of this data (i.e. a long list.) You can discover more parameters of a command by looking at it's man page.<br />
<br />
Yo dawg, take a look at the man page of the man command.<br />
man man<br />
<br />
A man page will typically give you a synopsis, description, examples of the command and what options(parameters) it will take.<br />
<br />
<br />
cd /<br />
cd ~<br />
pwd<br />
ls -l<br />
<br />
chmod 777 myNewDirectory<br />
ls -l<br />
rmdir myNewDirectory<br />
<br />
== External Links ==<br />
# linux.com : [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI''], Joe 'Zonker' Brockmeier</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1489Diving Into Bash2016-03-10T15:40:11Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your shell open and ready for input.<br />
<br />
To find which directory you are in type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
mkdir myNewDirectory<br />
<br />
<br />
== See contents of that Directory ==<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
cd myNewDirectory<br />
cd ..<br />
cd /<br />
cd /home/linux101<br />
ls -l<br />
Notice that we've added more to the end of the ls command. This is a parameter. You can learn more parameters by prefacing your command with man. <br />
i.e. ''man ls'' will output the man page of ''ls''<br />
<br />
cd /<br />
cd ~<br />
pwd<br />
ls -l<br />
<br />
chmod 777 myNewDirectory<br />
ls -l<br />
rmdir myNewDirectory<br />
<br />
== External Links ==<br />
# linux.com : [https://www.linux.com/learn/tutorials/272346-bash-101-working-at-the-cli ''Bash 101: Working at the CLI''], Joe 'Zonker' Brockmeier</div>Dfirehttps://wiki.hackrva.org/index.php?title=Diving_Into_Bash&diff=1488Diving Into Bash2016-03-10T15:36:26Z<p>Dfire: /* Where am I? */</p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
<br />
== Where am I? ==<br />
At this point you should have your shell open and ready for input.<br />
<br />
To find which directory you are in type the following command.<br />
<br />
pwd<br />
<br />
This will output the directory that you are currently working in.<br />
<br />
[http://linux.die.net/man/1/pwd pwd] stands for ''Print Working Directory''.<br />
<br />
== Make a directory==<br />
mkdir myNewDirectory<br />
<br />
<br />
== See contents of that Directory ==<br />
ls<br />
The ls command will ''list'' the contents of a directory. <br />
<br />
== Change Directory ==<br />
cd myNewDirectory<br />
cd ..<br />
cd /<br />
cd /home/linux101<br />
ls -l<br />
Notice that we've added more to the end of the ls command. This is a parameter. You can learn more parameters by prefacing your command with man. <br />
i.e. ''man ls'' will output the man page of ''ls''<br />
<br />
cd /<br />
cd ~<br />
pwd<br />
ls -l<br />
<br />
chmod 777 myNewDirectory<br />
ls -l<br />
rmdir myNewDirectory</div>Dfirehttps://wiki.hackrva.org/index.php?title=File_System&diff=1487File System2016-03-10T15:09:07Z<p>Dfire: </p>
<hr />
<div>[[Introduction to Linux(Linux 4 n00bs)]]<br />
<br />
<br />
== General ==<br />
For more specific information navigate here: http://tldp.org/LDP/intro-linux/html/sect_03_01.html<br />
<br />
<br />
<br />
<br />
== /bin ==<br />
Common programs, shared by the system, the system administrator and the users.<br />
<br />
== /boot ==<br />
The startup files and the kernel, vmlinuz. In some recent distributions also grub data. Grub is the GRand Unified Boot loader and is an attempt to get rid of the many different boot-loaders we know today.<br />
<br />
== /dev ==<br />
Contains references to all the CPU peripheral hardware, which are represented as files with special properties.<br />
<br />
== /etc ==<br />
Most important system configuration files are in /etc, this directory contains data similar to those in the Control Panel in Windows<br />
<br />
== /home ==<br />
Home directories of the common users.<br />
<br />
== /initrd ==<br />
(on some distributions) Information for booting. Do not remove!<br />
<br />
== /lib ==<br />
Library files, includes files for all kinds of programs needed by the system and the users.<br />
<br />
== /lost+found ==<br />
Every partition has a lost+found in its upper directory. Files that were saved during failures are here.<br />
<br />
== /misc ==<br />
For miscellaneous purposes.<br />
<br />
== /mnt ==<br />
Standard mount point for external file systems, e.g. a CD-ROM or a digital camera.<br />
<br />
== /net ==<br />
Standard mount point for entire remote file systems<br />
<br />
== /opt ==<br />
Typically contains extra and third party software.<br />
<br />
== /proc ==<br />
A virtual file system containing information about system resources. More information about the meaning of the files in proc is obtained by entering the command man proc in a terminal window. The file proc.txt discusses the virtual file system in detail.<br />
<br />
== /root ==<br />
The administrative user's home directory. Mind the difference between /, the root directory and /root, the home directory of the root user.<br />
<br />
== /sbin ==<br />
Programs for use by the system and the system administrator.<br />
<br />
== /tmp ==<br />
Temporary space for use by the system, cleaned upon reboot, so don't use this for saving any work!<br />
<br />
== /usr ==<br />
Programs, libraries, documentation etc. for all user-related programs.<br />
<br />
== /var ==<br />
Storage for all variable files and temporary files created by users, such as log files, the mail queue, the print spooler area, space for temporary storage of files downloaded from the Internet, or to keep an image of a CD before burning it</div>Dfire