How can I use my kernel on DP2?

Hi, everybody, I found a very strange thing about kernel on DP2. I do not know why I compiled my kernel, but I can not boot with it? Current# uname -a FreeBSD Current.wtwh.com.cn 5.0-DP2 FreeBSD 5.0-DP2 #1: Sat Nov 16 13:38:33 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386

Re: setfacl requirements?

Hi, everybody, From Robert N M Watson (1) UFS_ACL isn't enabled Yes, I am sure that in my kernel config: options UFS_ACL options UFS_EXTATTR options UFS_EXTATTR_AUTOSTART (2) Extended attributes aren't available on the file system (shouldn't happen for UFS2, but might happen for UFS1 if you

Another ACL problem in DP2

Hi, everybody, I have some problem when I using 'ACL'. My operations as follow: my kernel config file include: options UFS_ACL options UFS_EXTATTR options UFS_EXTATTR_AUTOSTART I want to do the ACL in the /usr filesystem. #mkdir -p /usr/.attribute/system #cd

How can I test RAIDFrame based on DEVFS GEOM?

Hi, everybody, I could not create the device name based on DEVFS. I use devfs rule apply path raidctl unhide command, but in /dev/, there is nothing about 'raidctl'. So I could not RAIDFrame. Another, I can use the 'disklabel -e da2s2' command, but I could not modify it. I need your help.

ksetest program cause the system crash!

Hi, everybody, Have somebody use the /usr/src/tools/KSE/ksetest/ksetest? I want to test about KSE. I cvsuped my box a few days ago. my kern_thread.c version is 1.66. When I use the ksetest, the box is crashed. the information as follow: Current# ./ksetest main() : 0x804c000 eip - 0x280ae973

about GEOM 'geoms' chain question

Hi, Poul-Henning This is my DP2 box's info about 'GEOM' when power on with 'boot -v'. GEOM: new disk da0 GEOM: new disk da1 GEOM: new disk da2 MBR Slice 1 on da0: 80 01 01 00 a5 fe ff 7b 3f 00 00 00 3d a8 da 00 |...{?...=...| [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):123/254/255 s:63

About gbde questions

Hi,everybody, I have some puzzles on the 'gbde' function. I saw the gbde(4), I do not understand the 'cold' true meaning. My point is that if the disk were stealed by somebody, he could not see anything in the disk unless he knows the pass-phrase. right? In the first barrier, the manual said

Re: About gbde questions

Hi Everybody, Poul-Henning Kamp write: Right. By cold disk we mean that the pass-phrase and key-material is not available. A laptop which is only suspended does _not_ meet this criteria. Thank you. Yes, you want to newfs and mount /dev/da0s1f.bde I think the -l is a mistake in the usage, it

Hi,a little question about DP2.

Hi, Everybody In the 4.x version, I can use mknod to create a device, for example: mknod raidctl c 201 0 root:operator. But in 5.0, If I use the devfs(default), I do not know how to use some command to create a device like 'mknod' doing in 4.x. Another question: In DP2: I found the disk

Re: Hi,a little question about DP2.

Dear David, From: David Wolfskill [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Hi,a little question about DP2. Date: Tue, 19 Nov 2002 18:47:39 -0800 (PST) From: kai ouyang [EMAIL PROTECTED] Date: Wed, 20 Nov 2002 10:29:16 +0800 Hi, Everybody In the 4.x version, I can use mknod

Re: Hi,a little question about DP2.

Dear smkelly, From: Sean Kelly [EMAIL PROTECTED] To: kai ouyang [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: Hi,a little question about DP2. Date: Tue, 19 Nov 2002 21:07:49 -0600 On Wed, Nov 20, 2002 at 10:29:16AM +0800, kai ouyang wrote: You can't `mknod` any device in /dev that isn't

Re: Hi,a little question about DP2.

Dear Wollman, From: Garrett Wollman [EMAIL PROTECTED] For backwards compatibility, the FreeBSD 4.x kernel would fake up the partition tables so that they would look like old (pre-slicing) FreeBSD partition tables; i.e., the starting offset of the slice would be subtracted from all of the

a queston about ACL acl_type_t

Hi, I am trying to understand the ACL implementation in FreeBSD-Current. I have a question about ACL. in acl.h, there are some acl_type_t value macro: /* * Possible valid values for acl_type_t arguments. */ #define ACL_TYPE_ACCESS 0x #define ACL_TYPE_DEFAULT 0x0001 #define

how to use the Giant?

Hi everyone, I find many system call under the control of Giant mutex, I do not know when we should call mtx_lock(Giant) and mtx_unlock(Giant). I only know it is a global mutex. normally, the two functions will occure together. But, in the /sys/dev/aac/aac.c aac_host_command(struct

Please help: why bufwait() will cause the thread status change to SSLEEP?

Dear John and everyone, I do not know the thread group means what in FreeBSD5.0.Could you give me some information?Now, I mask the code about thread group operations.When I want to get the RAIDFrame information(exist in the disk block).I can call raidread_component_label(), as the following:int

Help: from proc to thread?

Hi, Very thank your help! Now the box can boot. I have some other problems about proc and thread.From the FreeBSD5.0 viewpoint, there are real thread in kernel, there are associated with KSE.So many functions parameters change from proc to thread.There is the function in RAIDFrame in FreeBSD4.x.

Re:Help: from proc to thread?

Based on the explain of the thread: struct proc *td_proc; /* Associated process. */ in the struct thread. and refer to the CCD code. I modify this function as following: int raidlookup(path, td, vpp) char *path; struct thread *td; struct vnode **vpp; /* result */ { struct nameidata nd; struct

Help!

Hi, everybody I am working on transfer RaidFrame from FreeBSD4.x to FreeBSD5.0. Scott Long has transfered RAIDFrame from NetBSD to FreeBSD 4.x. Now, I am transfering those codes to FreeBSD5.0. This is my first strolling in FreeBSD5.0 kernel. Firstly, I transfered some codes based on the

Re:why change: from proc to thread?

and 5.0? On Mon, 27 May 2002, kai ouyang wrote: Hi,everybody I found many v_operations, such as VOP_UNLOCK, VOP_OPEN., there all have a parameter(struct proc) in FreeBSD4.x, but, there all be changed to thread in FreeBSD5.0. why? And what relation of the proc and thread ? Thank you!FreeBSD

Re:why change: from proc to thread?

kai On Mon, 27 May 2002, kai ouyang wrote: Hi,everybody I found many v_operations, such as VOP_UNLOCK, VOP_OPEN., there all have a parameter(struct proc) in FreeBSD4.x, but, there all be changed to thread in FreeBSD5.0. why? And what relation of the proc and thread ? Thank you!FreeBSD is plannig

why change: from proc to thread?

Hi,everybody I found many v_operations, such as VOP_UNLOCK, VOP_OPEN., there all have a parameter(struct proc) in FreeBSD4.x, but, there all be changed to thread in FreeBSD5.0.why? Andwhat relation of the proc and thread ? Thank you!Best RegardsOuyang Kai´ÓÍøÕ¾µÃµ½¸ü¶àÐÅÏ¢¡£MSN Explorer

How use UFS_ACL function?

Hi everyone, I has seen the manual and /sys/ufs/ufs/README.* . I add the following to the kernel conf: options UFS_EXTATTR options UFS_EXTATTR_AUTOSTART options UFS_ACL Then, I saw extattrctl and setextattr's manual. But I do not know what's meaning. For example, I has a user name Jack, who is a