Hi,
Curt wrote:
> I thought nobody said "should better not be used," but sticking that quoted
> phrase in a search engine produces over 12,000 hits.
12 thousand is not much. Popular germanisms get more. We are busy
spoilers of english language.
Hi,
Curt proposed:
> Wodim has proved to fail under certain conditions and as a general rule
> should probably be avoided when burning to DVD or BD media.
I like this better than what Brian (i assume) committed now:
https://wiki.debian.org/BurnCd?action=diff=36=37
"Wodim has proved much
Hi,
i wrote towards Jonathan Dowland:
> > Thanks for sparing me the questionable deed to revert the change myself.
> > So it is not a wiki war.
Brian wrote:
> Why is it questionable? Either you stand behind your statement or not.
Wikis going forth and back several times don't make a good
Hi,
i wrote:
> > So how should the statement be improved ?
> > ["wodim should better not be used with DVD or BD media."]
Curt wrote:
> You could say:
> It is preferable not to use wodim for DVD or BD media.
> Or
> It's better to avoid using wodim when burning to DVD or BD media.
> Or
> Wodim
Hi,
Steve McIntyre wrote:
> The only 2 reasons I've had for keeping the cdrkit package in Debian
> were:
> 1. hfs hybrid support in genisoimage, a topic that Thomas and I have
>spoken about in the past. Now that we no longer have powerpc in
>Debian stable and I don't have to care about
Hi,
Jonathan Dowland wrote:
> For the avoidance of any doubt, jmtd is me (Jonathan Michael Thomas
> Dowland).
Thanks for sparing me the questionable deed to revert the change myself.
So it is not a wiki war.
> I'm not involved in cdrkit development.
Nobody is involved there. Else i would chew
Hi,
Curt wrote:
> The French Wiki has something like:
> It is preferable not to use wodim with DVD or BD media.
It advise to stay with this for now.
> > I still hope for a statement by the (nominal) wodim maintainers.
Brian wrote:
> Keep hoping.
Well, Steve McIntyre does show up here from
Hi,
Brian wrote:
> Then revert the edit and link to this thread:
> wodim should [[https://lists.debian.org/debian-user/2018/09/msg01031.html
> better|not be used]] with DVD or BD media.
I still hope for a statement by the (nominal) wodim maintainers.
... or maybe StephenKeeling shows up ...
Hi,
deloptes wrote:
> I was trying to burn DVD+DL and had the feeling it does not do what I want
> it to do. I trashed couple of DL DVDs - each costs ~3€.
Yes. I too experienced that DVD+R DL are the most early type to fail
on an ageing drive. I still have half a spindle of them, but only
for
Hi,
Brian proposed:
> There is (strong? extensive?) evidence that wodim should not be used
> with DVD or BD media. However, the many variables involved, especially
> burner types and media type and quality, could result a successful
> burn.
There are not that many variables:
Drive type:
Hi,
Greg Wooledge wrote:
> In the case of the BurnCd page, I actually *do* think that it would be
> of general interest to readers to have a paragraph explaining the limits
> of wodim, and when not to use it.
Let me try ... hrr-umm ...
wodim was cloned from cdrecord in 2006. At that time,
Hi,
is perhaps the Debian wiki user StephenKeeling subscribed here ?
We need to discuss the recent wiki change
https://wiki.debian.org/BurnCd?action=diff=30=31
Alternatively:
- Does the wiki have means to contact a particular Debian wiki user ?
- Does the wiki have means to discuss facts or to
Hi,
Brian wrote:
> You're after a fight, aren't you? :)
Given the topic, it would be unnatural if no branches and twigs would
appear in this thread. (My apologies to Thakur Mahashaya.)
I wrote:
> > (Hey. You smuggled the word "system" between "standard" and "utility.)
> Does it count as going
Hi,
Markus Raps wrote:
> and the script should rebuild the disk.
> unfortunately UEFI only systems wont boot it.
> ...
> xorriso -as mkisofs \
Thank you for flying xorriso.
As for the lack of EFI boot equipment in your script, see
https://wiki.debian.org/RepackBootableISO
"Repacking a
Hi,
i wrote:
> > No command line CD/DVD/BD burning:
Dave Sherohman wrote:
> Sounds pretty far from "standard" to me. Bordering on "esoteric", even.
Burn programs compensate for a shortcomming of the Linux kernel and
the Unix device model. If a burner drive is built into the machine,
then a
Hi,
André Rodier wrote:
> Hello Debian pros,
No, no. We are just the users. Often quite confused.
> I am trying to build an ISO image with the package debian-cdd, and I am
> struggling with the following error:
The package's news list on
https://tracker.debian.org/pkg/simple-cdd
looks like
Hi,
Brian wrote:
> There can be no dispute over the meaning of "standard system
> utilities". These are the ones which have a "Priority: standard"
> field in the package description.
There can always be a dispute. q.e.d.
(Hey. You smuggled the word "system" between "standard" and "utility.)
Hi,
mick crane wrote:
> have a look in /usr/bin ?
Not to forget /bin, /sbin, /usr/sbin :
https://wiki.debian.org/FilesystemHierarchyStandard
/bin is specified to hold "essential" programs.
/sbin is its add-on for system administrators.
/usr/bin + /usr/sbin together hold nearly 4000 files on
Hi,
Thakur Mahashaya wrote:
> Please tell me what is the list of standard utilities in Debian?
If this is a trick question: Good one. It makes me think.
A standard utility is supposed to be installed often. The popularity of
Debian packages is ranked at
https://popcon.debian.org/by_inst
A
Hi,
> Sure, but a 32GB USB stick is now to be had for $10. Would that
> be suitable?
Well, it is an extra precondition. Maybe the USB stick is already planned
to finally hold the boot-ready ISO image.
Whatever, if an extra USB stick without valuable data is at hand, this
seems to be a viable
Hi,
David Wright wrote:
> I mount all the "foreign" partitions readonly (both NTFS and FAT)
That's a wise move in general, of course.
But if you are downloading a BD sized ISO of 20+ GiB, then RAM based
"disk" storage might be too small.
As soon as the ISO is composed from template file and
Hi,
Rick Thomas wrote:
> For example, if your home has limited Internet bandwidth, but you can drive
> to a library (or your place of work) where the bandwidth is better, it might
> be better to use the DVD or BD (blue-ray) install image on a USB stick.
Yeah. But will a public or workplace
Hi,
Kleene, Steven wrote:
> Yes. If I put the cursor in the little screenshot and type a command
> (echoed in a font too small to read), it does execute there.
I wonder how many inadverted people shot their foot already.
Did you try the settings which helped me to get some normal icon and
to
Hi,
David Wright wrote:
> > > It's generally recommended on this list that you install from netinst
> > > rather than from a live system.
Thakur Mahashaya wrote:
> > tell me why the network is better?
David Wright wrote:
> I follow this list, and keep an eye on others' reported problems;
Hi,
Kleene, Steve wrote:
> I have this in ~/.fvwm/config:
> Style "XTerm" Icon null.xpm, SloppyFocus, IconBox 200x200-1+8
> where null.xpm is intended to call /usr/share/pixmaps/fvwm/null.xpm, a
> zero-byte file I created.
Maybe fvwm is not happy with the zero size.
What happens if you put
Hi,
mick crane lured me into writing:
> > No loopback is needed.
David wrote:
> It is a "loop" device.
Indeed. Probably i would also have adopted "loo-thingy" while my head
was wrapped around the partition table stuff.
Have a nice day :)
Thomas
Hi,
i wrote:
> > You could even use program fdisk to delete partition entry 2 in the ISO
mick crane wrote:
> never really understanding this.
> If mount iso as loopback does it show up in fdisk ?
No loopback is needed. fdisk will operate directly on the ISO image file
as it would operate on the
Hi,
John Roman wrote:
> > netinst and live both create a dos partition table on dd, and cp.
Pascal Hambourg wrote:
> "On dd, and cp" ?
Steve McIntyre and i understood John's statement that after dd or cp
there is a MBR partition table on the USB stick. The following
conversation would make few
Hi,
John Roman wrote:
> As a Gentoo user,
In 2016 the Gentoo ISOs were BIOS-only.
I now downloaded install-amd64-minimal-20180913T214501Z.iso which looks
much like a Debian ISO, partition-wise.
xorriso -indev install-amd64-minimal-20180913T214501Z.iso \
-report_system_area plain
Hi,
John Roman wrote:
> As I understand, a Protective MBR may be located at LBA 0
In the case of the isohybrid partition layout of Matthew J. Garrett,
which is used by Debian for i386 and amd64, the MBR is not protective.
A bit confusing can be the GPT partition table debris that follows the
Hi,
Yanhui He wrote:
> I need to update a 3rd PR to Debian by sending mail
> to 896...@bugs.debian.org, but it always failed.
> 550 5.0.350 Remote server returned an error -> 550 Unknown or archived bug
The bug tracker page
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896911
says
Bug is
Hi,
i wrote:
> > What do you get from command stat index.html
Pétùr wrote:
> File: .cache/shotwell/thumbs/thumbs360/thumb0c5c.jpg
> Size: 24576 Blocks: 32 IO Block: 4096 regular file
> Device: 802h/2050d Inode: 4744568 Links: 1
> Access:
Hi,
Pétùr wrote:
> > d-wS--S--T 2 1061270772 2605320832 4096 oct. 7 2412 index.html
to...@tuxteam.de wrote:
> Whoa. 'S' is a setuid file which is not executable. Exotic, to say
> the least.
Not to speak of the year 2412, and "index.html" being a directory.
> Perhaps you are dealing with
Hi,
Reco wrote:
> Wait. You're *the* Thomas Schmitt who wrote xorriso?
Yep. I am the current developer of libburn, libisofs, libisoburn, cdrskin,
xorriso.
There were others involved, though.
libburn was forked from a half-dead project in 2006. Not more than 25
percent of the code is still f
Hi,
Reco wrote:
> > It's the usual. A compatibility wrapper can never exceed the original.
rhkra...@gmail.com wrote:
> Hmm, I don't see why it couldn't in some sense -- I'm trying to think of how
> to say what I want to say, let me try a made-up example.
I could offer my program cdrskin as real
Hi,
i wrote:
> That's probably because there is bash-ism in the script,
Of course i meant to say:
That's probably because there is _no_ bash-ism in the script,
Have a nice day :)
Thomas
Hi,
David Wright wrote:
> As I posted, I get the same behaviour whichever shebang I have,
> any of bash|dash|sh.
That's probably because there is bash-ism in the script, except the
variable READLINE_LINE which the boss bash is supposed to have set.
> If the script has no shebang, then (I
Hi,
Norbert Gruener wrote:
> after my upgrade to Stretch I got these problems :-(
Did you already check whether it is a matter of the terminal program ?
If it is a bit rot problem between readline and terminal, then you
might get lucky with a different one.
Have a nice day :)
Thomas
Hi,
i replayed this on Jessie.
I get printed lines "aaa" for every F1 i press.
No shell prompts get printed inbetween, but rather the shell prompt
and the text "aaa" stay in the base line of the xterm.
The text "aaa" can be edited and the new text gets printed with F1.
Like after three times
Hi,
Jonathan Dowland wrote:
> Many also permit the changing of the Subject: field when the topic has
> wandered away from the original value. It would be a great service to
> many of one's fellow mailing list participants if more people would take
> advantage of that.
In general i agree.
But
Hi,
Reco wrote:
> -INT_MAX. I win.
It is time for projective geometry.
Have a nice day :)
Thomas
Hi,
Richard Owlett wrote:
> With a good filename, nothing printed.
> With a bad filename, it reports file not found.
But it does not abort at that point, does it ?
When the file name is bad, is the resulting filenumber 0 ?
If not: Can you read or write to that filenumber ?
I cling so massively
Hi,
Note: this mail is purely nostalgic and not about yaboot.
David Wright wrote:
> [HP 9845B] If they had a weak point, it was those little tape drives
I once had a hidden line removal program reading a 3D model from one
tape and writing the intermediate result to the other. Then i had to
Hi,
Greg Wooledge wrote:
> But if BASIC is working for someone out there, then hey, great.
Sure. I am still wondering what will be the final solution to Richard's
riddle. (The typo theory seems to have died now. Remains the sticky error
theory.)
Have a nice day :)
Thomas
Hi,
i wrote:
> > why use such a C-BASIC when there is gcc, gdb and valgrind ?
> 'Cause the last time I used C was about 4 *DECADES* ago ;}
This way you missed the everlasting joy of hunting bugs which trigger
SIGSEGV at some arbitrary point of program execution.
valgrind widely industrialized
Hi,
i wrote:
> > (Found the booklet. It's HP BASIC 3.0, not 2.0. Newest techology of 1985.)
David Wright wrote:
> I thought we were up to version 4.0¹ by 1985,
Indeed, the booklet says "June 1984 ... First Edition".
I think i did not get to BASIC 4.0 because in 1986 i wrote a BASIC program
Hi,
Curt wrote:
> I ain't no programmer, but sure is butt ugly.
Yeah. This Yet-Another-BASIC lacks the ON ERROR GOTO gesture.
(Found the booklet. It's HP BASIC 3.0, not 2.0. Newest techology of 1985.)
Have a nice day :)
Thomas
Hi,
i still have a HP BASIC 2.0 Quick Reference somewhere ...
Richar Owlett wrote:
> fd_in=open("/home/richard/Documents/cherrytree/edit_bookmarks/expermental_copies/prettytest0txt","r")
> print peek$("error")
Although the open() call does not really look like BASIC, it is authorized
by
Hi,
Martin McCormick wrote:
> Ah, this sounds good. Thank you.
I assume that the system is very limited.
If you need more, consider the Debian Live ISOs at
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/
https://cdimage.debian.org/debian-cd/current-live/i386/iso-hybrid/
Hi,
Martin McCormick wrote:
> Maybe I am missing something obvious but is there a way
> to boot the CD, select language and keyboard and then skip
> directly to the rescue shell?
Trying it with
qemu-system-x86_64 -enable-kvm -m 512 -cdrom debian-9.3.0-amd64-netinst.iso
I select menu item
Hi,
Tabor Kelly
> How do I report this bug?
In general, do what
https://www.debian.org/Bugs/Reporting
prescribes. If you do not have a running system with program "reportbug",
then scroll down to paragraph "Sending the bug report via e-mail".
Main decision to take is the name to be given with
Hi,
i now understand that the page is not about _submitting_ bugs but rather
for operating the bug tracker.
In that light, Brian's statement would indeed explain the meaning.
Brian wrote:
> The subject of the mail has no importance and requ...@bugs.debian.org
> will completely ignore it. So you
Hi,
i too read on
https://www.debian.org/Bugs/server-request
"The Subject of the message is ignored, except for generating the Subject
of the reply."
This is indeed a riddling statement.
Last time i submitted a bug it had the subject:
live-wrapper: debian-live-9.4.0-amd64-xfce.iso
Hi,
Martin wrote:
> There is -or was, quite some time ago I've last seen this- a software called
> famd (File Alteration Monitor ->
> https://en.wikipedia.org/wiki/File_Alteration_Monitor). Looks like there is
> no .deb in a current repo, but may be the name has changes.
Maybe this ?
Hi,
I really really want to abstain from that thread. So a new one:
Gene Heskett wrotei in 'mailing list vs "the futur"':
> [...] NNTP [...]
> To fully support it needs 2000 times the bandwidth of an email server.
But not because of the transport protocoli or message format. NNTP belongs
to the
Hi,
Jude DaShiell wrote:
> The cdrecord program uses a different library
> and that always throws dma test skipped warning.
That's a consequence of its troublesome family background.
Always waiting for an opportunity to say "You do it wrong. *Pain!*".
> I don't know what wodim uses for a
Hi,
Jude DaShiell wrote:
> If bashburn and cdrskin can work together, you're likely to get serious
> performance increase in terms of how your drive does the actual burning.
wodim is quite ok on its own turf of CD burning.
Problems occur with bitrot.
E.g.
wodim --devices
finds no drive any
Hi,
i wrote:
> You could try to learn the effective wodim command by reporting it in
> /usr/share/bashburn/lib/burning/burning.sh
> at line 82:
Reading it again, i see that the proposal is too much progammer's jargon.
Let me try again.
In the said file at line 82 insert this shell command
Hi,
Cindy-Sue Causey wrote:
> Man, cdrskin is
> little. That always amazes me when a lot of power can be had in very
> small Linux programs.
That's because most of the brain sits in libburn.so. The static build is
three times as big.
Champion in size is growisofs, if we do not count the bloat
Hi,
Cindy-Sue Causey wrote:
> I test drove it with grub-pc the other day to
> make sure it did what I was about to tell fellow users it does. I had
> to wade thru... 550+ outstanding bugs to get to the part about...
The problem is that both GRUBs are little operating systems which are
Hi,
Curt wrote:
> report-bugged by Dan, who somehow cleverly extricated himself from the
> Catch 22
reportbug just sends a mail to sub...@bugs.debian.org.
It can be done completely by hand. See
https://www.debian.org/Bugs/Reporting
from
"Sending the bug report via e-mail"
up to and including
Hi,
Curt wrote:
> But then I told
> myself, "Just be wrong, Curt, completely, utterly, unqualifiedly, and
> enjoy it for once!"
It is not easy to achieve true perfection in this field.
I wrote:
> > only the most die-hard audiophiles will complain.
Curt wrote:
> I guess you need the die-hard
Hi,
Doug wrote:
> > > wav may be a lossy format, but
> > > you can get a heck of a lot of CDs on an 8GiB flash drive!
Curt wrote:
> > wav is lossless, I believe, not lossy,
Jeremy Nicoll wrote:
> Wav is a container format, which can contain compressed or uncompressed
> audio.
Yes. But in the
Hi,
(i reply to Doug's mail but adopt Dan Ritter's new subject text.)
Doug wrote:
> I would make some copies of CDs onto a flash drive, if I knew how!
The act of copying audio data from CD is usually called "ripping".
Program cdda2wav is specialized on that job.
I would use my own program
Hi,
Bob Bernstein wrote:
> The playback is jumpy, or skippy, anything but smooth and continuous.
https://www.cyberciti.biz/faq/linux-unix-mplayer-playing-audio-dvd-cd-using-bash-shell/
proposes option "-cache 5000":
mplayer -cdrom-device /dev/sr0 cdda:// -cache 5000
I guess it's a
Hi,
Nicolas George wrote:
> To be accurate, mount only directs the kernel into doing the reads and
> looking for filesystems.
Yes. But in hindsight my explanation was already more technical than
appropriate.
"mount(8) is not the right way to access an audio CD."
would have been better. But i
Hi,
Bob Bernstein wrote:
> bob@debian:~$ mount /dev/sr0
> mount: /dev/sr0 is write-protected, mounting read-only
> mount: wrong fs type, bad option, bad superblock on /dev/sr0, missing
> codepage or helper program, or other error
> [...]
> bob@debian:~$ dmesg |tail
> [...]
> [ 1005.988702] Sense
Hi,
if i had no other preferences, i'd use program "bc" in an xterm with
enormous scroll buffer.
Run in some shell window:
xterm -fg black -bg wheat -sl 10 &
and then in the newly emerged xterm shell window
bc
(My virtual paper is of eco-friendly color. I do not let xterm start bc
Hi,
> In pcmanfm's address bar, [...]
> [...]
> Any recomendations on how to diagnose and report this bug?
Since there is a package with name "pcmanfm", there is also a tracker page
for it
https://tracker.debian.org/pkg/pcmanfm
Registered maintainer contact is the mailing list
Hi,
Dave wrote:
> i have downloaded debian-9.4.0-amd64-DVD-1.iso
> when i double click on it, it says cannot open. the iso
> debian-9.4.0-amd64-DVD-2 and iso debian-9.4.0-amd64-DVD-3
> i can open and read. the same thing happened with debian 9.0.0.
> i am using mac pro 10.10.5 to download / open
Hi,
Rick Thomas wrote:
> Instead, I used
>firmware-9.4.0-amd64-netinst.iso
> to avoid any possible alpha/testing anomalies.
Normally i'd say that there is no decisive difference to expect.
In any case copying a "netinst" ISO is much faster than a "DVD-1".
> When I tried part (a) — just a
Hi,
i created an ISO with this partition table:
$ /sbin/gdisk -l test.iso
...
MBR: protective
...
GPT: present
...
Number Start (sector)End (sector) Size Code Name
1 64 7713831 3.7 GiB 0700 ISO9660
2 7713832
Hi,
Rick Thomas reported that the boot process of
firmware-buster-DI-alpha2-amd64-DVD-1.iso
fails with
Incorrect CD-ROM detected
after it was re-partitioned to GPT.
It seems that the software in the initrd of a Debian isohybrid wants a
mountable partition with the ISO 9660 filesystem and
Hi,
Rick Thomas wrote on Sun, 27 May 2018 03:28:20 -0700
> > > specifically, firmware-buster-DI-alpha2-amd64-DVD-1.iso
i wrote:
> > Point 4 of that tutorial says:
> > "NOTE: If your USB device is not listed in the Boot Manager list,
> >confirm that it’s GPT formatted and contains a valid
Hi,
i typo'ed:
> deletion of GPT partition 2 because it overlaps
> with the EFI partition,
Partition 1 needs to be delted. Number 2 is the EFI partition.
Further it comes to me that the gdisk session is best done one the
USB stick with the ISO already copied onto it. This will give gdisk
a
Hi,
didier gaumet wrote:
> > https://minnowboard.org/tutorials/best-practice-boot-media-selection
Rick Thomas wrote:
> [...] when I dd that same .iso
> onto a USB stick, then plug the stick into the USB slot on the Turbot, will
> not be recognized as a bootable medium.
Point 4 of that tutorial
Hi,
i wrote:
> Linux discontinued the /dev/sd* device files
I meant /dev/scd*, not /dev/sd*.
Have a nice day :)
Thomas
Hi,
davidson wrote:
> https://help.ubuntu.com/community/CdDvd/Burning#Burning_a_CD_or_DVD_using_C
ommand_Line_tools
"Sometimes Ubuntu fails to detect and configure your Burner. This results
in "no media found" if you use 'wodim dev=/dev/cdrw'. Even 'wodim -scanbus'
does not work [...] Ok
Hi,
Abdullah Ramazanoğlu wrote:
> > But beware of k3b's KDE dependencies.
Ben Oliver wrote:
> This is a good point, it does bring quite a lot in.
If it's about that, then i can beat them all with
https://packages.debian.org/sid/utils/xorriso-tcltk
(On older Debians install "tk", "bwidget",
Hi,
Herb Garcia wrote:
> I'm running Mate on my laptop. I don't see a CD/DVD burning software
> that came with the build. Any suggestions?
The big three with GUI are: K3B, Brasero, Xfburn.
Their Debian package names are "k3b", "brasero", "xfburn".
On the command line there are growisofs,
Hi,
Mike Kupfer wrote:
> there seems to be something odd going on with the live image ISOs.
> [...]
> alto$ sudo dd if=debian-live-9.4.0-amd64-xfce.iso of=/dev/sdb bs=32K
> [...]
> 1951465472 bytes (2.0 GB, 1.8 GiB) copied, 455.702 s, 4.3 MB/s
> alto$ sudo isosize -x /dev/sdb
> sector
Hi,
i wrote:
> > - Compromise is to set the boot flag on a dummy partition of type 0x00.
> > This is barely UEFI-compliant because the specs say that a partition of
> > type 0x00 shall be regarded as non-existent.
Pascal Hambourg wrote:
> - I had to use the old fdisk version from Wheezy
Hi,
Mike Kupfer wrote:
> I used sha256sum instead of sha512sum, but I otherwise followed
> the above instructions. The checksum from the dd pipeline does not
> match the checksum of the original .iso file.
That's not good.
Especially we do not have to show up at grub-devel as long as the test
Hi,
i wrote:
> > And as said previously, BIOS does not expect any partitions.
Pascal Hambourg wrote:
> experience taught me that many BIOS implementations wrongly
> expect an MBR partition entry with the boot flag set in order to boot from
> the disk.
You are right (and those firmwares are
Hi,
David Wright wrote:
> I read it as meaning that the USB stick works as a live system
> (first boot), but not as an installer (second boot).
Hm ... re-reading Mike's mails ...
Mike Kupfer wrote in his first mail:
> > > using a netinst image and a live image.
and today:
> > If I select the
Hi,
Mike Kupfer wrote:
> I'm booting using EFI.
So this could be a problem with GRUB about how it leaves the USB stick
after having loaded kernel and initrd from it.
The volatility of success and failure still gives me riddles. But if you
can reproduce failure within a bearable number of tries,
Hi,
Stefan Monnier wrote:
> > the behavior of the firmware
> > and OS when faced with a disk that has both a GPT and an MBR partitions
> > is largely unspecified and will vary depending on your system).
David Wright wrote:
> I've yet to see a GPT disk that didn't have a protective MBR.
> I
Hi,
i wrote:
> > [6.997775] usb 1-2: New USB device found, idVendor=abcd,
> > idProduct=1234
> > They are missing in the good log. Other kernel version ?
> The good and bad logs are both
> for the same kernel--they're different attempts to boot the same ISO
> using the same USB stick.
Hi,
Mike Kupfer wrote:
> (full files sent off-list)
Received.
> Hmm. The bad log has
>
> [7.015708] usbcore: registered new interface driver uas
> [ 25.552030] random: crng init done
It is quite sparse from that point on:
[ 29.034207] usb 1-2: reset high-speed USB device number 2
Hi,
i wrote:
> > The messages quoted by Kent could well indicate that the "CD-ROM" was
> > found
Curt wrote:
> I was laboring under another erroneous impression for some reason, but
> looking back at the OP he did say that the installer complained about
> not being able to "read" the cdrom (not
Hi,
Mike Kupfer wrote:
> usb 1-2: device descriptor read/64, error -110
If we assume that 110 is a Linux errno, then this would be
ETIMEDOUT 110 /* Connection timed out */
> usb 1-2: reset high-speed USB device number 2 using xhci_hcd
That's what my USB attached DVD drives
Hi,
Pascal Hambourg wrote:
> I have never seen a hard disk or flash drive with a sector size of 2048
> (only 512 or 4096) so the kernel must be correct and the Apple partition
> table must be wrong.
Both are correct. The kernel reports what it perceives as hardware block
size ("physical"). The
Hi,
Pascal Hambourg wrote:
> Why then does parted complain about a block size discrepancy ?
Because the Apple Partition Map announces to count blocks with size 2048
whereas the Linux device file announces 512 (via ioctl(BLKSSZGET) ?)).
It is quite a poor choice of parted to hop on the Apple
Hi,
Kent West wrote:
> Warning: The driver descriptor says the physical block size is 2048 bytes,
> but Linux says it is 512 bytes.
The Apple Partition Map block size is 2048 indeed. Else it could not
coexist with the GPT.
> Disk /dev/sdc: 62.7GB
> Sector size (logical/physical): 2048B/512B
>
Hi,
Kent West wrote:
> > I learned that EFI boot drives need to have a GPT partition table.
No. They do not. An MBR partition of type 0xEF is well ok, too.
> > discovered that the flash drive had a "mac" partition table.
> > Wha-a-ah-h-h??
It has an MBR partition table with partition 2 having
Hi,
Kent West wrote:
> The real problem is that after going through the first three or four
> screens, the install halts, complaining about not being able to read the
> CD-ROM.
Report this to debian...@lists.debian.org and add the original messages
of the complaing software.
I'd say that if the
Hi,
> Suggestions?
https://www.gnu.org/software/bash/manual/html_node/Bash-History-Builtins.html
and
man bash
To find the description of the command "history", use search expression:
/history \[n\]
The man page is full of details about the "history" as concept and
how to use it, quite
Hi,
Richard Owlett wrote:
> > I thought I had broken the loop by specifying -x.
Jonathan Dowland wrote:
> This is one excellent illustration of why cp is the wrong tool for this
> job.
cp -ax is not at fault, as it seems.
The reason for the problem has been identified as a file path on the
Hi,
Richard Owlett wrote:
> > /home/richard/.local/share/Trash/expunged/1449727740/
> └── grub2 problem-2018-02-13
> ...
> Goes on for 161 directories
The name is 24 bytes long.
Plus one slash yields 25.
161 times 25 = 4025 bytes for the problem directories.
Plus 53 for "/home/...40/" = 4078.
So
Hi,
Richard Owlett wrote:
> I couldn't interpret what I was seeing so below are excerpts of what was
> captured by script command.
It is hard to understand what "script" wants to tell us.
"less" would have been more useful for our purpose of displaying output
and navigating in it.
Whatever, we
901 - 1000 of 1741 matches
Mail list logo
