Re: disklabel differences FreeBSD, DragonFly

2006-07-30 Thread Matthew Dillon
: :* Matthew Dillon ([EMAIL PROTECTED]) wrote: : : felt that 8 partitions is restrictive. My main home server has 10 : and the main DragonFly box has 11. : : There is another solution for FreeBSD folks, however. You *DO* have : four slices to play with. You can put a

Re: disklabel differences FreeBSD, DragonFly

2006-07-30 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Andreas Klemm [EMAIL PROTECTED] writes: : Incompatible to UFS's like from Sun I think we are already, so we : don't have to honour them. Remember a current thread in german BSD : group where somebody complained about FreeBSD - mounting a Sun : filesystem

VM question related to faults

2006-07-30 Thread Divacky Roman
hi, while working on SoC linuxolator project I am in a need of this: I need to do some operation on memory like mem1 = mem1 + mem2 etc. where the mem1/mem2 access can trigger fault. (memory not mapped or something) currently I solve this by using pcb_onfault. this must be done in asm (kib@ told

Re: VM question related to faults

2006-07-30 Thread Peter Jeremy
On Sun, 2006-Jul-30 12:57:32 +0200, Divacky Roman wrote: while working on SoC linuxolator project I am in a need of this: I need to do some operation on memory like mem1 = mem1 + mem2 etc. where the mem1/mem2 access can trigger fault. (memory not mapped or something) This is normally only an

Re: disklabel differences FreeBSD, DragonFly

2006-07-30 Thread Dmitry Marakasov
* Matthew Dillon ([EMAIL PROTECTED]) wrote: Oh, very cute! A terrible hack if you ask me, but cute all the same! I don't consider it a hack. Pretty expected and consistent behaviour - any block device (be it a whole disk or just a partition) is scanned by geom for magic numbers, and if any

Re: disklabel differences FreeBSD, DragonFly

2006-07-30 Thread David Gilbert
Dmitry == Dmitry Marakasov [EMAIL PROTECTED] writes: Dmitry * Matthew Dillon ([EMAIL PROTECTED]) wrote: felt that 8 partitions is restrictive. My main home server has 10 and the main DragonFly box has 11. There is another solution for FreeBSD folks, however. You *DO* have four slices to

Re: disklabel differences FreeBSD, DragonFly

2006-07-30 Thread Dmitry Marakasov
* David Gilbert ([EMAIL PROTECTED]) wrote: Dmitry About `lack' of partitions - don't forget that labels can be Dmitry nested. Just do `bsdlabel -w /dev/ad0s1e` - you'll get Dmitry /dev/ad0s1ea. Don't also forget that gpt(8) exists and seems to provide for large numbers of partitions. It

Re: VM question related to faults

2006-07-30 Thread Intron
Divacky Roman wrote: hi, while working on SoC linuxolator project I am in a need of this: I need to do some operation on memory like mem1 = mem1 + mem2 etc. where the mem1/mem2 access can trigger fault. (memory not mapped or something) currently I solve this by using pcb_onfault. this must

Re: i386 page fault clobbers error code in trap frame

2006-07-30 Thread Tijl Coosemans
On Saturday 29 July 2006 21:57, Kip Macy wrote: Looking at siginfo it isn't clear that there is a right way to provide SIGSEGV, eva, and the error code. _fault._trapno should contain the machine's error code and si_signo should contain SIGSEGV, and si_addr contains the faulting pc. Maybe one

Re: disklabel differences FreeBSD, DragonFly

2006-07-30 Thread Matthew Dillon
: : Dmitry == Dmitry Marakasov [EMAIL PROTECTED] writes: : :Dmitry * Matthew Dillon ([EMAIL PROTECTED]) wrote: : felt that 8 partitions is restrictive. My main home server has 10 : and the main DragonFly box has 11. : : There is another solution for FreeBSD folks, however. You *DO* : have four

Re: i386 page fault clobbers error code in trap frame

2006-07-30 Thread Kip Macy
si_addr doesn't contain the faulting pc, it contains the address that So either the comment is wrong, or that is a technically incorrect kludge. However, given that a number of the other fields are not filled out at all, the real objective should be to keep applications working. ---

Re: i386 page fault clobbers error code in trap frame

2006-07-30 Thread Tijl Coosemans
On Sunday 30 July 2006 21:30, Kip Macy wrote: si_addr doesn't contain the faulting pc, it contains the address that So either the comment is wrong, or that is a technically incorrect kludge. However, given that a number of the other fields are not filled out at all, the real objective

Re: VM question related to faults

2006-07-30 Thread Divacky Roman
On Sun, Jul 30, 2006 at 12:57:32PM +0200, Divacky Roman wrote: hi, while working on SoC linuxolator project I am in a need of this: I need to do some operation on memory like mem1 = mem1 + mem2 etc. where the mem1/mem2 access can trigger fault. (memory not mapped or something) to make it

Re: VM question related to faults

2006-07-30 Thread Kip Macy
From kern_umtx.c: static int _do_lock(struct thread *td, struct umtx *umtx, long id, int timo) { struct umtx_q *uq; intptr_t owner; intptr_t old; int error = 0; uq = td-td_umtxq; /* * Care must be exercised when dealing with umtx structure. It

Re: disklabel differences FreeBSD, DragonFly

2006-07-30 Thread Dag-Erling Smørgrav
Dmitry Marakasov [EMAIL PROTECTED] writes: Afaik, one is unable to boot from gpt partitions. except on EFI machines (Itanium and Intel Macs), but it is possible to combine GPT with an MBR such that you get a bootable partition (if nothing else, GEOM allows you to stick a GPT in a partition or