Fetzie

Member
  • Content count

    3,510
  • Joined

  • Last visited

Reputation

  • check
    Agree 298
  • info_outline
    Informative 28
  • tag_faces
    Funny 117
  • thumb_up
    Thumbs Up 72
  • thumb_up
    Likes (Old) 1690

Awards


This user doesn't have any awards

3 Followers

About Fetzie

  • Title
    Don't Panic
  • Birthday 1987-08-18

System

  • CPU
    Intel Core i7 5820K (4.5GHz @1.3V)
  • Motherboard
    MSI X99A MPower
  • RAM
    32 GB Kingston HyperX Fury DDR4 2666MHz
  • GPU
    Gigabyte HD 7950 Windforcex3
  • Case
    Fractal Design Define R5
  • Storage
    Samsung 951 M.2 nVME 512GB, Crucial M200 1000GB, Crucial M500 256GB, Western Digital Caviar Black 2TB, Western Digital Caviar Green 1.5TB
  • PSU
    Seasonic 860 Platinum
  • Display(s)
    Dell U2414H, LG IPS234
  • Cooling
    Noctua NH-D15
  • Keyboard
    Corsair K90
  • Mouse
    Logitech G502
  • Sound
    Samson SR850
  • Operating System
    Windows 10 Pro x64

Contact Methods

Profile Information

  • Gender
    Male
  • Location
    127.0.0.1
  • Occupation
    Quality Assurance engineer, working with VoIP telephone systems

Recent Profile Visitors

1,656 profile views
  1. It depends on the company. I work for a company that builds VoIP telephone systems, so I do a lot of network stuff, occasionally setting up ISDN in the lab to reproduce issues and so on. I also do a certain amount of scripting, load test analysis and some programming of tests. In other companies you can be doing customer support, driving out to customers to fix things or install systems, maintaining internal IT infrastructure and so on.
  2. Activate the Linux Subsystem for Windows. then run apt-get install alien Convert .deb to .rpm with command alien -r /path/to/package.deb
  3. Anyway, to get back to answers to @Saddy 's OP (who asked how they can maybe recover the lost data), this is a great piece of software: https://www.piriform.com/recuva It has an option to install it on a USB stick to avoid writing to drive sectors that could contain files. The free edition can get pushy about upgrading to the paid version, but I have had great success recovering "lost" files with it in the past.
  4. Simply having a copy would have been useful though (I mirror my local stuff to a second drive so that I have a backup even if the Internet goes down or I have a git brainfart). Especially if you have not yet set up said vcs. Also, I never fucking said that the OP should not use a vcs so you can cut the high and mighty attitude.
  5. Your webserver does not have permission to read the file at /root/vendor/autoload.php /root/ is the home directory of the "root" user.
  6. Or even just make a copy of stuff if you can't be bothered learning git / svn / any other VCS
  7. @Joveice You can give your webserver's user permission to only execute sudo commands in scripts in certain locations (IIRC that's defined in in /etc/sudoers.d). You can also only give it permission to alter the folders and their contents that you want it to be able to alter ( chown -R and chmod xxx ). You can also run the webserver under a system user which doesn't have a shell (set in /etc/passwd - means that you can't su -u webserver as a different user to use those sudoer permissions). To make sure that nobody passes extra arguments to your scripts (service webserver restart&&rm -rf /) you can also whitelist the arguments permitted, which would be something like this: #!/bin/bash serviceName="webserver" passedCommand=${1} PERMITTED_ARGS=( "restart" "stop" "start" "status" "condrestart" ) for i in "${PERMITTED_ARGS[@]}"; do if [[ "${i}" = "${passedCommand}" ]]; then service ${servicename} ${passedCommand} fi done
  8. It will be interesting to see some undervoltage testing, because Polaris responded really well to reducing its voltage.
  9. Eh, you get fucked over either way tbh. You just have to find the compromise that works least badly for you.
  10. When the need for discussion is resolved before you finish reading the OP, can't really blame them for going OT
  11. I need this in my life. Why? Because reasons
  12. My desktop has an nVMe boot drive. My laptop has a sata SSD boot drive. There is literally no noticeable difference between the two when booting Windows (not counting the much longer X99 post time). The only difference is when reading very large (10GB and larger). The PC reads the file into ram much faster than the laptop.
  13. It isn't even teething problems with the new µArch, it's a barely-used operating system that is temperamental about hardware support to begin with that doesn't handle interrupts properly (the issue is reproduceable on Kabylake too).
  14. How easily it can be fixed relies on how much of the OS needs to be rewritten.
  15. It's an interrupt scheduling bug. Which part of the computer is responsible for interrupt scheduling? That's right, it's the OS.