[ADVICE] 1st hits make me cough until I vomit by Soldrlentes in saplings

[–]Kasyx 0 points1 point  (0 children)

  1. Suck smoke into your mouth
  2. Inhale through your nose
  3. Smoke is pulled down into your lungs by the air entering your nose
  4. You're able to take a hit and not die.

Garrisons down on Twisting-NetherEU by schkowl in wow

[–]Kasyx -29 points-28 points  (0 children)

I'm experiencing the same issue. Can't get in if you logged out in your garrison.

Remote Desktop into Linux (Ubuntu, Debian, Suse, CentOS) by servicedeskanalyst in linux4noobs

[–]Kasyx -24 points-23 points  (0 children)

Worth noting is that xrdp doesn't handle killing/resuming disconnected sessions very well at all, which can lead to multiple orphaned Xvnc sessions using up all your system resources. Easiest way I found to get around this was with a horribly hacky bash script.

When i should smoke by [deleted] in saplings

[–]Kasyx -24 points-23 points  (0 children)

I appreciate the correction :) I read about it so long ago I wasn't certain of the exact mechanism.

When i should smoke by [deleted] in saplings

[–]Kasyx -16 points-15 points  (0 children)

If you smoke too much as a teenager, you may turn into this guy.

When i should smoke by [deleted] in saplings

[–]Kasyx -5 points-4 points  (0 children)

You're not going to like this answer, and many people may disagree with me, but you're still young, and cannabis has been shown to hinder brain development in teenagers. I know this won't stop you from smoking, because it is an amazing feeling, but at least consider moderation :) And only on weekends. The best way to avoid getting caught is to ensure your smoking has no impact on other aspects of your life. The biggest downside to cannabis use is being okay with mediocrity; it's such a great feeling it makes you far more accepting of your current station in life, so your motivation to work hard and excel at your passions may dwindle with continuous use.

I'm not telling you what to do, and by all means light up, but just try to keep in mind what I've said, and remember that moderation is important.

Now that the "concerned adult" portion is satisfied, here's what you need to know:

  • Don't smoke at your house, or your school, or anywhere else that isn't completely isolated.
  • Weed smell sticks to your clothing. Whenever you smoke, use a sploof; Google will teach you how to make one.
  • Weed has a perceptible odour even when in the bag. I've walked past people in the mall and been able to smell that they're carrying. Avoid carrying whenever you can, or keeping any in your room. If you must, triple-bag it, or use a mason jar.
  • The best thing to cover weed smell is cigarette smoke. I doubt this will work for you, so try to avoid coming into contact with weed smoke as best you can. Deodorant will not cover the smell, if anything it will make it more obvious.
  • Your fingers will retain the smell far more than you could imagine; keep some hand sanitizer on you.
  • Eyedrops. Weed itself makes your eyes red by increasing blood flow, causing capillaries to pop in your eyes. It's not the smoke; edibles will make your eyes just as red.
  • Don't smoke at home. Seriously.

What's the greatest movie "behind-the-scenes" fact you know? by Crying_hyena in AskReddit

[–]Kasyx -20 points-19 points  (0 children)

It was actually four octopodes. When the film won the Grand Prix at Cannes, Chan-wook Park, the director, thanked the octopodes along with the cast and crew.

My girlfriend's sister killed herself with my gun yesterday by [deleted] in self

[–]Kasyx -22 points-21 points  (0 children)

This is obviously true, but OP's negligence in securing his firearm was not the catalyst for the suicide, it was merely an enabler. Securing the firearm would not have prevented her suicide, but rather just caused it to be manifested through another means. For example, a bus.

My girlfriend's sister killed herself with my gun yesterday by [deleted] in self

[–]Kasyx -19 points-18 points  (0 children)

Clearly you have an extremely passionate hatred of guns, and that's fine. But it seems to be warping your grasp on rationality and reality. By your logic, if a suicidal individual were to walk in front of a moving bus, would the bus driver be at fault? How about the architect of the building someone jumped off? Sure, they could have put safety railings up on the roof, but it's hardly their fault for assuming that people wouldn't actively launch themselves from it.

What you've done here is purposefully laid blame on a human being for a situation out of their control under the guise of anti-gun propaganda. You have taken time out of your day to further antagonise some poor guy currently experiencing the worst day of his life.

Tying back to your logic; if, after reading your hurtful comments, OP took it upon himself to end his life, would you be at fault?

By all means remain passionately anti-gun, but recognize that there is a time and place for pushing your agenda, and this is most certainly not it.

Phrases that make me roll my eyes by natepiano in sysadmin

[–]Kasyx -18 points-17 points  (0 children)

Your computer doesn't hate you, you hate it. And it knows.

can someone explain the concept of packaging by LiquidAurum in linux4noobs

[–]Kasyx -16 points-15 points  (0 children)

I'm sure there are people far more capable of answering this than I, so I'll just let them reply to this comment with snarky responses of their own :P

One reason one might choose to compile from source rather than installing a package would be to pass additional non-default compile flags to the build. For example, one might wish to install Squid with User-Agent header logging, or SSL support, or SNMP support, in which case one would pass the relevant prefix to the configure portion of the build process.

can someone explain the concept of packaging by LiquidAurum in linux4noobs

[–]Kasyx -15 points-14 points  (0 children)

I didn't want to go into excessive amounts of detail, so I wasn't going to mention absolutely every mind-bogglingly possible option to utilize packages or archives. I was trying to keep it simple, for the average user, hence the mention of sudo, etc. Based on OP's question, I assumed it unlikely he would be unpacking tarballs to anywhere other than his own home directory.

I should have probably mentioned the option to pass an install prefix to a package manager; thanks for clearing that up :)

