It is the way of things. *checks his uid* yeah,
It is the way of things. *checks his uid* yeah,
I'm one of the community directors at Louisville, Kentucky's community LVL1 Hackerspace. We're a 501(c)3 w/ a focus on education and outreach, and we're not tied or beholden to any specific school, commercial entity or large sponsor. I don't have the time this exact second to answer something this in depth thru the comment system here, but I'd be happy to provide any info I can if you want to reach out to us thru the email addresses or google groups listed at lvl1 dot org. Given our several year history, we've seen a lot of what works and what doesn't as well as ways to speed up involvement and to help explain the results of various compromises over the years.
I don't know your exact budget as it's not detailed but Axis has made quality webcams for >15 years (I've got a 2100 from ~2000 and it's still running fine) and they support ftp uploading. The small M10s are dirt cheap, but work well. Check out http://www.axis.com/products/m... to see. If you want something fancier look at their higher priced offerings with better features. I don't work there, own stock, resell them, etc, but I've had great luck with their cameras for a really long time.
If you don't care to 'win' the fight w/ comcast, then go get a budget ($1/month) VPS running CentOS like from somewhere cheap like Crissic or Ramnode and use it to route your outbound email. It'll cost you less in actual dollars than your time investment in fighting comcast to date at minimum wage or that you'll spend reading the comments on this 'ask me anything' I figure
Just an option!
Background: I've professionally administered Unix and Linux machines for >25 years, including various BSDs, Linuxes, Irix, HP-UX, Solaris/SunOS, AIX, etc. I've been certified by several vendors or distributions, including, since 1999, Red Hat (which gives me quite a bit of background on their specific implementations over the years). I don't work for a company doing development of any OS or platform. heck, other than random 401K type aggregate ownership, I don't own stock in any company that cares about this issue at a deep level, to the best of my knowledge
Personal Bias about this thread: You pretty much lose all the credibility possible with me when you start of with "I
Seriously, there're thousands of pages of documentation about what it is, how it works, and what most if not all of the design basis decisions are/were. I'll link you to a few of them because hey, you can get to slashdot and post, but you can't seem to use Google
Systemd has tons of upside and tons of downside. Most are pretty well detailed, although many of the gut reactions people seem to have to it are based on a lack of understanding about how it works and what it's compatible with, to wit "I can't use shell scripts for anything at startup anymore!" , "All of my old chkconfig or SysV scripts can't be included at all!", "It kills off syslog!", "The only reason it exists is to make laptops boot faster and in the server world we don't care", etc. Those are easily researched and the actual basis (or lack thereof) pretty easily found.
So, for why the systemd setup looks like it does, you can go back 4.5 years to where the announcement and rationale is described. Speed is part of it, as is device changability, as is double-forking, resource limits, and service state checking and recovery. Yes, it's a load of stuff. Definitely a system-wide approach VS a semi-random collection of various ways to do things all tacked together (which is, frankly, what most Unix and Unixlike systems are, through survival of the fittest).
Since RedHat's obviously the largest major proponent and arguably the source of the most production users, here's their documentation:
Here's the project page with loads of links about the software and uses cases:
And of course so many questions have been raised the developers have posted their rebuttals to myths or misunderstandings.
Google "250-XXXXXXXA asa cisco starttls" and you'll find this is almost certainly an ASA preventing TLS as configured on the device. Since it doesn't want TLS traffic, the config is to just mangle the packets. Well known effect, been around for years (5+). The FW admin needs to correctly deploy fixup, allow TLS or simply not inspect esmtp. Simple fix, documented in Cisco doc 118550, among many other places.
Just buy a dropcam; WiFi, 2 way audio, powered via supplied microUSB cable and wall wart, and even lets you use it as a security camera and such the rest of the time. I don't work for them, etc but I own a couple and they work.
I'm sad to say I'm agreeing with this post, and seeing my UID will also provide some frame of reference. I don't even mind story/ads as long as they're disclosed as such but this is just pathetic.
I have to agree about the lower average UIDs; this is my 'new' account when I wanted to use a nickname people would recognize me by, so I retired my 'old' account. It became a bit amusing once the UIDs got thru the roof!
Rob (And Hemos and ChrisD since they're reading) Thanks so much for all the hard work and effort.
Thanks, Guys. And why isn't there a poll up with options? My choice isn't there!
They had a simpler jitterbug without the numbers on it: Just a big green OPERATOR button. Found some snaps @ http://www.squidoo.com/SamsungJitterbug http://www.lomist.com/pics/JitterbugOneTouch.jpg It did have a screen, tho, to show the numbers that you'd called to have them enter for you, remotely!
Maybe Vyatta @ http://www.vyatta.org/ does what you want. I really don't have any idea what that is from the actual post, tho. You need some routing for thousands of users, and can't afford a Cisco UBR. I'm not sure exactly if you wanted to use the UBR for DOCSIS type support for some reason (a la cable modem) but the fact it'll be wireless leads me to believe it won't be. I'm assuming you don't need a lot of physical ports, just something to manage your VLANS, some routed subnets, a bit of BGP, etc. Maybe XORP is what you want, tho @ http://www.xorp.org/ so you may want to look there. IHeck, 'm not even sure if you want to take a server with a bunch of PCIe ports and slam multiport switchable fabric cards in there like the ones DSS @ http://www.dssnetworks.com/v3/gigabit_pcie_6468.asp makes, or do something else. Maybe these links will help, and hopefully there'll be a detailed followup so we can aim at the real target