Yar Tikhiy <[EMAIL PROTECTED]> writes:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > Can you guarantee that this will not f*** up the bootp / dhcp +
> > nfsroot case? There are dragons in that code which were decidedly
> > not funny to track down and fix.
> Indeed; or, as a Russian proverb
On 2008.02.18. 15:26, Yar Tikhiy wrote:
On Mon, Feb 18, 2008 at 01:50:34PM +0100, Dag-Erling Sm??rgrav wrote:
Yar Tikhiy <[EMAIL PROTECTED]> writes:
Log:
In the new order of things dictated by nmount(2), a read-only mount
is to be requested via a "ro" option. At the same time, MN
On Mon, Feb 18, 2008 at 01:50:34PM +0100, Dag-Erling Sm??rgrav wrote:
> Yar Tikhiy <[EMAIL PROTECTED]> writes:
> > Log:
> > In the new order of things dictated by nmount(2), a read-only mount
> > is to be requested via a "ro" option. At the same time, MNT_RDONLY
> > is gradually becoming a
Yar Tikhiy <[EMAIL PROTECTED]> writes:
> Log:
> In the new order of things dictated by nmount(2), a read-only mount
> is to be requested via a "ro" option. At the same time, MNT_RDONLY
> is gradually becoming an indicator of the current state of the FS
> instead of a command flag. Today
Thanks!
On Thu, Aug 24, 2006 at 06:52:28PM +, Marius Strobl wrote:
> marius 2006-08-24 18:52:28 UTC
>
> FreeBSD src repository
>
> Modified files:
> sys/kern vfs_mount.c
> Log:
> Fix a bug introduced with rev. 1.204; in vfs_donmount() use
> copyout(9) instead
On Fri, Jun 02, 2006 at 06:25:36PM -0400, Craig Rodrigues wrote:
+> On Fri, Jun 02, 2006 at 08:29:02PM +, Pawel Jakub Dawidek wrote:
+> > pjd 2006-06-02 20:29:02 UTC
+> >
+> > FreeBSD src repository
+> >
+> > Modified files:
+> > sys/kern vfs_mount.c
+> > Log:
+
On Fri, Jun 02, 2006 at 08:29:02PM +, Pawel Jakub Dawidek wrote:
> pjd 2006-06-02 20:29:02 UTC
>
> FreeBSD src repository
>
> Modified files:
> sys/kern vfs_mount.c
> Log:
> Fix a problem introduced in revision 1.220. On mount(2) failure, don't
> forget to u
On Sun, May 14, 2006 at 01:51:38AM +, Craig Rodrigues wrote:
> rodrigc 2006-05-14 01:51:38 UTC
>
> FreeBSD src repository
>
> Modified files:
> sys/kern vfs_mount.c
> Log:
> For nmount(), if "rw" is specified as a mount option,
> add "noro" to the list of mount
On Wed, Mar 08, 2006 at 11:43:39PM +, Tor Egge wrote:
+> tegge 2006-03-08 23:43:39 UTC
+>
+> FreeBSD src repository
+>
+> Modified files:
+> sys/kern vfs_mount.c vfs_vnops.c vfs_subr.c
+> sys/sys vnode.h mount.h
+> sys/ufs/ffs ffs_exte
On Sat, Dec 03, 2005 at 12:25:34PM +, Robert Watson wrote:
>
> On Sat, 3 Dec 2005, Ruslan Ermilov wrote:
>
> >On Sat, Dec 03, 2005 at 12:04:20PM +, Craig Rodrigues wrote:
> >>rodrigc 2005-12-03 12:04:20 UTC
> >>
> >> FreeBSD src repository
> >>
> >> Modified files:
> >>sys/kern
On Sat, 3 Dec 2005, Ruslan Ermilov wrote:
On Sat, Dec 03, 2005 at 12:04:20PM +, Craig Rodrigues wrote:
rodrigc 2005-12-03 12:04:20 UTC
FreeBSD src repository
Modified files:
sys/kern vfs_mount.c
Log:
Add "rdonly" to global_opts, and parse it in vfs_donmount().
On Sat, Dec 03, 2005 at 12:04:20PM +, Craig Rodrigues wrote:
> rodrigc 2005-12-03 12:04:20 UTC
>
> FreeBSD src repository
>
> Modified files:
> sys/kern vfs_mount.c
> Log:
> Add "rdonly" to global_opts, and parse it in vfs_donmount().
>
> Requested by: rwat
On Wed, Nov 09, 2005 at 10:01:50AM -0600, Sergey Babkin wrote:
> >From: John Baldwin <[EMAIL PROTECTED]>
> >On Wednesday 09 November 2005 09:30 am, Pawel Jakub Dawidek wrote:
> >> On Wed, Nov 09, 2005 at 03:08:39PM +0100, Poul-Henning Kamp wrote:
> >> +> In message <[EMAIL PROTECTED]>, Pawel Jakub
Pawel Jakub Dawidek wrote:
On Wed, Nov 09, 2005 at 12:18:47PM +0100, Poul-Henning Kamp wrote:
+> In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writes:
+>
+> >Of course we need to consider things like localization, etc.
+>
+> I'm sorry, but localization of messages of this caliber is a tot
On Wed, Nov 09, 2005 at 02:29:33PM +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Sergey Babkin writes:
>
> >>+> I'm sorry, but localization of messages of this caliber is a totally
> >>+> bogus concern which I intend to ignore 100%.
> >>
> >>Even then, this is quite annoying to
On Wed, Nov 09, 2005 at 08:35:16AM -0800, Frank Mayhar wrote:
> On Wed, 2005-11-09 at 08:01 +0100, Poul-Henning Kamp wrote:
> > Modify perror(3), err(3) and similar to pull out the "extended"
> > error, if there is one.
>
> As a data point, the way this problem was solved in one particular
> mainf
On Wed, 2005-11-09 at 08:01 +0100, Poul-Henning Kamp wrote:
> Modify perror(3), err(3) and similar to pull out the "extended"
> error, if there is one.
As a data point, the way this problem was solved in one particular
mainframe OS many years ago was with a more complex error code. Errors
looked
>From: John Baldwin <[EMAIL PROTECTED]>
>On Wednesday 09 November 2005 09:30 am, Pawel Jakub Dawidek wrote:
>> On Wed, Nov 09, 2005 at 03:08:39PM +0100, Poul-Henning Kamp wrote:
>> +> In message <[EMAIL PROTECTED]>, Pawel Jakub
>> Dawidek writes: +>
>> +>
>> +> >In current world order you can decid
On Wednesday 09 November 2005 09:30 am, Pawel Jakub Dawidek wrote:
> On Wed, Nov 09, 2005 at 03:08:39PM +0100, Poul-Henning Kamp wrote:
> +> In message <[EMAIL PROTECTED]>, Pawel Jakub
> Dawidek writes: +>
> +>
> +> >In current world order you can decide based on LC_ALL/LANG, etc.
> +>
> +> Read my
On Wed, Nov 09, 2005 at 03:08:39PM +0100, Poul-Henning Kamp wrote:
+> In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writes:
+>
+>
+> >In current world order you can decide based on LC_ALL/LANG, etc.
+>
+> Read my lips: printf(9) and panic(9) are _never_ going to respect
+> any environment
In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writes:
>In current world order you can decide based on LC_ALL/LANG, etc.
Read my lips: printf(9) and panic(9) are _never_ going to respect
any environment variable.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]
On Wed, Nov 09, 2005 at 02:36:24PM +0100, Poul-Henning Kamp wrote:
+> In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writes:
+>
+> >+> Fourth, there is a simple, easy to understand and fully available
+> >+> way to do it, should some happy bands of natives want to do it
+> >+> anyway: make a
In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writes:
>+> Fourth, there is a simple, easy to understand and fully available
>+> way to do it, should some happy bands of natives want to do it
>+> anyway: make a per language branch in perforce, translate the
>+> messages there and make a kerne
In message <[EMAIL PROTECTED]>, Sergey Babkin writes:
>>+> I'm sorry, but localization of messages of this caliber is a totally
>>+> bogus concern which I intend to ignore 100%.
>>
>>Even then, this is quite annoying to see one communicate in two
>>languages:
>>
>> Błąd wywołania mount(2): In
>From: Pawel Jakub Dawidek <[EMAIL PROTECTED]>
>On Wed, Nov 09, 2005 at 12:18:47PM +0100, Poul-Henning Kamp wrote:
>+> In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writes:
>+>
>+> >Of course we need to consider things like localization, etc.
>+>
>+> I'm sorry, but localization of messages
On Wed, Nov 09, 2005 at 12:18:47PM +0100, Poul-Henning Kamp wrote:
+> In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writes:
+>
+> >Of course we need to consider things like localization, etc.
+>
+> I'm sorry, but localization of messages of this caliber is a totally
+> bogus concern which I
In message <[EMAIL PROTECTED]>, Pawel Jakub Dawidek writes:
>Of course we need to consider things like localization, etc.
I'm sorry, but localization of messages of this caliber is a totally
bogus concern which I intend to ignore 100%.
For one thing, we're never going to see translation done com
On Wed, Nov 09, 2005 at 11:46:01AM +0100, Pawel Jakub Dawidek wrote:
+> On Wed, Nov 09, 2005 at 02:26:38AM +, Craig Rodrigues wrote:
+> +> rodrigc 2005-11-09 02:26:38 UTC
+> +>
+> +> FreeBSD src repository
+> +>
+> +> Modified files:
+> +> sys/kern vfs_mount.c
+> +>
On Wed, Nov 09, 2005 at 02:26:38AM +, Craig Rodrigues wrote:
+> rodrigc 2005-11-09 02:26:38 UTC
+>
+> FreeBSD src repository
+>
+> Modified files:
+> sys/kern vfs_mount.c
+> Log:
+> For nmount(), allow a text string error message to be propagated back
+> to user
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, Nate Lawson writes:
While I don't have ideas for a better general mechanism for this, I
think it sets a bad precedent. We can't have every complex syscall
transporting its own error message strings back to the user program.
And we can
On Tue, 8 Nov 2005, Nate Lawson wrote:
Craig Rodrigues wrote:
rodrigc 2005-11-09 02:26:38 UTC
FreeBSD src repository
Modified files:
sys/kern vfs_mount.c Log:
For nmount(), allow a text string error message to be propagated back
to user-space if a parameter named
In message <[EMAIL PROTECTED]>, Nate Lawson writes:
>While I don't have ideas for a better general mechanism for this, I
>think it sets a bad precedent. We can't have every complex syscall
>transporting its own error message strings back to the user program.
>And we can't expand errno to be th
Craig Rodrigues wrote:
rodrigc 2005-11-09 02:26:38 UTC
FreeBSD src repository
Modified files:
sys/kern vfs_mount.c
Log:
For nmount(), allow a text string error message to be propagated back
to user-space if a parameter named "errmsg" is passed into the iovec.
U
33 matches
Mail list logo