LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 02-23-2020, 04:09 PM   #121
scdbackup
Member
 
Registered: Oct 2013
Posts: 133

Rep: Reputation: Disabled

Hi,

> the sound suggest the disk is rotating in the tray. the sound
> continues for long periods after use of sr0 drive is through.
> is this common?

Yes. The drive has several stages of readiness for work ("power conditions"):
STANDBY, IDLE, ACTIVE. Noisy is in most cases ACTIVE. IDLE is some kind of
low-power mode. In condition STANDBY the drive cannot read or write.

On the first read command from the Linux kernel the drive goes into ACTIVE.
After some time of no work the drive decides to enter STANDBY. If commands
arrive which need ACTIVE or IDLE it lasts some time until the commands get
performed.

> attempted unmount with no joy.

xorriso brings the drive into STANDBY before giving it up. Try:
Code:
xorriso -outdev /dev/sr0
If it begins again to be noisy, then some program tries to read from it.
xorriso does so only when it is running. Any later noise was caused by others.

Have a nice day

Thomas
 
Old Yesterday, 11:46 AM   #122
wayne1937
Member
 
Registered: Dec 2019
Location: United States
Distribution: mint19 Cinnamon
Posts: 124

Original Poster
Rep: Reputation: Disabled
thomas :-)

changed media: DVD+RW up to 4X compatible. media a great improvement.
as you can see, bionicpup files burned fast and smooth.

have a question: why are "-" (dashes) used in front of the various xorriso code? and what language is xorriso written in?

included some snippets of libburn and libisof work.

below code: remove directory, surprised that it worked :-)

code: $ xorriso -dev /dev/sr0 -rmdir /x-file_dump.1
........................................................................

$ dir_on_disk=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso
$ dir_in_iso=/bionicpup64-8.0-uefi.iso.1
$ xorriso -dev /dev/sr0 -map "$dir_on_disk" "$dir_in_iso"

xorriso 1.4.8 : RockRidge filesystem manipulator, libburnia project.

Drive current: -dev '/dev/sr0'
Media current: DVD+RW
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 4483m free
xorriso : UPDATE : 1 files added in 1 seconds
Added to ISO image: file '/bionicpup64-8.0-uefi.iso.1'='/home/ddval/Downloads/bionicpup64-8.0-uefi.iso'
xorriso : UPDATE : Formatting. Working since 0 seconds
xorriso : UPDATE : Formatting. Working since 1 seconds
.
.
.
xorriso : UPDATE : Formatting. Working since 10 seconds
libburn : NOTE : Write start address is 32 * 2048
xorriso : UPDATE : Writing: 16s 0.0% fifo 100% buf 100%
xorriso : UPDATE : Writing: 592s 0.3% fifo 100% buf 100% 0.9xD
xorriso : UPDATE : Writing: 3024s 1.7% fifo 100% buf 99% 3.6xD
xorriso : UPDATE : Writing: 5760s 3.2% fifo 100% buf 99% 4.0xD
.
.
.
xorriso : UPDATE : Writing: 180832s 99.7% fifo 21% buf 99% 4.0xD
xorriso : UPDATE : Closing track/session. Working since 81 seconds
.
.
.
xorriso : UPDATE : Closing track/session. Working since 86 seconds
ISO image produced: 181271 sectors
Written to medium : 181440 sectors at LBA 32
Writing to '/dev/sr0' completed successfully.

cheers :-)
 
Old Yesterday, 12:20 PM   #123
scdbackup
Member
 
Registered: Oct 2013
Posts: 133

Rep: Reputation: Disabled
Hi,

> xorriso : UPDATE : Writing: 180832s 99.7% fifo 21% buf 99% 4.0xD
> xorriso : UPDATE : Closing track/session. Working since 86 seconds

Well 360 MiB is not very large for a DVD's content.
A full capacity burn run lasts about 15 minutes.


> why are "-" (dashes) used in front of the various xorriso code?

Purely ornamental in order to emphasize the difference between commands
and their parameters. You may prepend as many dashes as you want to a
command word or you may write its "_" underscores as dashes. These three
runs do all the same:
Code:
xorriso outdev /dev/sr0 list_formats
xorriso -outdev /dev/sr0 -list_formats
xorriso --outdev /dev/sr0 --list-formats
> what language is xorriso written in?

