Re: CVS commit: src/bin/sh

2009-10-06 Thread Thomas Klausner
One of these two changes broke booting into multi-user mode.
For me, on current/amd64, the boot (without -s) stops and asks for a
shell.
I choose /bin/sh, then leave it, and I get the prompt again.
When I replace /bin/sh with one from 20090922, boot succeeds to
multi-user mode without these symptoms.
 Thomas

On Tue, Oct 06, 2009 at 07:56:58PM +, Alan Barrett wrote:
> Module Name:  src
> Committed By: apb
> Date: Tue Oct  6 19:56:58 UTC 2009
> 
> Modified Files:
>   src/bin/sh: mkbuiltins
> 
> Log Message:
> Make this slightly more portable; it has to run on arbitary host
> platforms at build time.  Previousy, some shells were confused by
> some of the "[ ... ]" tests.
> 
> 
> To generate a diff of this commit:
> cvs rdiff -u -r1.21 -r1.22 src/bin/sh/mkbuiltins
> 
> Please note that diffs are not public domain; they are subject to the
> copyright notices on the relevant files.
> 

On Tue, Oct 06, 2009 at 04:05:10PM -0400, Christos Zoulas wrote:
> Module Name:  src
> Committed By: christos
> Date: Tue Oct  6 20:05:10 UTC 2009
> 
> Modified Files:
>   src/bin/sh: eval.c
> 
> Log Message:
> fix regression exit1: Don't exec the last command in a subshell if it has
> trap[0] (trap EXIT) set. Fork instead to give the shell a chance to execute
> the trap when it is done.
> 
> 
> To generate a diff of this commit:
> cvs rdiff -u -r1.96 -r1.97 src/bin/sh/eval.c
> 
> Please note that diffs are not public domain; they are subject to the
> copyright notices on the relevant files.
> 



Re: CVS commit: src/etc/rc.d

2009-10-06 Thread Jason Thorpe

On Oct 6, 2009, at 1:22 AM, Adam Hamsik wrote:

> Hi,
> On Oct,Tuesday 6 2009, at 9:03 AM, Alan Barrett wrote:
> 
>> On Mon, 05 Oct 2009, Adam Hamsik wrote:
>>> Modified Files:
>>> src/etc/rc.d: mountall
>>> 
>>> Log Message:
>>> Add support for mounting zfs filesystems to mountall script. ZFS 
>>> configuration
>>> is stored in /etc/zpool.cache and it is automatically loaded to kernel from
>>> filesystem. Filesystems are then configured accordingly to their properties
>>> loaded from cache file.
>> 
>> Is /etc/zpool.cache a human-edited configuration file (in which
>> case, why the ".cache" name?), or is it a machine-readable database (in
>> which case, why is it in /etc?), or is it something else?
> 
> It is a binary file. Something like binary plist. Do you have any better 
> place for it ? I think that we should keep it in etc until we start work on a 
> zfs on root support then we will need to move it some where else anyway.

It belongs in /var/db ... but I'd like to ask why you need it at all?

> 
> Regards
> 
> Adam.

-- thorpej



Re: CVS commit: src/etc/rc.d

2009-10-06 Thread Adam Hamsik

Hi,
On Oct,Tuesday 6 2009, at 9:03 AM, Alan Barrett wrote:


On Mon, 05 Oct 2009, Adam Hamsik wrote:

Modified Files:
src/etc/rc.d: mountall

Log Message:
Add support for mounting zfs filesystems to mountall script. ZFS  
configuration
is stored in /etc/zpool.cache and it is automatically loaded to  
kernel from
filesystem. Filesystems are then configured accordingly to their  
properties

loaded from cache file.


Is /etc/zpool.cache a human-edited configuration file (in which
case, why the ".cache" name?), or is it a machine-readable database  
(in

which case, why is it in /etc?), or is it something else?


It is a binary file. Something like binary plist. Do you have any  
better place for it ? I think that we should keep it in etc until we  
start work on a zfs on root support then we will need to move it some  
where else anyway.


Regards

Adam.



Re: CVS commit: src/etc/rc.d

2009-10-06 Thread Alan Barrett
On Mon, 05 Oct 2009, Adam Hamsik wrote:
> Modified Files:
>   src/etc/rc.d: mountall
> 
> Log Message:
> Add support for mounting zfs filesystems to mountall script. ZFS configuration
> is stored in /etc/zpool.cache and it is automatically loaded to kernel from
> filesystem. Filesystems are then configured accordingly to their properties
> loaded from cache file.

Is /etc/zpool.cache a human-edited configuration file (in which
case, why the ".cache" name?), or is it a machine-readable database (in
which case, why is it in /etc?), or is it something else?

--apb (Alan Barrett)