Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Sep 2004 18:09:14 +0200
From:      Michael Nottebrock <michaelnottebrock@gmx.net>
To:        kde-freebsd@freebsd.kde.org
Cc:        Mikhail Teterin <mi@corbulon.video-collage.com>
Subject:   Re: [kde-freebsd] Re: sysutils/k3b and burncd(8)
Message-ID:  <200409151809.16844.michaelnottebrock@gmx.net>
In-Reply-To: <200409151709.53071.groot@kde.org>
References:  <200409151337.i8FDb0oP052727@corbulon.video-collage.com> <200409151709.53071.groot@kde.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart1300613.bJFOES3jqB
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 15 September 2004 17:09, Adriaan de Groot wrote:
> On Wednesday 15 September 2004 15:36, Mikhail Teterin wrote:
> > > > The k3b application seems unable to use FreeBSD's burncd(8) utility
> > > > to burn on IDE CD/DVD devices. It supports many other burning
> > > > back-ends, so adding it should not be too difficult, but I don't
> > > > want to duplicate the work.
> > > >
> > > > Is anyone working on it? At the moment one can only use k3b to
> > > > create an image and then burn it from command line...
> > >
> > > I don't know whether adding support for burncd makes too much sense,
> > > since you always can add atapicam support to your kernel and use k3b's
> > > cdrecord backend...
> >
> > This seems like a serious kludge to me. If we did not have the burncd
> > utility, or if k3b did not support many different burners, I'd agree
> > with you, but since the app has supports the back-end diversity, I
> > think, we should use it. Yours,
>
> The atapicam support was merged into k3b based on the patches from Heiner.
> I didn't realize that atapicam was an unstable and wonky bit of code (as
> suggested by two other messages in this thread).

It's not. Merging support for burncd, a completely unportable and platform=
=20
specific burning backend into a tool that's supposed to be portable (and=20
therefore supports _portable_ backends) however is a wonky idea.=20

If you want burncd (or any other mainstream burning utility) to support the=
=20
cd-writing facilities of ata(4), submit patches for cdrecord.

If you want to improve ease of use of k3b on FreeBSD, consider working on a=
=20
setup-assistant similar to the one k3b feature for Linux, which helps=20
endusers to adjust device permissions and make other system configuration=20
changes necessary for burning.


=2D-=20
   ,_,   | Michael Nottebrock               | lofi@freebsd.org
 (/^ ^\) | FreeBSD - The Power to Serve     | http://www.freebsd.org
   \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org

--nextPart1300613.bJFOES3jqB
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQBBSGksXhc68WspdLARAg6oAJ4234YZoH0gjdlpaxsAQyr8Ih6faQCfbg+7
m4WrRqD2FPOlk34pCLAshv8=
=Khz5
-----END PGP SIGNATURE-----

--nextPart1300613.bJFOES3jqB--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409151809.16844.michaelnottebrock>