Ah, but you see, that is not the fault of cdrtools! Oh no! Rather, it is a flaw in the (unmaintained) Linux kernel, that should have simply adopted the design of Solaris' SCSI subsystem that has been in use since the year 1981!
If you continue to experience problems then it is recommended that you upgrade to Solaris or Linux 2.4.
Yeah, and how he claims that because they weren't instantly accepted that it is evidence that the kernel is unmaintained!
cdrtools should have been forked years ago purely based on the technical issues. If you try to run it on a modern system it bleats that you should "upgrade" to Solaris or Linux 2.4!
Maybe now Joerg will admit that the Linux port of cdrecord is unmaintained and he will finally drop it. I wish.
The Ubuntu community doesn't respect Debian? From what I hear about the "Fuck Ubuntu" t-shirts being worn at Debconf6, and the (verbal) attacks on DDs who also contribute to Ubuntu, I think the problem is exactly the opposite.:(
We need a feature addition to Slashcode that does that repeated-plunging-of-penis-shaped-sound-wave thing into the head of anyone who rehashes the thired, old ROT-13 joke in one of their posts.
At least '1, 2, ???, profit', 'I, for one...' and 'haha it says nothing to see here OMGWTFBBQAOLCIA' are finally being retired.
What's with all the irrational Maxtor hate? I only buy Maxtor drives. They have a three year warranty and offer an advance RMA service. This means that when a drive fails they will send me a replacement, and I can use the box that the replacement came in to send them back the old drive. No need to faff about trying to find suitable packing materials on my end.
At the end of the day, all hard drives fail. Install them using at least four mounting screws, keep them ventillated, use smartmontools to keep an eye on the drives and back up your data and you won't have any problems.
- automatic build process, generating a makefile, or at list a part of it (dependencies) if you want flexibility. And don't tell me you like telling which.h you need for every single.c /.cpp file you got... it's stupid, repetitive and SHOULD MUST BE automatized.
Of course, but you don't need to flee to an IDE to do this!:)
GCC creates a.d file for each source file, that lists its dependencies; GNU Make reads these files (building them if they don't already exist) and uses them to know exactly which files are needed to build which other files.
If I need anything more complicated (i.e. automated cross-compiling, or providing a build system that has to work on an old crawling horror of a machine that GCC and Gnu Make can't be run on) and I use the autotools.
Re:Wasn't firefox designed as the simple mozilla?
on
Marketing Mozilla
·
· Score: 1
This used to be called GRE, and nowadays is called Xulrunner. Unfortunately it won't catch on until the Mozilla developers get a clue about shared library versioning.:(
There is a reason that every damn bit of software on Windows bundles private copies of all the libraries it uses that are not themselves part of Windows. No program is immune.
Oh, definately. I think the shred(1) manual even states this fact. I was speaking about using shred to erase an entire disk, in which case you only have to worry about the clever tricks played by modern disks to cover up bad blocks and other errors.
Insufficient. You should at least use shred(1). Even then, data on blocks marked as bad by the drive firmware won't be deleted. Check your drive's documentation; if you are lucky then there may be a command you can send to it to erase everything.
Slashdot Mirror
Ah, but you see, that is not the fault of cdrtools! Oh no! Rather, it is a flaw in the (unmaintained) Linux kernel, that should have simply adopted the design of Solaris' SCSI subsystem that has been in use since the year 1981!
If you continue to experience problems then it is recommended that you upgrade to Solaris or Linux 2.4.
Yeah, and how he claims that because they weren't instantly accepted that it is evidence that the kernel is unmaintained!
cdrtools should have been forked years ago purely based on the technical issues. If you try to run it on a modern system it bleats that you should "upgrade" to Solaris or Linux 2.4!
Maybe now Joerg will admit that the Linux port of cdrecord is unmaintained and he will finally drop it. I wish.
s/linked to/a derivative work of/g
The GPL does not mention linking, it only speaks about the creation of derivative works.
What constitutes a derivative work? You'd have to go to court to find out.
Which non-proprietary software are you using it to run?
The Ubuntu community doesn't respect Debian? From what I hear about the "Fuck Ubuntu" t-shirts being worn at Debconf6, and the (verbal) attacks on DDs who also contribute to Ubuntu, I think the problem is exactly the opposite. :(
I don't see how you can blame the distribution maker because you are shackled to proprietary software only available for i386.
Which manual?
Plus the application has to be linked against libgnome, libgnomeui and libgnomevfs. This is a big problem with the GNOME platform.
Don't take this the wong way... I'm just wondering why you don't use the Debian Packages? :)
I guess I asked for it, didn't I? :)
We need a feature addition to Slashcode that does that repeated-plunging-of-penis-shaped-sound-wave thing into the head of anyone who rehashes the thired, old ROT-13 joke in one of their posts.
At least '1, 2, ???, profit', 'I, for one...' and 'haha it says nothing to see here OMGWTFBBQAOLCIA' are finally being retired.
Stencils don't allow our local governments to send a £700k computer systems contract to a councillor's brother in law.
What's with all the irrational Maxtor hate? I only buy Maxtor drives. They have a three year warranty and offer an advance RMA service. This means that when a drive fails they will send me a replacement, and I can use the box that the replacement came in to send them back the old drive. No need to faff about trying to find suitable packing materials on my end.
At the end of the day, all hard drives fail. Install them using at least four mounting screws, keep them ventillated, use smartmontools to keep an eye on the drives and back up your data and you won't have any problems.
I'm pretty sure if he paid attention to his drive's SMART data then he would have been able to replace the drive before it burst in to flames.
# smartctl -Asmartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
3 Spin_Up_Time 0x0027 192 190 063 Pre-fail Always -
4 Start_Stop_Count 0x0032 253 253 000 Old_age Always -
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail Always -
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail Offline -
7 Seek_Error_Rate 0x000a 253 252 000 Old_age Always -
8 Seek_Time_Performance 0x0027 241 225 187 Pre-fail Always -
9 Spontaneous_Combustion 0x002b 232 232 020 Pre-fail Always -
10 Spin_Retry_Count 0x002b 239 232 157 Pre-fail Always -
and so on
Not in that quotation he hasn't. Either you didn't bother reading the rest of the interview or you are deliberately misinterpreting his words.
- no protection from the accidental deletion of the backup files
- drive (and hence backups) can be destroyed by a hardware failure (e.g., power supply fault) while drive is online
- hard disks are highly prone to spontaneous catastrophic failure anyway
- AFAIK you can't even query the SMART data of an external drive
This is not a backup solution in my book, it is merely a disaster waiting to happen.:help window
:help tabpage
:)
I recently read the excellent Recursive Make Considered Harmful paper, and subsequently came up with this:
include $(sources:.cpp=.d)
%.d: %.cpp
$(CXX) -MM -MF $@ -MT '$*.o $*.d' $<
GCC creates a
If I need anything more complicated (i.e. automated cross-compiling, or providing a build system that has to work on an old crawling horror of a machine that GCC and Gnu Make can't be run on) and I use the autotools.
This used to be called GRE, and nowadays is called Xulrunner. Unfortunately it won't catch on until the Mozilla developers get a clue about shared library versioning. :(
There is a reason that every damn bit of software on Windows bundles private copies of all the libraries it uses that are not themselves part of Windows. No program is immune.
Works on architectures other than i386. Can actually display text reliably. Sound and video in sync. Doesn't crash the browser.
The downloaded illegally copies the data from his network hardware to his computer's RAM and hard disk.
Unfortunately adding a mini-game to the installer is not possible. This invention was patented by Namco in 1995.
Perhaps it is their own form of copy protection? I'm finding it difficult to read the page at all. :)
Oh, definately. I think the shred(1) manual even states this fact. I was speaking about using shred to erase an entire disk, in which case you only have to worry about the clever tricks played by modern disks to cover up bad blocks and other errors.
Insufficient. You should at least use shred(1). Even then, data on blocks marked as bad by the drive firmware won't be deleted. Check your drive's documentation; if you are lucky then there may be a command you can send to it to erase everything.