C. The language which gets you through any mud pit but lets you look
accordingly afterwards.

> $ xorriso -dev /dev/sr0 -map "$dir_on_disk" "$dir_in_iso"

If you let xorriso put the bionicpup ISO into a new ISO then it will
not boot. It will just be a data file like any other.

The way to make a bootable DVD would be to write it as disc image
by xorriso's -as cdrecord emulation.

Have a nice day

Thomas
 
1 members found this post helpful.
Old Yesterday, 12:46 PM   #124
wayne1937
Member
 
Registered: Dec 2019
Location: United States
Distribution: mint19 Cinnamon
Posts: 124

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by scdbackup View Post
Hi,

> xorriso : UPDATE : Writing: 180832s 99.7% fifo 21% buf 99% 4.0xD
> xorriso : UPDATE : Closing track/session. Working since 86 seconds

Well 360 MiB is not very large for a DVD's content.
A full capacity burn run lasts about 15 minutes.


> why are "-" (dashes) used in front of the various xorriso code?

Purely ornamental in order to emphasize the difference between commands
and their parameters. You may prepend as many dashes as you want to a
command word or you may write its "_" underscores as dashes. These three
runs do all the same:
Code:
xorriso outdev /dev/sr0 list_formats
xorriso -outdev /dev/sr0 -list_formats
xorriso --outdev /dev/sr0 --list-formats
> what language is xorriso written in?

C. The language which gets you through any mud pit but lets you look
accordingly afterwards.

> $ xorriso -dev /dev/sr0 -map "$dir_on_disk" "$dir_in_iso"

If you let xorriso put the bionicpup ISO into a new ISO then it will
not boot. It will just be a data file like any other.

The way to make a bootable DVD would be to write it as disc image
by xorriso's -as cdrecord emulation.

Have a nice day

Thomas
how do you make data appear in boxes such as this data:

xorriso outdev /dev/sr0 list_formats
xorriso -outdev /dev/sr0 -list_formats
xorriso --outdev /dev/sr0 --list-formats

>>Well 360 MiB is not very large for a DVD's content.

how did you arrive at this number?
 
Old Yesterday, 01:38 PM   #125
scdbackup
Member
 
Registered: Oct 2013
Posts: 133

Rep: Reputation: Disabled
Hi,

> how do you make data appear in boxes such as this data:

[code]
xorriso outdev /dev/sr0 list_formats
xorriso -outdev /dev/sr0 -list_formats
xorriso --outdev /dev/sr0 --list-formats
[/code]

There is also a "#" icon which sets a pair of CODE and /CODE (if Javascript
is enabled). First i did not find a description of this markup language
here, but it looks much like https://en.wikipedia.org/wiki/BBCode
... and indeed the "Posting Rules" at the bottom of this page has a link
BB code
which lists the tags and gives examples.
(So i learned how to use "noparse" to write "[code]"
rather than getting it interpreted as start of a code text block.)

Have a nice day

Thomas
 
Old Yesterday, 01:43 PM   #126
scdbackup
Member
 
Registered: Oct 2013
Posts: 133

Rep: Reputation: Disabled
Hi,

> > Well 360 MiB is not very large for a DVD's content.

> how did you arrive at this number?

xorriso told so:
> > > Written to medium : 181440 sectors at LBA 32

One sector contains 2048 bytes. So it's 371,589,120 bytes = 354.375 MiB.

Have a nice day

Thomas
 
Old Yesterday, 02:50 PM   #127
ehartman
Senior Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 1,185

Rep: Reputation: 662Reputation: 662Reputation: 662Reputation: 662Reputation: 662Reputation: 662
Quote:
Originally Posted by scdbackup View Post
xorriso told so:
> > > Written to medium : 181440 sectors at LBA 32
That's only the amount of data written TO the DVD.
The media should be able to store much more (a normal DVD is about 4.5 GB).
 
Old Yesterday, 03:21 PM   #128
scdbackup
Member
 
