headers
Stan Sorochan | 3 Feb 2005 00:10
Picon

Re: FreeBSD 5.2 How do I let ordinary users mount floppies, CDROMs and other removablemedia?I'

Thanks to those who've responded!

So I'm combining two of the emails that I've acted upon:

First: 
>/dev/xpt0?

>-- 
>Maxim Konovalov

Second:

> If you su to root, mount it, then unmount it, and then try to mount it as
> the regular user, does that work?
>
> Robert N M Watson

OK, I've added the follwing lines to my devfs.conf:

own     xpt0    root:usb #gid of those who need to mount a usb device
perm    xpt0    0660

so now I get this:

# ll /dev/ | grep xpt0
crw-rw----  1 root  usb       104,   0  1 лют 23:46 xpt0

this looks good, but I still can't mount the /dev/da0s1 without su rights.

Then I do a su, mount the device, unmount it - and now I can mount the device
(Continue reading)

Permalink | Reply | 2 comments |
headers
Arne "Wörner" | 3 Feb 2005 00:19
Picon
Favicon

Re: FreeBSD 5.2 How do I let ordinary users mount floppies, CDROMs and other removablemedia?I'

> OK, that sort of works, but the su part really has to go.... 
> How can I fix that?
> 
You could write a little shell script and put it in
/usr/local/etc/rc.d .

This shell script mounts and unmounts the device...

quod erat faciendum. Or not? :-))

-Arne

		
__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo 
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Stan Sorochan | 3 Feb 2005 23:02
Picon

Re: FreeBSD 5.2 How do I let ordinary users mount floppies, CDROMs and other removablemedia?'

Yes!!!  It's been figured out!

Thanks to great advice in this mailing list!  Many many thanks to those who 
spent their time to write!

So to recap!  In order to be able to mount removable media without su on 
FreeBSD 5.X this has to be done:

vfs.usermount=1

is to be put into /etc/sysctl.conf

The following lines are to be added to /etc/devfs.conf:

# Allow members of cdrom to mount the ide cdrom
own     acd0    root:cdrom
perm    acd0    0660

# Allow members of floppy group to mount fd
own     fd0     root:floppy
perm    fd0     0660

The follwing lines are to be added to /etc/devfs.rules:

[userbox_usb=10]
add path 'da*' mode 0660 group usb
#more of the usb devices are to be added here (scanners, digicams, etc)

The following line is to be added to /etc/rc.conf so that the rules are 
loaded:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jan Pechanec | 4 Feb 2005 00:47
Picon

fs oddity when moving from 4.4 to 5.3


	hi, after RW mounting UFS1 filesystem created using sysinstall under 
4.4 to 5.3 and extracting 1/2 of the only file there (tarball), the file got 
lost. Now I got that disk to salvage as much as I can. I don't want to give 
much details since I think it would be too much, but is there any chance 
that some changes in the code could do that? Fsck doesn't complain, the 
directory chunk for the file is now part of larger free chunk etc., but the 
file was not manually deleted, bash history was checked.

	just one thing: 'dumpfs -m' on 5.3 and then 'newfs -N...' shows:

/dev/ad1s1e: 38158.3MB (78148160 sectors) block size 8192, fragment size 1024
        using 846 cylinder groups of 45.15MB, 5779 blks, 11584 inodes.
