I am having a poblem accessing partitions. I use dosemu to access three fat32 partitions: dosc, dosd, and dose. They point to /media/dosc, ... My fstab follows: /dev/hda3 / reiserfs acl,user_xattr 1 1 /dev/hda5 /home reiserfs acl,user_xattr 1 2 /dev/hda1 /media/dosc vfat auto,rw,users,exec 0 0 /dev/hda8 /media/dose vfat auto,rw,users,exec 0 0 /dev/hda9 /media/extra reiserfs user,acl,user_xattr 1 2 /dev/hda2 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/dvdrecorder /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid, nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid ,nodev,nosuid,sync 0 0 When I created the partitions, the mount points for the dos partitions had a user or root and a group of root, as indicated below. I changed these to john users, but it seems that it has changed back, on its own. I am now unable to write to these partitions. What are the two bottom entries of the /media for? What does user_xattr mean and why is it needed? Why is acl needed? I read about these in the Suse doc, and the Yast partition edit screen, but they do not say whay they are used. drwxr-xr-x 6 root root 4096 1969-12-31 16:00 dosc drwxr-xr-x 2 root root 4096 1969-12-31 16:00 dosd drwxr-xr-x 9 root root 4096 1969-12-31 16:00 dose drwxr-xr-x 6 john users 720 2005-06-23 00:20 dosx drwxr-xr-x 2 root root 48 2005-06-16 00:02 dvdrecorder drwxr-xr-x 4 root root 80 2005-06-16 00:02 extra drwxrwxrwx 1 root root 0 2005-06-26 21:10 floppy drwxr-xr-x 2 root root 48 2005-06-16 13:07 MAXTOR__40G drwxr-xr-x 4 root root 80 2005-06-16 00:02 secure drwxr-xr-x 3 john users 184 2005-06-16 15:19 securex drwxr-xr-x 2 root root 48 2005-06-18 17:15 SU930_001 drwxr-xr-x 2 root root 48 2005-06-19 16:52 SU930_001_1 Thoughts? John
John R. Sowden a écrit :
I am having a poblem accessing partitions. I use dosemu to access three fat32 partitions: dosc, dosd, and dose. They point to /media/dosc, ... My fstab follows:
/dev/hda3 / reiserfs acl,user_xattr 1 1 /dev/hda5 /home reiserfs acl,user_xattr 1 2 /dev/hda1 /media/dosc vfat auto,rw,users,exec 0 0 /dev/hda8 /media/dose vfat auto,rw,users,exec 0 0 /dev/hda9 /media/extra reiserfs user,acl,user_xattr 1 2 /dev/hda2 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/dvdrecorder /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid, nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid ,nodev,nosuid,sync 0 0
When I created the partitions, the mount points for the dos partitions had a user or root and a group of root, as indicated below. I changed these to john users, but it seems that it has changed back, on its own. I am now unable to write to these partitions.
What are the two bottom entries of the /media for? What does user_xattr mean and why is it needed? Why is acl needed?
I read about these in the Suse doc, and the Yast partition edit screen, but they do not say whay they are used.
drwxr-xr-x 6 root root 4096 1969-12-31 16:00 dosc drwxr-xr-x 2 root root 4096 1969-12-31 16:00 dosd drwxr-xr-x 9 root root 4096 1969-12-31 16:00 dose drwxr-xr-x 6 john users 720 2005-06-23 00:20 dosx drwxr-xr-x 2 root root 48 2005-06-16 00:02 dvdrecorder drwxr-xr-x 4 root root 80 2005-06-16 00:02 extra drwxrwxrwx 1 root root 0 2005-06-26 21:10 floppy drwxr-xr-x 2 root root 48 2005-06-16 13:07 MAXTOR__40G drwxr-xr-x 4 root root 80 2005-06-16 00:02 secure drwxr-xr-x 3 john users 184 2005-06-16 15:19 securex drwxr-xr-x 2 root root 48 2005-06-18 17:15 SU930_001 drwxr-xr-x 2 root root 48 2005-06-19 16:52 SU930_001_1
Thoughts? John
Hello, man fstab and you'll see that if you add : umask=000 as an option, you'll be able to write to your partitions. /dev/hda1 /media/dosc vfat auto,rw,users,exec,umask=000 0 0 /dev/hda8 /media/dose vfat auto,rw,users,exec,umask=000 0 0 Michel.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2005-06-27 at 00:03 -0700, John R. Sowden wrote:
When I created the partitions, the mount points for the dos partitions had a user or root and a group of root, as indicated below. I changed these to john users, but it seems that it has changed back, on its own. I am now unable to write to these partitions.
The permissions are controlled by the fstab file. root:root is normal.
What are the two bottom entries of the /media for?
It is dificult to understand your question, your email is a bit dissorganized.
What does user_xattr mean and why is it needed?
user extended atributes, I think.
Why is acl needed?
access control lists.
drwxrwxrwx 1 root root 0 2005-06-26 21:10 floppy drwxr-xr-x 2 root root 48 2005-06-16 13:07 MAXTOR__40G drwxr-xr-x 4 root root 80 2005-06-16 00:02 secure drwxr-xr-x 3 john users 184 2005-06-16 15:19 securex drwxr-xr-x 2 root root 48 2005-06-18 17:15 SU930_001 drwxr-xr-x 2 root root 48 2005-06-19 16:52 SU930_001_1
Thoughts?
My crystall ball says that the above paragraph is your /media directory, and that your previous question refered to the last two lines. Well, that's the new system of automounting cdroms: the mount point is given the name of the volume label, automatically, but they are not deleted on disk change. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCv+91tTMYHG2NR9URAjIsAJ9r7D5KdZhsJGOLr1m0Ml2Go+44kgCeISfI E2imdsR6apXe2Lok1dON9Hs= =0ebd -----END PGP SIGNATURE-----
John R. Sowden wrote: <STUFF DELETED>
What are the two bottom entries of the /media for? What does user_xattr mean and why is it needed? Why is acl needed?
Have a look at the man pages for acl, setfacl and getfacl to see what you can do to restrict access to files and directories. You need acl enabled so you can lock out or restrict user access, great in a company environment and one of the security features Solaris used to boast Linux didn't have. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Hi, On Mon, 27 Jun 2005 00:03:17 -0700 "John R. Sowden" <.> wrote:
I am having a poblem accessing partitions. I use dosemu to access three fat32 partitions: dosc, dosd, and dose. They point to /media/dosc, ... My fstab follows:
/dev/hda3 / reiserfs acl,user_xattr 1 1 /dev/hda5 /home reiserfs acl,user_xattr 1 2 /dev/hda1 /media/dosc vfat auto,rw,users,exec 0 0 /dev/hda8 /media/dose vfat auto,rw,users,exec 0 0 /dev/hda9 /media/extra reiserfs user,acl,user_xattr 1 2 /dev/hda2 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/dvdrecorder /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid, nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid ,nodev,nosuid,sync 0 0
Maybe one of your 'poblems' is, that dosd doesn't point anywhere, concerning the fstab file you just c&p-ed here :( Pelibali
Hi,
On Mon, 27 Jun 2005 00:03:17 -0700
"John R. Sowden" <.> wrote:
I am having a poblem accessing partitions. I use dosemu to access three fat32 partitions: dosc, dosd, and dose. They point to /media/dosc, ... My fstab follows:
/dev/hda3 / reiserfs acl,user_xattr 1 1 /dev/hda5 /home reiserfs acl,user_xattr 1 2 /dev/hda1 /media/dosc vfat auto,rw,users,exec 0 0 /dev/hda8 /media/dose vfat auto,rw,users,exec 0 0 /dev/hda9 /media/extra reiserfs user,acl,user_xattr 1 2 /dev/hda2 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/dvdrecorder /media/dvdrecorder subfs noauto,fs=cdfss,ro,procuid, nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid ,nodev,nosuid,sync 0 0
Maybe one of your 'poblems' is, that dosd doesn't point anywhere, concerning the fstab file you just c&p-ed here :(
Pelibali Two of the partitions (a reiser fs and the dosd fat32 file system are handled by cryptotab, as they are encrypted. Adding umask=000 to the dosc and dose
On Monday 27 June 2005 15:16, pelibali wrote: partitions did not help. -- John R. Sowden AMERICAN SENTRY SYSTEMS, INC. Residential & Commercial Alarm Service UL Listed Central Station Serving the San Francisco Bay Area Since 1967 mail@americansentry.net www.americansentry.net
Hi everybody I've spent the whole day trying to install the 9.3 on a Dell Precision 370 (with a NVidia graphics card). The problem is the following : I can boot on the dvd and the install software do the 2 phases of the installation (partionning the system and installing the base, doing the first boot and finalizing the installation). When the installation is finished (basically I've installed a KDE complete system, accepting all the default + ssh) I've rebooted the system. The beginning of the boot seems to be ok and the differents settings are all marked "done". When the system try to start the kdm, it displays a clock during some seconds and then only the mouse pointer on a black screen and nothing else happen. Even the keyboard does not let me to do anything (like a ctrl-alt-f1 to have an terminal for example). I can access the machine through ssh and I don't see anything wrong. But something is wrong because an "init 3" through ssh session does not have any action. I know that my description of the problem is not precise enough to receive a solution, but if you can give me an hint for the direction where I should look... I did not found anything on the archive of the list ;-) Thank you very much for your help
On 6/28/05, Claude Fuhrer <claude.fuhrer@hti.bfh.ch> wrote:
Hi everybody
I've spent the whole day trying to install the 9.3 on a Dell Precision 370 (with a NVidia graphics card). The problem is the following :
I can boot on the dvd and the install software do the 2 phases of the installation (partionning the system and installing the base, doing the first boot and finalizing the installation). When the installation is finished (basically I've installed a KDE complete system, accepting all the default + ssh) I've rebooted the system. The beginning of the boot seems to be ok and the differents settings are all marked "done". When the system try to start the kdm, it displays a clock during some seconds and then only the mouse pointer on a black screen and nothing else happen. Even the keyboard does not let me to do anything (like a ctrl-alt-f1 to have an terminal for example). I can access the machine through ssh and I don't see anything wrong. But something is wrong because an "init 3" through ssh session does not have any action.
I know that my description of the problem is not precise enough to receive a solution, but if you can give me an hint for the direction where I should look... I did not found anything on the archive of the list ;-)
Thank you very much for your help
Put 3 in the boot prompt. This will boot in runlevel 3. Then login at the console and startx. See if something strange goes there. Also, you may try sax2 from the console, and setup some low resolution mode to see what will happen. Sunny
On 6/28/05, Sunny <sloncho@gmail.com> wrote:
On 6/28/05, Claude Fuhrer <claude.fuhrer@hti.bfh.ch> wrote:
Hi everybody
I've spent the whole day trying to install the 9.3 on a Dell Precision 370 (with a NVidia graphics card). The problem is the following :
I can boot on the dvd and the install software do the 2 phases of the installation (partionning the system and installing the base, doing the first boot and finalizing the installation). When the installation is finished (basically I've installed a KDE complete system, accepting all the default + ssh) I've rebooted the system. The beginning of the boot seems to be ok and the differents settings are all marked "done". When the system try to start the kdm, it displays a clock during some seconds and then only the mouse pointer on a black screen and nothing else happen. Even the keyboard does not let me to do anything (like a ctrl-alt-f1 to have an terminal for example). I can access the machine through ssh and I don't see anything wrong. But something is wrong because an "init 3" through ssh session does not have any action.
I know that my description of the problem is not precise enough to receive a solution, but if you can give me an hint for the direction where I should look... I did not found anything on the archive of the list ;-)
Thank you very much for your help
Put 3 in the boot prompt. This will boot in runlevel 3. Then login at the console and startx. See if something strange goes there.
Also, you may try sax2 from the console, and setup some low resolution mode to see what will happen.
Sunny
-- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
Claude Fuhrer wrote:
Hi everybody
I've spent the whole day trying to install the 9.3 on a Dell Precision 370 (with a NVidia graphics card). The problem is the following :
I can boot on the dvd and the install software do the 2 phases of the installation (partionning the system and installing the base, doing the first boot and finalizing the installation). When the installation is finished (basically I've installed a KDE complete system, accepting all the default + ssh) I've rebooted the system. The beginning of the boot seems to be ok and the differents settings are all marked "done". When the system try to start the kdm, it displays a clock during some seconds and then only the mouse pointer on a black screen and nothing else happen. Even the keyboard does not let me to do anything (like a ctrl-alt-f1 to have an terminal for example). I can access the machine through ssh and I don't see anything wrong. But something is wrong because an "init 3" through ssh session does not have any action.
I know that my description of the problem is not precise enough to receive a solution, but if you can give me an hint for the direction where I should look... I did not found anything on the archive of the list ;-)
Thank you very much for your help
You should do a text install and then use Yast-Sax2 to properly config the X system. If it can't figure it out, choose the VESA driver and you will be able to see a X screen. You can also telinit 2 and then SaX2. Fix it and then sync sync sync then telinit 5. Adam
On Tuesday 28 June 2005 21:40, Claude Fuhrer wrote:
Hi everybody
I've spent the whole day trying to install the 9.3 on a Dell Precision 370 (with a NVidia graphics card). The problem is the following :
I can boot on the dvd and the install software do the 2 phases of the installation (partionning the system and installing the base, doing the first boot and finalizing the installation). When the installation is finished (basically I've installed a KDE complete system, accepting all the default + ssh) I've rebooted the system. The beginning of the boot seems to be ok and the differents settings are all marked "done". When the system try to start the kdm, it displays a clock during some seconds and then only the mouse pointer on a black screen and nothing else happen. Even the keyboard does not let me to do anything (like a ctrl-alt-f1 to have an terminal for example). I can access the machine through ssh and I don't see anything wrong. But something is wrong because an "init 3" through ssh session does not have any action.
I know that my description of the problem is not precise enough to receive a solution, but if you can give me an hint for the direction where I should look... I did not found anything on the archive of the list ;-)
Thank you very much for your help
I some way I had similar problems you have, that means "no response to keyboard, mousepointer not moving, but being able to SSH login. I did not have this problem during install, but during normal work and at random points in time. What I also noticed is that X was using almost 100 % CPU at that time, and the only way to get around it, is by sending it a kill -9 . What I did last week is applying the latest fixes for X (dont know exactly which package, but it was posted on this list last week) and I haven't experienced the problem for a week now, while I had a few times a week before. So, it might be a completely different issue, but maybe worth a try ? regards, Harry Metske
Hello, I'm trying to configure SuSE 9.3 Pro on my Dell Dimension 9100. Just now I've a little problem with sound. If I log in as user, the application KMix say that it cannot found any mixer and therefore, I don't have any sound. But if I log in as root in KDE, the sound does not shows any problem ans I can hear all the system alarm I've set. I suspect that the installation does not set the right for the users to use the sound system, but I don't know how to fix that... Can you please give me an hint ? thanx claude
Claude Fuhrer wrote:
Hello,
I'm trying to configure SuSE 9.3 Pro on my Dell Dimension 9100. Just now I've a little problem with sound. If I log in as user, the application KMix say that it cannot found any mixer and therefore, I don't have any sound. But if I log in as root in KDE, the sound does not shows any problem ans I can hear all the system alarm I've set. I suspect that the installation does not set the right for the users to use the sound system, but I don't know how to fix that... Can you please give me an hint ?
thanx claude
Looks like sound driver problems, run "rcalsasound restart" and see if it fails, if it works, kmix will fire up. Also "lsmod|grep snd" to see what is loaded. I found 9.3 didn't configure my intel8x0 on-board sound card, luckily I had the old /etc/modprobe.d/sound file stashed away. Details of the sound card would help. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Le Lundi 8 Août 2005 16:19, Sid Boyce a écrit :
Claude Fuhrer wrote: [...]
Looks like sound driver problems, run "rcalsasound restart" and see if it fails,
this command (started as root) gives : #> rcalsasound restart Shutting down sound driver done Starting sound driver: emu10k1 done #> lsmod | grep snd snd_pcm_oss 69280 0 snd_mixer_oss 23040 1 snd_pcm_oss snd_seq_midi 12480 0 snd_emu10k1_synth 10880 0 snd_emux_synth 48512 1 snd_emu10k1_synth snd_seq_virmidi 9984 1 snd_emux_synth snd_seq_midi_event 10496 2 snd_seq_midi,snd_seq_virmidi snd_seq_midi_emul 10368 1 snd_emux_synth snd_seq 73024 5 snd_seq_midi,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_event,snd_seq_midi_emul snd_emu10k1 134564 1 snd_emu10k1_synth snd_rawmidi 33824 3 snd_seq_midi,snd_seq_virmidi,snd_emu10k1 snd_seq_device 11664 6 snd_seq_midi,snd_emu10k1_synth,snd_emux_synth,snd_seq,snd_emu10k1,snd_rawmidi snd_ac97_codec 101720 1 snd_emu10k1 snd_pcm 123016 3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec snd_timer 31368 3 snd_seq,snd_emu10k1,snd_pcm snd_util_mem 7168 2 snd_emux_synth,snd_emu10k1 snd_hwdep 13472 2 snd_emux_synth,snd_emu10k1 snd 79336 17 snd_pcm_oss,snd_mixer_oss,snd_seq_midi,snd_emu10k1_synth,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_event,snd_seq_midi_emul,snd_seq,snd_emu10k1,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer,snd_util_mem,snd_hwdep snd_page_alloc 13704 2 snd_emu10k1,snd_pcm soundcore 12704 1 snd
if it works, kmix will fire up. Also "lsmod|grep snd" to see what is loaded. I found 9.3 didn't configure my intel8x0 on-board sound card, luckily I had the old /etc/modprobe.d/sound file stashed away. Details of the sound card would help.
Since my first mail, I've tried different thing. For example, if I try to start alsamixer as user, the error message is : alsamixer: function snd_ctl_open failed for default: Permission denied If I try to start it as root, no problem...
Regards
thank you for your help !
Sid. --
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2005-06-28 at 11:38 -0700, John R. Sowden wrote:
Maybe one of your 'poblems' is, that dosd doesn't point anywhere, concerning the fstab file you just c&p-ed here :(
Two of the partitions (a reiser fs and the dosd fat32 file system are handled by cryptotab, as they are encrypted. Adding umask=000 to the dosc and dose partitions did not help.
I'm not sure that dosemu will be able to access a cryptotab partition :-? dosemu is suposedly designed to access DOS (ie, fat) drives. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFCxE1ktTMYHG2NR9URAq8IAJ40hdwpsFjkCdKhYqOi4M9COmljewCfcGlA p7LeUpdkFoT2I/5/amBbz9Y= =/nN3 -----END PGP SIGNATURE-----
participants (9)
-
Adam Vazquez Kb2Jpd -
Carlos E. R. -
Catimimi -
Claude Fuhrer -
Harry Metske -
John R. Sowden -
pelibali -
Sid Boyce -
Sunny