On Tue, Jan 09, 2024 at 10:57:29AM -0500, Stefan Monnier wrote:
> >>What are you talking about? FAT does not get “overloaded” by long
> >>filenames.
> > Seen it happen;
>
> I have serious doubts about the "it".
>
> > Long filenames, mixed case, and files saved at the beginning of
> > a session
On Tue, 9 Jan 2024 10:07:26 -0600
David Wright wrote:
Hello David,
>The size of that is fixed when formatted, at least up to FAT16.
>Long filenames will eat it up more quickly still. Create
>subdirectories and the problem goes away.
Yes, this is exactly what I experienced. So not the FAT at
On Tue 09 Jan 2024 at 10:57:29 (-0500), Stefan Monnier wrote:
> >>What are you talking about? FAT does not get “overloaded” by long
> >>filenames.
> > Seen it happen;
>
> I have serious doubts about the "it".
>
> > Long filenames, mixed case, and files saved at the beginning of
> > a session of
>>What are you talking about? FAT does not get “overloaded” by long
>>filenames.
> Seen it happen;
I have serious doubts about the "it".
> Long filenames, mixed case, and files saved at the beginning of
> a session of copying multiple files would be lost because the FAT was
> filled, and
On Tue, 9 Jan 2024 16:15:27 +0100
Nicolas George wrote:
Hello Nicolas,
>Pictures or it did not happen.
Didn't bother because it appeared to be a well-understood phenomenon,
based on my limited research.
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The
Brad Rogers (12024-01-09):
> Seen it happen; Long filenames, mixed case, and files saved at the
> beginning of a session of copying multiple files would be lost because
> the FAT was filled, and overwritten from the start by files added later
> in the session.
>
> We are talking in excess of
On Tue, 9 Jan 2024 13:25:52 +0100
Nicolas George wrote:
Hello Nicolas,
>What are you talking about? FAT does not get “overloaded” by long
>filenames.
Seen it happen; Long filenames, mixed case, and files saved at the
beginning of a session of copying multiple files would be lost because
the
Brad Rogers (12024-01-09):
> Depends; I ended up buying three smaller sticks, because the
> limitations of the file system meant that the File Allocation Table
> got filled up wy before the larger capacity memory sticks did.
The USB sticks we were discussing in this thread are way below the
he command from play to Play, and now it
> works without the cache problem. The Play command is:
I personally choose to have both a scripts directory not in my $PATH,
where I call the commands with explicit path, and a ~/bin directory at
the beginning of my path.
> mplayer /dev/sr0 cdd
On Mon, 8 Jan 2024 21:09:54 +
Michael Kjörling <2695bd53d...@ewoof.net> wrote:
Hello Michael,
>Alternatively, they also offer SanDisk SDXC 128 GB memory cards at $14
>a piece. One such will easily hold 1000 CDs at near-CD quality MP3.
Depends; I ended up buying three smaller sticks,
On Monday 08 January 2024 03:49:17 pm Haines Brown wrote:
> where can find an inexpensive drive to hold about 1000 cds and find
> the time do all the converting? ㋡
The 4TB drive in my server has about 77GB roughly holding a similar amount of
stuff. The time was over a rather lengthy period
> The time to physically go through all those CDs, now that's a slightly
> different issue.
Once you've setup your "rip" tool (I used mostly `grip` back then,
not sure what's still maintained, maybe `abcde`?), it's a small matter
of putting the next CD in the drive when the previous one is
On 8 Jan 2024 15:49 -0500, from hai...@histomat.net (Haines Brown):
>> But unless you cannot spare 60 megaoctets somewhere, save yourself a lot
>> of trouble: just run cdparanoia -B then opusenc and put back the audio
>> CD at the back of the shelf where it belongs.
>
> where can find an
On Mon, Jan 08, 2024 at 05:37:00PM +0100, Michel Verdier wrote:
> On 2024-01-08, Haines Brown wrote:
> > But the $ play command only returns the aplay -help info. Why won't
> > the script work?
>
> You fumble on another "play" program. Try "type -a play" to
> confirm. Then just rename your
On Mon, Jan 08, 2024 at 04:32:37PM +, Michael Kjörling wrote:
> I suspect this is because of insufficient read-ahead or insufficient
> bandwidth, as you seems to assume to based on your comment on buffer
> size. You might be able to use --cache=yes to improve matters.
To judge by the man
On Mon, Jan 08, 2024 at 05:23:34PM +0100, Nicolas George wrote:
> Haines Brown (12024-01-08):
> > I find that often (such as wiki.debian.org/CDDVD) I'm told to mount
Understood about not mounting CDROM disks. Confused music with data
disks
> > The mplayer command $ mplayer -cd
Hi,
i cannot contribute much to the practical issues with playing music.
But i'd like to clarify technical properties of CD-DA media:
Nicolas George wrote:
> compared to data CDs, audio CDs lack one layer of error-correcting code
True.
Another drawback is that CD-DA sectors cannot be read by
Michael Kjörling (12024-01-08):
> Note that while CD-DA disks are technically CD-ROM disks (compact disk
> read only media), in typical usage "CD-ROM" is taken to mean a CD
> which contains _data organized as files within a file system_, often
> an ISO-9660 file system typically with extensions
On 2024-01-08, Haines Brown wrote:
> I find that often (such as wiki.debian.org/CDDVD) I'm told to mount
> the cdrive. But I can play cds without mounting. Wny is mounting
> sometimes recommended?
It talks about mounting "data" CD. Audio CD cannot be mounted and are
accessed by device (like
SO-9660 file system typically with extensions (Rockridge, Juliet,
...).
> I wanted to use aplay to play music on cdrom, but have concluded
> it cannot be done in any straightforward way. Why not?
Likely simply because nobody has implemented that. Software to play
audio CDs exists aplenty; is th
oo use it.
> But I can play cds without mounting. Wny is mounting
> sometimes recommended?
Either people are wrong to recommend it or you are mistaken in thinking
they recommend it.
> I wanted to use aplay to play music on cdrom, but have concluded
> it cannot be done in any straig
I wish to play cdrom music discs from an exterrnal USB CDROM drive. It
is the Rioddas drive recomended for linux.
I find that often (such as wiki.debian.org/CDDVD) I'm told to mount
the cdrive. But I can play cds without mounting. Wny is mounting
sometimes recommended?
I wanted to use aplay
On Mon, Dec 4, 2023, 3:30 AM Thomas Schmitt wrote:
> .
> This seems to indicate that the firmware has a stake in the problem ...
>
> > Both the Thinkpad E14 Gen 5s had the same specifications and type number,
> > differing only in that the one with corruption of the installer has 24GB
> of
>
On Thu 15 Jun 2023 at 21:32:41 (+), Totoro wrote:
> After entering
>
> sudo apt update
>
> The following messages appeared on the console:
>
> Ign:1 cdrom://[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD
> Binary-1 with firmware 20230610-10:23"] boo
. sudo apt-cdrom -m -d=/mnt/mount-iso add
4. sudo apt update
After entering
sudo apt update
The following messages appeared on the console:
Ign:1 cdrom://[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD Binary-1
with firmware 20230610-10:23"] bookworm InRelease
Err:2 cdrom://[D
Install the 1st DVD (Debian
> OS) it's work. not work for CD 2 and 3 because the format then, I think I
> need to extract the files into flashdisk.
>
> but, I can't install samba because the "apt-cdrom" stay read from CDRom
> while the File was on Flashdisk
apt-cdrom has a
Hi,
SteffenTAN wrote:
> They only give Me 3 files with name of DVD 1, 2 and 3
> so, I searching for answer then, I use rufus to Install the 1st DVD (Debian
> OS) it's work.
I guess you could install a base system from the "DVD-1" stick and then
put the mount point addresses of the two other
files iso images. Do they end in .iso?
> but, I can't install samba because the "apt-cdrom" stay read from CDRom
> while the File was on Flashdisk
> please help Me
>
Can't you install software from the online repos?
> I'm very frustated
>
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠
the format then, I think I
need to extract the files into flashdisk.
but, I can't install samba because the "apt-cdrom" stay read from CDRom
while the File was on Flashdisk
please help Me
I'm very frustated
Hi
did you solve this? i got this problem, too with qemu 7 and ubuntu 22.04.1
--
--
cordially
Charlie Schindler
+66 9 1083 7897
Please help me use DVDs to install additional packages. I can do a clean
install from DVDs, but not add additional packages. 'apt update' says it
disables the DVDs because it cannot find their release files.
My understanding, the purpose of 'apt-cdrom' is to save summary
information from
Here the complete grep cdrom /var/log/syslog:
Jul 7 10:48:44 bilbo automount[31697]: key "cdrom" not found in map
source(s).
Jul 7 11:35:04 bilbo automount[31697]: key "cdrom" not found in map
source(s).
Jul 7 11:39:20 bilbo automount[31697]: key "cdrom" not fou
On Lu, 06 iul 20, 07:49:09, Reiner Buehl wrote:
> Hello,
>
> I keep getting messages from syslog "key "cdrom" not found in map
> source(s)." on the console of my Debian Stretch system but I don't even
> have a cd rom installed in this system.
>
> I alread
Hello,
I keep getting messages from syslog "key "cdrom" not found in map
source(s)." on the console of my Debian Stretch system but I don't even
have a cd rom installed in this system.
I already checked /etc/fstab, /etc/samba/smb.conf, /etc/autofs.conf and all
t
En plein dans le 1000 !!!
Merci à vous 2 pour vos conseils !
Le 30/04/2020 à 12:46, Raphaël POITEVIN a écrit :
> Petrusko writes:
>> Je me demande comment accéder à mon lecteur de CDROM/DVD, à partir
>> duquel j'aimerais créer une image .iso du disque qu'il contient.
>>
On 4/30/20 12:11 PM, Petrusko wrote:
Bonjour à tous !
Je me demande comment accéder à mon lecteur de CDROM/DVD, à partir
duquel j'aimerais créer une image .iso du disque qu'il contient.
En voyant plusieurs tutos, je n'arrive pas à trouver dans quel
/dev/x il se trouve ! (ou alors j'ai un
Petrusko writes:
> Je me demande comment accéder à mon lecteur de CDROM/DVD, à partir
> duquel j'aimerais créer une image .iso du disque qu'il contient.
> En voyant plusieurs tutos, je n'arrive pas à trouver dans quel
> /dev/x il se trouve ! (ou alors j'ai un problème hardwa
Bonjour à tous !
Je me demande comment accéder à mon lecteur de CDROM/DVD, à partir
duquel j'aimerais créer une image .iso du disque qu'il contient.
En voyant plusieurs tutos, je n'arrive pas à trouver dans quel
/dev/x il se trouve ! (ou alors j'ai un problème hardware, possible
aussi!)
Y
Hi,
basti wrote:
> I have the same problem, with netinstall iso on usb stick it search for
> cd at hatdware detection step ab abort this with an error.
>
> usb stick is create with unetbootin an test in kvm.
Does the trick of
https://askubuntu.com/questions/671159/bootable-usb-needs-cd-rom
ll boot devices in the BIOS, except the USB drive. It works
>> now.
>
> This is surprising and unplausible even within the usual range of firmware
> madness.
>
> I understand that the "mount CDROM step" is performed by a Linux kernel
> on behalf of software
On Sat 27 Jul 2019 at 18:51:37 +0200, basti wrote:
> usb stick is create with unetbootin an test in kvm.
It's amazing! We have an Installation Guide. Is it read? When it
is read, how many ignore the advice? Even users with experience
of Debian.
--
Brian.
ll boot devices in the BIOS, except the USB drive. It works
>> now.
>
> This is surprising and unplausible even within the usual range of firmware
> madness.
>
> I understand that the "mount CDROM step" is performed by a Linux kernel
> on behalf of software
Hi,
TomK/Brian_S wrote:
> I disabled all boot devices in the BIOS, except the USB drive. It works
> now.
This is surprising and unplausible even within the usual range of firmware
madness.
I understand that the "mount CDROM step" is performed by a Linux kernel
on be
Received from Thomas on Fri, 19 Jul 2019 23:14:06 +0200 Re:
Buster installer on USB searches for CDROM instead of using USB
drive
> I got "The CD-ROM autodetection was successful... The installation
> will now continue."
> ... and so the installation c
On Fri 19 Jul 2019 at 15:29:34 (-0400), TomK wrote:
> In the Debian installer, on the "debian-10.0.0-amd64-DVD-1.iso"
> written to USB flash drive works perfectly, up to the mount CDROM step.
> There is no way to tell the installer to use the USB drive.
>
> Since I be
M
> autodetection was successful... The installation will now continue."
> ... and so the installation continued.
>
> (The other proposals on that page are quite questionable.)
>
+1
>
> If this helps, then i'd bet on a race condition between kernel device
> detection and Debia
tion between kernel device
detection and Debian's search for the filesystem with its favorite
marker file. (That's how mounting "CDROM" is supposed to work. Afaik
it is well aware that "CDROM" can be a /dev/sdX rather than a /dev/srX.)
Have a nice day :)
Thomas
On 2019-07-19 20:29, TomK wrote:
In the Debian installer, on the "debian-10.0.0-amd64-DVD-1.iso"
written to USB flash drive works perfectly, up to the mount CDROM step.
There is no way to tell the installer to use the USB drive.??
Since I began using USB flash media for the installati
In the Debian installer, on the "debian-10.0.0-amd64-DVD-1.iso"
written to USB flash drive works perfectly, up to the mount CDROM step.
There is no way to tell the installer to use the USB drive.
Since I began using USB flash media for the installation disk, I have
always simply down
..
> initrd (loop0)/install.amd/initrd.gz
>
> after pressing 'c' in GRUB
>
> I get the very annoying cdrom-detect program running which prompts me
> to insert a CD. Since this is a ISO install, I want to skip that.
I wonder whether there is such an option. It does not make sen
cdrom-detect program running which prompts me
to insert a CD. Since this is a ISO install, I want to skip that.
Additionally, I am trying to preseed.cfg from
(hd0,3)/files/preseed.cfg and this does not work because /hd-media is
not created or mounted - how do i fix this?
Also, what's the purpose
On seg, 23 jul 2018, Doug wrote:
This may or may not be off topic,
I wouldn't call it completely off-topic, but it's definitely a thread
hijacking. It would have been better to start a new thread.
My friend has just gotten a Korean car--it's either a Hundai or a
Kia, I don't remember,
On 07/22/2018 04:57 PM, Thomas Schmitt wrote:
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 -cd
Bob Bernstein (2018-07-22):
> mplayer [cdda|cddb]://track[-endtrack][:speed][/device] [options]
^
>
> I first tried 'mplayer cdda:///dev/cdrom'
^^
This is not a track.
> The playback is jumpy, or skippy, anythin
On Sun, 22 Jul 2018, Thomas Schmitt wrote:
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
Joy reigns supreme in Mudville!
It has dawned on my somewhat d
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 gues
:
mplayer [cdda|cddb]://track[-endtrack][:speed][/device]
[options]
I first tried 'mplayer cdda:///dev/cdrom' but apparently I did
not grasp the syntax of the suggested "[/device]", above:
--start snip--
Playing cdda:///dev/cdrom.
++ WARN: Can't get file status for dev/cdrom:
No
Thomas Schmitt wrote:
...
> The classic CD-DA ripper is cdda2wav.
i like jack, but it's broken at the moment in
unstable, unfortunately i don't know python well
enough to debug it yet.
so for my temporary hackish project i'm trying
to convert it all to python3 acceptable code, but
i'm not
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
Thomas Schmitt (2018-07-22):
> Your reader program needs to use command READ CD or READ CD MSF.
> mount(8) or dd(1) won't do this. (Also mount(8) would find no filesystem.)
To be accurate, mount only directs the kernel into doing the reads and
looking for filesystems.
There was a kernel patch to
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
Bob Bernstein composed on 2018-07-22 01:37 (UTC-0400):
> /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0
> You can see where, on the last line, I tried monkeying
> with sr0's options. I've left the file now as it was
> installed by jessie, which flavor I am still running,
> albeit
I'll try to provide some useful signs/symptoms of the
particular difficulty. The principal message I get is:
--start snip--
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
Le 31/01/2018 à 11:57, andre_deb...@numericable.fr a écrit :
> Bonjour,
>
> À mon sens, des vieux ordinateurs ne peuvent servir
> que pour des connexions Terminaux / Serveur,
> Ce n'est qu'un déport, les clients légers recevront la puissance
> du serveur, si il le supporte.
>
> Des clients légers
Bonjour,
À mon sens, des vieux ordinateurs ne peuvent servir
que pour des connexions Terminaux / Serveur,
Ce n'est qu'un déport, les clients légers recevront la puissance
du serveur, si il le supporte.
Des clients légers qui ne réclament aucune puissance,
à faible coût, ou de vieux coucous
Le 30/01/2018 à 17:27, err...@free.fr a écrit :
Je peux comprendre qu'en choisissant un ordinosaure tu veuille échapper à
Spectre et Meltdown (mais pas forcement sur le serveur) :D
Les Pentium II sont egalement concernes, le multi-pipelining ayant ete
generalises aux environs du Pentium Pro,
Oui, la consommation + l'encombrement + la poussière...
J'ai remplacé un ancêtre par un jeune "HYSTOU" passif (boitier 20 x20cm,
i3). Bien content.
Avec une minute de silence, un instant de recueillement, puis recyclage
avec dignité dans le bac d'un magasin d'électro-ménager ?
Le 30/01/2018 à
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/30/2018 07:19 PM, Christophe Moille wrote:
> Le mardi 30 janv. 2018 à 17:27:45 (+0100), err...@free.fr a écrit :
>> Bonjour Bernard
>>
>> Je peux comprendre qu'en choisissant un ordinosaure tu veuille échapper à
>> Spectre et Meltdown (mais
Le mardi 30 janv. 2018 à 17:27:45 (+0100), err...@free.fr a écrit :
> Bonjour Bernard
>
> Je peux comprendre qu'en choisissant un ordinosaure tu veuille échapper à
> Spectre et Meltdown (mais pas forcement sur le serveur) :D
>
> mais faire tourner cette machine va te coûter plus cher en
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/30/2018 04:27 PM, Bernard Schoenacker wrote:
> bonjour,
>
> je n'arrive pas à booter sur cdrom avec une image iso
> et j'ai besoin de disquettes contenant un équivalent
> de plop boot usb ...
>
> c'est un P2 avec 400 MH
bonjour,
je n'arrive pas à booter sur cdrom avec une image iso
et j'ai besoin de disquettes contenant un équivalent
de plop boot usb ...
c'est un P2 avec 400 MHz et 256 Mo sdram que je souhaite
faire passer en client léger en mettant x2go client
slt
bernard
> > Does command dmesg report something about "sr0" after this
> > happened ?
> >
> >
> > Have a nice day :)
>
> Do you have a bios selection for the cdrom drive?? Last time this
> happened to me, replacement of the drive fixed the problem. Ric
On Wed, 11 Jan 2017 11:52:30 -0500 Ric Moore sent:
> Do you have a bios selection for the cdrom drive?? Last time this
> happened to me, replacement of the drive fixed the problem. Ric
After contemplation, my reply is:
Thanks Thomas and Ric,
Nothing in dmesg report and I wil
selection for the cdrom drive?? Last time this
happened to me, replacement of the drive fixed the problem. Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome.&qu
Hi,
Charlie wrote:
> mount: /dev/sr0 is write-protected, mounting read-only
> mount: special device /dev/sr0 does not exist
Does command dmesg report something about "sr0" after this happened ?
Have a nice day :)
Thomas
On Wed, 11 Jan 2017 13:09:59 +1100 Charlie sent:
> Hello,
>
> Debian testing 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64
> GNU/Linux
>
> Suddenly have a CDROM problem:
> $ mount /media/cdrom
> mount: /dev/sr0 is write-protected, mounting read-only
>
Hello,
Debian testing 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64
GNU/Linux
Suddenly have a CDROM problem:
$ mount /media/cdrom
mount: /dev/sr0 is write-protected, mounting read-only
mount: special device /dev/sr0 does not exist
Did:
# ls -l /dev/sr0
ls: cannot access
ly sets suitable permission
> > on /dev/sr0.
>
> Anyway I do not think that it helps.
>
> > So the problem is at mount point level. The cdrom is
> > mounted under /media/CDROM, but whatever permission I give to /media the
> > CDROM subdirectory is owned by user 1000 and n
it seems that GROUP and MODE are simply
ignored.
Sorry, I'm wrong again: the above line actually sets suitable permission
on /dev/sr0.
Anyway I do not think that it helps.
So the problem is at mount point level. The cdrom is
mounted under /media/CDROM, but whatever permission I give to /media
On Mon, 2016-12-26 at 22:16 +0100, Nimrod wrote:
> On Mon, 2016-12-26 at 18:29 +0100, Pascal Hambourg wrote:
>
> > Le 26/12/2016 à 17:28, Nimrod a écrit :
> > > On Sat, 2016-12-24 at 05:20 +0100, Michael Biebl wrote:
> > >
> > >> Does it help if
On Mon, 2016-12-26 at 18:29 +0100, Pascal Hambourg wrote:
> Le 26/12/2016 à 17:28, Nimrod a écrit :
> > On Sat, 2016-12-24 at 05:20 +0100, Michael Biebl wrote:
> >
> >> Does it help if you mount the cdrom as shared?
> >> See https://udisks.freedesk
Le 26/12/2016 à 17:28, Nimrod a écrit :
On Sat, 2016-12-24 at 05:20 +0100, Michael Biebl wrote:
Does it help if you mount the cdrom as shared?
See https://udisks.freedesktop.org/docs/latest/udisks.8.html →
UDISKS_FILESYSTEM_SHARED
No, it doesn't. The disk is already mounted in a shared
omputer at home (shared among relatives, each
> > with his/her own account), the first user that logs in after boot locks
> > the cdrom drive, and any other user that logs in can't eject the cdrom:
> > only the first user can eject it.
> >
> > Is there a way to avoid t
at logs in after boot locks
> the cdrom drive, and any other user that logs in can't eject the cdrom:
> only the first user can eject it.
>
> Is there a way to avoid this? Being a home computer there are no privacy
> issues: the cdrom drive is used just for CD ripping or burning, there
; program getfacl to see all permissions.
>
> $ getfacl /dev/sr0
> getfacl: Removing leading '/' from absolute path names
> # file: dev/sr0
> # owner: root
> # group: cdrom
> user::rw-
> user::rw-
> group::rw-
> mask::rw-
> other::---
>
>
te path names
# file: dev/sr0
# owner: root
# group: cdrom
user::rw-
user::rw-
group::rw-
mask::rw-
other::---
I.e. my desktop user explicitely has rw permission independently of his
group memberships.
> > putting them all into group "cdrom".
> They all are alre
On Fri, 2016-12-23 at 20:54 +0100, Pascal Hambourg wrote:
> Le 23/12/2016 à 18:54, Nimrod a écrit :
> >
> > This is the issue: on a computer at home (shared among relatives, each
> > with his/her own account), the first user that logs in after boot locks
> > the cdro
Thanks for your kind answer, below is mine.
On Fri, 2016-12-23 at 20:30 +0100, Thomas Schmitt wrote:
> Hi,
>
> Nimrod wrote:
> > the first user that logs in after boot locks the cdrom
> > drive, and any other user that logs in can't eject the cdrom: only the fir
Le 23/12/2016 à 18:54, Nimrod a écrit :
This is the issue: on a computer at home (shared among relatives, each
with his/her own account), the first user that logs in after boot locks
the cdrom drive, and any other user that logs in can't eject the cdrom:
only the first user can eject it.
I
Hi,
Nimrod wrote:
> the first user that logs in after boot locks the cdrom
> drive, and any other user that logs in can't eject the cdrom: only the first
> user can eject it.
Are you sure that it is the existence of the a user's ACL permission
which prevents the other's from
Hi,
sorry for this trivial question, but I really tried to find an answer on
the web without any result.
This is the issue: on a computer at home (shared among relatives, each
with his/her own account), the first user that logs in after boot locks
the cdrom drive, and any other user that logs
On Sunday 04 October 2015 16:17:24 Richard Owlett wrote:
> Lisi Reisz wrote:
> > On Sunday 04 October 2015 15:41:37 Richard Owlett wrote:
> >> It may address the
> >> one thing I've found most annoying while trying to move to Linux.
> >> Users [*PLURAL*] and Groups [*PLURAL*] may make sense in a
>
Brian wrote:
On Sat 26 Sep 2015 at 17:11:32 -0500, Richard Owlett wrote:
Brian wrote:
I see what you mean.
Try
gsettings set org.mate.media-handling automount false
"apparently" works
*NOTE BENE* the quotation marks
I ran one DVD
am now running a second
Successfully, we expect.
On Sunday 04 October 2015 15:41:37 Richard Owlett wrote:
> It may address the
> one thing I've found most annoying while trying to move to Linux.
> Users [*PLURAL*] and Groups [*PLURAL*] may make sense in a
> universe of mainframes. Not so much in a setting where only one
> individual has access.
Lisi Reisz wrote:
On Sunday 04 October 2015 15:41:37 Richard Owlett wrote:
It may address the
one thing I've found most annoying while trying to move to Linux.
Users [*PLURAL*] and Groups [*PLURAL*] may make sense in a
universe of mainframes. Not so much in a setting where only one
individual
Lisi Reisz wrote:
On Sunday 04 October 2015 16:17:24 Richard Owlett wrote:
Lisi Reisz wrote:
On Sunday 04 October 2015 15:41:37 Richard Owlett wrote:
It may address the
one thing I've found most annoying while trying to move to Linux.
Users [*PLURAL*] and Groups [*PLURAL*] may make sense in a
On Sat 26 Sep 2015 at 17:11:32 -0500, Richard Owlett wrote:
> Brian wrote:
> >
> >I see what you mean.
> >
> >Try
> >
> > gsettings set org.mate.media-handling automount false
> >
>
> "apparently" works
> *NOTE BENE* the quotation marks
> I ran one DVD
> am now running a second
Successfully,
Brian wrote:
On Sat 26 Sep 2015 at 09:13:27 -0500, Richard Owlett wrote:
I'm trying to troubleshoot a problem.
That Jessie (and IIRC Squeeze) automatically mount the cdrom drive every
time the drawer is closed is a nuisance requiring to manually run umount
before I can proceed.
/etc/fstab has
...
>>> Jessie ... automatically mounts the cdrom drive
>>> every time the drawer is closed is a nuisance requiring to manually
>>> run umount before I can proceed.
I have a similar experience when plugging in an external USB drive. I
wish to mount each of several d
On Sat 26 Sep 2015 at 09:13:27 -0500, Richard Owlett wrote:
> I'm trying to troubleshoot a problem.
> That Jessie (and IIRC Squeeze) automatically mount the cdrom drive every
> time the drawer is closed is a nuisance requiring to manually run umount
> before I can proceed.
>
&
1 - 100 of 3410 matches
Mail list logo
