Talk:Libburnia

Comments

Please verify 'Cross-platform' specification - seems to be only for Linux/Unix ??

There is no cross-platform support, it does not even compile on UNIX. Cdrskin is Linux only. 87.158.117.56 (talk) 19:54, 16 October 2008 (UTC)

It is included in various Linux xand BSD distributions (FreeBSD, NetBSD, Dragonfly BSD) and Solaris clones (OpenIndiana). No idea about other operating systems. Tzafrir (talk) 00:52, 10 April 2014 (UTC)

Technical statement by me as libburnia developer: libburn >= 1.3.6 can perform SCSI/MMC drive operations on Linux, FreeBSD, Solaris, and NetBSD. So there it can burn to all optical media. On other X/Open compliant systems it is restricted to POSIX i/o, which enables libisofs/libisoburn/xorriso to operate on filesystem image files.

Request by libburnia developer: Please consider to mention the use case of xorriso's emulation of mkisofs in the production of bootable ISO 9660 images. It works with GRUB2 underneath grub-mkrescue. It is used with ISOLINUX to produce live CD or installation ISOs of Debian, Ubuntu, Archlinux, ... http://www.gnu.org/software/grub/manual/html_node/Making-a-GRUB-bootable-CD_002dROM.html http://www.syslinux.org/wiki/index.php/Isohybrid

move to libburnia?

cdrskin is one of the binaries included with libburnia. Libburnia also includes xorriso, which should be the binary to use (or the library is used directly). Any objection for moving it? Tzafrir (talk) 15:59, 14 April 2014 (UTC)

Wikipedia prefers the common name. Use whatever fits best: libburnia, Burnia Project, keep the current name, or whatever… --KAMiKAZOW (talk) 17:41, 14 April 2014 (UTC)

Recent vandalism / edit warring by User:Knutjb

This user repeatedly tries to add false claims to the Cdrtools article and similar articles.

All his claims are void because it is a verifyable fact that CD/DVD/BluRay burning requires more than the privileges of a normal user. In addition, this is confirmed by many bug reports in the bug tracking systems of various Linux distros that confirm that burning fails with programs like "wodim" when done as a normal user but works with the same programs under the otherwise same conditions when called as root.

Wodim and similar software has no concept of dealing with this problem, but cdrtools implement support for Solaris fine grained privileges and for Linux capabilities via setcap, so cdrtools currently is the only burning software that allows a non-root user to burn optical media without problem.

It seems that the account Knutjb only exists for attacks against the cdrtools project. @Knutjb: Stop your attacks, or you will be blocked. Schily (talk) 11:50, 3 November 2015 (UTC)

This is cdrskin not wodim and you can write to cd when you are members of cdrom group that has write access to /dev/cdrom. Stop this vandalism. — Preceding unsigned comment added by Knutjb (talk • contribs) 19:52, 16 November 2015 (UTC)

• Helping to maintain WP articles to become or stay correct is not vandalism. What you are doing is at least edit warring. Adding false and unverified claims (this is what you did several times), harms Wikipedia.

• On all known operating systems (including Linux), you need to have root privileges or at least a list of special privileges. The latter is what cdrtools do in order to be able to correctly write CDs, DVDs and BluRays.

• The fact that Linux permits some of the needed SCSI command to be run by unprivileged users, does not verify your claims. The fact that the authors of libburnia do not know that special privileges are needed identifies them as partial informed people, but not as experts.

• Cdrtools implement a lot of features that need to send special (e.g. vendor specific) SCSI commands that cannot be send from an unprivileged user - even on Linux. These features are missing in simple tools like libburnia, This does not verify that libburnia is a solution for the privileges problem, this just identifies libburnia as a low end implementation for Linux that cannot be run in the documented way on other platforms that require root privileges for all SCSI commands.

• BTW: the fact that you need special privileges in order to write optical media is a verification that it makes no sense to write burning software that is put into a library. You cannot implement privileges separation in a library. If you e.g. like to do what is obvious from the existence of libburnia: implement a burning GUI on top of libburnia, you would need to run this GUI with root privileges. But running a GUI with root privileges is commonly seen as a big security risk. Cdrtools are well audited programs that separate the needed privileges from a complex GUI program. You cannot audit a GUI for not being a security risk, but you don't need to audit the GUI if it just calls the cdrtools programs. Schily (talk) 11:22, 17 November 2015 (UTC)

Schily, always up for a fight... his definition of "false" is: "does not agree with my personal opinion". Most people are not concern with dead os like Os/2. — Preceding unsigned comment added by 2001:464A:38F6:0:99C8:E87B:89EE:60E8 (talk) 15:39, 22 November 2015 (UTC)

Hi 2001:464A:38F6:0:99C8:E87B:89EE:60E8 you again forgot to log in and you forgot to mention why you started with a red herring (OS/2), that was never mentioned before, instead of giving us fact based arguments. Schily (talk) 11:41, 23 November 2015 (UTC)

We have another attempt of edit warring from User:Knutjb. He tries to add a claim that is verified to be false with the citation he added. Note that the citation mentions that you need to be root to call cdrskin with full features and that changes to the device permissions will make the system insecure. Schily (talk) 11:51, 25 November 2015 (UTC)

knutjb (talk · contribs) wants to offer a third opinion. To assist with the process, editors are requested to summarize the dispute in a short sentence below.

Viewpoint by (Scilly)

....

Scily: do not think program can burn cd or dvd as normal user when write permission is grant to /dev/cdrom

Viewpoint by (knutjb)

....

I think that both cdrskin and cdrkit can write cdrom as normal user when write permission is grant to /dev/cdrom.

Third opinion by knutjb

....

Knutjb (talk) 12:40, 25 November 2015 (UTC)

There are plenty of entries in the Debian bug tracking system that verify your claims as false. There is even a notice from "Eduard Bloch" where re recommends to run wodim as root. Schily (talk) 13:21, 25 November 2015 (UTC)

This is not wodim but cdrskin or libburina. Schily. You should at least use the correct name for this program. 2001:464A:38F6:0:1535:6097:6E35:4993 (talk) 14:33, 25 November 2015 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified 3 external links on Libburnia. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://web.archive.org/web/20120220123040/http://www.xfce.org/projects/xfburn to http://www.xfce.org/projects/xfburn
• Added archive https://web.archive.org/web/20110603234222/https://wiki.ubuntu.com/Xubuntu/MaverickMeerkat/Final to https://wiki.ubuntu.com/Xubuntu/MaverickMeerkat/Final
• Added archive https://web.archive.org/web/20160220020545/http://manpages.ubuntu.com/manpages/natty/man1/cdrskin.1.html to http://manpages.ubuntu.com/manpages/natty/man1/cdrskin.1.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 17:28, 22 December 2017 (UTC)