super-block backups (for fsck -b #) at:
 32, 92496, 184960, 277424, 369888, 462352, 554816, 647280, 739744, 832208,

	the same 'newfs -N' (without '-O 1') on 4.11 shows this:

/dev/ad1s1e:    78148160 sectors in 19080 cylinders of 1 tracks, 4096 sectors
        38158.3MB in 868 cyl groups (22 c/g, 44.00MB/g, 10944 i/g)
super-block backups (for fsck -b #) at:
 32, 90144, 180256, 270368, 360480, 450592, 540704, 630816, 720928, 811040,

	you can see that number of cylinder groups is different (and 
superblocks too of course) and no wonder that all superblocks except of 32 
don't work with 'fsck -b'. The real 2nd backup superblock (manually found 
using the magic) is 65568, which is quite far from what 5.3/4.11 thinks. 
Apparently the real number of cylinder group is very different. Can anyone 
explain that, please? I'm quite confused. Tomorrow I will install 4.4 to see 
the filesystem behaviour there.
(Continue reading)

Permalink | Reply | 2 comments |
headers
rick | 4 Feb 2005 02:43
Picon

fyi: NFS v4 server

I've put a version of the NFSv4 beta test server that works on FreeBSD5.3
up. Just anonymous ftp ftp.cis.uoguelph.ca and look in pub/nfsv4

rick
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Doug White | 4 Feb 2005 06:28

Re: fs oddity when moving from 4.4 to 5.3

On Fri, 4 Feb 2005, Jan Pechanec wrote:

>
> 	hi, after RW mounting UFS1 filesystem created using sysinstall under
> 4.4 to 5.3 and extracting 1/2 of the only file there (tarball), the file got
> lost. Now I got that disk to salvage as much as I can. I don't want to give
> much details since I think it would be too much, but is there any chance
> that some changes in the code could do that? Fsck doesn't complain, the
> directory chunk for the file is now part of larger free chunk etc., but the
> file was not manually deleted, bash history was checked.
>
> 	just one thing: 'dumpfs -m' on 5.3 and then 'newfs -N...' shows:
>
> /dev/ad1s1e: 38158.3MB (78148160 sectors) block size 8192, fragment size 1024
>         using 846 cylinder groups of 45.15MB, 5779 blks, 11584 inodes.
> super-block backups (for fsck -b #) at:
>  32, 92496, 184960, 277424, 369888, 462352, 554816, 647280, 739744, 832208,
>
> 	the same 'newfs -N' (without '-O 1') on 4.11 shows this:
>
> /dev/ad1s1e:    78148160 sectors in 19080 cylinders of 1 tracks, 4096 sectors
>         38158.3MB in 868 cyl groups (22 c/g, 44.00MB/g, 10944 i/g)
> super-block backups (for fsck -b #) at:
>  32, 90144, 180256, 270368, 360480, 450592, 540704, 630816, 720928, 811040,

Its possible between 4.4 and 4.11 (I haven't checked the CVS history) the
newfs default for the '-g' option, which sets the cylinder group size,
changed from the old BSD default to "the max possible" which is generally
better for performance. You would need the original FS parameters to feed
to newfs on 4.11 in order to calculate the correct superblock positions.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Kris Kennaway | 4 Feb 2005 06:31

Re: fs oddity when moving from 4.4 to 5.3

On Thu, Feb 03, 2005 at 09:28:48PM -0800, Doug White wrote:
> On Fri, 4 Feb 2005, Jan Pechanec wrote:
> 
> >
> > 	hi, after RW mounting UFS1 filesystem created using sysinstall under
> > 4.4 to 5.3 and extracting 1/2 of the only file there (tarball), the file got
> > lost. Now I got that disk to salvage as much as I can. I don't want to give
> > much details since I think it would be too much, but is there any chance
> > that some changes in the code could do that? Fsck doesn't complain, the
> > directory chunk for the file is now part of larger free chunk etc., but the
> > file was not manually deleted, bash history was checked.
> >
> > 	just one thing: 'dumpfs -m' on 5.3 and then 'newfs -N...' shows:
> >
> > /dev/ad1s1e: 38158.3MB (78148160 sectors) block size 8192, fragment size 1024
> >         using 846 cylinder groups of 45.15MB, 5779 blks, 11584 inodes.
> > super-block backups (for fsck -b #) at:
> >  32, 92496, 184960, 277424, 369888, 462352, 554816, 647280, 739744, 832208,
> >
> > 	the same 'newfs -N' (without '-O 1') on 4.11 shows this:
> >
> > /dev/ad1s1e:    78148160 sectors in 19080 cylinders of 1 tracks, 4096 sectors
> >         38158.3MB in 868 cyl groups (22 c/g, 44.00MB/g, 10944 i/g)
> > super-block backups (for fsck -b #) at:
> >  32, 90144, 180256, 270368, 360480, 450592, 540704, 630816, 720928, 811040,
> 
> Its possible between 4.4 and 4.11 (I haven't checked the CVS history) the
> newfs default for the '-g' option, which sets the cylinder group size,
> changed from the old BSD default to "the max possible" which is generally
> better for performance.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ola Theander | 7 Feb 2005 01:38

Prblm: software RAID boot, FreeBSD panic.

Dear subscribers

I'm trying to setup an old Dell Dimension computer as a simple file server 
in a small network. For this I've purchased two ATA-disks at 200 GB each. 
The idea is to use the software RAID features of FreeBSD to have some 
primitive redundancy. The computer doesn't have any RAID controller 
whatsoever so I'm stuck with just plain software RAID.

What I tried to do is to use "atacontroller create mirror ad0 ad1" to create

mirroring between the two disks. Then I installed FreeBSD 5.3 stable as 
usual on ad0. When the installation was finished I booted the OS and edited 
the /etc/fstab file, replacing all "ad0*" with "ar0*" and rebooted. I.e 
fstab is changed to this:

# Device Mountpoint FStype Options Dump Pass#
/dev/ar0s1b  none  swap sw  0 0
/dev/ar0s1a  /  ufs rw  1 1
/dev/ar0s1e  /tmp  ufs rw  2 2
/dev/ar0s1f  /usr  ufs rw  2 2
/dev/ar0s1d  /var  ufs rw  2 2
/dev/acd0 /cdrom cd9660 ro,noauto 0 0

 At the boot, after changing fstab, the kernel panics and says:

ar0: 194xxxxxxxx MB <ATA RAID 1 array> [24792/255/63] Status: READY 
subdisks:

disk0 READY on ad0 at ata0-master
disk1 READY on ad1 at ata0-slave
(Continue reading)

Permalink | Reply | 1 comment |
headers
Arne "Wörner" | 7 Feb 2005 02:11
Picon
Favicon

Re: Prblm: software RAID boot, FreeBSD panic.

Hi Ola!

--- Ola Theander <ola.theander <at> otsystem.com> wrote:
> What I tried to do is to use "atacontroller create mirror ad0
> ad1" to create
>
Have you tried a
  cmp /dev/ad0s1a /dev/ad1s1a
in single user mode with
  /
and
  /usr
mounted read-only?

> mirroring between the two disks. Then I installed FreeBSD 5.3
> stable as usual on ad0.
>
Are you sure, that writes to ad0 are automatically copied to ad1?

Maybe you should try to install to ar0?

Maybe you should do a
  dd if=/dev/ad0 of=/dev/ad1 bs=256k

> Would this be the best way to configure software RAID. It seems
> like there are several different techniques for this e.g.
> vinum, atacontrol, geom, 
> gmirror etc. Which one of these is the recommended one?
>
I like to use geom_vinum, which works quite fine, if the disk
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marco Pizzi | 8 Feb 2005 14:53

Swap problem on FreeBSD 5.2.1-RC

Hello,

We've installed (a long time ago) the FreeBSD version 5.2.1-RC on a server.
We've noticed, at least two times, very bad problems on the swap system; in the
detail, we've found the well known error in the messages file:

swap_pager: indefinite wait buffer: device: da0s1a

The fact strange is that the da0s1a device is not a swap partition!

-------------------------------------------------------------------------------------------------------
# Device                Mountpoint      FStype  Options         Dump    Pass#
/dev/da0s1b            none            swap    sw              0       0
/dev/da0s1a             /               ufs     rw              1       1
-------------------------------------------------------------------------------------------------------

Have you ever seen such a problem?

Thanks,

--

Marco.  

_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 5 comments |

Gmane