Wouter Schoot | 1 Jun 2007 18:36

NetBSD Live... Pendrive!

Hi!

I was wondering, using the same methods as creating a livecd, can they 
also be used for making a live usb stick with NetBSD?

I now run into the problem that when I install onto the USB disc and 
boot it, it all goes fine but it bails on the root disc mount. Since it 
hasn't loaded the drivers yet, it can't boot from it. When I for example 
enter "vr0" (the NICs name), it tries bootp on vr0, loads the SD driver, 
fails on the bootp (I haven't set that up :)) and then I can succesfully 
enter sd0a as root. Any idea's?

mvg,

Wouter

--

-- 
Er was eens een boer. Hij had 3 koeien, 2 witte en 1 witte.
Maar dat gaf niet, want de koe gaf ook niet.  De boer vond een
horloge, de koe vond van niet.  Ra-ra kameel politiepet.

Mark Thomas | 6 Jun 2007 17:28
Picon

generic.mp kernel and single processor

Stupid question perhaps but ....

If I'm installing 3.1 on a dual processor i386 machine with one
processor do I use the generic.mp kernel?

thanks
--

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Greg Troxel | 6 Jun 2007 18:20
Picon

Re: generic.mp kernel and single processor

There are three flavors of GENERIC from the MP point of view:

  GENERIC: runs fine on dual-processor machines, but only uses 1
  processor

  GENERIC.MP: uses MPBIOS to find/start additional processors.
  Typically useful for pretty old machines

  GENERIC.MPACPI: uses ACPI for additional processors.  Typically useful
  for moderate to new machines

If you have a machine that can take 2 processors but only has 1, you
might as well use just GENERIC.

Mark Thomas | 6 Jun 2007 19:46
Picon

Re: generic.mp kernel and single processor

On 6/6/07, Greg Troxel <gdt <at> ir.bbn.com> wrote:
> There are three flavors of GENERIC from the MP point of view:
>
>   GENERIC: runs fine on dual-processor machines, but only uses 1
>   processor
>
>   GENERIC.MP: uses MPBIOS to find/start additional processors.
>   Typically useful for pretty old machines
>
>   GENERIC.MPACPI: uses ACPI for additional processors.  Typically useful
>   for moderate to new machines
>
>
> If you have a machine that can take 2 processors but only has 1, you
> might as well use just GENERIC.

Thanks for the info Greg, Joseph.

--

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Jeremy C. Reed | 7 Jun 2007 23:33

where are directory group permissions documented?

What man page(s) discuss that when a file is created it inherits the group 
ID of its directory (instead of the gid of the creating process)?

Linux doesn't do that by default and calls it "BSD semantics". Linux can 
enable that with S_ISGID bit.

Can it be disabled on a BSD system? In other words on NetBSD, how to make 
it so new files are automatically created with the group of creating 
process (instead of the group of the directory)? I am just curious and I 
don't need this.

  Jeremy C. Reed

Johnny Billquist | 7 Jun 2007 23:47
Picon

Re: where are directory group permissions documented?

tor 2007-06-07 klockan 23.33 skrev Jeremy C. Reed:
> What man page(s) discuss that when a file is created it inherits the group 
> ID of its directory (instead of the gid of the creating process)?

open(2)

> Linux doesn't do that by default and calls it "BSD semantics". Linux can 
> enable that with S_ISGID bit.
> 
> Can it be disabled on a BSD system? In other words on NetBSD, how to make 
> it so new files are automatically created with the group of creating 
> process (instead of the group of the directory)? I am just curious and I 
> don't need this.

Don't seem to be a way of doing that. (by reading the man-pages anyway)

	Johnny

Jeremy C. Reed | 7 Jun 2007 23:45

Re: where are directory group permissions documented?

On Thu, 7 Jun 2007, Jeremy C. Reed wrote:

> What man page(s) discuss that when a file is created it inherits the group 
> ID of its directory (instead of the gid of the creating process)?

I answer that myself. It is clearly documented in open(2) which is linked 
from chmod(2).

Since it is not documented in same place, I assume disabling it is not 
possible.

> Linux doesn't do that by default and calls it "BSD semantics". Linux can 
> enable that with S_ISGID bit.
> 
> Can it be disabled on a BSD system? In other words on NetBSD, how to make 
> it so new files are automatically created with the group of creating 
> process (instead of the group of the directory)? I am just curious and I 
> don't need this.

  Jeremy C. Reed

Chuck Swiger | 7 Jun 2007 23:51
Picon

Re: where are directory group permissions documented?

Hi, Jeremy--

On Jun 7, 2007, at 2:33 PM, Jeremy C. Reed wrote:
> What man page(s) discuss that when a file is created it inherits  
> the group
> ID of its directory (instead of the gid of the creating process)?

It probably should be documented in chmod(1), chmod(2), and/or mount 
(8), if it isn't already.

> Linux doesn't do that by default and calls it "BSD semantics".  
> Linux can
> enable that with S_ISGID bit.

Yep, that's right.

> Can it be disabled on a BSD system? In other words on NetBSD, how  
> to make
> it so new files are automatically created with the group of creating
> process (instead of the group of the directory)? I am just curious  
> and I
> don't need this.

Does NetBSD's mount have the nosuid or suiddir options?

--

-- 
-Chuck

Christos Zoulas | 8 Jun 2007 20:22

Re: where are directory group permissions documented?

In article <Pine.NEB.4.64.0706071629130.1832 <at> glacier.reedmedia.net>,
Jeremy C. Reed <reed <at> reedmedia.net> wrote:
>What man page(s) discuss that when a file is created it inherits the group 
>ID of its directory (instead of the gid of the creating process)?
>
>Linux doesn't do that by default and calls it "BSD semantics". Linux can 
>enable that with S_ISGID bit.
>
>Can it be disabled on a BSD system? In other words on NetBSD, how to make 
>it so new files are automatically created with the group of creating 
>process (instead of the group of the directory)? I am just curious and I 
>don't need this.

There is currently no way. I wanted to change this a while ago so that
NFS interoperability between NetBSD and other systems would improve,
but I feared the wrath of the BSD gods.

christos

Huub | 9 Jun 2007 09:03
Picon

Updating gnome 2.16 -> 2.18

Hi,

Running 3.1/i396, I want to update gnome. Reading chapter 22.3 in the 
Docs, I find it's no easy task. I thought there used to be a script 
taking care of it. Am I correct (if yes: where can I find it?)

Thanks,

Huub


Gmane