Registered: Oct 2013
Posts: 133

Rep: Reputation: Disabled
Hi,

> The media should be able to store much more (a normal DVD is about 4.5 GB).

Yes. xorriso told roughly:

> > > Media summary: 0 sessions, 0 data blocks, 0 data, 4483m free

Exactly measured, a DVD+RW is supposed to have 2,295,104 blocks
= 4,700,372,992 bytes = 4482.625 MiB.

Have nice day

Thomas
 
Old Yesterday, 03:25 PM   #129
wayne1937
Member
 
Registered: Dec 2019
Location: United States
Distribution: mint19 Cinnamon
Posts: 124

Original Poster
Rep: Reputation: Disabled
$ iso=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso
$ xorriso -as cdrecord -v dev=/dev/sr0 -eject "$iso"
xorriso 1.4.8 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev '/dev/sr0'
Media current: DVD+RW
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 4483m free
Beginning to write data track.
xorriso : UPDATE : Formatting. Working since 0 seconds
xorriso : UPDATE : Formatting. Working since 1 seconds
xorriso : UPDATE : Formatting. Working since 2 seconds
xorriso : UPDATE : Formatting. Working since 3 seconds
libburn : NOTE : Write start address is 0 * 2048
xorriso : UPDATE : 1 of 354 MB written (fifo 99%) [buf 100%] 0.9x.
xorriso : UPDATE : 4 of 354 MB written (fifo 96%) [buf 99%] 2.6x.
xorriso : UPDATE : 9 of 354 MB written (fifo 98%) [buf 99%] 4.0x.
xorriso : UPDATE : 15 of 354 MB written (fifo 96%) [buf 99%] 4.0x.
.
.
.
xorriso : UPDATE : 346 of 354 MB written (fifo 98%) [buf 99%] 4.0x.
xorriso : UPDATE : 351 of 354 MB written (fifo 57%) [buf 99%] 4.0x.
xorriso : UPDATE : Closing track/session. Working since 73 seconds
xorriso : UPDATE : Closing track/session. Working since 74 seconds
xorriso : UPDATE : Closing track/session. Working since 75 seconds
xorriso : UPDATE : Closing track/session. Working since 76 seconds
xorriso : UPDATE : Closing track/session. Working since 77 seconds
Writing to '/dev/sr0' completed successfully.

xorriso : NOTE : Re-assessing -outdev '/dev/sr0'
Drive current: -outdev '/dev/sr0'
Media current: DVD+RW
Media status : is written , is appendable
Media summary: 1 session, 181030 data blocks, 354m data, 4129m free
ddval@ddval-p6653w:~$ xorriso -as cdrecord -v dev=/dev/sr0 -eject "$iso"

the bionicpup iso burn posted before was not run with cdrecord in the code. when the burned iso was opened there were no files, but there was object when clicked gave no response. therefore ran the previous code using cdrecord and got an good burn. looks like MiB on both burns are close, kinda weird.

thanks for info. really do appreciate your taking the time and working with me :-)

cheers
 
Old Yesterday, 06:19 PM   #130
wayne1937
Member
 
Registered: Dec 2019
Location: United States
Distribution: mint19 Cinnamon
Posts: 124

Original Poster
Rep: Reputation: Disabled
used this code:

$ dir_on_disk=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso
$ dir_in_iso=/bionicpup64-8.0-uefi.iso.1
$ xorriso -dev /dev/sr0 -map "$dir_on_disk" "$dir_in_iso"
..........................................................................
snippets of executed xorriso code:
.
.
.
xorriso : UPDATE : Writing: 179600s 99.0% fifo 81% buf 99% 4.0xD
xorriso : UPDATE : Writing: 181440s 100.0% fifo 0% buf 99% 2.7xD
.
.
.
xorriso : UPDATE : Closing track/session. Working since 81 seconds
ISO image produced: 181271 sectors
Written to medium : 181440 sectors at LBA 32
Writing to '/dev/sr0' completed successfully.
...........................................................................
opened libburn/libsofs iso. expected to find 14 files, however, discovered
single Binary (application/octet-stream). wanted to send screen shots, but could not figure how to attach to this reply. could send via email provided you want them.
..........................................................................
quite mysterious: why does this code produce a binary, while this code:
xorriso -as cdrecord -v dev=/dev/sr0 -eject "$iso" produce 14 files?

