By default, reiserfs stores small files and `file tails' directly into the tree. This confuses some utilities like LILO. The notail option is
used to disable packing of files into the tree.
Unfortunately old technologies never seem to die;) Most BIOS still support the 2.8 MB floppy disks. Hell, most BIOSes still support DOS! And remember ISA? Yeah its still around.
Now that the Athlon 4 is here, the big question everyone is asking is "will it work with current
Socket-A motherboards?" AMD actually told us that as long as motherboard manufacturers
adhere to the guidelines they set forth, a motherboard purchased today would work with not only
the Athlon 4 but also the Thoroughbred and Barton cores. This means that the Thoroughbred
and Barton cores will both be on Socket-A Athlons as well.
Don't get too excited though. Unfortunately not all motherboard manufacturers to adhere to
AMD's guidelines properly. Voltage and BIOS support is necessary for your motherboard to work
with the Athlon 4 as well as the upcoming Thoroughbred and Barton cores. And even if your
current motherboard does work with the future cores, you may not want to even use it since
newer motherboards will have more features, newer chipsets, greater performance etc? But it is
nice to know that AMD is sticking with Socket-A for the Athlon family.
Will the processor use ACPI support to use the power-stepping features? ACPI doesn't work in Linux yet.
Please! Make sure you get the printer-friendly version of the Microsoft document.
Otherwise you'll overflow your printer's buffer, too.
(It turns out the latest development code of Retina was able to find a buffer overflow within the.printer ISAPI filter (C:\WINNT\System32\msw3prt.dll) which provides Windows 2000 with support for the Internet Printing Protocol (IPP) which allows for the Web based control of various aspects of networked printers.)
Okay: here's the deal. We can keep free software free while simultaneously keeping [your favorite support-based free software company] in business and making money for ourselves!
Impossible you say?
No! We just have to monopolize the support area.
Here's the idea: each of us (the 31337 unix admin/coders/users) enters in a "business partnership" with our favorite support-based company (SBC), i.e. Eazel, RedHat, etc. We agree to forbid ourselves from answering tech support questions online, i.e. in #linux on IRC, usenet, etc.. Instead, we redirect the luser who has a question to our personal address at our SBC where the luser can find out his answer--for a small fee (micropayment). Then, the resulting pool of money is collected and divided between us and our SBCs. It's a win win! Help the economy! Help yourself! Don't compromise your software's freedom!
IRC Example:
#linux
Bob: Hi I'm bob I new to linux help me set up my isa winmodem
[silence ensues due to all on the channel being bound by agreements]
Cardhore: Okay Bob I'll help you.
Bob: Okay thanks. My modem is not working in the redhat...how do i make driver for it?
Cardhore: Well, I happen to have the answer right here: www.redhat.com/support/query.cgi-bin?ref=cardhore? q=winmodem
[bob goes to the url]
Bob: YOU ASS HOLE I'M NOT PAYING $40 TO LEARN HOW TO DO THAT.
Bob leaves.
[twenty minutes pass]
Bob has entered #linux.
Bob: Cardhore...so are you still up for that offer?
Success!! Bob successfuly gets his modem working, Cardhore makes $$$, and RedHat pleases its shareholders!
Can a company make money off support for a product that is open source--a product that continues to evolve until it is "perfect" (and (potentially) not needing support)? And how? [These are an open ended question, not a troll.]
...there's the newly started GNOME Packaging Project here.
The project intends to provide binaries for most platforms so that you don't have to compile them yourself. Its binaries will also be un-branded--there will be no Eazel or Ximian logos, features, etc.
Also, just because someone can compile GNOME himself, it doesn't mean that he wants to. In fact, on moderate hardware it will take about two days to compile this. Experienced power users don't necessarily have time to waste on this.
From the article:..where information wants to be free so long as it's other people's information.
Do people who believe this agree with it when their personal information is free?
I've tried ReiserFS since Linux 2.4.1 . . . big mistake. 2.4.1 corrupted the filesystem. 2.4.2 corrupted every one of my Resier filesystems beyond recovery. Then I switched to Mandrake 8.0 (which caused an extremely large amount of corruption). It corrupted my EXT2 filesystems as well (which were fixable) due to IDE problems. 2.4.3 finally fixed these problems, but it had a new set of problems with threaded processes that got hung in the 'D' state. (A process in the 'D' state can not be killed; it is necessary to reboot the machine. Processes like Mozilla were especially suseptible.) Also, if there were a problem with the filesystem, it was near impossible to fix with the ReiserFS tools.
Finnaly, 2.4.4 was released, and it is fixed: it's the first "stable" kernel in the new series.
I never read a single bad review of ReiserFS until I actually used it--it worked "flawlessly" for everyone who had tried it. I didn't find out that it had these problems, and that it doesn't work over NFS, until it was too late.
The thing I learned is that when things--especially filesystems--claim stability, the user still has to test things out for himself.
ReiserFS is a good filesystem; don't get me wrong, but it may not be the best for you. (In fact, Red Hat does not plan to use ReiserFS in its distribution, because in the event of filesystem failure, it is near impossible to recover the filesystem with standard tools.)
I have used XFS in the past on Irix machines and have been very happy with it. But be careful before you deploy this filesystem--even on your home machine--without thoroughly testing it. And not simply creating two files and saying, "Hey! They're still there! I guess it's stable." I fell into that trap.
I would highly reccomend anyone running the 2.4 kernel to upgrade to at least 2.4.4, especially if he uses IDE or ReiserFS.
If you're going to use XFS, test it first.
By the way, does anyone know what's going on with moderation? I've had mod points three times this week, and there are a huge amount of +5 comments.
Now I can finally have TrueType fonts in X Windows*!! I've been waiting for this since XFree 3.3!! I'm so happy! However, I don't think Linus Torvalds will be too happy to include a font server in his kernel...
*Yes, I know it's called the "X Window System." Yes, I'm joking.
What if someone were to change all of the tabs in some musical way? In other words, do enough to the song so that if played, it wouldn't sound much like the original.
Like XOR them! Or change their filenames from Hanson.tab to hhhhhhhhhhHanson.tab!
change the tempo
Good idea: We could change the ASCII indicated tempo from, say, 130 BPM to 130 + 10^-17, resulting in a completely different song! HA ha! That'll teach 'em.
Check out Snarfoo's thourough review of this application here.
From his review:
April 23th, 2001 12:00am GMT
"Free Expression is a Basic Human Right"
(32 Expressions Per Lifetime, Per Human, Only!)
Website: http://freeweb.dynodns.net
FreeWeb is silly. I can't think of any other way to start out this review. This closed-source Microsoft-only OS application uses Freenet and freenetmirror, both Open Source software.
After the mention on Slashdot on Sunday, I decided to review FreeWeb. While most of the criticism in the comments there was harsh, there were a few people who praised FreeWeb for 'finally making an easy to use front-end to Freenet'. Of course these people hadn't actually tried FreeWeb. Fproxy makes accessing websites in Freenet easy, not FreeWeb.
From the FreeWeb documentation:
Simply put, FreeWeb is an 'alternative world-wide web'.
A web without censorship or surveillance.
A web which allows you to publish and view any type of information with complete privacy and anonymity.
A web which honours your rights to individual choice as to the information you choose to view and/or publish.
Actually none of these are features of FreeWeb, but are of course features of the technology it relies on, namely Freenet and freenetmirror.
What it is.
FreeWeb is simply a proxy that looks for domain names ending in.free and then does a lookup on the author's computer and sends back the corresponding MSK@SSK@ key. That's right. The DNS system is sitting on some guys computer and updated approximately every 48 hours.
The DNS records are submitted using Freenet's new in-Freenet index method. Once somebody uses a hex editor to see what name he's using... well, you can imagine how well this is going to work.
While the.free pseudo-name sounds nice, you would have to tell everyone who doesn't know about Freenet that in order to access their website they would have to install Freenet. People trying www.whatever.free in Internet Explorer will get a 'domain name not found' or some such error and think the site has vanished from the World Wide Web and will have no idea that they need additional software to access it. Adding a 'freenet://' might be a better approach because the browser would inform them the protocol isn't supported.
FreeWeb is also a GUI for Mr. Bad's freenetmirror, which lets you publish websites in Freenet with ease. After using freenetmirror to insert your site, it inserts an in-Freenet index record and the author then updates the DNS server on his computer with your domain name.
FreeWeb states that 'once a site is published on FreeWeb, it can't be taken down by anyone except the site's author'. This is of course false because you can't delete information from Freenet. They might not be able to access it via the.free pseudo-domain name, but the MSK@SSK@ site will still be there.
If you do try FreeWeb be warned that there are a couple of problems on Windows 98. It will not automatically start when Windows 98 does and when you manually start it you will get this message:
Site sync: warming up thread
Ignore it, because you never will know when it is done warming that thread.
I think the author was a little too quick to get this out the door. He states "The purpose of alpha testing is to weed out such embarrassing stuff-ups."
Well, no, alpha testing should have been done by the developer(s). He has only tested it on Windows 2000.
FreeWeb is a hefty 7meg download. It requires a working Freenet, and thus the Java Runtime Environment, so I'm not sure why the JRE is included with FreeWeb.
In Conclusion:
You get a nice wrapper for Mr. Bad's excellent freenetmirror program. You get a psuedo-domain name ending in.free, which relies on one person's computer somewhere.
If FreeWeb were published by a reputable company, an executable-only file might be acceptable. Because the program involves encryption, anonimity, security and an unkown person's server to work, I can't recommend it without source.
There are just too many vulnerabilities in this system. Keeping the source code stashed away isn't going to stop anyone from breaking the system.
The author mentions that the code is 'too messy' to be released now and that he may release parts of it increments.
Presence & Messaging is what instant messaging is all about. All those are available in old protocols.
Everyone who is on the internet has its own IP address. If you don't like numbers, there's DNS. That way your machine can have its own name. Want to know if your "buddies" are online? Ping their machines. Are they at their machines? Send them a "talk" request.
Let's see...that covers presence and messaging. What about file sharing? There's FTP and Telnet.
Problems with this? Definiately. Practically no one has its own IP address, so it doesn't have its own domain name as well. No one runs talkd on its machine. Talkd is unix only. Currently there are not enough IP addresses for everyone.
Advantages? You don't have to use anyone's central server.
Is instant messaging a better solution? Every instant messaging system tries too hard to hide its users' IP addresses: this makes it very annoying for me to try and use useful protocols--FTP, games, etc--with whom I'm trying to communicate because I have to do all this work to get their addresses. Messages are not encrypted.
On the other hand, Jabber will probably be extremely successful. Why? One word: XML. I have never had a bad experience with any software that uses XML ever, and I don't plan to.
Slashdot Mirror
For more information on reiserfs mount options, see http://www.reiserfs.com/mount-options.html
Exactly.
I don't think so, because you wouldn't say "they runs" or "they is going".
"The handles are angled outwards, eliminating the need for the user to bend their [sic] hands inward"
Thanks for the constructive criticism, asshole. :)
No doubt. Family Guy was the funniest show.
Unfortunately old technologies never seem to die ;) Most BIOS still support the 2.8 MB floppy disks. Hell, most BIOSes still support DOS! And remember ISA? Yeah its still around.
Will the processor use ACPI support to use the power-stepping features? ACPI doesn't work in Linux yet.
How do you speak question marks?
I'm predicting that 0.9.1.1 will be the super fast "Porsche" version of Mozilla.
Hey'! It's 9 megabytes too!
The device's theme song will be "E-mail my Heart" by Britney Spears. God that's an awful title for a song.
Don't they, however, usually say "the United States is planning to . . ."?
Man's genetic code has been modifying since the beginning of man.
Otherwise you'll overflow your printer's buffer, too.
(It turns out the latest development code of Retina was able to find a buffer overflow within the .printer ISAPI filter (C:\WINNT\System32\msw3prt.dll) which provides Windows 2000 with support for the Internet Printing Protocol (IPP) which allows for the Web based control of various aspects of networked printers.)
Impossible you say?
No! We just have to monopolize the support area.
Here's the idea: each of us (the 31337 unix admin/coders/users) enters in a "business partnership" with our favorite support-based company (SBC), i.e. Eazel, RedHat, etc. We agree to forbid ourselves from answering tech support questions online, i.e. in #linux on IRC, usenet, etc.. Instead, we redirect the luser who has a question to our personal address at our SBC where the luser can find out his answer--for a small fee (micropayment). Then, the resulting pool of money is collected and divided between us and our SBCs. It's a win win! Help the economy! Help yourself! Don't compromise your software's freedom!
IRC Example:
#linux
Bob: Hi I'm bob I new to linux help me set up my isa winmodem
[silence ensues due to all on the channel being bound by agreements]
Cardhore: Okay Bob I'll help you.
Bob: Okay thanks. My modem is not working in the redhat...how do i make driver for it?
Cardhore: Well, I happen to have the answer right here: www.redhat.com/support/query.cgi-bin?ref=cardhore? q=winmodem
[bob goes to the url]
Bob: YOU ASS HOLE I'M NOT PAYING $40 TO LEARN HOW TO DO THAT.
Bob leaves.
[twenty minutes pass]
Bob has entered #linux.
Bob: Cardhore...so are you still up for that offer?
Success!! Bob successfuly gets his modem working, Cardhore makes $$$, and RedHat pleases its shareholders!
Can a company make money off support for a product that is open source--a product that continues to evolve until it is "perfect" (and (potentially) not needing support)? And how? [These are an open ended question, not a troll.]
The project intends to provide binaries for most platforms so that you don't have to compile them yourself. Its binaries will also be un-branded--there will be no Eazel or Ximian logos, features, etc.
Also, just because someone can compile GNOME himself, it doesn't mean that he wants to. In fact, on moderate hardware it will take about two days to compile this. Experienced power users don't necessarily have time to waste on this.
From the article: ..where information wants to be free so long as it's other people's information.
Do people who believe this agree with it when their personal information is free?
Finnaly, 2.4.4 was released, and it is fixed: it's the first "stable" kernel in the new series.
I never read a single bad review of ReiserFS until I actually used it--it worked "flawlessly" for everyone who had tried it. I didn't find out that it had these problems, and that it doesn't work over NFS, until it was too late.
The thing I learned is that when things--especially filesystems--claim stability, the user still has to test things out for himself.
ReiserFS is a good filesystem; don't get me wrong, but it may not be the best for you. (In fact, Red Hat does not plan to use ReiserFS in its distribution, because in the event of filesystem failure, it is near impossible to recover the filesystem with standard tools.)
I have used XFS in the past on Irix machines and have been very happy with it. But be careful before you deploy this filesystem--even on your home machine--without thoroughly testing it. And not simply creating two files and saying, "Hey! They're still there! I guess it's stable." I fell into that trap.
I would highly reccomend anyone running the 2.4 kernel to upgrade to at least 2.4.4, especially if he uses IDE or ReiserFS.
If you're going to use XFS, test it first.
By the way, does anyone know what's going on with moderation? I've had mod points three times this week, and there are a huge amount of +5 comments.
*Yes, I know it's called the "X Window System." Yes, I'm joking.
Like XOR them! Or change their filenames from Hanson.tab to hhhhhhhhhhHanson.tab!
Good idea: We could change the ASCII indicated tempo from, say, 130 BPM to 130 + 10^-17, resulting in a completely different song! HA ha! That'll teach 'em.At first I thought you were referring to LILO and that error where it only displays LI.
would this be news (here) if it had been Linux...or BSD...or XFree that had crashed?
From his review:
Everyone who is on the internet has its own IP address. If you don't like numbers, there's DNS. That way your machine can have its own name. Want to know if your "buddies" are online? Ping their machines. Are they at their machines? Send them a "talk" request.
Let's see...that covers presence and messaging. What about file sharing? There's FTP and Telnet.
Problems with this? Definiately. Practically no one has its own IP address, so it doesn't have its own domain name as well. No one runs talkd on its machine. Talkd is unix only. Currently there are not enough IP addresses for everyone.
Advantages? You don't have to use anyone's central server.
Is instant messaging a better solution? Every instant messaging system tries too hard to hide its users' IP addresses: this makes it very annoying for me to try and use useful protocols--FTP, games, etc--with whom I'm trying to communicate because I have to do all this work to get their addresses. Messages are not encrypted.
On the other hand, Jabber will probably be extremely successful. Why? One word: XML. I have never had a bad experience with any software that uses XML ever, and I don't plan to.