All Activity

This stream auto-updates   

  1. Today
  2. Finally decided to get MPLAB X up and going on my Slackware workstation, so I can pull the SSD out of my laptop and do a clean install on a new SSD. MPLAB X is NetBeans based and mostly Java, but apparently there are some system libs that are 32-bit x86 only Up til now, I just used it on my Arch Linux install on the laptop, since Arch makes multilib pretty painless. Slackware64 is "multilib ready," but does not include multilib stuff in the base install -- this gives you a clean 64-bit Slackware. I've never needed multilib under Slackware before, turns out it's not difficult. I followed alienbob's multilib guide: Beware that the mirror he gives is *very* slow, I ended up letting it run overnight. It worked fine, and provides everything you need to run MPLAB X (some GCC libs, X libs, et c.). Decided to do a proper SlackBuild and make a package. It's not been accepted to yet but you can find it here:
  3. NEW 'Off The Hook' ONLINE Posted 19 Jan, 2017 4:56:25 UTC The new edition of Off The Hook from 18/01/2017 has been archived and is now available online. "Off The Hook" - 18/01/2017 Download the torrent here!!!! View the full article
  4. Yesterday
  5. Since getting the HP 420 squared away with a proper mirrored ZFS volume, I've been working on getting to the point where I can shut down my old workstation, which was still limping along running a few applications, like my Dynamic DNS widget. I needed somewhere to run things like the Dynamic DNS system, and leave a tmux running for persistent IRC. I don't have a server rack up yet, so my old VM hosting box is currently offline. It's really too loud to run out in the main workshop area (you can hear it upstairs, the workshop is in the basement). Until then, I dug into the junk bin and put together a server: The case is a massive Lian Li aluminum ATX server case. I picked it up at a local tech surplus auction for, I think $10, with a power supply and a DVD drive. It looks kinda silly with so little hardware in it: The motherboard is an Intel Desktop Board DP43TF from a machine I built in probably 2009 and dismantled in 2010 or 2011 -- it developed a RAM error and I stole the Xeon CPU out of it to use in something else. The CPU is an Intel Core 2 Duo E4300, 1.8 GHz LGA775, 2 MB cache, that came from a computer we found in the trash that had exploded motherboard caps, but a good CPU and RAM. Power supply came from a friend's junk PC that I was given when he replaced it. There's no onboard video on the DP43TF so I've got a GeForce 8800GT stuck in there for the console at the moment 8 GB DDR2 came from another junk PC someone gave me. DVD drive and WD RE4 250 GB drive were on the spare parts shelf. I updated the BIOS to the 2011 release (was the original 2008 release) which is supposed to improve stability. It's currently running OpenBSD 6.0 AMD64, with various applications deployed to it with Capistrano (manages your deploys over plain SSH). Telephoney is going to send me a less power hungry PCIe card with VGA so I can get the GeForce 8800 out of there! I've though about finding another Xeon X3360 (quad core, 12 MB cache) for the board -- that's what I originally ran in it, and it's the fastest thing it will support, but it doesn't really seem worthwhile since this box is pretty old and should be temporary anyway.
  6. NEW 'Off The Wall' ONLINE Posted 18 Jan, 2017 3:13:54 UTC The new edition of Off The Wall from 17/01/2017 has been archived and is now available online. "Off The Wall" - 17/01/2017 Download the torrent here!!!! View the full article
  7. Last week
  8. I'm curious why you included the phone bill, is there a reason that I am missing?
  9. Rain. Rain. Rain. Rain. Rain. Rain. Rain. Rain. Rain. Snow. Snow. Ice. Ice. Ice. Ice. Ice. Ice. Ice. Freezing rain. Rain. Rain. Rain. Rain. Rain. Flood. Rain. Rain. Rain. Rain. Rain. Rain. Rain. Rain. God, I fucking hate LATA 672 winters.

  10. Dallas vs. Green Bay game was OBVIOUSLY hacked by the Russians....

  11. "supported" == don't call us, if you are getting kernel panics with something else. ;-) That Xeon also supports non-eec, assuming the MoBo does not complain, I'd use non-eec on a desktop. Unless one needs uptimes in the months - to years.... unsure the overhead of EEC is beneficial.
  12. I'll call that a shellacking. Hard to win NFL playoff games when the Lineman are stepping on the QB in their own end zone. 

  13. Actually, had an interview a few years ago and the lead I.T. guy really dawged me, because I didn't know Chef. I asked, "if I know Linux and Python how hard could it be? How many systems are you deploying each day?" After the discussion shifted to OS X, I pretty much got he was a gommer and didn't want someone who knew too much. "Yes... I love OS X, there is something to be said for a Unix operating system I could recommend to my Grandma' I.T. Admin Guy: "Really? I like it because of Open Directory structure for user and groups. It simplifies user and group and management... We look at things professionally...". Me: "Microsoft has been doing that since Server 2000? Active Directory is really light-years beyond OS X based Open Directory for professional use?". At that point figured he was just wasting time. Funny, he was an Autrailain guy living in the USA and ranting how Alibaba did not have chance in the USA because Americans were racist bigots. Haha. Thanks, I'll check that out after some NodeJS and JQueryUI/BootStrap.
  14. Here's my telephone bill from Southwestern Bell and I just turned 18 last month.
  15. Thank you guys, I wasn't sure if it was the adapter or not. For the school I go to, we have a project that we do that involves us going to a place of interest to stay there for a couple of weeks. I'll be working with VoIP switching (specifically PBX's) and SIP trunking. I'm glad you guys helped me out here, I'll be doing more research on VoIP and SIP protocols and I'll definetly ask questions if needed! By the way, I would've responded quicker but I slipped on ice and I'm pretty sure I broke my tailbone, so I haven't had the chance to respond.
  16. I forgot to run `lilo` after a kernel update, and finally powered the machine off last night for some rewiring, so this morning it kernel panic'ed on boot and I took the opportunity to redo the system with proper drives and configuration -- I just transplanted the disks out of the AMD Bulldozer machine, so it was booting off of a 128 MB boot partition (on a 1 TB drive, lol) and using a SSD as root, since the Bulldozer box's BIOS couldn't boot M.2 PCIe SSDs directly. New config: * Upgraded to BIOS 3.91 for M.2 boot support * Samsung SM951 M.2 SSD PCIe x4 128 GB * 2x WD RAID Edition 4 250 GB SATA drives * UEFI boot/UUIDs for disks * Slackware 14.2 x86_64 * ZFS on Linux, 1x mirrored volume across the two SATA disks BIOS update was the hardest part. The BIOS on the z420 will let you flash updates through the BIOS menu itself -- no having to come up with a DOS boot disk or anything. I didn't have a USB Flash drive around, so I tried with a CF card in a multi-card reader, which it didn't like. You can use a CD, too, so I dug out a spindle of CD-Rs only to get an unhelpful message about the BIOS image being missing or corrupt. Turns out the CD must be in the drive when you power the machine on! I had to clear CMOS settings using the little yellow reset switch on the motherboard after the update, it locked up after counting RAM. Slackware + UEFI was easy, I'd never done it before. The only "challenge" was that `cgdisk` had some issue where it was complaining that the console terminal wasn't at least 80x14, so I had to use `gdisk` (GPT version of `fdisk`). You of course use `elilo` instead of regular `lilo` with a UEFI system. Slackware's setup was able to successfully insert a Slackware entry into the workstation's EFI menu, so if I punch ESC at boot-up Slackware is now listed as an option, along with CD/USB/Network/et c. So, it boots directly from the M.2 SSD without having to have a boot partition on a SATA disk, and as a bonus, the BIOS update seems to have fixed my flaky SATA channel issue (I could run the SATA 3gbps channel in IDE mode, but AHCI mode would intermittently not boot). Ended up using GPT UUIDs for mounting the root disk, since adding the two WD drives threw off the boot order. Again, this is really easy, you add it to `/etc/fstab` and `elilo.conf` and that's it. ZFS on Linux was the usual simple Slackbuild install, I already had the packages built so I just copied them over from the fileserver. New install is working fine, and it's nice to be able to offload files to a mirrored ZFS volume, and keep the SSD free for stuff that actually needs fast access/high bandwidth. Plus now I can put the side cover on
  17. Earlier
  18. On the 12th of January 33 years ago, we released the very first issue of 2600. On that same date in 2017, we are officially releasing the brand new Winter Issue. (Incidentally, you could find all sorts of fun facts like this if you had your own 2017 Hacker Calendar.) It's never been easier to get the latest issue. Subscribing means you barely have to move. If you feel like going outside, you can find the current issue at all sorts of bookstores and newsstands. For those who prefer to go digital, we have Kindle subscriptions available in the United States and United Kingdom, and other digital subscriptions in those and other countries through Google Play and the Nook. And, of course, you can also get available back issues digitally or in print. A lot has happened since 1984. We suspect a great deal more is looming on the horizon. We hope you join us for the journey. View the full article
  19. Layered encryption really wears an HDD out fast!  Thought I had a good idea. :-(

  20. NEW 'Off The Hook' ONLINE Posted 12 Jan, 2017 4:19:55 UTC The new edition of Off The Hook from 11/01/2017 has been archived and is now available online. "Off The Hook" - 11/01/2017 Download the torrent here!!!! View the full article
  21. 303-223-9995 - Dialtone via Global Crossing Local Services DMS-500 213-455-9999 - Same thing, but via a CS-2000 in Anaheim. Both are toll restricted, so hopefully they'll be used to hone better switch playing techniques instead of being abused. Also, note the noticeable delay and comfort noise on the calls, even when you're local to them.
  22. Sure, but keep in mind that the one time password algorithm for the Definity is based on DES. I'm not a crypto guy, but based on what I know about DES, having faith in that even if an attacker doesn't have the keys seems like a dangerous game. Much like the passwords as well, the ASG keys for init and inads are probably the same for every processor using a specific build. Though I guess the problem with that is you don't know what build it is until you log in or physically look at the sticker on the processor. This'll definitely have to be explored further at some point - maybe they use the same inads or craft or whatever key on every build. Ostensibly, yeah. The header and object files we got from the RPM should allow anybody who uses it in their code to encode and decode license keys, and from the look of the functions, probably make and test valid ASG keys as well. The idea behind disassembling the object files was to try and get an idea of how the functions work - and that's still a valid choice, but it might be less work to just use them as is through trial and error. Of particular note in asg.h is this: struct lic_info { unsigned char version[4]; unsigned char filler[6]; unsigned char hexkey1[8]; unsigned char hexkey2[8]; }; along with the four functions in license.h . Since gewt has a switch with a valid license, I was hoping we could use this to test data we know for sure works against anything we happen to write with these ASG functions. Sure! I'll send you a PM.
  23. As much as I wish something like that were true, I don't think it is. Here's how I understand it: The server processing your calls has no involvement in the local calling area. It's, let's say for example, in Texas. Wherever Vonage feels is cheapest and has the best internet connectivity. When your call hits the switch - or really, the call agent (if I understand correctly) in voip terms in Texas, it does a ported number dip on what you're calling, and looks at a least cost routing database. From there, it determines the cheapest carrier to terminate traffic to whatever exchange you're calling. Sometimes this is via a switch in the terminating local calling area. Other times, it's terminated back onto a toll trunk and completes like a normal long distance call. It all depends on what's more practical for the carrier. If it's an expensive destination, sometimes a carrier will use under the table methods of terminating traffic. For incoming, it's a little different. A DID provider will have their own switch in your local calling area - probably something made by Sonus, and they sell those incoming numbers to Vonage. Vonage uses DIDs if I remember right. Anyway, when it hits the number, it sends the call via the internet to that switch in Texas, which in turn knows to relay it to you. Anyway, as JCSwishMan said, the analog telephone adapter in your house counts rotary dial pulses itself. What it thinks you're done dialing, it'll put the digits in the SIP invite header along with other information, and send it to the switch in Texas. All good, man. Almost everybody starts in this sort of hobby in their teens. If someone implies they're in that age group, I think it's just an unspoken truth here.
  24. So, one of the things with Puppet/Chef/Ansible/Salt, et c. is you get a base configuration set up, and you work off of that. A quick way to get up and going is to play with Vagrant, which includes many premade generic "boxes" (VM appliances, whatever you're used to calling them): We usually skip Chef on our development VMs and just use the command line provisioner -- you just script it like you would a regular bring-up before all of these devops tools were available. Our VMs that use Chef in production are written with Vagrant first, though, so we not only have a same-as-production VM to develop against, but we also don't have to use a remote VM to get the Chef recipes tweaked. I don't know if it's just us, but it seems to me that every time we Chef a VM, it takes an order of magnitude more time to get the Chef scripts just right as compared to manually deploying the same number of machines. I guess the benefit is repeatability and documentation. It often seems like these tools are trying to solve social/organizational problems with technology, which ultimately I think is doomed to fail. Yeah, dumping legacy tools is frustrating. I like that both Slackware and Arch provide a replacement for `ifconfig` -- I don't know if it's the old code or merely a wrapper around `ip`. I find `ip` syntax to be kind of obtuse. It feels like it tries to do too many things.
  25. Yes. I am actually doing a CentOS tutorial for a Lynda(ish) company. CentOS is great with the GUI. To put my comment in light: "I wish CentOS had an out-of-the-box CLI version like Ubuntu server. I really need to learn Puppet. Like really, badly now. So hard to keep skills up-to-date these days, I miss the 90's and cushy I.T. work. When I installed the minimal CentOS for a CMD install: I jumped through a million hoops to get WiFi working. Was not please to see: adapter: wisdf9i80s8ifs08fsdfsdf0. I could not copy and paste. :-( My memory sucks and the hardest part of the job (despite trying to find packages) was memorizing wsiakjjkwresadfsadflk;kjl90. Finally renamed then to: wifi0 and eth1. :-) After reading, yes, ifconfig is now considered obsoleted. Guess I can blame that on myself and not keeping up. But it is still there with every other distro. I'll possibly think of updating my skillset instead of bitching and complaining. :-/
  26. Thought writing would be fun. :-(  Complete new CentOS Admin Tutorial in 3! 1... 2... (wait, my coffee needs refill)... 

  27. I think all of the grunt work of 'translating' rotary / dial pulse to MF (or whatever TF digital channel crap is used in CCIS / SS7) to send via VoIP would be done within the adapter box. What it does with the data that comes out of the box... Well, this is purely guesswork... But I'd think that whoever your ISP is has an exchange (or several) reserved at a switch (which may or may not be local), that's basically a forwarding address. VoIP traffic acts like Internet traffic til it gets to the switch, the switch recognizes is as 'telco' data, shunts it to the proper connector for the phone number, and then shunts it to the data pipe that feeds your house. Please by all means correct me if I'm wrong, you other experts.
  28. I have an old rotary phone that I like to use to talk on, and apparently Vonage (it's my mom's line, I wish we had a POTS or something similar) allows it to work. Does anybody know why it works? I'm guessing Vonage directly forwards the VoIP packets to the local switch, but i thought I might as well ask to see if anybody else knows. In case you are wondering why I'm using my mom's line, I'm 17 and still in her house.
  29. NEW 'Off The Wall' ONLINE Posted 11 Jan, 2017 3:37:57 UTC The new edition of Off The Wall from 10/01/2017 has been archived and is now available online. "Off The Wall" - 10/01/2017 Download the torrent here!!!! View the full article
  1. Load more activity