All but the cpufreq applet part is possible with Gnome Shell Extensions and I am pretty sure there is actually an extension out there for cpufreq that I just haven't found useful yet.
That said, one of the issues with prompting the shift to Gnome 3 was that the code base for Gnome 2 was unwieldy. Hopefully, they will be able to maintain it.
It was that GTK+ 2.x code was becoming unwieldly and so GTK+ 3.x started a big cleanup. That principle may have also applied to some other individual packages. But the desktop as a whole wasn't really in that position.
The Undo/Redo file manager functionality was backported from GNOME 3. Good for them for merging new features from GNOME 3, but it's not like they developed the feature.
VMWare by default bridges your network interface into the VM. Wireless drivers have such poor support for network bridging that this almost never works. It especially doesn't work with WPA or any such.
If you NAT your VM network traffic, then things work (well sorta, with all the nastiness that NAT comes with).
... The best solution, IMHO, is to stop using threads. Instead, fork a separate process for each document and one more for the UI, and use IPC for them to communicate. This way, when a web page or plugin inevitably causes the browser to crash or even just grow too big, killing that one window or tab won't bring down the whole browser, and the memory it used will be returned to the OS. This will have the side-effect of making the browser much more responsive, because you're not kept from switching tabs while a DNS lookup hangs the browser for one document. Naturally, they didn't like my solution.
Do you have any idea what that would entail? Such an architecture change would basically mean rewriting the browser. As a seasoned programmer I shudder at the thought of having to implement such a fundamental change in a codebase like Mozilla. I'm not suprised they "didn't like it".
> France and Texas are the same size, and shape, but Texas along the I-80 is filled with > 10 hours of nothing but desert and homocidal cops (a long story for another time).
Texas has no I-80. The I-80 runs from Chicago to San Francisco.
* Off-topic, but can someone explain to me why (at least with ISC dhcpd) I can't assign IPs on two different subnets on the same physical LAN? Can this be done with a different DHCP server? Is there any kind of limitation to the protocol that makes this impossible, or is it just an implementation problem?
Are you serious? This sort of question takes the credence out of the rest of your post. It's because DHCP uses physical link broadcast (ie: 255.255.255.255 and also strange addresses like 0.0.0.0) to do it's work.
Of course there's ways to do what you want to do, but it's not simple on any level. You can use use VLAN aware equipment and OS and have isc-dhcp listen on the two vlan NICs. Or you can record all the MAC addresses for the "other" subnet in dhcpd.conf.
Recently we switched a large set of servers to another netblock (yeah, I know sucks). We discovered after that the previous netblock owner had gotten themselves on a bunch of black-lists. Maybe that has something to do with it.
Slashdot Mirror
All but the cpufreq applet part is possible with Gnome Shell Extensions and I am pretty sure there is actually an extension out there for cpufreq that I just haven't found useful yet.
Here you go: https://extensions.gnome.org/extension/47/cpu-frequency/
Eh? File manager Undo/Redo is a feature in GNOME 3.4 that they've back ported.
That said, one of the issues with prompting the shift to Gnome 3 was that the code base for Gnome 2 was unwieldy. Hopefully, they will be able to maintain it.
It was that GTK+ 2.x code was becoming unwieldly and so GTK+ 3.x started a big cleanup. That principle may have also applied to some other individual packages. But the desktop as a whole wasn't really in that position.
The Undo/Redo file manager functionality was backported from GNOME 3. Good for them for merging new features from GNOME 3, but it's not like they developed the feature.
Yes, the Eschede ICE accident happened on normal tracks.
VMWare by default bridges your network interface into the VM. Wireless drivers have such poor support for network bridging that this almost never works. It especially doesn't work with WPA or any such.
If you NAT your VM network traffic, then things work (well sorta, with all the nastiness that NAT comes with).
Do you have any idea what that would entail? Such an architecture change would basically mean rewriting the browser. As a seasoned programmer I shudder at the thought of having to implement such a fundamental change in a codebase like Mozilla. I'm not suprised they "didn't like it".
> France and Texas are the same size, and shape, but Texas along the I-80 is filled with
> 10 hours of nothing but desert and homocidal cops (a long story for another time).
Texas has no I-80. The I-80 runs from Chicago to San Francisco.
That's what the semicolon at the end of an SQL statement (on any real database server) is there for.
Are you serious? This sort of question takes the credence out of the rest of your post. It's because DHCP uses physical link broadcast (ie: 255.255.255.255 and also strange addresses like 0.0.0.0) to do it's work.
Of course there's ways to do what you want to do, but it's not simple on any level. You can use use VLAN aware equipment and OS and have isc-dhcp listen on the two vlan NICs. Or you can record all the MAC addresses for the "other" subnet in dhcpd.conf.
I was amazed to see this on the front page. But I'm shocked to see a slashdot editor using slashdot.org as a soap box for his personal beliefs.
I don't care what what Hemos thinks about ID, anymore than I care what he thinks about abortion or the afterlife.
If this is where slashdot is going I'll go somewhere else for my technical news from now on.
This is fixed in GNOME 2.12 with the exception of starting apps from the terminal (where the problem becomes real complex).
ClamSMTP is what I use. Nice, light and efficient. It does transparent proxying if you need that too.
http://memberwebs.com/nielsen/software/clamsmtp/
Only the development version (2.5.x) of wxWidgets works with GTK2. The stable version (2.4.x) uses the old GTK.
KDE apps typically have so many settings that they need a whole top-level menu for them. Most other apps only need one menu item.
That already exists. Run gconf-editor and you'll have all the options exposed to you in a nice editable format.
Use regedt32.exe (which is an older incarnation of regedit), go to the key in question, choose Security | Permissions ... from the menu etc...
Seems like everyone's written one of these. Here's one a friend of mine wrote.
http://memberwebs.com/nielsen/windows/scrounge/
... as do many people. For 50 bucks a month too. Of course Japan is much smaller physically, but there's got to be some way to do it.
With no cost to the sending computer, it can spawn tens thousands of concurrent email sessions, which all wait a painless 10 seconds.
Hashcash (although it has it's drawbacks) forces the sending machine to actually do something. That's the difference.
last -x | grep "shutdown\|reboot"
:)
Don't forget the quotes
From the article:
for(i=0 to 100)
array[i]=0
Maybe I missed something but since when is that C?
EditPlus. A great little text editor with almost everything you'd need.
Recently we switched a large set of servers to another netblock (yeah, I know sucks). We discovered after that the previous netblock owner had gotten themselves on a bunch of black-lists. Maybe that has something to do with it.