John Culleton
man growisofs
Or just use K3b (or some other burner app).
Duh.
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
The Usenet Improvement Project: http://improve-usenet.org
if you really want/need/desire to do it on the command line here
are the two fast ways I sometimes use:
# the stunt way, no holds barred, nothing to stop an
(under|over)flow, hence not really recommended if you
don't occasionnaly need to have a chance to renew you
collection of beermats ;-)
$ dd if=yourimage.iso of=yourDVDdevice bs=
example:
$ dd if=slackcurrent.iso of=/dev/sr1 bs=2352
(Note that I had no problem, so far, on a quiet machine
with a quite correct hardware)
# safe ways
growisofs -dvd-compat -Z /dev/sr1=yourimage.iso
or even safer:
growisofs -speed=4 -dvd-compat -Z /dev/sr1=yourimage.iso
(modify the file and device names as needed, your dvd
device is most probably /dev/hdc)
> Dan C wrote:
>
>> Or just use K3b (or some other burner app).
>
> I'll second that, K3B is the easy way to go, even I can manage it.
I quite like graveman. This application is much smaller than the KDE
things and seems to do all the things I want to do with it.
JB
OK Iĺl give it a go. but in the meantime, while waiting for
googlegroups to start working again,
I tried a cdrecord -dummy etc. command and it told me the file (5.7
gigs) was too big for any drive.
Not that familiar with dvd devices. Is 5.7 gigs too big altogether?
John Culleton
Just use the same command.
Make sure that you have the real cdrtools installed
ftp://ftp.berlios.de/pub/cdrecord/alpha/
The most recent version is 2.01.01a50
--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni)
schi...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily
> I tried a cdrecord -dummy etc. command and it told me the file (5.7
> gigs) was too big for any drive.
>
> Not that familiar with dvd devices. Is 5.7 gigs too big altogether?
I ran into the same issue. I think this may be due to all the extra KDE4
stuff in /testing. I tried burning it on a dual layer DVD (8 GiG
capacity), but it would not boot correctly so I went for an NFS install of
-current off my server. I'm interested to see if you have a similar
problem. You will need to omit /testing if you want to fit it under 4.0
GIG (capacity of single layer DVD's)
Just a note from the dark side, I've never burned CD/DVD under linux,
wimped out instead, and burn .iso over localnet on windoze box :o)
Grant.
--
http://bugsplatter.id.au/
> OK I'll give it a go. but in the meantime, while waiting for
> googlegroups to start working again,
> I tried a cdrecord -dummy etc. command and it told me the file (5.7
> gigs) was too big for any drive.
>
> Not that familiar with dvd devices. Is 5.7 gigs too big altogether?
By the very nature of these n00bish posts of yours, one must ask the
obvious question: Do you really think you should be trying to run
-current? Why do you think you need to run -current, anyway? What will
it do for you that Slackware 12.1 won't?
>OK I=E5l give it a go. but in the meantime, while waiting for
>googlegroups to start working again,
>I tried a cdrecord -dummy etc. command and it told me the file (5.7
>gigs) was too big for any drive.
>
>Not that familiar with dvd devices. Is 5.7 gigs too big altogether?
If you get a message like "too big for any drive", it does not look
as if you used cdrecord.
For more than 4 GB you need to use Dual Layer DVD media or BluRay media.
> Just a note from the dark side, I've never burned CD/DVD under linux,
> wimped out instead, and burn .iso over localnet on windoze box :o)
>
> Grant.
I'm just the oposite. I could never figure out how to copy or burn dvd's
in windows so I always did it in linux with K3B. I could never figure out
how to watch dvd's in windows either so I always watched in linux with
mplayer or xine.
I still need windows for work, but there are quite a few things I can say
I can't live without linux for. Managing my camera/photos is another.
Tagging mp3s is easier/better (for me) in linux as well.
Or omit the source, don't need that on an install DVD, you'll need to
loopback mount the downloaded iso image and write a script to build a
new .iso image with some missing bits, script I have is:
$ cat make-boot-dvd
#!/bin/bash
#
# build a slackware boot dvd, from isolinux/README.TXT
#
mkisofs -o /home/common/slackware-dvd.iso \
-R -J -V "Slackware Install" \
-x ./source \
-hide-rr-moved \
-v -d -N -no-emul-boot -boot-load-size 32 -boot-info-table \
-sort isolinux/iso.sort \
-b isolinux/isolinux.bin \
-c isolinux/isolinux.boot \
-A "Slackware Install DVD" .
is called from slackware-* install tree root directory.
Grant.
--
http://bugsplatter.id.au/
>In article <1e005cab-437e-4e30...@p59g2000hsd.googlegroups.com>,
>jo...@wexfordpress.com <jo...@wexfordpress.com> wrote:
>>I know how to burn a cd using cdrecord. But how do I burn a dvd given
>>the same hardware?
>>I have Slack-current in iso file form and I want to transfer it to the
>>external media. For a cdr I use
>>cdrecord dev=1001,0,0 foo.iso
>>The drive is dvd-capable, read and write.
>
>Just use the same command.
>
>Make sure that you have the real cdrtools installed
>
>ftp://ftp.berlios.de/pub/cdrecord/alpha/
Not into beta yet, after all these years? :)
Grant.
--
http://bugsplatter.id.au/
> Or omit the source, don't need that on an install DVD,
You are correct. My main point was that "something" needed
to be omitted from the iso iomage to fit it on one DVD.
> you'll need to loopback mount the downloaded iso image and write a
> script to build a new .iso image with some missing bits, script I have
> is:
>
> $ cat make-boot-dvd
> #!/bin/bash
> #
> # build a slackware boot dvd, from isolinux/README.TXT #
> mkisofs -o /home/common/slackware-dvd.iso \
> -R -J -V "Slackware Install" \
> -x ./source \
> -hide-rr-moved \
> -v -d -N -no-emul-boot -boot-load-size 32 -boot-info-table \
> -sort isolinux/iso.sort \
> -b isolinux/isolinux.bin \
> -c isolinux/isolinux.boot \
> -A "Slackware Install DVD" .
>
> is called from slackware-* install tree root directory.
>
> Grant.
I used the following from the isolinux directory:
mkisofs -o /tmp/slackware-dvd.iso \
-R -J -A "Slackware Install" \
-hide-rr-moved \
-v -d -N \
-no-emul-boot -boot-load-size 4 -boot-info-table \
-sort isolinux/iso.sort \
-b isolinux/isolinux.bin \
-c isolinux/isolinux.boot \
-V "SlackDVD" .
The resulting iso was burned to DVD (dual layer) and would not boot
correctly. Tried twice, made 2 coasters, and went with nfs install using
the 12.1 CD1 to get things started.
Heh, and all these years, I haven't burned a single coaster with cdrecord....
- Kurt
> Not that familiar with dvd devices. Is 5.7 gigs too big altogether?
An ordinary DVD has room for 4.7GB, so yes 5.7GB is too big.
--
Thomas O.
This area is designed to become quite warm during normal operation.
> jo...@wexfordpress.com wrote :
>
>> Not that familiar with dvd devices. Is 5.7 gigs too big altogether?
>
> An ordinary DVD has room for 4.7GB, so yes 5.7GB is too big.
It depends whether those are decimal or binary GB too, because it turns
out that
4.7 GB = 4.2 GB
to a first approximation.
The latest version of several graphical DTP packages require qt4 which
is compatible with kde4.
These include Scribus 1.3.5 and Inkscape 46.
Kde4 comes with testing. So I want to set up a separate partition for
current-testing for these apps.
I prefer that to butchering up my work partition with upgrades to this
and that.
What I don´t need is 12.1. There is a bug in the video routines that
causes freezes with Nvidia cards. Since there is no
particular feature of 12.1 that I need I use my 12.0 partition. There
is a patch to fix the video problem in 12.1 but I´ll just wait for the
next major release.
I very much appreciate the courtesy and helpfulness of most of the
responses on this newsgroup.
There are of course exceptions...
John Culleton
OK if I mount the iso file using the loop parameter, go to the mounted
area, delete the kernel sources,
the iso file should now be small enough to fit on a single layer DVD.
One small problem. The mounted file system thinks it is read-only even
though it is mounted rw.
Given all that I will install 12.0 on the new partition, copy over the
slackware directory from the mounted iso image,
then follow the instructions in UPGRADE.TXT using upgradepkg etc.
Anyone see any flaws in that?
John C.
>> By the very nature of these n00bish posts of yours, one must ask the
>> obvious question: Do you really think you should be trying to run
>> -current? Why do you think you need to run -current, anyway? What
>> will it do for you that Slackware 12.1 won't?
> The latest version of several graphical DTP packages require qt4 which
> is compatible with kde4. These include Scribus 1.3.5 and Inkscape 46.
> Kde4 comes with testing. So I want to set up a separate partition for
> current-testing for these apps. I prefer that to butchering up my work
> partition with upgrades to this and that.
I see. I do seem to recall a recent thread in here regarding QT4, and
that it could be installed completely alongside (seperately) QT3, with no
ill effects, and quite easily. If you think it's easier to do a whole new
install of -current, then have at it. You are mistaken, however.
> What I don愒 need is 12.1. There is a bug in the video routines that
> causes freezes with Nvidia cards.
Nonsense. I've got 4 systems here (including this Sony laptop) with
Nvidia cards in them, and NEVER ONCE have I had ANY of them freeze with
video problems. Do you have the Nvidia driver loaded?
> Since there is no particular feature of 12.1 that I need I use my 12.0
> partition. There is a patch to fix the video problem in 12.1 but I惻l
> just wait for the next major release.
There is no "video problem" in 12.1.
> The mounted file system thinks it is read-only even though it is
> mounted rw.
It doesn't matter how the iso file is mounted, ISO 9660 is a read-only
filesystem.
>
>jo...@wexfordpress.com wrote :
>
>> The mounted file system thinks it is read-only even though it is
>> mounted rw.
>
>It doesn't matter how the iso file is mounted, ISO 9660 is a read-only
>filesystem.
John missed:
http://groups.google.com.au/group/alt.os.linux.slackware/msg/d0adc8fcde1f03fb ??
I'm shattered... All those electrons twisted to my will gone to waste ;)
Grant.
--
http://bugsplatter.id.au/