1fps? Something's seriously wrong with your setup. My family just got a DVB card as a prelude to me setting up a MythTV box for them. I wanted to test things out before commiting to specific hardware. You're right that HDTV does need a lot of CPU power. The windows software was able to play a 1080i test channel ok on an Athlon XP 2400+ with a Radeon video card. Under Linux it was jumpy, but that's with unoptimized binaries from a third-party repository of Debian packages. If/when I put together the MythTV box(es) I'd like to use Gentoo to create optimized binaries. Still, cooling an Athlon XP/64 while being quiet enough to sit next to the TV, might be difficult. I'm diving into the world of overclockers looking for large heatsinks, and quiet fans and power supplies.
Right. Just do a grep through the Linux kernel source for swear words. The kernel hackers are often complaining about buggy or poorly designed hardware.
*sigh. You were making a good point there, until you started talking about "on the left" and "Gods plan". I don't see how left/right politics come into this problem. And playing the "oh dear, I guess I'm not PC" card is just immature.
I'm certainly "on the left", but I agree that it's bad to force or encourage someone into a field in a simple effort to balance some demographics. It's really quite selfish and dishonest of this professor you cite, and others like her, to do things like that. I believe in equality and allowing people to do what they like. I even believe that some encouragement or even incentives are good, to a certain degree. But trying to paint IT as not being geeky is just dishonest. And telling female students that they're "making girls in CS look bad" when they fail is really just blaming the girl for this professors' actions.
Don't always try to place things on the left/right political spectrum. Like the love/hate line in Donnie Darko, things don't always fit into a simple one-dimensional line. And sometimes the two end-points aren't diamtrically opposed, or even form a (near) circle.
x86 emulation is only needed if you want to run the original EXE file. If you have the source code, then you can use libwine to compile your windows source on Unix platforms. It then doesn't matter what architecture you're on, except perhaps for endian differences.
Re:been thinking about mythtv for a while...
on
MythTV 0.17 Released
·
· Score: 1
I don't know about your first question, but the second part I know about. MythTV is setup as a frontend and backend. The backend has the tuner and storage (or you can use NFS). The frontend is the part that displays material. They can be on separate machines. You can have multiple frontends and backends. A backend can have multiple tuners. It's all very flexible. I think you can even have separate machines for the commercial detection and other CPU-hungry tasks.
So, don't go running coax or anything around your house. Put a backend box near your source, probably in the ceiling cavity for terrestrial reception or the basement for cable. Then make up some little diskless, netbooting frontends with remote controls. They're each separate machines and can watch the same program (probably not synced to each other) or watch pre-recorded material. Cat5 cable is cheaper and easier to run than coax, or 802.11g should be enough for wireless operation.
Under windows there is a list of "executable" file extensions. It includes things like exe, com, bat, cmd, dll(?), scr, pif, etc. If windows encounters one of these files and is told "open it", it will assume it's executable no matter what. It will look at the start of the file to discover what "type" it is and how to handle it. e.g binary executable to be loaded natively, a bat/cmd file to be sent off to cmd.exe, a VBS/WSH file to be sent off to the WSH interpreter, etc. So the contents of a file don't have to match the file extension. That's a trick that many worms use. They have a.pif extension or something that the user doesn't recognize. The unsuspecting user thinks "I wonder what this is?" and double-clicks on it. The file is actually an executable and it goes off to do its wormy evilness. All thanks to the naivety of the user and Windows' broad description of what an executable is.
When fanatical North Koreans fly airplanes into American buildings then I'll start to worry about them more.
Oh man, you sound like some parody of Bush. Is Bush now trying to recycle the September 11/Saddam Hussein links into an excuse to attack Iran? Sorry, we don't get Fox news here in Australia.
I agree with most of what you're saying. And you even agree that Iran is slowly changing and opening up. But then you go and tack that bit on the end about religious fanatics and flying airplanes into buildings. WTF?
And WTF does Iran have to do with Jihadists? From I've read and seen (on the news), Iran is slowly becoming more moderate. There's a younger generation that grew up after the islamic revolution (or whatever it was called). A lot of them want the country to open up to the west. President Khatami is a reformist and has often clashed with the hard-line islamists that run the government. The country is slowly changing and it would help if GWB and his posse don't make any more stupid remarks about it being in "the axis of evil". George W. would make a terrible diplomat...
On the other hand we have a country with an extremely strong cult of personality around its leader. We have a populace that is brainwashed constantly about it being under threat and the evil of the USA. Its citizens are taught that the US started the Korean war by attacking them, even though there's documents showing that the north started it by attacked the south. There's a monument where visitors go to weep over the fallen "heros" of the Korean war. Every evening the government-controlled TV shows a military parade. The country is a f**king powerkeg of anti-US, anti-west sentiment just waiting to go off.
No sir, North Korea is the country I'm worried about.
Ok, I've done my research. As found on Christopher Brownes' pages, a page about filesystems:
``I need to have files bigger than 2GB. What's the big problem?''
ext2fs in linux-2.2 supports files bigger than 2GB (up to 1TB for filesystems with sufficiently big blocks (the limit comes from the triple-indirect blocks)).
On Linux-2.0, there is no support for more than 2GB files.
On Linux-2.2, files bigger than 2GB are supported but only on 64 bit architectures (alpha, Sparc64,...). So on Intel, you're out of luck.
So no, both 32-bit and 64-bit platforms did not get large file support at the same time. It was originally developed on 64-bit platforms where it was simplest, and later a suitable mechanism was added to the 32-bit platforms that Linus was happy with. Sometime in the 2.3 development kernels I suppose. I have trouble remembering all these little historical trivia anymore.
And I never said that a system needs to address every byte. That's why I put "4G * 512 = 2T" in brackets. Didn't you notice the number 512? What I was saying was that as drive/array sizes grow, they will nolonger be (easily) addressable by 32-bit systems. Mind you, I'm sure there's lots of RAID arrays out there larger than 2T on 32-bit systems. Hell, LaCie has a portable 1T FireWire enclosure. So they obviously already have the capability and have had for some time. My bad.
My point was that it's simply easier and more efficient to pass those offsets around in single registers and do calculations in single operations. As to whether the small increase in speed/efficiency is worth the cost is another matter. But Athlon-64's are pretty cheap. And Opterons or G5's aren't much more expensive either.
No, the mini does have a single fan. From what I've read, it's temperature activated. It only comes on when needed by the CPU or GPU.
As for the use of a 64-bit CPU in a fileserver, you're only partially right. Having lots of ram in a fileserver can help with caching/buffering of data from disk. But 64 bits isn't just useful for addressing large amounts of ram. While 4G of ram is still very large for most home users, files of 2G or more are not that uncommon. DVD's and raw audio/video can easily produce multi-gigabyte files. For 32-bit cpu's to work on large files, various kludges and work-arounds have to be used. I know that Linux didn't support "large files" (>2G) on 32-bit machines until only a few years ago (2.4? 2.3?), because Linus had rejected earlier schemes as inefficient or messy. Before then, such files could only be made and accessed on 64-bit platforms. And hard disks (let alone RAID arrays[sic]) are getting so large that the sectors can't be addressed with 32-bit integers (4G * 512 = 2T). So 64-bit fileservers are needed (or at least beneficial) in some cases.
I think most of those steps can be done with the NetPBM tools. There doesn't appear to be anything like that Clearize program in NetPBM, but it should be pretty simple to whip up something yourself. I've written PPM/PNM filters before. The package comes with libraries for the formats, and it's fairly simple to use.
There is an xcftoppm script that comes with gimp-perl, but I suspect that it starts up The Gimp. Or something like that. Maybe not what you're looking for. Maybe you could skip the whole XCF issue and do all your compositing with the NetPBM tools.
I'm not sure what you're saying about the license. You lost me at this part:
I can't just distribute the graphical assets under a separate license because the program runs on an embedded system with no file system; all assets have to be linked into the executable.
What does the build system have to do with the embedded system with no file system?
I really don't how it works on Windows. Why do you need to process the XCF in your build process anyway? Why not flatten the image into a PNG file once and convert from there? Just keep the XCF around if anyone wants the "source" to edit it. The only problem then is that people have to remember to also save the PNG version after they've edited it.
For scripting I can thoroughly recommend the gimp-perl scripting extension. It's much nicer than the scheme language. On my Debian unstable/sid system it's built right into the main gimp package, so it might be standard part of the build now. Just write a perl script in you plugin directory and make it executable. It mirrors much of the script-fu interface, as well as adding an OO set of objects/classes. The documentaton is a little lacking, but I've figured out most of it from the built-in procedure browser. And there are lots of examples already in the plugin directory. Just use file to find the perl scripts amongst the native executables. It would be nicer if they left.pl on the end of the filenames. There's also a python scripting extension.
As to XCF files, I know what you mean. A few times I've wanted some CLI tools for working on XCF files, although for different reasons. The classic NetPBM tools allow me to do on the command-line most of the things I'd do in The Gimp.
Really? That's good. I only got it because my younger brother was upgrading his machine. He's a gamer. I see that the Mac Mini also has a Radeon 9200 in it, so that bodes well for running Linux or one of the BSD's on that little beauty.
I've been using the Open Source radeon driver for about a year with my Radeon 9200 Pro. There appeared to be some stability problems at first and I tried to stay away from OpenGL programs to avoid crashing. But it seems to have cleared up since about the middle of last year. I'm not a gamer, so the performance of this 2-year-old card is perfectly fine.
I was never able to get the ATI binary driver to work on my Debian system. That's one of the main reasons I don't like binary drivers: I don't use a "popular" Linux distro. So I either f**k around with Alien and their broken RPM's, or I just use the Open Source driver included in the Debian-supplied package.
Oh right, so I'm a troll for agreeing with the W3C?
...An alternative system stores the session ID in the URL.
This is not what the URL was design for. It was designed to identify the web page, not the session. An advantage is that this will work even if a user does not have cookies. A disadvantage is that proxy caches and user caches do not save the information, even though it may be exactly the same as for previous sessions. Another disadvantage is that it can mess up the bookmarking -- and bookmarking can mess it up.
(emphasis mine)
...It is normally best not to use the URL to identify the session.
...they have the name brand, they have a market of established consumer software.
I think you'll increasingly find that this is all that Microsoft really has going for Windows anymore. Apple is making a resurgence on the Desktop front. Linux and the BSD's are strong in many of the server roles. F/OSS in general is encroaching on MS's turf (e.g Mozilla/Firefox and OpenOffice). Attention is turning to small embedded devices (phones, PDA's) and media devices. MS is putting focus in these areas but hasn't been overly successful. Linux is showing up increasingly in small embedded devices. The fight isn't over yet but MS is definitely under pressure in this and other areas.
The biggest thing MS has going for it is momentum. People know Windows and Office. Once a cheaper and better product is available then it's just a matter of time before people switch over. That's why MS and their followers have been pumping out so much FUD of late. As time goes by, Linux and F/OSS in general gets better and more people learn about it. It's already "good enough" in many fields and is fast approaching MS's golden goose: the corporate desktop. Don't forget that Windows and Office are the only products out of MS that actually turn a profit for the company. Once those two pillars start crumbling, the whole company will come tumbling down. Mind you, $35B goes a long way to keeping a company afloat...:(
The main problem with the x86 'PC' market is drivers. There's an aweful lot hardware out there and they all need drivers. If you're aiming at home users, then they're going to want to plug in their latest toy and expect it to work. Trust me, as a devoted Linux user of 9 years I know how hard it is to get things working on a non-Windows OS without the support of the manufacturer. The nice thing about Apple hardware is that they control the platform and a number of the gadgets that plug into it. Go to the x86 platform and you need drivers for every single IDE/ATA controller, USB host (ok only two or three), SCSI host, sound chip, graphics chip, etc on the motherboard and PCI/ISA cards. Just look at the number of drivers in the Linux kernel source tree. And that's nowhere near complete or perfect. Apple would have to put in a tremendous amount of work to get even half of the current PC's and their gadgets working with OS/X. And/or get the vendors to do a lot of work for them.
Sorry, OS/X on x86 hardware just isn't going to happen. It would be too risky. The PowerPC (and POWER) processors are more than adequate for Apple. Let them stick with what they're good at.
...someone stupid hurt themselves with their product, because the warning label did not state something that should have been common sense.
Heh, reminds me of a Billy Connolly recording I have, where he expresses his dismay at finding a "do not use in the shower" warning label on a hairdryer in a hotel room. My god, anyone stupid enough to do something like that deserves whatever happens to them!
Look it's very simple for the Linux kernel. In the base of the kernel directory (usually at/usr/src/linux) there are three files. The CREDITS file lists almost every person who has contributed to the Linux kernel. It contains names, email addresses, a description of their contribution, and even street addresses in some cases. There's also MAINTAINERS which lists in the same format the people responsible for the various sections of the kernel. At the beginning of the file there's even a long description of how to get your patches into the kernel. Lastly, there is the REPORTING-BUGS file. It contains instructions on how to report bugs to the LKML (Linux kernel mailing list, in case you didn't know).
Is that not enough for you? Or do you really think the real solution is a single email address that will be spammed to hell and have newbies asking for help getting their nVidia graphics card working with Fedora?
Slashdot Mirror
1fps? Something's seriously wrong with your setup. My family just got a DVB card as a prelude to me setting up a MythTV box for them. I wanted to test things out before commiting to specific hardware. You're right that HDTV does need a lot of CPU power. The windows software was able to play a 1080i test channel ok on an Athlon XP 2400+ with a Radeon video card. Under Linux it was jumpy, but that's with unoptimized binaries from a third-party repository of Debian packages. If/when I put together the MythTV box(es) I'd like to use Gentoo to create optimized binaries. Still, cooling an Athlon XP/64 while being quiet enough to sit next to the TV, might be difficult. I'm diving into the world of overclockers looking for large heatsinks, and quiet fans and power supplies.
Right. Just do a grep through the Linux kernel source for swear words. The kernel hackers are often complaining about buggy or poorly designed hardware.
*sigh. You were making a good point there, until you started talking about "on the left" and "Gods plan". I don't see how left/right politics come into this problem. And playing the "oh dear, I guess I'm not PC" card is just immature.
I'm certainly "on the left", but I agree that it's bad to force or encourage someone into a field in a simple effort to balance some demographics. It's really quite selfish and dishonest of this professor you cite, and others like her, to do things like that. I believe in equality and allowing people to do what they like. I even believe that some encouragement or even incentives are good, to a certain degree. But trying to paint IT as not being geeky is just dishonest. And telling female students that they're "making girls in CS look bad" when they fail is really just blaming the girl for this professors' actions.
Don't always try to place things on the left/right political spectrum. Like the love/hate line in Donnie Darko, things don't always fit into a simple one-dimensional line. And sometimes the two end-points aren't diamtrically opposed, or even form a (near) circle.
I just love stupid trolls that can't even use Google.
Tsearch2 - full text extension for PostgreSQL
DevX: Implementing Full Text Indexing with PostgreSQL - about Tsearch2.
Tsearch2 is included in the postgresql-contrib package of at least Debian and Novell/SuSE. Is that "out of the box" enough for a clueless MySQL user?
x86 emulation is only needed if you want to run the original EXE file. If you have the source code, then you can use libwine to compile your windows source on Unix platforms. It then doesn't matter what architecture you're on, except perhaps for endian differences.
I don't know about your first question, but the second part I know about. MythTV is setup as a frontend and backend. The backend has the tuner and storage (or you can use NFS). The frontend is the part that displays material. They can be on separate machines. You can have multiple frontends and backends. A backend can have multiple tuners. It's all very flexible. I think you can even have separate machines for the commercial detection and other CPU-hungry tasks.
So, don't go running coax or anything around your house. Put a backend box near your source, probably in the ceiling cavity for terrestrial reception or the basement for cable. Then make up some little diskless, netbooting frontends with remote controls. They're each separate machines and can watch the same program (probably not synced to each other) or watch pre-recorded material. Cat5 cable is cheaper and easier to run than coax, or 802.11g should be enough for wireless operation.
How does that sound?
Under windows there is a list of "executable" file extensions. It includes things like exe, com, bat, cmd, dll(?), scr, pif, etc. If windows encounters one of these files and is told "open it", it will assume it's executable no matter what. It will look at the start of the file to discover what "type" it is and how to handle it. e.g binary executable to be loaded natively, a bat/cmd file to be sent off to cmd.exe, a VBS/WSH file to be sent off to the WSH interpreter, etc. So the contents of a file don't have to match the file extension. That's a trick that many worms use. They have a .pif extension or something that the user doesn't recognize. The unsuspecting user thinks "I wonder what this is?" and double-clicks on it. The file is actually an executable and it goes off to do its wormy evilness. All thanks to the naivety of the user and Windows' broad description of what an executable is.
Oh man, you sound like some parody of Bush. Is Bush now trying to recycle the September 11/Saddam Hussein links into an excuse to attack Iran? Sorry, we don't get Fox news here in Australia.
I agree with most of what you're saying. And you even agree that Iran is slowly changing and opening up. But then you go and tack that bit on the end about religious fanatics and flying airplanes into buildings. WTF?
And WTF does Iran have to do with Jihadists? From I've read and seen (on the news), Iran is slowly becoming more moderate. There's a younger generation that grew up after the islamic revolution (or whatever it was called). A lot of them want the country to open up to the west. President Khatami is a reformist and has often clashed with the hard-line islamists that run the government. The country is slowly changing and it would help if GWB and his posse don't make any more stupid remarks about it being in "the axis of evil". George W. would make a terrible diplomat...
On the other hand we have a country with an extremely strong cult of personality around its leader. We have a populace that is brainwashed constantly about it being under threat and the evil of the USA. Its citizens are taught that the US started the Korean war by attacking them, even though there's documents showing that the north started it by attacked the south. There's a monument where visitors go to weep over the fallen "heros" of the Korean war. Every evening the government-controlled TV shows a military parade. The country is a f**king powerkeg of anti-US, anti-west sentiment just waiting to go off.
No sir, North Korea is the country I'm worried about.
Ok, I've done my research. As found on Christopher Brownes' pages, a page about filesystems:
So no, both 32-bit and 64-bit platforms did not get large file support at the same time. It was originally developed on 64-bit platforms where it was simplest, and later a suitable mechanism was added to the 32-bit platforms that Linus was happy with. Sometime in the 2.3 development kernels I suppose. I have trouble remembering all these little historical trivia anymore.
And I never said that a system needs to address every byte. That's why I put "4G * 512 = 2T" in brackets. Didn't you notice the number 512? What I was saying was that as drive/array sizes grow, they will nolonger be (easily) addressable by 32-bit systems. Mind you, I'm sure there's lots of RAID arrays out there larger than 2T on 32-bit systems. Hell, LaCie has a portable 1T FireWire enclosure. So they obviously already have the capability and have had for some time. My bad.
My point was that it's simply easier and more efficient to pass those offsets around in single registers and do calculations in single operations. As to whether the small increase in speed/efficiency is worth the cost is another matter. But Athlon-64's are pretty cheap. And Opterons or G5's aren't much more expensive either.
Good luck getting rid of Dell at your workplace :)
No, the mini does have a single fan. From what I've read, it's temperature activated. It only comes on when needed by the CPU or GPU.
As for the use of a 64-bit CPU in a fileserver, you're only partially right. Having lots of ram in a fileserver can help with caching/buffering of data from disk. But 64 bits isn't just useful for addressing large amounts of ram. While 4G of ram is still very large for most home users, files of 2G or more are not that uncommon. DVD's and raw audio/video can easily produce multi-gigabyte files. For 32-bit cpu's to work on large files, various kludges and work-arounds have to be used. I know that Linux didn't support "large files" (>2G) on 32-bit machines until only a few years ago (2.4? 2.3?), because Linus had rejected earlier schemes as inefficient or messy. Before then, such files could only be made and accessed on 64-bit platforms. And hard disks (let alone RAID arrays[sic]) are getting so large that the sectors can't be addressed with 32-bit integers (4G * 512 = 2T). So 64-bit fileservers are needed (or at least beneficial) in some cases.
Some misguided individuals have taken offense to the daemon character.
I think most of those steps can be done with the NetPBM tools. There doesn't appear to be anything like that Clearize program in NetPBM, but it should be pretty simple to whip up something yourself. I've written PPM/PNM filters before. The package comes with libraries for the formats, and it's fairly simple to use.
The pipeline would look something like this:
There is an xcftoppm script that comes with gimp-perl, but I suspect that it starts up The Gimp. Or something like that. Maybe not what you're looking for. Maybe you could skip the whole XCF issue and do all your compositing with the NetPBM tools.
I'm not sure what you're saying about the license. You lost me at this part:
What does the build system have to do with the embedded system with no file system?
I really don't how it works on Windows. Why do you need to process the XCF in your build process anyway? Why not flatten the image into a PNG file once and convert from there? Just keep the XCF around if anyone wants the "source" to edit it. The only problem then is that people have to remember to also save the PNG version after they've edited it.
For scripting I can thoroughly recommend the gimp-perl scripting extension. It's much nicer than the scheme language. On my Debian unstable/sid system it's built right into the main gimp package, so it might be standard part of the build now. Just write a perl script in you plugin directory and make it executable. It mirrors much of the script-fu interface, as well as adding an OO set of objects/classes. The documentaton is a little lacking, but I've figured out most of it from the built-in procedure browser. And there are lots of examples already in the plugin directory. Just use file to find the perl scripts amongst the native executables. It would be nicer if they left .pl on the end of the filenames. There's also a python scripting extension.
As to XCF files, I know what you mean. A few times I've wanted some CLI tools for working on XCF files, although for different reasons. The classic NetPBM tools allow me to do on the command-line most of the things I'd do in The Gimp.
Really? That's good. I only got it because my younger brother was upgrading his machine. He's a gamer. I see that the Mac Mini also has a Radeon 9200 in it, so that bodes well for running Linux or one of the BSD's on that little beauty.
I've been using the Open Source radeon driver for about a year with my Radeon 9200 Pro. There appeared to be some stability problems at first and I tried to stay away from OpenGL programs to avoid crashing. But it seems to have cleared up since about the middle of last year. I'm not a gamer, so the performance of this 2-year-old card is perfectly fine.
I was never able to get the ATI binary driver to work on my Debian system. That's one of the main reasons I don't like binary drivers: I don't use a "popular" Linux distro. So I either f**k around with Alien and their broken RPM's, or I just use the Open Source driver included in the Debian-supplied package.
Oh right, so I'm a troll for agreeing with the W3C?
(emphasis mine)
hey mate, what's with the [tt]: bit in your titles? Is that some bit of markup from another forum or something? Just wondering.
That's a good thing. Session Id's don't belong in URLs and this excercise should have shown you a good reason why.
I think you'll increasingly find that this is all that Microsoft really has going for Windows anymore. Apple is making a resurgence on the Desktop front. Linux and the BSD's are strong in many of the server roles. F/OSS in general is encroaching on MS's turf (e.g Mozilla/Firefox and OpenOffice). Attention is turning to small embedded devices (phones, PDA's) and media devices. MS is putting focus in these areas but hasn't been overly successful. Linux is showing up increasingly in small embedded devices. The fight isn't over yet but MS is definitely under pressure in this and other areas.
The biggest thing MS has going for it is momentum. People know Windows and Office. Once a cheaper and better product is available then it's just a matter of time before people switch over. That's why MS and their followers have been pumping out so much FUD of late. As time goes by, Linux and F/OSS in general gets better and more people learn about it. It's already "good enough" in many fields and is fast approaching MS's golden goose: the corporate desktop. Don't forget that Windows and Office are the only products out of MS that actually turn a profit for the company. Once those two pillars start crumbling, the whole company will come tumbling down. Mind you, $35B goes a long way to keeping a company afloat... :(
The main problem with the x86 'PC' market is drivers. There's an aweful lot hardware out there and they all need drivers. If you're aiming at home users, then they're going to want to plug in their latest toy and expect it to work. Trust me, as a devoted Linux user of 9 years I know how hard it is to get things working on a non-Windows OS without the support of the manufacturer. The nice thing about Apple hardware is that they control the platform and a number of the gadgets that plug into it. Go to the x86 platform and you need drivers for every single IDE/ATA controller, USB host (ok only two or three), SCSI host, sound chip, graphics chip, etc on the motherboard and PCI/ISA cards. Just look at the number of drivers in the Linux kernel source tree. And that's nowhere near complete or perfect. Apple would have to put in a tremendous amount of work to get even half of the current PC's and their gadgets working with OS/X. And/or get the vendors to do a lot of work for them.
Sorry, OS/X on x86 hardware just isn't going to happen. It would be too risky. The PowerPC (and POWER) processors are more than adequate for Apple. Let them stick with what they're good at.
Heh, reminds me of a Billy Connolly recording I have, where he expresses his dismay at finding a "do not use in the shower" warning label on a hairdryer in a hotel room. My god, anyone stupid enough to do something like that deserves whatever happens to them!
Each with a licensed copy of Win XP Media Centre Edition. I think you're onto Billy's plan right there!
Look it's very simple for the Linux kernel. In the base of the kernel directory (usually at /usr/src/linux) there are three files. The CREDITS file lists almost every person who has contributed to the Linux kernel. It contains names, email addresses, a description of their contribution, and even street addresses in some cases. There's also MAINTAINERS which lists in the same format the people responsible for the various sections of the kernel. At the beginning of the file there's even a long description of how to get your patches into the kernel. Lastly, there is the REPORTING-BUGS file. It contains instructions on how to report bugs to the LKML (Linux kernel mailing list, in case you didn't know).
Is that not enough for you? Or do you really think the real solution is a single email address that will be spammed to hell and have newbies asking for help getting their nVidia graphics card working with Fedora?