headers
Jukka Salmi | 1 Apr 2004 19:11
Picon

NetBSD Guide: RAID question

Hi,

I just started learning about RAIDframe and read chapter 23 of the
NetBSD Guide. I noticed that the disklabels of raid0 shown in
"23.5. Setting up filesystems" [2] and "23.6. Setting up kernel dumps" [3]
are not the same. This confuses me, and now I'm not sure whether this
is simply an error in the guide or I misunderstand something completely...

Thanks for any enlightenment!

Jukka

[1] http://www.netbsd.org/guide/en/chap-rf.html#id2611876
[2] http://www.netbsd.org/guide/en/chap-rf.html#id2612002

--

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~
Permalink | Reply | 2 comments |
headers
Daniel Bolgheroni | 1 Apr 2004 16:29
Picon
Favicon

/usr/obj deleted

Hi,

Recently, I've made the mistake of deleting /usr/obj. Now, every time I
try a kernel build or something like that, I get the following message:

# ./build.sh tools
===> Bootstrapping nbmake
checking for sh... /bin/sh
checking for gcc... cc
checking for C compiler default output... configure: error: C compiler
cannot create executables

ERROR: configure of nbmake failed
*** BUILD ABORTED ***
#

Is there any way to recover my /usr/obj?

Thank you.
Permalink | Reply | 4 comments |
headers
Jukka Salmi | 1 Apr 2004 19:33
Picon

Re: /usr/obj deleted

Daniel Bolgheroni --> netbsd-help (2004-04-01 14:29:08 +0000):
> Is there any way to recover my /usr/obj?

You could use your backups ;-)

Alternatively, just create the directory before using build.sh.

HTH, Jukka

--

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~
Permalink | Reply | 3 comments |
headers
Martti Kuparinen | 1 Apr 2004 20:11
Picon
Picon
Favicon

Re: NetBSD Guide: RAID question

Jukka Salmi wrote:

> I just started learning about RAIDframe and read chapter 23 of the
> NetBSD Guide. I noticed that the disklabels of raid0 shown in
> "23.5. Setting up filesystems" [2] and "23.6. Setting up kernel dumps" [3]
> are not the same. This confuses me, and now I'm not sure whether this

I must check my server (I wrote this part of the guide using actual
values from my home server) but I can't do it tonight...

Martti
Permalink | Reply | 0 comments |
headers
Daniel Bolgheroni | 1 Apr 2004 17:15
Picon
Favicon

Re: /usr/obj deleted

I did. But the error remains the same.

On Thu, 1 Apr 2004 19:33:24 +0200
Jukka Salmi <jukka-netbsd <at> 2004.salmi.ch> wrote:

> Daniel Bolgheroni --> netbsd-help (2004-04-01 14:29:08 +0000):
> > Is there any way to recover my /usr/obj?
> 
> You could use your backups ;-)
> 
> Alternatively, just create the directory before using build.sh.
> 
> 
> HTH, Jukka
> 
> -- 
> bashian roulette:
> $ ((RANDOM%6)) || rm -rf ~
Permalink | Reply | 2 comments |
headers
Jukka Salmi | 1 Apr 2004 21:01
Picon

Re: /usr/obj deleted

Daniel Bolgheroni --> netbsd-help (2004-04-01 15:15:56 +0000):
> I did. But the error remains the same.

What does config.log say?

--

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~
Permalink | Reply | 1 comment |
headers
Daniel Bolgheroni | 1 Apr 2004 18:30
Picon
Favicon

Re: /usr/obj deleted

The only config.log I found is:

/usr/src/gnu/dist/gdb/gdb/doc/config.log

config.log:
-------
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

configure:556: checking for a BSD compatible install
configure:609: checking whether ln -s works
-------

Thank you.

On Thu, 1 Apr 2004 21:01:59 +0200
Jukka Salmi <jukka-netbsd <at> 2004.salmi.ch> wrote:

> Daniel Bolgheroni --> netbsd-help (2004-04-01 15:15:56 +0000):
> > I did. But the error remains the same.
> 
> What does config.log say?
> 
> -- 
> bashian roulette:
> $ ((RANDOM%6)) || rm -rf ~
Permalink | Reply | 0 comments |
headers
Daniel Bolgheroni | 1 Apr 2004 18:53
Picon
Favicon

Re: /usr/obj deleted

On Thu, 1 Apr 2004 21:46:18 +0200
Jukka Salmi <jukka <at> salmi.ch> wrote:

> After that, you could try updating your source tree using CVS
> and watch out for lines which start with '?'. Delete those files.
> 
> Building the toolchain should work then...

This is exactly what I tried.

# ./build.sh tools

Anyway, thank you.
Permalink | Reply | 0 comments |
headers
Joel Rees | 2 Apr 2004 02:19
Picon
Favicon

vi temporary permissions problems

Just finished installing a special soft-float build of mac68k by hand 
copying everything after base and etc into /, then using tar -zx.

Then I set up an admin user, with gid=uid, but with secondary groups 
set to wheel, operator, staff, guest, and users.

I can log on as root and use vi with no problems. But I get the message

     ex/vi: Error: Unable to create temporary permissions file: 
Permission denied

I checked /var/tmp/vi.recover and the owner is root, group was wheel. 
So I changed the group to users, just for fun, and still get the same 
message. (Makes sense, permission string is drwxrwxrwx.)

Just for grins, I set up another user, -G to the list above, but let 
primary user default to users, and I can't vi with that user either.

Searching the web for the error message didn't turn anything useful up. 
Any ideas where I should start poking around next?
Permalink | Reply | 2 comments |
headers
Michael W. Lucas | 2 Apr 2004 03:26

Re: vi temporary permissions problems

First thought: 

maybe you should have used the -p flag to tar in the install?

On Fri, Apr 02, 2004 at 09:19:47AM +0900, Joel Rees wrote:
> Just finished installing a special soft-float build of mac68k by hand 
> copying everything after base and etc into /, then using tar -zx.
> 
> Then I set up an admin user, with gid=uid, but with secondary groups 
> set to wheel, operator, staff, guest, and users.
> 
> I can log on as root and use vi with no problems. But I get the message
> 
>     ex/vi: Error: Unable to create temporary permissions file: 
> Permission denied
> 
> I checked /var/tmp/vi.recover and the owner is root, group was wheel. 
> So I changed the group to users, just for fun, and still get the same 
> message. (Makes sense, permission string is drwxrwxrwx.)
> 
> Just for grins, I set up another user, -G to the list above, but let 
> primary user default to users, and I can't vi with that user either.
> 
> Searching the web for the error message didn't turn anything useful up. 
> Any ideas where I should start poking around next?

--

-- 
Michael Lucas		mwlucas <at> FreeBSD.org, mwlucas <at> BlackHelicopters.org

Today's chance of throwing it all away to start a goat farm: 49.1%
(Continue reading)

Permalink | Reply | 1 comment |

Gmane