@valentina Aren't those super little?

@travisdh1 said in Making a Bootable USB Stick on Linux Mint 17.3:

@Dashrender said in Making a Bootable USB Stick on Linux Mint 17.3:

For the sake of the thread - those on Windows - use Rufus to create a bootable USB stick from the ISO.

I've been using YUMI from within Windows.

If I want more than a single distro on a single usb stick, I'll even use it in Linux, just because it's so much easier/quicker to do.

Yumi has also been my tool of choice when creating bootable usbs. I really like having several distros and tools easily available without the need to carry around several sticks.

Happy Birthday @scottalanmiller !!

I always thought with 2 dns servers you set them to point at each other as primary and then to themselves as secondary. Most people always told my something like this:

If multiple DCs are configured as DNS servers, they should be configured to use each other for resolution first and themselves second. Each DC's list of DNS servers should include its own address, but not as the first server in the list. If a DC uses only itself for resolution, it may stop replicating with other DCs. This is obviously not an issue in a domain with only one DC.

@WrCombs Everything in the same network is being switched no matter if its wireless or wired. In order to route, you need to move the packets to a different network.

I use cloudways, mainly because I was actually not comfortable hosting a public facing web page on my own. It is in my plans to properly learn to manage a stack such as the one used by cloudways including the different layers of caching but I am not there yet.

@WrCombs For networking basics, I would also recommend using PacketTracer. You will need to have some basic Cisco routing and switching cli knowledge (guides and resources are available all over the web). Having the ability, to actually see packets travel to your lab network is super valuable when you are starting and will help you really understand routing. You can work with static routes or dynamic routing protocols like OSPF, rip v2, etc. inside packet tracer.

Here is a work in progress lab, using L3 switches as core internal routers and several vlans. Its simulating a network transitioning from a big flat 10.10.0.0/20 to several vlans

Computer objects have cmd terminals, webbrowsers and other stuff so you can troubleshoot network stuff via ping, tracert, etc.

I really like it and use it quite a lot when I am troubleshooting network issues that I need to have a diagram and see how the packets can flow within the network.

@Joel Do you want to change the regional settings per user or system wide?

@Pete-S only Cisco gear that label along with the sonic wall was more as documentation for myself.

@Romo said in Creating an anonymous samba share in CentOS 7:

@wirestyle22 said in Creating an anonymous samba share in CentOS 7:

@Romo Still don't know where I'm going wrong here Is this correct?

-Modify your global config settings :
map to guest = Bad User you wrote Bad user

Restart your services
systemctl restart smb.service
systemctl restart nmb.service

Check your folder owner and permissions again.

Did you change your global configuration settings?

@wirestyle22 Great!!

@JaredBusch It's true, totally forgot we used setenforce 0 in the guide, so I am not actually finished just yet then =P

Using setsebool -P httpd_can_connect_zabbix=1 everything appears to be working.

I use iftop as well.

@Sparkum Agents listen on port 10050 and apparently the server listens on port 10051;

so runnning the following on the server:
firewall-cmd --permanent --add-port=10051/tcp
systemctl restart firewalld

Should get the agents connecting properly to the server, I haven't tested it because I have not set any agents to monitor yet in the lab, but from reading the documentation is should work.

If you are talking of the default server root for nginx, it is actually located in /usr/share/nginx/html .

You can modify the location by editing the nginx global config file found in /etc/nginx/nginx.conf

@hobbit666 You can use either way, they both accomplish the same thing that is downloading the newest source files.

Step 1: Backup your database
While logged in, go to Admin > Backups and generate a new backup. Download that file and keep it somewhere safe, in case you need to restore back to that version if something goes wrong with your upgrade.

Step 2: Backup your old version
The easiest way to do this will be to just rename your old Snipe-IT install directory and create a new, empty directory that uses the old directory name, but you can handle this any way that works for you.

For example, if your Snipe-IT was installed in /var/www/snipe-it, you could rename that directory to /var/www/snipe-it-backup and then create a new directory /var/www/snipe-it.

Step 3: Download/clone the new release
Download the zip from: https://github.com/snipe/snipe-it/archive/master.zip
or
git clone https://github.com/snipe/snipe-it.git

Step 4: Update dependencies
Whenever you pull down a new version, you should update the dependencies via Composer and dump the autoloader.

NOTE: Never run composer as a super-user or Administrator. Always run it as the user that owns the Snipe-IT files. Running composer as a super-user will break things in ways that will be difficult to debug later. Just don't do it.

1st you'll need to install composer into the directory if you don't have it installed globally:

cd <install-dir>
curl -sS https://getcomposer.org/installer | php 

Noq update dependencies and dump the auto-loader.

php composer.phar install --no-dev --prefer-source
php composer.phar dump-autoload

Step 5: Copy over your configuration settings

IMPORTANT:
This step will only need to be done once, while upgrading to v3.0. Once you've upgraded to v3.0, you won't ever have to do this part again.

