Mount removable media when inserted
> >
> > A USB stick is a removable drive. A DVD is removable media.
> >
> So I guess my Kobo is 'removable media' because it used to automount
> itself in /media/chris.
Oh, no. That's another category. Dan is correct, bu
ust in settings. While I'm here what's the difference
> > between:-
> >
> > Mount removable drives when hot-plugged
> > and:-
> > Mount removable media when inserted
>
> A USB stick is a removable drive. A DVD is removable media.
>
So I gues
Chris Green wrote:
> Dan Ritter wrote:
> Typical! I'm sure I tried that yesterday, but anyway it mounts
> manually perfectly OK now. So all I'm missing is the automatic
> mounting.
>
> ... and that's just in settings. While I'm here what's the difference
> between:-
>
> Mount removable d
Dan Ritter wrote:
> Chris Green wrote:
> > I have a Kobo Forma reader (like a Kindle), on xubuntu versions up to
> > 24.04 it automounted without problems. Now I'm running Debian 12 it's
> > failing to automount, I can't mount it manually either.
> >
Chris Green wrote:
> I have a Kobo Forma reader (like a Kindle), on xubuntu versions up to
> 24.04 it automounted without problems. Now I'm running Debian 12 it's
> failing to automount, I can't mount it manually either.
>
> I get the usual messages at the Kobo e
I have a Kobo Forma reader (like a Kindle), on xubuntu versions up to
24.04 it automounted without problems. Now I'm running Debian 12 it's
failing to automount, I can't mount it manually either.
I get the usual messages at the Kobo end and fdisk shows me /dev/sdc
but no file syst
On Wed 14 Sep 2022 at 10:34:23 (+0200), Jürgen Bausa wrote:
> > Gesendet: Dienstag, 13. September 2022 um 20:13 Uhr
> > Von: "David Wright"
> >
> > I don't remember the details of the complaint, but there are
> > circumstances where systemd kills off jobs that it is controlling.
> >
> > You coul
Hi David,
if I understood you correctly you propose to run a script in the background to
check for
the condition I am interested in (is the nfs server available?) and do the
changes accordingly.
In fact I am doing this at the moment. But I think its an ugly hack and thought
a better solution
s
On Mon 12 Sep 2022 at 09:31:07 (+0200), Jürgen Bausa wrote:
> I am using systemd automount units (see below) to mount network shares on my
> laptop
> (debian bullseye). This works fine in principle but I have one big issue:
>
> At home it is enough to set TimeoutSec to 2 s in
OT from time to time!
> >
>
> I already asked at systemd-devel, but got no answer. Is there another
> systemd mailing list?
The question that was asked in this thread seems on-topic to me. It was
about setting up systemd automount file systems on Debian. That's abo
> Gesendet: Montag, 12. September 2022 um 21:06 Uhr
> Von: "Darac Marjal"
> An: debian-user@lists.debian.org
> Betreff: Re: systemd automount unit: run only when server is reachable
>
> systemd has a number of Condition* rules which can be added to units:
> https
> Gesendet: Dienstag, 13. September 2022 um 08:17 Uhr
> Von: "john doe"
>
> I would say the Systemd mailing list but this list is awsome and I'm
> also guilty of being OT from time to time!
>
I already asked at systemd-devel, but got no answer. Is there another
systemd mailing list?
Jürgen
On 9/12/2022 7:05 PM, Joe wrote:
On Mon, 12 Sep 2022 09:31:07 +0200
Jürgen Bausa wrote:
>> I am sure this is not the
best place to ask it (I know, its off-topic), But posting to other
lists I didnt get an answer. So if you know a better place to ask it
please point me there.
I would say the
on its usage. I am sure this is not the best place to ask it (I know,
its off-topic),
But posting to other lists I didnt get an answer. So if you know a better place
to ask it please
point me there.
I am using systemd automount units (see below) to mount network shares on my
laptop
(debian bulls
Hi Joe,
> Gesendet: Montag, 12. September 2022 um 19:05 Uhr
> Von: "Joe"
> An: debian-user@lists.debian.org
> Betreff: Re: systemd automount unit: run only when server is reachable
>
>
> I have a number of shares (samba rather than nfs) listed in /etc
et an answer. So if you know a better place to ask it
> please point me there.
>
> I am using systemd automount units (see below) to mount network
> shares on my laptop (debian bullseye). This works fine in principle
> but I have one big issue:
>
> At home it is enough to set Ti
.
I am using systemd automount units (see below) to mount network shares on my
laptop
(debian bullseye). This works fine in principle but I have one big issue:
At home it is enough to set TimeoutSec to 2 s in the mount unit. Normally the
server is
available and the share is mounted. If the
Hi,
I'm providing more information and answering my own question (for my
laptop's installation).
On Mar/03/2022, David Wright wrote:
> On Thu 03 Mar 2022 at 10:00:09 (+0100), Carles Pina i Estany wrote:
> >
> > My desktop computer (Debian 11.2) auto-mounts USB devices (hard disks,
> > etc.)
>
On Thu 03 Mar 2022 at 10:00:09 (+0100), Carles Pina i Estany wrote:
>
> My desktop computer (Debian 11.2) auto-mounts USB devices (hard disks,
> etc.)
That doesn't help a great deal because there are several automounters
available in Debian.
> I would like the devices to be mounted in read only
with having udisks on the system or
> remounting a disk rw, or even how it fits your objectives.
For the remounting I'm not worried.
My use case is that I have about 10 or 15 hard disks that I want to
automount in ro because... I only need to read from them and I want to
avoid making acc
On Thu 03 Mar 2022 at 10:00:09 +0100, Carles Pina i Estany wrote:
>
> Hi,
>
> My desktop computer (Debian 11.2) auto-mounts USB devices (hard disks,
> etc.)
>
> I would like the devices to be mounted in read only mode by default. I
> will remount them in rw if I need to.
>
> They are not in my
Hi,
My desktop computer (Debian 11.2) auto-mounts USB devices (hard disks,
etc.)
I would like the devices to be mounted in read only mode by default. I
will remount them in rw if I need to.
They are not in my /etc/fstab
I've been looking at udev configuration files, rules, etc. but I'm
unsure
On 8/17/2021 4:28 PM, Erwan David wrote:
Hello,
I have some CIFS shares automounted through automount units. If I am
not connected to the right network, mounting fails, and I am OK with
that. However after too many failures the unit is disabled, and thus
does not work when I connect again. I
Hello,
I have some CIFS shares automounted through automount units. If I am
not connected to the right network, mounting fails, and I am OK with
that. However after too many failures the unit is disabled, and thus
does not work when I connect again. I did not find how to say to
systemd "I d
On Thu, May 17, 2018 at 11:36:01AM +0100, Darac Marjal wrote:
> However, before you go doing that, consider that systemd ALSO comes with a
> program called "systemd-fstab-generator". Contrary to its name, this
> generates unit files FROM an fstab (rather than generating an fstab).
> Therefore, fol
ome or at least /[users] on the microSD
card. this of course requires mounting it at boot. > > i've been much of a week searching and i cannot find any way to
configure this to automount in systemd. i do not even know if under systemd it must be mounted to a mountpoint or if it's hand
se requires mounting it at boot. > > i've been much of a week searching and i cannot find any way to
configure this to automount in systemd. i do not even know if under systemd it must be mounted to a mountpoint or if it's handled
at the /dev level. so what was once a trivial configur
ard. this of course requires
> mounting it at boot. > > i've been much of a week searching and i cannot find
> any way to configure this to automount in systemd. i do not even know if
> under systemd it must be mounted to a mountpoint or if it's handled at the
> /dev lev
a 128gb microSD card formatted ext4. to reduce write wear on the device's
internal memory, it's my hope to put /home or at least /[users] on the microSD
card. this of course requires mounting it at boot.
i've been much of a week searching and i cannot find any way to configure this
On May 16, 2018 2:35 PM, Joe wrote:
> Not what you want, but related, possibly it will help to make sense
>
> of other documentation. I have network drives set to automount on first
>
> use. Here is a typical /etc/fstab line:
>
> ///Media /mnt//Media cifs
>
> noau
>
> i've been much of a week searching and i cannot find any way to
> configure this to automount in systemd. i do not even know if under
> systemd it must be mounted to a mountpoint or if it's handled at
> the /dev level. so what was once a trivial configuration ha
4. to reduce write wear on the device's
internal memory, it's my hope to put /home or at least /[users] on the microSD
card. this of course requires mounting it at boot.
i've been much of a week searching and i cannot find any way to configure this
to automount in systemd. i do not
x27;ve looked at automount(8), autofs(5), autofs(8), autofs.conf(5),
auto.master(5), mount(8). autofs_ldap_auth.conf(5), several tutorials
without becoming wiser ;<
[The most readable tutorial was written 14 years ago and the relevant
Debian Wiki page starts by saying "NB This informa
Hi,
David Christensen wrote:
> Could you please describe how you mount/unmount devices and file systems
> "the old way"?
I become superuser and execute commands like
mount /dev/sr0 /mnt/iso
mount -o loop /mnt/iso/boot/grub/efi.img /mnt/fat
mount /dev/sdc2 /mnt/fat2
umount /mnt/fat
umoun
On 03/11/2017 11:59 PM, Thomas Schmitt wrote:
I am very happy that i disabled automounting on my system. Life becomes
so clear and straightforward if one does it the old way.
I use Jesse and Xfce:
2017-03-12 12:42:20 dpchrist@jesse ~
$ cat /etc/debian_version; uname -a
8.7
Linux jesse 3.16.0-4
s parameter is completely
>>> ignored and the device never unmounted.
>>>
>>> Is it a bug, or what did i miss to get it working?
>>
>> Are you sure nothing is keeping that FS busy?
>
> yes, I'm quite sure. The device is empty, lsof shows no open handl
re you sure nothing is keeping that FS busy?
yes, I'm quite sure. The device is empty, lsof shows no open handle, and the
only access to the filesystem was 'ls -al ' to trigger the
automount and to list its content.
I've installed systemd from the debian-backports repository, because the
current stable version for jessie doesn't offer this functionality. Could it
be a compatibility issue?
regards,
andy
--
signature.asc
Description: OpenPGP digital signature
Am 08.12.2016 um 13:33 schrieb Andreas Born:
> Hi all,
> I need a device to be automatically mounted on access and unmounted when being
> idle. My /etc/fstab entry:
>
> /dev/sdc1 /mnt/auto ext4 defaults,noauto,x-systemd.automount,\
> x-systemd.idle-timeout=10 0 0
>
> Systemd correctly crea
Hi all,
I need a device to be automatically mounted on access and unmounted when being
idle. My /etc/fstab entry:
/dev/sdc1 /mnt/auto ext4 defaults,noauto,x-systemd.automount,\
x-systemd.idle-timeout=10 0 0
Systemd correctly creates the mnt-auto.mount und mnt-auto.automount unit files
and
looking at the currently available distributed file systems, for
example glusterFS, but they are very heavyweight because they are for
heavyweight systems.
I'm almost wondering if I can set-up some scripts under automount and simply
rsync to maintain sync.
Brian
On Fri, 17 Jun 2016, bri...@aracnet.com wrote:
I have my nfs shares set-up to automount to
/home/nfs4/
and then that directory name is used in the /etc/passwd file.
What i'd like to do is have it use /home/ in the event it
can't see the nfs server.
it seems like some automoun
I have my nfs shares set-up to automount to
/home/nfs4/
and then that directory name is used in the /etc/passwd file.
What i'd like to do is have it use /home/ in the event it can't see
the nfs server.
it seems like some automount trickery might be possible if, for example, nfs
mo
my small contribution for a similar issue:
http://ddumont.wordpress.com/2016/04/24/automount-usb-devices-with-systemd/
Let's hope we'll see more on the subject to help people understand systemd.
All the best
--
https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/
http://ddum
Michael Biebl wrote:
> Am 01.05.2015 um 11:01 schrieb Takahide Nojima:
> >* Another debian box automounts under /media/usb0,and
> > only root user's permission(owner root) are given to /media/usb0
> >
> > I'm looking up settings/documentations,but I haven't
> > gotten any idea,yet.
>
Am 01.05.2015 um 11:01 schrieb Takahide Nojima:
>* Another debian box automounts under /media/usb0,and
> only root user's permission(owner root) are given to /media/usb0
>
> I'm looking up settings/documentations,but I haven't
> gotten any idea,yet.
Can you post your /etc/fstab? I su
Hello,
I use 2 debian sid box. Both box are running Gnome3. There is a
different action about automounting usb stick to both machine.
Its difference is:
* One debian box automounts usb stick under /media/username/, and
also username's permissions(owner username,write permittive) are
Hi.
On Thu, Sep 04, 2014 at 02:20:52AM -0400, PaulNM wrote:
> Hi folks,
>
> I seem to remember hearing about a way to enable/disable the system
> mounting /boot whenever a package needs to install or read files from
> it, then unmount it again afterwards. (Like during kernel upgrades, for
Hi folks,
I seem to remember hearing about a way to enable/disable the system
mounting /boot whenever a package needs to install or read files from
it, then unmount it again afterwards. (Like during kernel upgrades, for
example.)
I can't seem to find out how to do this, any pointe
On Tue, 16 Jul 2013, tony mollica wrote:
> Thanks,
>
> I've looked through /lib/udev/rules.d but I will check again more
> carefully.
>
> I think the key to this is that the first automount uses ehci-hcd
> while the second automount shows ohci_hcd . I'm at a los
Thanks,
I've looked through /lib/udev/rules.d but I will check again more carefully.
I think the key to this is that the first automount uses ehci-hcd while the
second automount shows ohci_hcd . I'm at a loss to figure out what,
exactly, controls this.
tm
On 07/16/2013 08:02 A
On Tue, Jul 16, 2013 at 1:26 PM, tony mollica wrote:
> Any other locations used to store udev rules?
you may try to look in /lib/udev/rules.d/ directory
best regards,
marco
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact li
the drive is disconnected and then remounted
using ohci_hcd. There seems to be two separate auto mounting
daemons or programs running to do the automount. A regular USB
disk drive does not behave like this, only memory cards and sticks.
I'm at a loss to find the culprit. Any suggestions?
Soun
en
> needs to removed/unmounted a second time.
>
> dmesg shows the mounted drive to beusing ehci_hcd. After the
> 'safely remove drive', the drive is disconnected and then remounted
> using ohci_hcd. There seems to be two separate auto mounting
> daemons or programs runn
hcd. After the
'safely remove drive', the drive is disconnected and then remounted
using ohci_hcd. There seems to be two separate auto mounting
daemons or programs running to do the automount. A regular USB
disk drive does not behave like this, only memory cards and sticks.
I'm at
On 10.12.2012 00:09, Roger Leigh wrote:
> On Sun, Dec 09, 2012 at 02:43:36PM -0700, Bob Proulx wrote:
>> Ross Boylan wrote:
>>> Bob Proulx wrote:
This nfs startup part is a part that seems to have suffered from the
transition from boot time scripts to event driven scripts. This kind
On Vi, 14 dec 12, 22:23:21, Bob Proulx wrote:
>
> > Some things which need addressing:
> > - use of tmpfses for non-writable locations like /media: we should
> > be doing this by default; introducing /run/media on the /run
> > tmpfs was one thing looked at for wheezy; but it didn't get done
>
Roger Leigh wrote:
> This is an area which could use quite a bit of work. Unfortunately,
> as you point out there isn't a single place to fix things--it
> touches a whole host of packages, from the initramfs to the
> initscripts, to udev and networking.
It does touch many things. The configurati
On Sun, Dec 09, 2012 at 02:43:36PM -0700, Bob Proulx wrote:
> Ross Boylan wrote:
> > Bob Proulx wrote:
> > > This nfs startup part is a part that seems to have suffered from the
> > > transition from boot time scripts to event driven scripts. This kind
> > > of thing use to work in the previous in
Wolfgang Karall wrote:
> On 12/11/2012 11:08 AM, Chris Davies wrote:
>> Bob Proulx wrote:
>>> The dhcpd will ping the address after the lease has expired and before
>>> assigning it again and will notice that it is still in use and will
>>> avoid assigning that address to another client.
>>
>> I
On 12/11/2012 11:08 AM, Chris Davies wrote:
> Bob Proulx wrote:
>> The dhcpd will ping the address after the lease has expired and before
>> assigning it again and will notice that it is still in use and will
>> avoid assigning that address to another client.
>
> ICMP ping? Are you sure?
I suppo
Bob Proulx wrote:
> The dhcpd will ping the address after the lease has expired and before
> assigning it again and will notice that it is still in use and will
> avoid assigning that address to another client.
ICMP ping? Are you sure?
According to the documents I've read (RFC2131 amongst others
Ross Boylan wrote:
> Bob Proulx wrote:
> > This nfs startup part is a part that seems to have suffered from the
> > transition from boot time scripts to event driven scripts. This kind
> > of thing use to work in the previous init script way. I don't know
> > the best design to make this work in
On Sun, 2012-12-09 at 14:11 -0700, Bob Proulx wrote:
>
> http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_basic_network_configuration_with_ifupdown_legacy
>
> P.P.S. Unanswered Question: Since the PXE boot used dhcp to obtain an
> address that means there is a limited lease t
Bob Proulx wrote:
> Ross Boylan wrote:
> > I have a theory that the mounts are supposed to happen when the network
> > device comes up; the regular network up routines are not triggered to
> > avoid screwing up the root fs. /etc/network/interfaces has
> >
> > # The primary network interface
> > #
The solution is to run
mount -a -t nfs
in /etc/rc.local.
Depending on your aesthetics, this might be considered a work-around.
More details below.
On Sun, 2012-12-09 at 01:19 -0700, Bob Proulx wrote:
> Ross Boylan wrote:
> > I have a theory that the mounts are supposed to happen when the network
Bob Proulx wrote:
> I don't think using dhcp is correct because the network is already up
> and assigned. But perhaps it is because that would allow the system
> to migrate to a different address after the lease expires. I don't
> know. I didn't do any testing of that configuration. (Maybe late
Ross Boylan wrote:
> I have a theory that the mounts are supposed to happen when the network
> device comes up; the regular network up routines are not triggered to
> avoid screwing up the root fs. /etc/network/interfaces has
>
> # The primary network interface
> # do not bring up interface twice
kground. Not what you want long term but perhaps a
good debug point.
> Can anyone suggest why the NFS automount is not working, or what to do
> about it?
>
> I have a theory that the mounts are supposed to happen when the network
> device comes up; the regular network up routines a
On Sat, Dec 08, 2012 at 02:09:47PM -0800, Ross Boylan wrote:
> I have a diskless workstation running testing, and although
> its /etc/fstab is
> /dev/nfs / nfs defaults 0 0
> none /tmptmpfs defaults 0 0
> none /var/runtmpfs defaults 0 0
>
but the other 2 NFS filesystems are not. I can mount
> them manually once the system is up.
>
> Can anyone suggest why the NFS automount is not working, or what to do
> about it?
Use the _netdev option [1] or autofs [2].
Cheers,
Michael
[1] man mount
[2] http://linux.die.net/man/5/auto
gets to fstab), but the other 2 NFS filesystems are not. I can mount
them manually once the system is up.
Can anyone suggest why the NFS automount is not working, or what to do
about it?
I have a theory that the mounts are supposed to happen when the network
device comes up; the regular network up
On Mon, Oct 29, 2012 at 02:40:28PM -0400, Len Berman wrote:
> I am running Debian stable (Linux foobar 3.2.0-0.bpo.3-amd64 #1 SMP Thu
> Aug 23 07:41:30 UTC 2012 x86_64 GNU/Linux).
>
> If rhythmbox is up when I plug in my digital camera, rhythmbox grabs it
> as a 'removable device' and I cannot
I am running Debian stable (Linux foobar 3.2.0-0.bpo.3-amd64 #1 SMP Thu
Aug 23 07:41:30 UTC 2012 x86_64 GNU/Linux).
If rhythmbox is up when I plug in my digital camera, rhythmbox grabs it
as a 'removable device' and I cannot get photos from the camera. (Apps
like gthumb or gphotofs fail.) Onc
On Tue, 03 Apr 2012 11:53:13 +0200, Alberto Fuentes wrote:
> On 02/04/12 19:31, Camaleón wrote:
>> That's what usually happens when "syncing" or "mirroring", each of the
>> copies are keep the same but I think this can be customized, at least
>> in Unison. Or maybe you need a backup/archive utilit
On 02/04/12 19:31, Camaleón wrote:
That's what usually happens when "syncing" or "mirroring", each of the
copies are keep the same but I think this can be customized, at least in
Unison. Or maybe you need a backup/archive utility more than just a mere
syncing approach.
Im still building my solu
On Mon, 02 Apr 2012 18:30:16 +0200, Alberto Fuentes wrote:
> On 02/04/12 17:04, Camaleón wrote:
(...)
>>> also, if you know of some tool that is already able to perform all
>>> these tasks, it would save me some troble :)
>>
>> Rsync? Unison? Self-made script?
>
> I was thinking about using rsy
details of the
backup attempt.
The only part im not sure is how to automount the disk and launch the
script
I bet you can use/write an udev rule to launch a script/program to be run
when the automounter detects the device insertion.
nice, udev rules is certainly what i was looking for :)
also, if
ckup attempt.
>
> The only part im not sure is how to automount the disk and launch the
> script
I bet you can use/write an udev rule to launch a script/program to be run
when the automounter detects the device insertion.
> also, if you know of some tool that is already able to perfo
Im planning to have an external usb disk that i can plug to all my
computers, and without interaction, sync all data i want with the disks.
Also, umount at the end and send me and email with the details of the
backup attempt.
The only part im not sure is how to automount the disk and launch
t; > to
> > >> > connect to my computer like cameras, phones and a USB drive so I
> > >> > thought
> > >> > it might be time to look into getting automount working. What's the
> > >> > easiest way to do this without running Gnome (or
).
> >> > I haven't had many devices to connect to my computer so I have mounted
> >> > as needed. Over the last couple of years I've gathered devices I like to
> >> > connect to my computer like cameras, phones and a USB drive so I thought
> >&g
ted
>> > as needed. Over the last couple of years I've gathered devices I like to
>> > connect to my computer like cameras, phones and a USB drive so I thought
>> > it might be time to look into getting automount working. What's the
>> > easiest way to d
years I've gathered devices I like to
> > connect to my computer like cameras, phones and a USB drive so I thought
> > it might be time to look into getting automount working. What's the
> > easiest way to do this without running Gnome (or KDE)?
> >
> > I&
er like cameras, phones and a USB drive so I thought
> it might be time to look into getting automount working. What's the
> easiest way to do this without running Gnome (or KDE)?
>
> I'm running Sid
I have installed usbmount that automatically mount and unmount USB mas
so I thought
it might be time to look into getting automount working. What's the
easiest way to do this without running Gnome (or KDE)?
I'm running Sid
--
//Christian Dysthe
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscr
Mike Castle wrote:
> Did some more testing. All of the problems seems to be client side.
I don't have any additional information to add. The latest of my NFS
clients are Squeeze. But I did want to say thank you for posting your
problem and findings. Just so that there was some response for you
Did some more testing. All of the problems seems to be client side.
Dropping back to 2.6.32, both automounts and the flock $0 script work over NFS.
But did discover something interesting.
After a fresh boot, the follow both work with 2.6.32:
$ ls /share/images
$ ls /share/images/
With 2.6.39,
me other issue. Any suggestions on what kind of
debugging to turn on would be helpful as well.
The effect I'm seeing is: Immediately after boot, a normal user can
access any NFS directory causing it to automount. After some amount
of time though, after the mount is automatically unmounted,
lates to the automounter at all.
>
it's deja vu all over again :-)
this was the issue last time, I was using "user", and since automount,
i.e. the system was mounting the filesystem I could not umount. So I
changed the keyword to users and everything was working fine, until
now.
> The option specified by mount(8)'s manpage is "user", not "users". I
> don't recall if that relates to the automounter at all.
Your statement regarding user vs users is correct.
It doesn't affect the automounter however, as I don't have an fstab
line regarding my external drives - this may be t
On 11 March 2011 06:32, wrote:
> Howdy,
>
> Here's the option line from the auto.media file:
>
> /media/thingy -fstype=vfat,users,flush,rw,umask= :/dev/ipod
>
> I could have sworn this was working...
>
> I posted a while back and found out that the "users" option had to be in
> there.
The
Brian,
I am experiencing the same issue with external EXT formatted drives
with the automounter (in Gnome). They mount just fine, but I must
become root to umount them.
If you find a solution, please share it with the mailing list ;)
Best of luck,
George
--
To UNSUBSCRIBE, email to debian-us
On Fri, 11 Mar 2011 08:17:47 +0100
Klistvud wrote:
> Dne, 11. 03. 2011 07:32:31 je bri...@aracnet.com napisal(a):
> > Howdy,
> >
> > Here's the option line from the auto.media file:
> >
> > /media/thingy
> > -fstype=vfat,users,flush,rw,umask= :/dev/ipod
> >
> > I could have sworn this
Dne, 11. 03. 2011 07:32:31 je bri...@aracnet.com napisal(a):
Howdy,
Here's the option line from the auto.media file:
/media/thingy -fstype=vfat,users,flush,rw,umask= :/dev/ipod
I could have sworn this was working...
I posted a while back and found out that the "users" option had to be
Howdy,
Here's the option line from the auto.media file:
/media/thingy -fstype=vfat,users,flush,rw,umask= :/dev/ipod
I could have sworn this was working...
I posted a while back and found out that the "users" option had to be in
there.
Now I get this :
umount: /media/thingy is not in
On Wed, 05 Jan 2011 23:25:35 +0100, Filipe Freire wrote:
> On 5 January 2011 21:21, Camaleón wrote:
>
>> > sound-juicer -d /dev/sr0
>> >
>> > but it tells me I have no permission. I tried again with sudo and it
>> > works. When I press play, it plays but gives the message:
>> >
>> > Cannot conn
On 5 January 2011 21:21, Camaleón wrote:
> On Wed, 05 Jan 2011 19:24:01 +0100, Filipe Freire wrote:
>
> > On 3 January 2011 19:07, Camaleón wrote:
> >
> >> > besides this audio cd are not detected ay least by sound-juicer and
> >> > totem. tried all audio devices.
> >>
> >> I'm also facing this p
On Wed, 05 Jan 2011 19:24:01 +0100, Filipe Freire wrote:
> On 3 January 2011 19:07, Camaleón wrote:
>
>> > besides this audio cd are not detected ay least by sound-juicer and
>> > totem. tried all audio devices.
>>
>> I'm also facing this problem:
>>
>> sound-juicer: doesn't find any CD drives, e
Hi,
I looked at the bug report and tried (my drive is ATAPI)
sound-juicer -d /dev/sr0
but it tells me I have no permission. I tried again with sudo and
it works. When I press play, it plays but gives the message:
Cannot connect to server socket err = No such file or directory
Cannot connect t
On Sun, 02 Jan 2011 22:17:56 +0100, Filipe Freire wrote:
> automounting is not working since my upgrade to squeeze. the loader is
> now grub2.
>
> I can mount usb and, dvd's and data cd's only manually from the command
> line. /etc/fstab and nautilus options are as they should be. Only for
> dv
1 - 100 of 289 matches
Mail list logo
