Re: Usage of files for config

2008-10-30 Thread Dag-Erling Smørgrav
Srinivas [EMAIL PROTECTED] writes:
 I would like to know the usage of files and files.[arch] in sys/conf.

files and options are used to determine which source files should be
included and which preprocessor macros should be defined according to
the device and option lines in the kernel config.

However, as a beginner of freebsd kernel, I would recommend that you
spend your time reading (and writing or modifying) source code, not
trying to understand the Makefiles.

DES
-- 
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


7.0R amd does not unmount USB-based UFS

2008-10-30 Thread Matthias Apitz

Hello,

I'm using the amd to mount CDFS and MSDOSFS on USB without any kind of
problems for years; now I formated a new USB key with UFS, added the
config in amd's map and encounter that it does not unmount the file
system after the configured time of 20 secs:

any idea? thanks in advance;

matthias

details:

# cat /etc/amdmaps/amd.ufs
ufs   type:=ufs;fs:=/mnt/ufs;dev:=/dev/da0s1a;opts:=rw


# tail -f /var/log/amd
Oct 30 12:06:04 rebelion amd[23331]/info:  /f: disabling nfs congestion window
Oct 30 12:06:04 rebelion amd[23328]/info:  initializing amd.conf map 
/etc/amdmaps/amd.usb of type file
Oct 30 12:06:04 rebelion amd[23328]/info:  first time load of map 
/etc/amdmaps/amd.usb succeeded
Oct 30 12:06:04 rebelion amd[23328]/info:  /etc/amdmaps/amd.usb mounted fstype 
toplvl on /u
Oct 30 12:06:04 rebelion amd[23328]/info:  initializing amd.conf map 
/etc/amdmaps/amd.cdrom of type file
Oct 30 12:06:04 rebelion amd[23328]/info:  first time load of map 
/etc/amdmaps/amd.cdrom succeeded
Oct 30 12:06:04 rebelion amd[23328]/info:  /etc/amdmaps/amd.cdrom mounted 
fstype toplvl on /a
Oct 30 12:06:04 rebelion amd[23328]/info:  initializing amd.conf map 
/etc/amdmaps/amd.ufs of type file
Oct 30 12:06:04 rebelion amd[23328]/info:  first time load of map 
/etc/amdmaps/amd.ufs succeeded
Oct 30 12:06:04 rebelion amd[23328]/info:  /etc/amdmaps/amd.ufs mounted fstype 
toplvl on /f

entering the dir /f/ufs mounts the FS:

Oct 30 12:08:02 rebelion amd[23328]/map:   Trying mount of /dev/da0s1a on 
/f/usf fstype ufs
Oct 30 12:08:02 rebelion amd[23328]/info:  /dev/da0s1a mounted fstype ufs on 
/mnt/ufs

here another example of entering /a/cdrom which gets unmounted after 20
secs:

Oct 30 12:54:49 rebelion amd[23328]/map:   Trying mount of /dev/acd0 on 
/a/cdrom fstype cdfs
Oct 30 12:54:50 rebelion amd[23328]/error: /cdrom: mount: Input/output error
Oct 30 12:54:50 rebelion amd[23328]/error: mount_cdfs: Input/output error
Oct 30 12:54:59 rebelion amd[23328]/map:   Trying mount of /dev/acd0 on 
/a/cdrom fstype cdfs
Oct 30 12:55:00 rebelion amd[23328]/info:  /dev/acd0 mounted fstype cdfs on 
/cdrom
Oct 30 12:55:20 rebelion amd[23328]/info:  /dev/acd0 unmounted fstype cdfs from 
/cdrom


the UFS stays mounted forever:

$ mount
/dev/ad4s1a on / (ufs, local)
devfs on /dev (devfs, local)
/dev/ad4s1e on /tmp (ufs, local, soft-updates)
/dev/ad4s1f on /usr (ufs, local, soft-updates)
/dev/ad4s1d on /var (ufs, local, soft-updates)
[EMAIL PROTECTED]:/u on /u (nfs)
[EMAIL PROTECTED]:/a on /a (nfs)
[EMAIL PROTECTED]:/f on /f (nfs)
/dev/da0s1a on /mnt/ufs (ufs, local)


a umount by hand helps:

# umount /mnt/ufs
# mount
/dev/ad4s1a on / (ufs, local)
devfs on /dev (devfs, local)
/dev/ad4s1e on /tmp (ufs, local, soft-updates)
/dev/ad4s1f on /usr (ufs, local, soft-updates)
/dev/ad4s1d on /var (ufs, local, soft-updates)
[EMAIL PROTECTED]:/u on /u (nfs)
[EMAIL PROTECTED]:/a on /a (nfs)
[EMAIL PROTECTED]:/f on /f (nfs)

-- 
Matthias Apitz
Manager Technical Support - OCLC GmbH
Gruenwalder Weg 28g - 82041 Oberhaching - Germany
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e [EMAIL PROTECTED] - w http://www.oclc.org/ http://www.UnixArea.de/
b http://gurucubano.blogspot.com/
A computer is like an air conditioner, it stops working when you open Windows
Una computadora es como aire acondicionado, deja de funcionar si abres Windows
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