Open up your .env file in your new Snipe-IT install directory, and update the configuration placeholders you see there with the values you were previously using in your individual config files.

If you don't have a .env file, just copy the existing .env.example over to .env and use that:

cp .env.example .env

The files you'll be copying from are:

• app/config/app.php
• app/config/production/app.php
• app/config/production/database.php
• app/config/production/mail.php
• app/config/production/session.php

New .env Setting	Old Config File	Old Config File Key	Notes
APP_ENV	N/A	N/A	Set to production
APP_DEBUG	/app/config/production/app.php	debug
APP_KEY	/app/config/production/app.php	key	Make SURE you keep this app key the same from your old version.
APP_URL	/app/config/production/app.php	url
APP_TIMEZONE	/app/config/app.php	timezone
APP_LOCALE	/app/config/app.php	locale
DB_CONNECTION	/app/config/production/database.php	default	This should be mysql
DB_HOST	/app/config/production/database.php	connections-> mysql-> host
DB_DATABASE	/app/config/production/database.php	connections-> mysql-> database
DB_USERNAME	/app/config/production/database.php	connections-> mysql-> username
DB_PASSWORD	/app/config/production/database.php	connections-> mysql-> password
DB_PREFIX	/app/config/production/database.php	connections-> mysql-> prefix
DB_DUMP_PATH	N/A	N/A	Path to your dabase dump binary (such as mysqldump)e.g. '/usr/local/bin'
MAIL_DRIVER	/app/config/production/mail.php	driver
MAIL_HOST	/app/config/production/mail.php	host
MAIL_PORT	/app/config/production/mail.php	port
MAIL_USERNAME	/app/config/production/mail.php	username
MAIL_PASSWORD	/app/config/production/mail.php	password
MAIL_ENCRYPTION	/app/config/production/mail.php	encryption
MAIL_FROM_ADDR	/app/config/production/mail.php	from->address
MAIL_FROM_NAME	/app/config/production/mail.php	from->name
IMAGE_LIB	N/A	N/A	Should be set to gd or imagick, depending on which library you have on your server.
SESSION_LIFETIME	/app/config/production/session.php	lifetime
EXPIRE_ON_CLOSE	/app/config/production/session.php	expire_on_close
ENCRYPT	N/A	N/A	Should be set to true if you wish to encrypt your cookies.
COOKIE_NAME	/app/config/production/session.php	cookie
COOKIE_DOMAIN	/app/config/production/session.php	domain
SECURE_COOKIES	/app/config/production/session.php	secure

Everything else in your .env can be left alone, as they are more advanced settings that are not commonly used.

Step 6: Move uploaded files and check permissions
Since Laravel's file structure has changed, you're going to need to move a few files around to make sure your uploaded files (logo, uploaded asset files, asset model files, etc) are in their new location.

cp ../snipe-it-backup/app/storage/dumps/* snipe-it/storage/app/backups/
cp ../snipe-it-backup/app/private_uploads/* snipe-it/storage/private_uploads/
cp ../snipe-it-backup/public/uploads/* snipe-it/public/uploads/

Also confirm that your entire storage directory (and subdirectories) is writable by the web server.

Step 7: Migrate the database
Always run your database migrations on any upgrade, as this will make sure your database schema is up to date with what the new code expected.

php artisan migrate

Forgetting to run these commands can mean your DB might end up out of sync with the new files you just pulled, or you may have some funky cached autoloader values.

It’s a good idea to get into the habit of running these every time you pull anything new down. If there are no database changes to migrate, it won't hurt anything to run migrations anyway, you’ll just see "Nothing to migrate".

Step 8: Launch Snipe-IT in a browser
You should be all set now, so just go to your old Snipe-IT URL and make sure everything is working.

I have been researching a bit more about hyperconvergence and found them. I just wanted to hear the opinion of the community about their products. As I understand they have a similar product to what @scale have.

@cnewman said in What is a Linux Distro:

@stacksofplates said in What is a Linux Distro:

@cnewman said in What is a Linux Distro:

@scottalanmiller said in What is a Linux Distro:

@cnewman said in What is a Linux Distro:

Please show me my response to that and let's get back to the REAL subject you;re avoiding the Linux Kernel

That's been covered thoroughly. We are waiting for you to figure out what you got wrong, contact the sources you have (that don't exist) and send us their responses. The ball is in your court. As I said, asking us to do anything further to contact your sources and correct them (or to show that they agreed) is the same as admitting you made it up.

Awesome you have no balls, sorry about that, THE LINUX KERNEL MY MAN WHAT ABOUT THAT DUDE?

He already asked you how you use the Kernel. But you never answered.

Ignorant question, I said to tell at LEAST Linux.com they are stupid for saying it's an OS BUT YOU FAILED TO DO SO = NO BALLS

This response is just...so....no can't describe it.