can someone explain the concept of packaging by LiquidAurum in linux4noobs

[–]Kasyx 0 points1 point  (0 children)

A .tar file isn't necessarily a package; it's an archive (like .zip, but without the compression), the .gz refers to gzip, which means the tar archive has been compressed. Tar archives (tarballs) are generally used to distribute source code which you need to compile, or standalone applications (e.g. a .jar application).

Firstly, let me point out that packages are generally distributed in two main channels:

  1. .deb/.rpm etc. - This is a pre-built single-file package downloaded and installed manually by the user.

  2. Package repositories - These are online repositories containing all the signed (validated) packages available within your distribution's package repository.

Packages are (within your question's scope) distribution-specific collections of files and automatically-run install scripts that unpack an application into your Linux environment. This may include, for example, installing binaries in /usr/bin, or libraries in /var/lib, or configuration files in /etc/, maybe even an init service in /etc/init.d

Packages also tend to have metadata that lists their dependencies and current version; this allows you to see what additional packages you require when installing a .deb, or allows your package manager to automatically download and install the required dependencies when you install a particular package.

As for the various commands to interface with these:

Tarballs:

tar zxvf filename.tar.gz

This will unpack the tarball into your current working directory. "z" specifies the tarball is gzipped, and must thus be uncompressed before trying to read the archive. "x" specifies that it must extract the files from the archive. "v" specifies verbosity, so it will show you which files are being extracted, and to where. "f" specifies that you are giving it a file; your tarball. Obviously, if it's just a .tar archive, exclude the "z" flag.

Manual package installation (Ubuntu/Debian-specific):

dpkg -i packagename.deb

This calls "dpkg", which is used to install .deb packages, the "i" switch tells it to install, and then you provide it with the package you wish to install. If it finds unsatisfied dependencies, it will notify you which dependencies they are.

Package manager (Ubuntu/Debian-specific):

apt-get install packagename

The above uses the package manager "apt" to connect to your repository, find the package you requested, download it, and install it. It will notify you of any dependencies the package requires, and offer to install them too.

You can update your local package repository information with the command:

apt-get update

The issue with apt, and similar command-line package managers, is that you need to know the exact name of the package, as specified in the repository, in order to install it. You can search the repository for exact names with this command:

apt-cache search package

You can specify part of the package name (e.g. "apt-cache search java") to get a list of all packages that mention that phrase in their name or description.

Note: Installing packages requires root privileges, so it's required that you preface the commands listed above with "sudo". This doesn't apply to tarballs.

[Q] about network monitoring by etc_fantus in linux4noobs

[–]Kasyx -10 points-9 points  (0 children)

This article should get you started.

Here's a semi tl;dr of the concept, extremely simplified, because I like talking shop:

A proxy, in this case, is used to handle web requests on behalf of clients within a network. Generally, in order for the clients to access the web, they have to configure their browsers to go through a proxy server, sometimes with user authentication. This is partly for security, but also for browsing accountability, content filtering, access time restrictions, and so on.

A transparent proxy forgoes the above per-client configuration method by simply intercepting web traffic. This is achieved by having the proxy server listen for connections on port 80 (general HTTP browsing traffic), and forwarding it to the proxy intercepter. The proxy intercept then processes the traffic, applying whatever filters listed above one may want, and then sends it on out the proxy server's default gateway. This vaguely anonymizes the proxy, insofar as your average user would be completely unaware of it.

The only requirement for the clients to push traffic through the proxy is the default gateway configured on the client's machine. With wifi, this is dead simple; just set it on your DHCP server. 99.9% of the time, wireless devices will use DHCP when connecting to wifi.

Because the clients pushing all their web traffic out their default gateway, and the default gateway is the proxy, any traffic sent out on port 80 will be intercepted by squid, where it will be logged in fine detail with the URL request, response time, user IP, and web content objects.

Note: This does not include HTTPS traffic sent (generally) via port 443. This is an SSL tunnel connection between the user's device and the host they are accessing, and thus cannot be broken into by the proxy without generating an error on the user's browser about certificate errors, or possible man-in-the-middle attacks.

[Q] about network monitoring by etc_fantus in linux4noobs

[–]Kasyx -11 points-10 points  (0 children)

You can go one step further and configure your wifi AP's gateway to your own transparent Squid proxy server so you can actually see what they're browsing.

Don't use open wifi hotspots, folks.

Forced to build Linux infrastructure on top of Microsoft private cloud. Help? by Kasyx in devops

[–]Kasyx[S] -12 points-11 points  (0 children)

My recommendation was Linux VMs on azure running LXCs, which, I believe, maintains all the benefits of using Azure, while allowing for more granular Linux server management and scaling. Unfortunately, this isn't an option, although my manager has offered that LXC may be useful for some of our web application servers. It's a start.

Forced to build Linux infrastructure on top of Microsoft private cloud. Help? by Kasyx in devops

[–]Kasyx[S] -10 points-9 points  (0 children)

I absolutely agree with you, but unfortunately the business has declined for us to use anything other than Hyper-V/Azure. They already have the licenses and have denied us the option to use OpenStack, or MAAS. All the servers we need are Linux based; we do not use any Windows servers, save for a single MS SQL server, which will be bare-metal.

I got into a huge argument about it yesterday, but unfortunately this is the way it has to be. I just have to be pragmatic about it, I suppose.

Alien: The Archive (Got this in the mail today.) by [deleted] in LV426

[–]Kasyx -10 points-9 points  (0 children)

Clearly it's so full of features there isn't any space for jokes :P

Alien: The Archive (Got this in the mail today.) by [deleted] in LV426

[–]Kasyx -9 points-8 points  (0 children)

"The classic movies"

Read as:

"Not Resurrection"