process hibernation and process descriptor table

2008-10-30 Thread aniket pansare
hi guys
i am doing a project on process hibernation.
i am new to linux and i want u to tell me how can i print the contents of a
process descriptor table.

i had a look at the softwares like cryopid and BLCR but i am not able to get
it at this stage.

Any  suggestions about how i should go about the project.



Aniket Pansare
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: process hibernation and process descriptor table

2008-10-30 Thread Dag-Erling Smørgrav
aniket pansare [EMAIL PROTECTED] writes:
 i am new to linux and i want u to tell me how can i print the contents of a
 process descriptor table.

You should probably ask some Linux people.

DES
-- 
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


open(2) and O_NOATIME

2008-10-30 Thread Jeremy Chadwick
I've recently been reading about Linux's O_NOATIME flag to open(2), and
I'm curious why we haven't implemented this.  There seem to be a lot of
good reasons to implement such a thing.

Chances are it's due to lack of time/interest, which is expected, but I
was wondering if there were other reasons.

I realise mount's noatime trumps this, but there are lots of scenarios
where atime is desired as a default, but disabled in specific cases.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: process hibernation and process descriptor table

2008-10-30 Thread jT
Hello,
   This list is unrelated to linux, it was designed for technical
discussion concerning the FreeBSD operating system: www.freebsd.org.
If you are looking for linux help I recommend you check kernel.org for
documentation and online forums.

On 10/30/08, aniket pansare [EMAIL PROTECTED] wrote:
 hi guys
 i am doing a project on process hibernation.
 i am new to linux and i want u to tell me how can i print the contents of a
 process descriptor table.

 i had a look at the softwares like cryopid and BLCR but i am not able to get
 it at this stage.

 Any  suggestions about how i should go about the project.



 Aniket Pansare
 ___
 freebsd-hackers@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
 To unsubscribe, send any mail to [EMAIL PROTECTED]



-- 
/jT
http://git.zen-sources.org/?p=kernel/zenmm.git;a=summary
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


memtest86+ can not link: binutils issue?

2008-10-30 Thread Andriy Gapon

0.
FreeBSD 7.1-PRERELEASE r184195 i386
$ ld -v
GNU ld version 2.15 [FreeBSD] 2004-05-23

1. obtain and extract
http://www.memtest.org/download/2.01/memtest86+-2.01.bin.gz

2. run gmake:
$ gmake
gcc -E -traditional head.S -o head.s
as -32   -o head.o head.s
gcc -c -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC -fno-strict-aliasing reloc.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o main.o main.c
gcc -c -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding test.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o init.o init.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o lib.o lib.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o patn.o patn.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o screen_buffer.o screen_buffer.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o config.o config.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o linuxbios.o linuxbios.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o memsize.o memsize.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o pci.o pci.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o controller.o controller.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o random.o random.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o extra.o extra.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o spd.o spd.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o error.o error.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o dmi.o dmi.c
ld --warn-constructors --warn-common -static -T memtest_shared.lds \
-o memtest_shared head.o reloc.o main.o test.o init.o lib.o
patn.o screen_buffer.o config.o linuxbios.o memsize.o pci.o controller.o
random.o extra.o spd.o error.o dmi.o  \
ld -shared -Bsymbolic -T memtest_shared.lds -o memtest_shared
head.o reloc.o main.o test.o init.o lib.o patn.o screen_buffer.o
config.o linuxbios.o memsize.o pci.o controller.o random.o extra.o spd.o
error.o dmi.o
head.o(.text+0x7): In function `startup_32':
: undefined reference to `_GLOBAL_OFFSET_TABLE_'
Segmentation fault (core dumped)
gmake: *** [memtest_shared] Error 139


Not only linking fails, but ld even crashes.
Things are more complicated than usual because of the custom linker
script memtest_shared.lds.

The same compiles/links nicely on Fedora 9.
$ ld -v
GNU ld version 2.18.50.0.6-5.fc9 20080403


Can anybody suggest anything about this problem?
If somebody is working on newer version of binuitls for FreeBSD I can
help as a tester.

-- 
Andriy Gapon
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: memtest86+ can not link: binutils issue?

2008-10-30 Thread Peter Jeremy
On 2008-Oct-30 18:08:35 +0200, Andriy Gapon [EMAIL PROTECTED] wrote:
1. obtain and extract
http://www.memtest.org/download/2.01/memtest86+-2.01.bin.gz

This is a compressed bootable image and can't be compiled.  Possibly
you mean http://www.memtest.org/download/2.01/memtest86+-2.01.tar.gz

2. run gmake:
$ gmake
gcc -E -traditional head.S -o head.s
as -32   -o head.o head.s
gcc -c -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC -fno-strict-aliasing reloc.c
gcc -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding -fPIC   -c -o main.o main.c
gcc -c -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin
-ffreestanding test.c