cheers :-)
 
Old Yesterday, 06:29 PM   #131
wayne1937
Member
 
Registered: Dec 2019
Location: United States
Distribution: mint19 Cinnamon
Posts: 124

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by scdbackup View Post
Hi,

> how do you make data appear in boxes such as this data:

[code]
xorriso outdev /dev/sr0 list_formats
xorriso -outdev /dev/sr0 -list_formats
xorriso --outdev /dev/sr0 --list-formats
[/code]

There is also a "#" icon which sets a pair of CODE and /CODE (if Javascript
is enabled). First i did not find a description of this markup language
here, but it looks much like https://en.wikipedia.org/wiki/BBCode
... and indeed the "Posting Rules" at the bottom of this page has a link
BB code
which lists the tags and gives examples.
(So i learned how to use "noparse" to write "[code]"
rather than getting it interpreted as start of a code text block.)

Have a nice day

Thomas
This is great, just what i needed to clarify my post.
 
Old Today, 03:23 AM   #132
scdbackup
Member
 
Registered: Oct 2013
Posts: 133

Rep: Reputation: Disabled
Hi,

> $ xorriso -dev /dev/sr0 -map "$dir_on_disk" "$dir_in_iso"
> quite mysterious: why does this code produce a binary, while this code:
> xorriso -as cdrecord -v dev=/dev/sr0 -eject "$iso" produce 14 files?

The difference between both xorriso runs is that
Code:
xorriso -dev /dev/sr0 -map "$dir_on_disk" "$dir_in_iso"
wraps "$dir_on_disk" in a newly created ISO 9660 filesystem, where it
appears under the name "$dir_in_iso". Since you set
Code:
dir_on_disk=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso
dir_in_iso=/bionicpup64-8.0-uefi.iso.1
your new ISO will contain exactly this single data file under the name
/bionicpup64-8.0-uefi.iso.1.

On the other hand, the run
Code:
iso=/home/ddval/Downloads/bionicpup64-8.0-uefi.iso
xorriso -as cdrecord -v dev=/dev/sr0 -eject "$iso"
does not wrap anything into a filesystem but rather copies the bytes of
the data file "$iso" unchanged onto the DVD medium.
Your data file is a filesystem image with all the necessary bytes to
represent the 14 files which it contains. So after it was copied,
there will be the 14 files to see in the mounted DVD.

(As i explained in comment 102, three of the 14 files in
bionicpup64-8.0-uefi.iso are filesystem images themselves:
/efi.img, /puppy_bionicpup64_8.0.sfs, and /zdrv_bionicpup64_8.0.sfs.
If the ISO and these three image files get mounted, they bear in sum
35908 directories and files.)

Why the names:
"cdrecord" is a program which burns data to optical media. "mkisofs"
is its companion to produce ISO 9660 filesystems.
xorriso is younger than these and integrates both tasks in one program.
But since many old programs and users are used to the options of mkisofs
and cdrecord, xorriso offers by its command -as an emulation of their most
frequent use cases.
The emulations have their own man pages:
https://www.gnu.org/software/xorriso...xorrecord.html
https://www.gnu.org/software/xorriso...xorrisofs.html
beneath the man page of xorriso's native personality
https://www.gnu.org/software/xorriso/man_1_xorriso.html

Have a nice day

Thomas
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] XFburn, Slackware 13 64bit, "error while loading shared libraries: libburn.so.4" fearfactory Linux - Software 1 05-16-2010 09:30 PM
xfburn keeps crashing richard.donavan Linux - Software 1 11-27-2009 05:57 PM
[SOLVED] xfburn keeps crashing on slackware 13 64 hoodooman Slackware 2 11-13-2009 01:55 PM
Slackbuild XFburn - What order do I install related files 12.1 NightSky Slackware 7 10-15-2009 12:11 AM
XFburn - slow start when burning audio cd samac Slackware 2 09-28-2009 06:01 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 02:36 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration