Matthew N. Dodd | 2 Apr 00:13 2003
Picon

setfstab()/getfstab()

ftp://ftp.jurai.net/users/winter/patches/setfstab.patch

This allows you to use getfsent, getfsspec, getfsfile etc against files
other than "/etc/fstab".

'mount' and 'umount' have not yet been modified to directly use this so to
play with it you'll have to use the PATH_FSTAB environment variable.

Comments?

--

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| winter <at> jurai.net |       2 x '84 Volvo 245DL        | ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |
_______________________________________________
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"

Robert Watson | 2 Apr 22:30 2003
Picon

Re: setfstab()/getfstab()


Hmm.  Maybe an issetugid() check before using the environmental variable?

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert <at> fledge.watson.org      Network Associates Laboratories

On Tue, 1 Apr 2003, Matthew N. Dodd wrote:

> ftp://ftp.jurai.net/users/winter/patches/setfstab.patch
> 
> This allows you to use getfsent, getfsspec, getfsfile etc against files
> other than "/etc/fstab".
> 
> 'mount' and 'umount' have not yet been modified to directly use this so to
> play with it you'll have to use the PATH_FSTAB environment variable.
> 
> Comments?
> 
> -- 
> | Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
> | winter <at> jurai.net |       2 x '84 Volvo 245DL        | ix86,sparc,pmax |
> | http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |
> _______________________________________________
> 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"
> 

_______________________________________________
freebsd-fs <at> freebsd.org mailing list
(Continue reading)

Matthew N. Dodd | 2 Apr 22:38 2003
Picon

Re: setfstab()/getfstab()

On Wed, 2 Apr 2003, Robert Watson wrote:
> Hmm.  Maybe an issetugid() check before using the environmental variable?

Something like this? (whitespace damaged)

%%%
 <at>  <at>  -226,7 +254,13  <at>  <at> 
                LineNo = 0;
                return(1);
        }
-       if ((_fs_fp = fopen(_PATH_FSTAB, "r")) != NULL) {
+       if (fsp_set == 0) {
+               if (issetugid())
+                       setfstab(NULL);
+               else
+                       setfstab(getenv("PATH_FSTAB"));
+       }
+       if ((_fs_fp = fopen(path_fstab, "r")) != NULL) {
                LineNo = 0;
                return(1);
        }
%%%

--

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| winter <at> jurai.net |       2 x '84 Volvo 245DL        | ix86,sparc,pmax |
| http://www.jurai.net/~winter |  For Great Justice!  | ISO8802.5 4ever |
_______________________________________________
freebsd-fs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-fs
(Continue reading)

Robert Watson | 2 Apr 23:38 2003
Picon

Re: setfstab()/getfstab()

On Wed, 2 Apr 2003, Matthew N. Dodd wrote:

> On Wed, 2 Apr 2003, Robert Watson wrote:
> > Hmm.  Maybe an issetugid() check before using the environmental variable?
> 
> Something like this? (whitespace damaged)

Yes, that looks reasonable to me.

> %%%
>  <at>  <at>  -226,7 +254,13  <at>  <at> 
>                 LineNo = 0;
>                 return(1);
>         }
> -       if ((_fs_fp = fopen(_PATH_FSTAB, "r")) != NULL) {
> +       if (fsp_set == 0) {
> +               if (issetugid())
> +                       setfstab(NULL);
> +               else
> +                       setfstab(getenv("PATH_FSTAB"));
> +       }
> +       if ((_fs_fp = fopen(path_fstab, "r")) != NULL) {
>                 LineNo = 0;
>                 return(1);
>         }
> %%%
> 
> 
> -- 
> | Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
(Continue reading)

Greg 'groggy' Lehey | 4 Apr 07:53 2003
Picon

Announcing a Vinum mailing list

I've been neglecting Vinum for some time now: I have been very busy.

Times are now changing, and I hope to have time to work on Vinum in
the near future.  To start off, I have created a mailing list
vinum-devel <at> lemis.com.  I invite you to sign up: send a message to 
majordomo <at> lemis.com with the text 'subscribe vinum-devel' if you're
interested.

There are a number of things to do:

1.  We have a Sourceforge project (at least in name),
    http://sourceforge.net/projects/vinum/.  There's nothing on the
    site, and we need somebody to set it up and put a CVS tree there.

2.  Atul Kabra, Ramsubramanyam and Shajid Thirvuthodi have ported
    Vinum to NetBSD.  I have the sources, but I haven't done anything
    with them yet.  I know that others of you are also interested in
    this project; we should discuss it on the list.

3.  There's also interest in Vinum on OpenBSD and Linux.  I'd assume
    that there isn't much work involved in adapting the NetBSD port to
    OpenBSD.  Linux is definitely a different matter.

I hope to see you on the list soon.

Greg
--
See complete headers for address and phone numbers
Geoff Buckingham | 4 Apr 16:52 2003

newfs_msdos modifies BPB for bootable dos partition?


When creating a new FAT32 filesystem withe newfs_msdos using the -B option
to provide a boot sector (Larger than one sector) should newfs_msdos make
all the required changes to the BPB to produce a bootable  dos partition?
(Provided that IO.SYS, MSDOS.SYS and COMMAND.COM corresponding to the
boot secotor are copied into the fs next)

I am using 28 sectors from win95sr2 and success seems dependant on using similar
disk geometry to the doner fs. Do I need this much data? Most of it must be
that bitmap image that gets splashed all over the screen. 

Am I just missing out some obscure parameter, or is work required on one of the
other FAST32 specific structures?

http://www.file-recovery.net/downloads/filerecovery.pdf
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/win9x/fat32_6re8.asp

_______________________________________________
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"

Michael W . Lucas | 4 Apr 22:01 2003

Fact-checking for FAQ

Folks,

I'm double-checking any FAQ that mentions "3.0-CURRENT", as part of my
"Terminate the 2.X FAQ" search.  As part of this, I would like to
direct your attention to the following FAQ.

http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#FFS-LIMITS

Have these numbers changes for UFS1 filesystems since 3.0?  Might we
have similar numbers for UFS2 filesystems?

Thanks!

==ml

--

-- 
Michael Lucas		mwlucas <at> FreeBSD.org, mwlucas <at> BlackHelicopters.org
http://www.BlackHelicopters.org/~mwlucas/

           Absolute BSD:   http://www.AbsoluteBSD.com/
_______________________________________________
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"

Michael G. Jung | 5 Apr 01:21 2003

5.0 Raidframe / SMP / Questions

First I'm new to raidframe... but I have a few questions/problems - thanks to all
in advance...

--mikej
Michael Jung

The scenario - I have 20xFastWide 18.2 disks - would like to mirror two for boot 
2 hot spare and use 16 raid 5(4?).... I'm looking for drive space and not necessarily 
raw speed.

I'm testing with: 

FreeBSD dual-450.mikej.com 5.0-RELEASE FreeBSD 5.0-RELEASE #0: Thu Jan 16 22:16:53 GMT 2003    
root <at> hollin.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC  i386

0) I've been reading the netbsd list and it seems problems exist with smp... is that 
   the case with FreeBSD ????