Blows up at this point for me:
gcc -c -Wall -march=i486 -m32 -Os -fomit-frame-pointer -fno-builtin 
-ffreestanding test.c
test.c:14:20: error: sys/io.h: No such file or directory
test.c: In function 'beep':
test.c:1410: warning: implicit declaration of function 'outb_p'
test.c:1410: warning: implicit declaration of function 'inb_p'
test.c:1417: warning: implicit declaration of function 'outb'
gmake: *** [test.o] Error 1

I can't find sys/io.h in CVS or any declarations for outb_p or inb_p
in my source tree.

ld --warn-constructors --warn-common -static -T memtest_shared.lds \
-o memtest_shared head.o reloc.o main.o test.o init.o lib.o
patn.o screen_buffer.o config.o linuxbios.o memsize.o pci.o controller.o
random.o extra.o spd.o error.o dmi.o  \
ld -shared -Bsymbolic -T memtest_shared.lds -o memtest_shared
head.o reloc.o main.o test.o init.o lib.o patn.o screen_buffer.o
config.o linuxbios.o memsize.o pci.o controller.o random.o extra.o spd.o
error.o dmi.o
head.o(.text+0x7): In function `startup_32':
: undefined reference to `_GLOBAL_OFFSET_TABLE_'
Segmentation fault (core dumped)
gmake: *** [memtest_shared] Error 139

I can't help here.  _GLOBAL_OFFSET_TABLE_ is related to the binutils
PIC support and it appears that the linker doesn't like the code (in
head.S) is explicitly referencing it.

Not only linking fails, but ld even crashes.

I agree this shouldn't happen.

Can anybody suggest anything about this problem?

It looks like stand-alone PIC code on FreeBSD needs some different
incantations to Linux.  My understanding is that several of the
i386 bootstraps are relocatable so you might like to peruse the
code in /usr/src/sys/boot/i386 for ideas.

-- 
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.


pgpmHMDH1fDJe.pgp
Description: PGP signature


Re: open(2) and O_NOATIME

2008-10-30 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jeremy Chadwick wrote:
 I've recently been reading about Linux's O_NOATIME flag to open(2), and
 I'm curious why we haven't implemented this.  There seem to be a lot of
 good reasons to implement such a thing.
 
 Chances are it's due to lack of time/interest, which is expected, but I
 was wondering if there were other reasons.
 
 I realise mount's noatime trumps this, but there are lots of scenarios
 where atime is desired as a default, but disabled in specific cases.

Em...  Allowing administrators to disable NOATIME would be a good thing,
but wouldn't allowing arbitrary program to decide whether atime should
be changed, be a serious security disaster?

Disclaimer: I'm not a big atime fan myself, actually I disable atime on
a lot of my servers for performance reasons :)

Cheers,
- --
Xin LI [EMAIL PROTECTED]  http://www.delphij.net/
FreeBSD - The Power to Serve!
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkkKaooACgkQi+vbBBjt66CImQCgj51GGHXFaGhsFk4fAAWhmfV5
+s4An2Hn2TCVhqXEpzEL3xNwxy6YE84M
=n7f/
-END PGP SIGNATURE-
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: open(2) and O_NOATIME

2008-10-30 Thread Joerg Sonnenberger
On Thu, Oct 30, 2008 at 07:16:42PM -0700, Xin LI wrote:
 Em...  Allowing administrators to disable NOATIME would be a good thing,
 but wouldn't allowing arbitrary program to decide whether atime should
 be changed, be a serious security disaster?

Think of backup programs.

Joerg
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: open(2) and O_NOATIME

2008-10-30 Thread Jeremy Chadwick
On Thu, Oct 30, 2008 at 07:16:42PM -0700, Xin LI wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Jeremy Chadwick wrote:
  I've recently been reading about Linux's O_NOATIME flag to open(2), and
  I'm curious why we haven't implemented this.  There seem to be a lot of
  good reasons to implement such a thing.
  
  Chances are it's due to lack of time/interest, which is expected, but I
  was wondering if there were other reasons.
  
  I realise mount's noatime trumps this, but there are lots of scenarios
  where atime is desired as a default, but disabled in specific cases.
 
 Em...  Allowing administrators to disable NOATIME would be a good thing,
 but wouldn't allowing arbitrary program to decide whether atime should
 be changed, be a serious security disaster?

How?

There's only one condition I can think of: where a system administrator
is, for some reason, relying upon atimes as a form of proof of something
bad happening (which is a horrible concept in general, being as the
amount of false positives seen would be tremendous; using atime as a
security auditing method is stupid).

If that's what you were referring to, then possibly making O_NOATIME
only to root would be a suitable compromise.

 Disclaimer: I'm not a big atime fan myself, actually I disable atime on
 a lot of my servers for performance reasons :)

I can't disable atime on any systems I maintain, because they all
provide access to classic UNIX mbox spools where atime is used to
determine if new mail has arrived.  The instant filesystem-level
backups run, atime is lost, and users have no way of knowing if
they have new mail or not.  Switching to Maildir is an option, but
the performance hit of readdir() + stat() on thousands of files is
tremendous (which is why mail clients like mutt have features like
header caching via Oracle/Sleepycat DB).

Anyway, I just was reading about it and realise that a lot of backup
solutions out there can make use of O_NOATIME if available, which it
isn't on FreeBSD.

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]