Recently I read into the whole analogue/digital thing awhile back after encountering someone like Sue who swore up and down that analogue could never be matched by digital.
In my research I found quite a few sources that said in listening tests with expert listeners, 48khz was the sweet-spot as far as resolution goes and anything higher than that was almost always a waste of bandwidth.
A CD may have superior dynamic range over analogue recordings but they beat the pants off any standard digital recording in terms of frequency response. What analogue format are you talking about? CD has a superior frequency response to vinyl and it blows away standard audio cassettes.
None, except that you have to manually initiate the "restart" when a config change is made. I never implied that there was any particular fault in Apache. I just pointed out some things you didn't seem to know about IIS and you took it as some sort of slam on Apache, which it wasn't.
Reload keeps Apache running. No. It doesn't. On some init.d scripts I've seen for apache 'restart' simply calls '$0 reload' or vice versa. Either way httpd must be stopped and started to read the config file again.
Log onto one of your Apache servers and look at the/etc/init.d/apache script if you don't believe me.
I cannot remember a time I couldn't do/etc/init.d/apache reload (or whatever the init.d file for your apache install is called). Yes. And... /etc/init.d/apache reload ...is the equivalent of... /etc/init.d/apache stop &&/etc/init.d/apache start
Most server-related exploits are not through visible and administrated or configured services but rather through side-services like RPC in combination with ineptness of programmers and admins. That's what makes the Microsoft platform so darn insecure, there's by default hundreds of services running that nobody knows about or everybody forgets and that have open ports to the outside world. It's also 'too simple' for any CIO to set a server up so there are hundreds of servers that are clicked rather than built together. Yes. Damn Microsoft for making their server products so easy to use.
Yes, they're trying to catch up and yes, you should have a firewall, but the power in services/servers on *nux is (for most distro's) the defaults it comes with and the simplicity yet strength and visibility of the configuration and security (who doesn't like to see ALL settings in a single flatfile with the possibility of extra comments instead of through hundreds of windows with unexplained commands and options or with a single command see all rules applied to the firewall). I'm not sure what your complaint is. If you want to administer Win2k/IIS6 from the cli you can, as Win2k3 comes with all the necessary cli tools. IIS6's config file happens to be an xml file too, so you can configure IIS6 with nothing but your favorite text editor - and unlike Apache, you don't even have to restart the IIS after editing it's configuration.
True, according to the law, the old company can't say much. This is a myth. There is no law that says what your former employer is allowed to say about you outside of standard defamation laws. If you were fired because you were caught looking at donkey porn, then your employer can say that you were fired for looking at donkey porn. You can sue them for it, but if the employer can prove that they were not lying then you have no case.
Due to the litigious nature of our society, pretty much all companies have a policy of not saying anything about former employers, but this is to avoid litigation, not because of any law.
That's not true at all in my town. Regardless if weather or not service is attached to them, all phone lines here have a dial-tone and can call 911. They can even get incoming calls if you can find out the number. When moving into a new apartment several years ago, I called someone with my calling card and had them give me the number via caller ID. Until I got my phone service moved to the new apartment I was able to receive calls.
Let me rephrase it. I actually meant "any properly designed unix system. A normal user cannot use cron in unix at all." Well then there are not many properly designed UNIX systems, because almost every one I've ever seen allows any user to have a crontab. This includes HPUX, Solaris, Various GNU/Linux distros, and FreeBSD. OpenBSD is one exception, as I think users must be put in an allow list in order to use crontab by default.
Plus, in windows, you'll get administrator rights when using the "cron"-like feature in some ways. Can you please explain what you are talking about here? In what ways do users get administrative rights by using the task scheduler?
Please talk using arguments, not using your high degrees in nonsense studies. I can't help it if you are ignorant and don't realize it.
Lol, that is highly incorrect. On any properly installed unix system, normal users don't have any rights unless root have given them. No. It's not incorrect. Ever hear of cron? On just about every UNIX system I've used, every user could have their own crontab by default. Windows has the task scheduler, which regular users can use to start programs at bootup. Both cron in unix and the task scheduler in Windows can be restricted to only administrators, but by default they are available to users.
It's the other way around on windows. You have a lot to learn about both Windows and UNIX. Most of what you think you know is wrong.
It's probably something to do with fast user switching, or maybe the keyboard layout is a global setting that all users have access to. I'm not sure, but changing the keyboard layout is not something that can compromise the security of the system.
it's pretty easy to let an application start on boot even when you don't own any rights to do so. Pretty much all users have the right to do this is various ways. The same applies to Linux, *BSD and OS X too BTW.
you can do a lot like these things, no matter the permissions you got You are able to do these things because of the permissions you have.
I work at a school IT dept (higher education, not K-12) and one of my duties is several student labs. From your posts it sounds like the admins at your highschool are typical, incompetent sysadmins that K-12 school districts hire. They hire incompetent techs because they generally don't pay them very well. When you move higher up the educational (you'll need to work on your writing skills to do so.;) ) ladder the pay for IT people rises and the competency of the staff does accordingly (though I have seen plenty of incompetence in higher ed IT too). The proper way to set up student labs that run Windows is not to deploy stupid policy hack like disabling the control panel, because as I said, policies do not necessarily equate to security. In my labs, students log on a "guests", which are the same as users except their user profiles are not persistent after they log off. I tweak various file/registry ACLs so that all of the programs students need run properly as a non-admin. I don't have any policies that restrict access to the control panel. If the student wants to change their system font to lucida console, their background to pink ponies and their keyboard layout to dvorak, that's fine by me. Those changes will go away as soon as they log off.
Because IPv6 will never be implemented widely anyway.
Why will it not you say?
Because too many people are happy with the current IPv4 + NAT insanity that is in place now. Nevermind the fact that the insanely ridiculous kludge that is NAT and all of the insanely ridiculous mini-kludges (DynDNS, UDP Connection "Warming", etc.) that currently keep the internet glued together and working (sort of) like it is supposed to work probably cost as much or more time and energy that a multi-year dual-stack IPv4 to IPv6 transition would.
I'm sorry to burst your bubble, but dvassist is not working around the Windows security model.
Switching keyboard layouts requires no special access to the operating system as it is a user preference. You are being restricted from the control panel due to a policy setting, not a security setting.
Though changing this setting probably writes to the user portion of the registry, no access to the system portions of the registry are required.
Slashdot Mirror
Recently I read into the whole analogue/digital thing awhile back after encountering someone like Sue who swore up and down that analogue could never be matched by digital.
In my research I found quite a few sources that said in listening tests with expert listeners, 48khz was the sweet-spot as far as resolution goes and anything higher than that was almost always a waste of bandwidth.
Comparing a professional analogue audio format to a digital consumer format?
Nice.
You have no idea what you are talking about.
I suggest you read the portion of the US Copyright Law that pertains to fair use.
You are experiencing a bug with Microsoft Update, not WGA. It's been driving us crazy here at work for months now.
Thankfully, Microsoft finally released a hotfix for it.
root is not required to turn Linux (or Windows or OSX) into a Spam/DDoS bot, so I think Grandma can do plenty of damage without it.
The disadvantage?
None, except that you have to manually initiate the "restart" when a config change is made. I never implied that there was any particular fault in Apache. I just pointed out some things you didn't seem to know about IIS and you took it as some sort of slam on Apache, which it wasn't.
Reload keeps Apache running. No. It doesn't.
On some init.d scripts I've seen for apache 'restart' simply calls '$0 reload' or vice versa. Either way httpd must be stopped and started to read the config file again.
Log onto one of your Apache servers and look at the
Thanks for the encouragement.
Looks my my number one fan has mod points today - all of my recent posts have suddenly been modded down.
Maybe she needs to take up smoking to relieve all that pent-up anger.
That was not a troll, you fucking idiot. It was flamebait.
Stupid-ass moderators.
Due to the litigious nature of our society, pretty much all companies have a policy of not saying anything about former employers, but this is to avoid litigation, not because of any law.
It'd be pretty tough to do in Explorer, since it's not a fucking cli, but I guarantee you I could do it with in cmd.
How about you try to do the same thing in Konqueror and get back to me with your results?
I decided to quit smoking a couple of days ago, and coffee is a "trigger".
I so liked my coffee too.
Beer too.
Fuck.
That's not true at all in my town. Regardless if weather or not service is attached to them, all phone lines here have a dial-tone and can call 911. They can even get incoming calls if you can find out the number. When moving into a new apartment several years ago, I called someone with my calling card and had them give me the number via caller ID. Until I got my phone service moved to the new apartment I was able to receive calls.
I work at a school IT dept (higher education, not K-12) and one of my duties is several student labs. From your posts it sounds like the admins at your highschool are typical, incompetent sysadmins that K-12 school districts hire. They hire incompetent techs because they generally don't pay them very well. When you move higher up the educational (you'll need to work on your writing skills to do so.
NAT is *not* a security mechanism.
Th "security" of NAT is a side effect of it BREAKING the peer to peer model of the internet.
Why you say?
:)
Because IPv6 will never be implemented widely anyway.
Why will it not you say?
Because too many people are happy with the current IPv4 + NAT insanity that is in place now. Nevermind the fact that the insanely ridiculous kludge that is NAT and all of the insanely ridiculous mini-kludges (DynDNS, UDP Connection "Warming", etc.) that currently keep the internet glued together and working (sort of) like it is supposed to work probably cost as much or more time and energy that a multi-year dual-stack IPv4 to IPv6 transition would.
Ok, I'm done ranting.
Have a great weekend everyone!
No. A zero day exploit is an exploit that the general public does not know about at all.
I'm sorry to burst your bubble, but dvassist is not working around the Windows security model.
Switching keyboard layouts requires no special access to the operating system as it is a user preference. You are being restricted from the control panel due to a policy setting, not a security setting.
Though changing this setting probably writes to the user portion of the registry, no access to the system portions of the registry are required.
Try again.
I just love it when users of distros like n00buntu try to pretend that they know anything about operating systems.
Thanks for the clarification.