1) "man raidcontrol" indicates that you need to set the disklabel to "RAID" if you want
    the kernel to boot from the partition but disklabel stubbornly insists that "RAID" is not a valid
    type...  I get this error when trying to do so with disklabel......

   "line 23: Warning, unknown file system type RAID"

   and it kindly marks the partion type to "unknown"

2) Does RAID 4 work?????  for write performance would this not be a better option?

3)  I have two drives in the chain that I get "unknown IOCTL" when they are in my raid
    config... yet they are labeled exactly like the rest.....  this is when running raidctl -C myconfigfile
(Continue reading)

Scott Long | 5 Apr 14:42 2003

Re: 5.0 Raidframe / SMP / Questions

On Fri, Apr 04, 2003 at 06:21:50PM -0500, Michael G. Jung wrote:
> First I'm new to raidframe... but I have a few questions/problems - thanks to all
> in advance...
> 
> --mikej
> Michael Jung
> 
> The scenario - I have 20xFastWide 18.2 disks - would like to mirror two for boot 
> 2 hot spare and use 16 raid 5(4?).... I'm looking for drive space and not necessarily 
> raw speed.
> 
> I'm testing with: 
> 
> FreeBSD dual-450.mikej.com 5.0-RELEASE FreeBSD 5.0-RELEASE #0: Thu Jan 16 22:16:53 GMT 2003    
root <at> hollin.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC  i386
> 
> 0) I've been reading the netbsd list and it seems problems exist with smp... is that 
>    the case with FreeBSD ????

There are a lot of issues with the locking semantics in RAIDframe that make
it at risk in SMP.  A lot of work needs to be done to fix it, unfortunately.

> 
> 1) "man raidcontrol" indicates that you need to set the disklabel to "RAID" if you want
>     the kernel to boot from the partition but disklabel stubbornly insists that "RAID" is not a valid
>     type...  I get this error when trying to do so with disklabel......
> 
>    "line 23: Warning, unknown file system type RAID"
> 
>    and it kindly marks the partion type to "unknown"
(Continue reading)

Kris Kennaway | 7 Apr 10:32 2003

"panic: sleeping thread owns a mutex" in bremfree()

I just got the following panic on alpha:

panic: sleeping thread owns a mutex

propagate_priority() at propagate_priority+0x148
_mtx_lock_sleep() at _mtx_lock_sleep+0x264
_mtx_lock_flags() at _mtx_lock_flags+0x84
bremfree() at bremfree+0x30
vfs_backgroundwritedone() at vfs_backgroundwritedone+0x1c8
bufdone() at bufdone+0x1c4
bufdonebio() at bufdonebio+0x1c
biodone() at biodone+0x90
g_dev_done() at g_dev_done+0xd8
biodone() at biodone+0x90
g_io_schedule_up() at g_io_schedule_up+0x128
g_up_procbody() at g_up_procbody+0x5c
fork_exit() at fork_exit+0x100
exception_return() at exception_return
--- root of call graph ---

As usual, no gdb backtrace possible because it's broken on alpha.

Kris

Gmane