I have OnChip USB 2.0 support on a VIA chipset and am using it under FreeBSD, with no problems. I also have OnChip Firewire support as well as Ethernet over Firewall which is correctly detected, although I haven't messed with it yet.
WRONG! Whenever I have to use lsof to find a goddamned open file handle on the CD-ROM, my blood boils.
I didn't read all the responses justifying this bug, but how the hell can you have an open file on an unmounted drive? Since, of course, you have to unmount your CDROM in order to eject it, wouldn't unmounting close all open files on that partition?
umount -f/cdrom
"-f" is for "force"; it should unmount your CD-ROM drive and allow you to eject it. I don't get you Linux users.
2. what if you don't want to kill that app? Often you're already browsing a completely different directory or -in case of Konqueror instead of Nautilus- you have a number of additional tabs open.
I didn't read all the replies justifying this bug, but in Galeon, you can do File -> Exit with session. Once you restart Galeon, all your tabs and open windows will be restored. Very cool. All Unix applications should have this feature.
"I recommend" is basically a euphemism for "I highly am pleased with". I thought everyone knew that.
Nothing wrong with saying "I recommend FreeBSD". This statement of fact uses a timeless tense, spreading across the spectrum of time endlessly. It does not refer to a particular instance, or even imply that one exists. It does not suggest that I have ever even recommended FreeBSD; merely that if I was asked for a recommendation, that I would recommend it.
"I recommend" is more like one's political beliefs than a recount of history or what was has done in the past. You should try using this idiom sometime; you'll get suprising results.
You might want to contact Soren Schmidt; he is currently developing the ATA driver last time I checked. His website is freebsd.dk, this is an excerpt of the relevant text:
I'm currently the author and maintainer of the FreeBSD ATA driver (disk, cdrom, DVD, ZIP, LS120 etc).
I also wrote the Linux emulator, the FreeBSD console driver syscons and libvgl graphics lib, plus various other bits and pieces,
most of which I have handed over to new maintainers to concentrate on the ATA driver.
The latest patches/enhancements to the ATA driver can be found here
A list over supported CDR / CDRW drives (burncd + ATA driver) is here
If you have ATA/ATAPI/IDE hardware that is not supported, please contact me at sos@FreeBSD.dk
I remember one day, long ago, upgrading my FreeBSD system and noticing the hard disk names changed from/dev/wd to/dev/ad (for ATA disk). I'm pretty sure SOS was responsible for that; today, I'm using a RAID subsystem (/dev/ar0) with a CD burner supported by the ATA driver. (/dev/acd). Very cool. I'm sure I'm not the only one that appreciates his work.
Definitely get in touch with Soren, I'm sure he would be able to help. There may be licensing issues in porting the Linux driver; though. Probably best to write it from scratch (as is sadly common with BSD and GPL software today.)
I can crash my system with Alt-Enter in X. Apparantly this is a "key sequence" to cause X to switch video modes; to an invalid mode in this case. After I do this, I have to use Ctrl-Alt-Bang to terminate X, and my console window is heavily dimmed, and X won't start again. So I have to reboot. I think we can say that I have crashed FreeBSD, since its GUI is now useless.
Note: I've done all this as a normal user. I'd like to configure FreeBSD's X to not recognize the Alt-Enter keystroke in any case. How?
There was a show a while back on broadcast television about a portion of land set off for zero electromagnetic energy. It was well out of the range of civilization; and everyone that lived there rode bikes. (No cars - the sparks create EMF). Of course, light is itself a form of electromagnetic radiation.
If you're going to dim all light, attenuate the EMF too! Its arguably more harmful, and you might as well kill several trillion possible wavelengths than just a small, limited, range of visible light. EMFs (electromagnetic fields) are much too pervasive in our daily life's, and it would be something to be able to travel to a place where none exist.
Re:Why not try it out indeed?
on
Perl 1.0?
·
· Score: 1
That's very torpor of you.
Re:There's one good thing about it.
on
Perl 1.0?
·
· Score: 1
Then why don't you use an EDITOR that eliminates repetitive tasks?
Re:I have been working on another one
on
Replacing SMTP?
·
· Score: 1
That's pretty cool. Consider, the Internet itself is:
Unreliable
Untrusted
Unsecure
All of the above. Various technologies have been developed to assuage these problems with IP (not really problems; as they can be "fixed" at higher layers, but if you use IP directly you definitely have to worry about reliability, trust, and security).
To address the unreliability of IP, TCP was developed.
To address the sniffability/insecureness of IP (anyone with access to a router, proxy server, or wireless network can see certain traffic that passes through), SSL/TLS and other encryption was developed.
I see your project, CAKE, as the final step. Layered over TCP for reliability, one could send mail with verified authenticity without the slowdown of encryption. Very nice.
\
Re:Why not try it out indeed?
on
Perl 1.0?
·
· Score: 1
Secondly you contradict yourself. First you say: I mean crap, as in the stuff that comes out of everyones ass.. This cleary coincides with the first definition of crap:
1 a usually vulgar : EXCREMENT b usually vulgar : the act of or product of defecating
However, then you say: Perl is crap!. Needless to say this usage corresponds to the second definition:
2 sometimes vulgar : NONSENSE, RUBBISH; also : STUFF 4b
You appear to be confused, I suggest you read the Carp documentation, its very informative, and you'll learn a lot about Perl.
Maybe my pirated windows installation is fucked, but when I change virtual desktops, it appears that all the windows are minimized. The transisition is very choppy. Contrast to my GNOME install, which is much more quick (even with a slower CPU).
I tried a couple illegally-downloaded cracked commercial "virtual desktop" utilities but none of them made the cut. Whilst trying to find the software I ripped off; I came across a Slashdot article: Virtual Desktops for Win32. Maybe those stuck on Microsoft will find it useful.
Interestingly enough, the linked article recommends LiteStep, a GPL'd application for a Win32 virtual desktop alternative shell. So here I am, on a cracked commercial OS, downloading cracked software, and I find that the freely available programs (LiteStep and GNOME for Unix) work better.
Re:The title must not say it all
on
Perl 1.0?
·
· Score: 1
Also on my annoyance list: "Needless to say." If it's needless to say, then why say it?
The clause "needless to say" is used to avoid patronizing the more advanced readers, while still providing seemingly-obvious information to the neophytes. Needless to say, what is obvious to one is not necessarly obvious to another; therefore what needs to be said to a neophyte does not need to be said to a guru.
Re:Why not try it out indeed?
on
Perl 1.0?
·
· Score: 0, Troll
Never knew "crap" was an adjective. Maybe you mean Carp? (Its not an adjective either.)
Re:There's one good thing about it.
on
Perl 1.0?
·
· Score: 1
Um, vi? or awk? or sed? or even ed?
Maybe the reason Perl programmers like it so much is that they're too lazy to learn any other tool. Just as if the only tool you have is a hammer, every problem looks like a nail, then if you're a Perl hacker, every problem looks like it needs a Perl solution...
Perl is more like a swiss army knife than a hammer.
Re:There's one good thing about it.
on
Perl 1.0?
·
· Score: 1
Oh, so now I need a special text editor to use Python.
No, all you need is to learn how to repeatedly press the spacebar instead of the tab.
Re:Some things to point out.
on
Perl 1.0?
·
· Score: 1
Nothing wrong with dispatch tables. Very maintable in my opinion.
Slashdot Mirror
If I did that I'd have to restart X, which I must avoid. Restarting is for Windows users.
Use webmail.
Maybe its the drivers that suck?
Median is a type of average.
Nothing wrong with saying "I recommend FreeBSD". This statement of fact uses a timeless tense, spreading across the spectrum of time endlessly. It does not refer to a particular instance, or even imply that one exists. It does not suggest that I have ever even recommended FreeBSD; merely that if I was asked for a recommendation, that I would recommend it.
"I recommend" is more like one's political beliefs than a recount of history or what was has done in the past. You should try using this idiom sometime; you'll get suprising results.
I remember one day, long ago, upgrading my FreeBSD system and noticing the hard disk names changed from /dev/wd to /dev/ad (for ATA disk). I'm pretty sure SOS was responsible for that; today, I'm using a RAID subsystem (/dev/ar0) with a CD burner supported by the ATA driver. (/dev/acd). Very cool. I'm sure I'm not the only one that appreciates his work.
Definitely get in touch with Soren, I'm sure he would be able to help. There may be licensing issues in porting the Linux driver; though. Probably best to write it from scratch (as is sadly common with BSD and GPL software today.)
Good luck...
Note: I've done all this as a normal user. I'd like to configure FreeBSD's X to not recognize the Alt-Enter keystroke in any case. How?
Alright, its illegal to steal copyrighted material through file-sharing. How do you suggest I steal copyrighted material?
If you're going to dim all light, attenuate the EMF too! Its arguably more harmful, and you might as well kill several trillion possible wavelengths than just a small, limited, range of visible light. EMFs (electromagnetic fields) are much too pervasive in our daily life's, and it would be something to be able to travel to a place where none exist.
Thanks for reading.
You don't think so?
That's very torpor of you.
Then why don't you use an EDITOR that eliminates repetitive tasks?
All of the above. Various technologies have been developed to assuage these problems with IP (not really problems; as they can be "fixed" at higher layers, but if you use IP directly you definitely have to worry about reliability, trust, and security).
To address the unreliability of IP, TCP was developed.
To address the sniffability/insecureness of IP (anyone with access to a router, proxy server, or wireless network can see certain traffic that passes through), SSL/TLS and other encryption was developed.
I see your project, CAKE, as the final step. Layered over TCP for reliability, one could send mail with verified authenticity without the slowdown of encryption. Very nice. \
Secondly you contradict yourself. First you say: I mean crap, as in the stuff that comes out of everyones ass.. This cleary coincides with the first definition of crap:
However, then you say: Perl is crap!. Needless to say this usage corresponds to the second definition:You appear to be confused, I suggest you read the Carp documentation, its very informative, and you'll learn a lot about Perl.
Maybe my pirated windows installation is fucked, but when I change virtual desktops, it appears that all the windows are minimized. The transisition is very choppy. Contrast to my GNOME install, which is much more quick (even with a slower CPU).
I tried a couple illegally-downloaded cracked commercial "virtual desktop" utilities but none of them made the cut. Whilst trying to find the software I ripped off; I came across a Slashdot article: Virtual Desktops for Win32. Maybe those stuck on Microsoft will find it useful.
Interestingly enough, the linked article recommends LiteStep, a GPL'd application for a Win32 virtual desktop alternative shell. So here I am, on a cracked commercial OS, downloading cracked software, and I find that the freely available programs (LiteStep and GNOME for Unix) work better.
Never knew "crap" was an adjective. Maybe you mean Carp? (Its not an adjective either.)
Nothing wrong with dispatch tables. Very maintable in my opinion.