maybe they'll drop underage defendants as well. i'm a named defendant, i have no clue why they continue to list me although i'm STILL 17 and a MINNESOTA resident. geez.
interestingly, as kids, trying to see if a cable signal originating from one node could reach another node, we hooked up a shortwave transmitter to a cable line, turned it to the lowest possible wattage. at another house, we had a dinky radioshack portable fm/am/sw receiver hooked up to the cable as well, we were surprised to find that the reception was crystal clear.
we had a couple old bnc network cards (and connectors) that we had planned to try across the cable network... but we never got around to it... probably out of fear of frying several hundred televisions with the signal interference...
Yes, for apps that support it, mini-icon support is automatic. Since a couple beta-release cycles ago, almost every single GNOME app has a mini-icon associated with it. Even Netscape's mini-icons work.
Sawfish (was sawmill), the new default WM for GNOME, has preliminary mini-icon support.
This was originally an April Fool's Day joke, (many of you really wanted to believe, didn't you?). But to our suprise, there actually is a Palm theming site/utility, however it is neither open source or free (shareware, expires in 15 days). Originally, garrett and I had no idea, so this is quite eerie.
no, that was the preliminary name, but we insisted to the author that it be palm.themes.org instead of pilot because of the fore-mentioned copyright issues.
egg.microsoft.com used to report that it was running Apache/Linux (by Netcraft). It was used to host "internal projects and specifications". All the information on it was unprotected, but it was next to worthless things. Now on port 80, it just redirects you to www.microsoft.com and returns an Unknown/Unknown reply.
GNOME seems like it is playing catchup because the teams did not work in the same track. KDE quickly finished their panel to look like CDE, finished. GNOME refined and tweaked it so (by now) it 1) looks beautiful 2) acts like a next-generation Dock.
With the extra time, KDE developers developed their KOffice suite. GNOME's core developers (actually, mostly Miguel) developed Gnumeric (very Excel-like) as a sample application for others to mimic and integrate other Office apps.
Gnumeric is very Excel-like for a good reason: like-it-or-not, businesses nowadays rely on Excel/Word/Powerpoint. If you provide a good and similar alternative on Linux/*BSD, it is more likely that they will switch.
This sample app -> mimic approach didn't work quite how it was expected. Gnumeric is hailed, but there are no other major apps (word processor, presentation creator, personal information manager) that mimic its level of functionality and integration with GNOME. (AbiWord for GNOME is pretty GNOME-like, but it doesn't integrate like Gnumeric does.) This is why Miguel and Nat created Helix Code. While they will still pretty much control the core libraries and such, they will focus on developing these other applications. They are currently working on Evolution (couldn't find an URL at the moment), an extensive personal information manager which will combine the functions of Balsa, GnomeCard, GnomePilot and others into one Outlook-like functional product. Their main goal is to develop desktop apps for GNOME.
To finally answer your question, I'm not even sure that GNOME is ready for the business environment yet, but don't dismiss it as a "wannabe" or "johnny-come-lately". GNOME's core architecture seems to have many advantages over KDE, so we'll see what comes down the pipe.
> The only thing is why replace Imlib with gdk-pixbuf? I thought that Imlib did its job well. Does anyone know why they decided to do this?
(forgive me if this is a repeat, something bad happened and I'm not sure if it was posted)
imlib was not designed for the purposes which gnome delegated it for, it provided suboptimal performance and had some memory leak problems... (which are now fixed, but nevertheless, injured the reputation of GNOME). gdk-pixbuf is being designed by GNOME people for taks which are important to running gnome (quick and light loading/displaying of small pixmaps with antialiasing and alpha transparency).
> The next step after that will probably be alternative interfaces to mozilla, such as a GTK interface
In fact, when you compile mozilla, it builds a GtkMozilla widget, so that you can link to this library and use the mozilla rendering engine as a widget, very cool. (somewhat like how Internet Explorer can be used as an ActiveX control in Windows (case in point: Winamp's minibrowser))
Reasons: Using seasons instead of months increases the grace period for releases and thus relieves any user-inflicted pressure upon the development team to shoot for a specific month. (you get a 3 month period to shoot for instead of 1). Using seasons instead of Q1 2000, Q2 2000, etc. makes you/the project look like less of a suit-ish person/project. People can perceive things off of the tiniest off hand remark or quirk like using business-like quarters instead of seasons or something. Plus, remember October GNOME? Yes, they did use a month to denote a release date in that case.
*insert Daniel's comments here as to why GNOME seems slow* In addition to this is the fact that Enlightenment is currently the default Window Manager for GNOME. This will change to sawmill soon because it is so fast and it integrates so well with GNOME (it stays out of the way when it should). (Sawmill author is even going to GUADEC -- GNOME Conference in Paris)
You may run WindowMaker with GNOME, it works almost perfectly, except WindowMaker doesn't have session management (or at least doesn't work with GNOME'S), therefore it gets screwy. If you plan to try GNOME again, try sawmill with it.
I completely agree, the desktop issue isn't an either-or dillema. GNOME and KDE (especially with a window manager that supports both -> Enlightenment) work well together. GNOME has a much nicer panel (and applets) than KDE, but KDE has more well-developed applications. So, use both. It can be a very simple, very inclusive desktop.
Well, I fought off the pangs of paranoia and doubt and su'ed and ran this thing. Scanning running processes... Scanning/tmp... Scanning/... OOPS.. load JUMPS, mem AND swap usage jumps from 15% and 0% to 100% and 100%. X halts: mouse doesn't move, xmms pauses. I try to telnet in from another machine for about 6 minutes, NOTHING. I finally go back, and it's killed X along with rc5des and itself.
Sounds like a denial of service attack itself. geez. Now I feel dirty, excuse me while I go buy a new harddrive. eww.
I was watching ZDTV just a few seconds ago and realized something: even the technically "savvy" news people seem to be confused. They said "denial of service attacks have been around for years, but the tools to do distributed denial of service attacks have only come around in the last 6 months or so." This just nags at me. I seem to remember this (first?) distributed denial of service attack: smurf.
This probably is a little different from what people are theorizing, but it works essentially the same way (or even better). Basically the perpetrator sends out a few spoofed ICMP packets with the victim's IP as the source address. These packets have subnets as their destination, so theoretically thousands of machines reply to these false ICMP packets towards an unwitting victim while the perpetrator only sent maybe a few packets.
Must... put... more... servers... that's kinda what's nice about icecast/shoutcast, you can have one streaming location that streams to several servers that can handle a lot of bandwidth.
Well, frankly I hadn't known about it. In fact, I had a class upstairs not 15 minutes before this started. Gr.
maybe they'll drop underage defendants as well. i'm a named defendant, i have no clue why they continue to list me although i'm STILL 17 and a MINNESOTA resident. geez.
interestingly, as kids, trying to see if a cable signal originating from one node could reach another node, we hooked up a shortwave transmitter to a cable line, turned it to the lowest possible wattage. at another house, we had a dinky radioshack portable fm/am/sw receiver hooked up to the cable as well, we were surprised to find that the reception was crystal clear.
we had a couple old bnc network cards (and connectors) that we had planned to try across the cable network... but we never got around to it... probably out of fear of frying several hundred televisions with the signal interference...
Sawfish (was sawmill), the new default WM for GNOME, has preliminary mini-icon support.
i apologize, i must have overlooked it. that was pretty stupid of me.
this is a x86-only binary solution, since LinuxPPC isn't for x86, you can't run mtv or mtvp on LinuxPPC
i just tried it and it works just fine.
cheers!
no, that was the preliminary name, but we insisted to the author that it be palm.themes.org instead of pilot because of the fore-mentioned copyright issues.
anyone make a mpeg video capture of this one -- since many pbs stations did not/will not air this?
What will be the featureset (and projected date) of the next Slackware release? XFree86 4.0.x, Linux 2.4.x?
egg.microsoft.com used to report that it was running Apache/Linux (by Netcraft). It was used to host "internal projects and specifications". All the information on it was unprotected, but it was next to worthless things. Now on port 80, it just redirects you to www.microsoft.com and returns an Unknown/Unknown reply.
With the extra time, KDE developers developed their KOffice suite. GNOME's core developers (actually, mostly Miguel) developed Gnumeric (very Excel-like) as a sample application for others to mimic and integrate other Office apps.
Gnumeric is very Excel-like for a good reason: like-it-or-not, businesses nowadays rely on Excel/Word/Powerpoint. If you provide a good and similar alternative on Linux/*BSD, it is more likely that they will switch.
This sample app -> mimic approach didn't work quite how it was expected. Gnumeric is hailed, but there are no other major apps (word processor, presentation creator, personal information manager) that mimic its level of functionality and integration with GNOME. (AbiWord for GNOME is pretty GNOME-like, but it doesn't integrate like Gnumeric does.) This is why Miguel and Nat created Helix Code. While they will still pretty much control the core libraries and such, they will focus on developing these other applications. They are currently working on Evolution (couldn't find an URL at the moment), an extensive personal information manager which will combine the functions of Balsa, GnomeCard, GnomePilot and others into one Outlook-like functional product. Their main goal is to develop desktop apps for GNOME.
To finally answer your question, I'm not even sure that GNOME is ready for the business environment yet, but don't dismiss it as a "wannabe" or "johnny-come-lately". GNOME's core architecture seems to have many advantages over KDE, so we'll see what comes down the pipe.
(forgive me if this is a repeat, something bad happened and I'm not sure if it was posted)
imlib was not designed for the purposes which gnome delegated it for, it provided suboptimal performance and had some memory leak problems... (which are now fixed, but nevertheless, injured the reputation of GNOME). gdk-pixbuf is being designed by GNOME people for taks which are important to running gnome (quick and light loading/displaying of small pixmaps with antialiasing and alpha transparency).
In fact, when you compile mozilla, it builds a GtkMozilla widget, so that you can link to this library and use the mozilla rendering engine as a widget, very cool. (somewhat like how Internet Explorer can be used as an ActiveX control in Windows (case in point: Winamp's minibrowser))
Reasons: Using seasons instead of months increases the grace period for releases and thus relieves any user-inflicted pressure upon the development team to shoot for a specific month. (you get a 3 month period to shoot for instead of 1). Using seasons instead of Q1 2000, Q2 2000, etc. makes you/the project look like less of a suit-ish person/project. People can perceive things off of the tiniest off hand remark or quirk like using business-like quarters instead of seasons or something. Plus, remember October GNOME? Yes, they did use a month to denote a release date in that case.
*insert Daniel's comments here as to why GNOME seems slow* In addition to this is the fact that Enlightenment is currently the default Window Manager for GNOME. This will change to sawmill soon because it is so fast and it integrates so well with GNOME (it stays out of the way when it should). (Sawmill author is even going to GUADEC -- GNOME Conference in Paris)
You may run WindowMaker with GNOME, it works almost perfectly, except WindowMaker doesn't have session management (or at least doesn't work with GNOME'S), therefore it gets screwy. If you plan to try GNOME again, try sawmill with it.
I completely agree, the desktop issue isn't an either-or dillema. GNOME and KDE (especially with a window manager that supports both -> Enlightenment) work well together. GNOME has a much nicer panel (and applets) than KDE, but KDE has more well-developed applications. So, use both. It can be a very simple, very inclusive desktop.
This is Nautilus -- the eazel-written GNOME 2.0 Filemanager/Desktop.
these GTK+ Pixmap theme / flickering / sluggishness issues are likely to be fixed with gdk-pixbuf and gtk 1.3 (which is only in CVS at the moment).
These are not GNOME issues per se, but because of what it relies on.
About gmc, I think most everyone agrees with you, Nautilus is GNOME's messiah.
Well, I fought off the pangs of paranoia and doubt and su'ed and ran this thing. Scanning running processes... Scanning /tmp... Scanning /... OOPS.. load JUMPS, mem AND swap usage jumps from 15% and 0% to 100% and 100%. X halts: mouse doesn't move, xmms pauses. I try to telnet in from another machine for about 6 minutes, NOTHING. I finally go back, and it's killed X along with rc5des and itself.
Sounds like a denial of service attack itself. geez. Now I feel dirty, excuse me while I go buy a new harddrive. eww.
I was watching ZDTV just a few seconds ago and realized something: even the technically "savvy" news people seem to be confused. They said "denial of service attacks have been around for years, but the tools to do distributed denial of service attacks have only come around in the last 6 months or so." This just nags at me. I seem to remember this (first?) distributed denial of service attack: smurf.
This probably is a little different from what people are theorizing, but it works essentially the same way (or even better). Basically the perpetrator sends out a few spoofed ICMP packets with the victim's IP as the source address. These packets have subnets as their destination, so theoretically thousands of machines reply to these false ICMP packets towards an unwitting victim while the perpetrator only sent maybe a few packets.
Who's playing the accordian?!?!?
Must... put... more... servers... that's kinda what's nice about icecast/shoutcast, you can have one streaming location that streams to several servers that can handle a lot of bandwidth.