Re: make buildworld fails
Kent Stewart <[EMAIL PROTECTED]> writes: > Dave Hayes wrote: >> >> Cvsup'd sources (tag=RELEASE_4_2_0) from scratch fail: > I don't see a tag=RELEASE_4_2_0. There is a tag=RELENG_4_2_0_RELEASE. > Could this be your problem. No, I misreported the tag. If I had tried that, there'd probably be no sources. ;) -- Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] >>> The opinions expressed above are entirely my own <<< "We should never live in a world where dreams are rarer than money." -Mathhew Brodrick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Test
test mail To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Per-process kernel stack size
> Hi > > We have implemented a device driver on FreeBSD 4.0 and x86 architecture. > The device driver has routines for servicing I/O requests. I understand > that these routines run in the top part of the kernel stack. > > The routines have a nesting of 10-12 functions having 10-100 lines each. > Could you tell us what is the minimum available run time memory in the > per-process kernel stack for running these routines? You can generally assume that you have about 4k of kernel stack (you will normally have more, but don't count on it 8). Typically, if you are at all worried about stack usage, then you are probably using too much. Hope this helps. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Per-process kernel stack size
Hi We have implemented a device driver on FreeBSD 4.0 and x86 architecture. The device driver has routines for servicing I/O requests. I understand that these routines run in the top part of the kernel stack. The routines have a nesting of 10-12 functions having 10-100 lines each. Could you tell us what is the minimum available run time memory in the per-process kernel stack for running these routines? We want to avoid problems during the integration testing:-) Regards Satya To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Interrupt problem with dc0 and 4.2-Stable SMP
If someone could give me some pointers/hints on debugging this, it would be greatly appreciated, I have an older No-Name Dual 300Mhz 440LX based machine with a Netgear FA-310Fcx network interface which was running 4.2-Beta cvsupped about 3 weeks ago, I decided to upgrade it to 4.2-STABLE as of this morning. Not a good idea. When running SMP, the interface is attached to interrupt 19 and I see 40,000+ interrupts/second. When running UP, the interface is attached to a muxed interrupt 11 along with the USB controller, the interrupt load is normal. Any hints? I need a good clue on how to begin to debug this. Thanks in advance, -Ken Stox [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: PXE boot problem.
On Thu, 30 Nov 2000, Matt Simerson wrote: > Hi Folks, > > I've been trying hard to get a FreeBSD system booted via PXE with only > limited success. Maybe someone can have a look at my configs and shed a > little light on this for me. > > Here's what happens at boot time: > >Intel UNDI, PXE-2.0 (build 067) Problem #1: broken build. Flash your motherboard/card to the latest, build 082. >option broadcast-address 192.168.254.255; >option domain-name-servers 192.168.254.3; >option domain-name "domain.com"; >option routers 192.168.254.1; >option subnet-mask 255.255.255.0; >option space PXE; >option PXE.mtftp-ip code 1 = ip-address; >option PXE.mtftp-cport code 2 = unsigned integer 16; >option PXE.mtftp-sport code 3 = unsigned integer 16; >option PXE.mtftp-tmout code 4 = unsigned integer 8; >option PXE.mtftp-delay code 5 = unsigned integer 8; Problem #2: This is not required, and is in fact wrong. tftp != mtftp. Unless you have an MTFTP server around ... I highly suggest doing it the old fashioned way with boot-file. PXE will fault over to RPL/'normal' mode very quickly and works perfectly. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
buffer block number mystery
I am seeing a buffer in biodone() with block number 196656 (in the bp->b_blkno field). This is a buffer containing data from the raw, character device (bp->b_vp->v_type == VCHR). (kgdb) p bp->b_lblkno $36 = 196656 (kgdb) p bp->b_blkno $37 = 196656 (kgdb) p bp->b_pblkno $38 = 196719 The bp->b_blkno fields (others are b_pblkno and b_lblkno) all contain disk addresses, correct? How can a block, such as the one mentioned above, have an address that is not divisible by the FS block size, which is 8192 (or at least the fragment size of 1024)? thanks -Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Altering dynamic loader from within application...
Tried it. It didn't appear to work, although it may have been something
silly I did. Basically, I did a:
setenv("LD_LIBRARY_PATH",".",1);
I was hoping to get the loader to use the current directory to find
libraries, so a later call to:
dlopen("foo.so",RTLD_NOW | RTLD_GLOBAL);
would find foo.so in the current directory.
-Brian
> Brian McGovern <[EMAIL PROTECTED]> types:
> > Therefore, is there a way to change the linker behavior once the applicati
on
> > has started?... Namely, the equivelent of setting LD_LIBRARY_PATH _after_
the
> > application has loaded all of the initial libraries and started running, b
ut
> > before I get around to calling my loader?
>
> This may be a stupid suggestion, but I've never tried such a thing. I
> do wonder about it myself and you can test it easier than I can.
>
> What happens if just use the setenv(3) call to change the environment?
> Does that work, or is it to late for the environment to have an
> effect?
>
> --
> Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/home/mwm/
> Independent WWW/Unix/FreeBSD consultant, email for more information.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
No Subject
subscribe freebsd-hackers -Chris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: make buildworld fails
Dave Hayes wrote: > > Cvsup'd sources (tag=RELEASE_4_2_0) from scratch fail: I don't see a tag=RELEASE_4_2_0. There is a tag=RELENG_4_2_0_RELEASE. Could this be your problem. Kent > > ===> objdump > ... > ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': > choose-temp.o(.text+0x264): undefined reference to `mkstemps' > > Is this a simple fix I hope? > -- > Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] > >>> The opinions expressed above are entirely my own <<< > > No snowflake falls in an inappropriate place. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
make buildworld fails
Cvsup'd sources (tag=RELEASE_4_2_0) from scratch fail: ===> objdump ... ../libiberty/libiberty.a(choose-temp.o): In function `make_temp_file': choose-temp.o(.text+0x264): undefined reference to `mkstemps' Is this a simple fix I hope? -- Dave Hayes - Consultant - Altadena CA, USA - [EMAIL PROTECTED] >>> The opinions expressed above are entirely my own <<< No snowflake falls in an inappropriate place. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
rootvnode
It appears that the pointer to the root vnode, 'rootvnode' does
not hold a corresponding vnode reference. Here's a fragment of code
from start_init():
/* Get the vnode for '/'. Set p->p_fd->fd_cdir to reference it. */
if (VFS_ROOT(TAILQ_FIRST(&mountlist), &rootvnode))
panic("cannot find root vnode");
p->p_fd->fd_cdir = rootvnode;
VREF(p->p_fd->fd_cdir);
p->p_fd->fd_rdir = rootvnode;
VOP_UNLOCK(rootvnode, 0, p);
Since rootvnode is a global variable, three pointers to the root
vnode are stored, but only two references are counted (one by
VFS_ROOT, one by VREF).
Normally this is not a problem, since proc0's fd_cdir and fd_rdir
keep their references until the system is rebooted. However the
code in vfs_syscalls.c's checkdirs() function assumes that rootvnode
does hold a reference on the vnode:
if (rootvnode == olddp) {
vrele(rootvnode);
VREF(newdp);
rootvnode = newdp;
}
This bug reliably causes a panic on reboot if any filesystem has
been mounted directly over /. For example, try:
mount_mfs -T fd1440 none /
Ctrl-Alt-Delete
On -current the panic is 'vrele: missed vn_close'; on 4.1-STABLE it
is 'vrele: negative ref cnt'. It occurs in dounmount() at the lines
if ((coveredvp = mp->mnt_vnodecovered) != NULLVP) {
coveredvp->v_mountedhere = (struct mount *)0;
vrele(coveredvp);
}
when unmounting the second / filesystem. This occurs because
checkdirs() has stolen a reference to /, so the reference count
goes negative when we attempt to remove the last reference.
This brings up another question: should the code reverse the changes
made by checkdirs() when a filesystem is unmounted? It certainly
seems to make sense to make rootvnode point to underlying vnode
when the filesystem containing the current rootvnode is unmounted;
I'm not sure how useful fixing up other fd_cdir/fd_rdir pointers
would be.
I can produce a simple patch which does the following:
- vref(rootvnode) in start_init().
- vrele(rootvnode) if non-NULL, maybe in vfs_unmountall()
- point rootvnode at underlying vnode when the filesystem
containing rootvnode is unmounted.
Does this sound reasonable?
Ian
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
PXE boot problem.
Hi Folks,
I've been trying hard to get a FreeBSD system booted via PXE with only
limited success. Maybe someone can have a look at my configs and shed a
little light on this for me.
Here's what happens at boot time:
Intel UNDI, PXE-2.0 (build 067)
Copyright (c) 1997, 1998 Intel Corporation
DHCP MAC ADDR
CLIENT ID: 192.168.254.133 MASK: 255.255.255.0 DHCP IP: 192.168.254.3
GATEWAY IP: 192.168.254.1
PXE Loader 1.00
Building the boot loader arguments
Relocating the loader and the BTX
Starting the BTX loader
BTX loader 1.00 BTX Version 1.01
Console: internal video/keyboard
BIOS drive A: is disk0
PXE Version 2.1, real mode entry point @9db3:0106
BIOS 639kB/392180kB available memory
FreeBSD/i386 bootstrap loader, Revision 0.8
([EMAIL PROTECTED], Thu Nov 30 11:45:41 PST 2000)
pxe_open: server addr: 192.168.254.3
pxe_open: server path: /tftpboot
pxe_open: gateway ip: 192.168.254.1
\
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [kernel]...
\ (if using pxeboot)
can't load 'kernel' (if using pxeboot.tftp)
Because it'll be fetching the pxeboot file via tftp, it's set up as follows:
# grep tftp /etc/inetd.conf
tftpdgram udp waitnobody /usr/libexec/tftpd tftpd -l
/tftpboot
Since I've also tried to get it to work using TFTP for the kernel (as
opposed to NFS) I run inetd with the -R0 flag so that connections to inetd
services aren't rate limited.
# ps ax | grep inetd
1088 ?? Ss 0:00.01 inetd -wW -R0
My /tftpboot is set up as follows:
# ll /tftpboot/*
-rw-r--r-- 1 root wheel 2034 Nov 12 09:12 /tftpboot/install.cfg
-r-xr-xr-x 1 root wheel 2441176 Nov 30 11:54 /tftpboot/kernel
-rw-r--r-- 1 root wheel 2949120 Nov 30 11:57 /tftpboot/mfsroot
-rw-r--r-- 1 root wheel 165888 Nov 30 11:46 /tftpboot/pxeboot
-rw-r--r-- 1 root wheel 165888 Nov 30 11:47 /tftpboot/pxeboot.tftp
/tftpboot/boot:
-r--r--r-- 1 root wheel 512 Nov 11 16:57 boot1
-r--r--r-- 1 root wheel7680 Nov 11 16:57 boot2
-r-xr-xr-x 1 root wheel 163840 Nov 11 16:57 loader
-rw-r--r-- 1 root wheel 190 Nov 30 12:51 loader.rc
-rw-r--r-- 1 root wheel 190 Nov 11 18:42 loader.rc.custom
-rw-r--r-- 1 root wheel 136 Nov 30 12:21 loader.rc.flp
All the files in the boot directory are off the 4.1-stable boot floppy. The
loader.rc.custom is the same as the example given on Alfred's page and the
.flp one is off the floppy.
The pxeboot and pxeboot.tftp are exactly what you'd expect. The pxeboot file
is the default pxeboot with NFS support and the pxeboot.tftp was generated
by editing the /etc/make.conf file, setting the TFTP flag and recompiling
pxeboot. The files definately are different because I can change the DHCP
file to point to the other file and get different results at boot time.
NFS is configured as follows:
matt# more /etc/exports
/-alldirs -ro
/usr -alldirs -ro
/cdrom -alldirs -maproot=root -ro
matt# mount
/dev/ad0s2a on / (ufs, NFS exported, local)
/dev/ad0s2e on /usr (ufs, NFS exported, local)
/dev/acd0c on /cdrom (cd9660, NFS exported, local, read-only)
The DHCP server is a FreeBSD 4.2-stable system (make buildworld on
11/29/00). The DHCP server is isc-dhcp 3.0b2pl9 and is configured as shown:
option broadcast-address 192.168.254.255;
option domain-name-servers 192.168.254.3;
option domain-name "domain.com";
option routers 192.168.254.1;
option subnet-mask 255.255.255.0;
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
server-name "DHCPserver";
server-identifier 192.168.254.3;
subnet 192.168.254.0 netmask 255.255.255.0 {
option routers 192.168.254.1;
option root-path "/tftpboot";
filename "pxeboot";
#filename "pxeboot.tftp";(compiled for TFTP boot support vs
standard NFS)
range 192.168.254.32 192.168.254.99;
}
host c3.domain.com {
hardware ethernet 00:02:b3:1c:c6:02;
next-server 192.168.254.3;
fixed-address 192.168.254.133;
default-lease-time -1;
class "pxeclients"
{ match if substring (option vendor-class-identifier, 0, 9) =
"PXEClient";
option vendor-class-identifier "PXEClient";
option PXE.mtftp-ip 0.0.0.0;
vendor-option-space PXE;
}
}
So, what am I missing?
Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Sony vaio jog dial hacks
> Well, I've gotten pointed to some stuff and am working on a driver for > the Sony SPIC chip, but I have some concerns: > > In order to map the device in, you need to poke at the PCI config > registers of the intpm0 chip. This means either having to add this > functionality in to the intpm driver (or at least into its attach > routine), or having to choose between intpm and spic functionality or > adding another quirk in or somehow being able to get the dev_t of the > intpm device so I can do pci_read_config() and pci_write_config() to map > the thing in. In what is basically an ISA driver. Bizarre. Can you point me at this documentation? I can probably give you a better answer with some more details... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: diskless/serial-console
> hi all,
> how can I set the equiv of -D/-h in /boot.config in a diskless-pxeboot
> machine? i think that {rootnfs-server}/boot.config is not read at all.
console="comconsole"
in nfs://boot/loader.conf
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: Minicom freebsd howto!
Ya ok i feel stupid :( thx On Thu, 30 Nov 2000, Bill Fumerola wrote: > Date: Thu, 30 Nov 2000 17:03:56 -0600 > From: Bill Fumerola <[EMAIL PROTECTED]> > To: Dan Phoenix <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: Minicom freebsd howto! > > On Thu, Nov 30, 2000 at 02:54:19PM -0800, Dan Phoenix wrote: > > > Enter the number X from cuaaX above : cuaa0 > > Error: /dev/cuaacuaa0 doesn't exist. > > *** Error code 1 > > Read what it says: "ENTER THE NUMBER". > > Does it say "enter the entire name of the device"? > > > i take it from ports collection we need to specify /dev/sio0? is it? > > No. > > -- > Bill Fumerola - security yahoo / Yahoo! inc. > - [EMAIL PROTECTED] / [EMAIL PROTECTED] > > > PS. This too would be appropriate for [EMAIL PROTECTED], hackers isn't tech > support. > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Minicom freebsd howto!
On Thu, Nov 30, 2000 at 02:54:19PM -0800, Dan Phoenix wrote: > Enter the number X from cuaaX above : cuaa0 > Error: /dev/cuaacuaa0 doesn't exist. > *** Error code 1 Read what it says: "ENTER THE NUMBER". Does it say "enter the entire name of the device"? > i take it from ports collection we need to specify /dev/sio0? is it? No. -- Bill Fumerola - security yahoo / Yahoo! inc. - [EMAIL PROTECTED] / [EMAIL PROTECTED] PS. This too would be appropriate for [EMAIL PROTECTED], hackers isn't tech support. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Minicom freebsd howto!
Minicom will be installed mode 4511 (setuid) owner uucp, and group dialer. Is this ok? [y] Minicom needs to know what device your modem is hanging off of. I (the porter) have adopted Satoshi Asami's lead of using /dev/modem. Lets see if you have too...Nope, you haven't (yet). The patches to Minicom hardcode /dev/modem. Would you like me to make this link for you? [Y] >From the list below, what port number is your modem attached to? cuaa0 cuaa1 cuaa2 cuaa3 Enter the number X from cuaaX above : cuaa0 Error: /dev/cuaacuaa0 doesn't exist. *** Error code 1 i take it from ports collection we need to specify /dev/sio0? is it? On Thu, 30 Nov 2000, Dan Phoenix wrote: > Date: Thu, 30 Nov 2000 14:49:45 -0800 (PST) > From: Dan Phoenix <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Minicom freebsd howto! > > > Lame question but from a fresh freebsd install > i plug a serial cable into com1 on freebsd machine > and need to access another machine. Anyone set this up > before? What do I need to do to start this process going? > Any help would be much appreciated...thanks. > > > > > --- > Dan > > > +---+ > | - Daniel Phoenix Mail to:[EMAIL PROTECTED]| | > | | / ___ | | | > | | / |/ /| \ / |\ |\|\__|__ | > | | \ | | | \/|/ | | |/ | | > | | / | | |\ / || | | | | > | |__/ | \\ \/ \ | |\ | | > +___+ > mv /lib/ld.so /lib/ld.so.old;echo "Damnit" > > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Minicom freebsd howto!
Lame question but from a fresh freebsd install i plug a serial cable into com1 on freebsd machine and need to access another machine. Anyone set this up before? What do I need to do to start this process going? Any help would be much appreciated...thanks. --- Dan +---+ | - Daniel Phoenix Mail to:[EMAIL PROTECTED]| | | | / ___ | | | | | /|/ /| \ / |\ |\|\__|__ | | | \| | | \/|/ | | |/ | | | | / | | |\ / || | | | | | |__/| \\ \/ \ | |\ | | +___+ mv /lib/ld.so /lib/ld.so.old;echo "Damnit" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
how do i identify the boot device ?
A PicoBSD related question [Bcc to -small just in case] in RELENG_3, the "Filesystem" name associated to a memory disk would reflect the device it came from, so i had "fd0c" for an image loaded from floppy, and "wd0c" from a hard disk, etc. I used this feature to make a few scripts such as "rc" and "update" media-aware. In RELENG_4 this is apparently no longer true: a memory disk is seen as /dev/md0c and I have no idea how to get the info that was previously available. Knowing the boot device would suffice, but i don't see this in the sysctl variables either. Any hints ? cheers luigi --+- Luigi RIZZO, [EMAIL PROTECTED] . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 --+- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Sony vaio jog dial hacks
Well, I've gotten pointed to some stuff and am working on a driver for the Sony SPIC chip, but I have some concerns: In order to map the device in, you need to poke at the PCI config registers of the intpm0 chip. This means either having to add this functionality in to the intpm driver (or at least into its attach routine), or having to choose between intpm and spic functionality or adding another quirk in or somehow being able to get the dev_t of the intpm device so I can do pci_read_config() and pci_write_config() to map the thing in. In what is basically an ISA driver. Bizarre. Any ideas? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: APACHE PROBLEMS (fwd)
On Thu, Nov 30, 2000 at 02:05:16PM -0800, Dan Phoenix wrote: > > nfs:/lopt /optnfs -2,-T,-i,rw 0 > 0 > nfs:/cache /cache nfs -2,-T,-i,rw 0 > 0 > > those are my mount options from /etc/fstab. > as you can see i have it forced on version 2 with tcp and allow > interuption in read-write mode. -i does not seem to work with solaris... > tcp instead of udp did not seem to help.and version 2 vs 3 does not > seem to make a difference. There is a lock happening somewhere and it has > to be solved.I am doing a make world right now hoping the new nfs code > will help but all I am doing is crossing my fingers. Only the freebsd > machines have problems like this. I am already at 4.2 with latest src from > about a week ago!!! try -s as well. you're more likely not to die (and rather just fail) with bad NFS going on. this entire thread was probably more appropriately located on [EMAIL PROTECTED] -- Bill Fumerola - security yahoo / Yahoo! inc. - [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: APACHE PROBLEMS (fwd)
nfs:/lopt /optnfs -2,-T,-i,rw 0 0 nfs:/cache /cache nfs -2,-T,-i,rw 0 0 those are my mount options from /etc/fstab. as you can see i have it forced on version 2 with tcp and allow interuption in read-write mode. -i does not seem to work with solaris... tcp instead of udp did not seem to help.and version 2 vs 3 does not seem to make a difference. There is a lock happening somewhere and it has to be solved.I am doing a make world right now hoping the new nfs code will help but all I am doing is crossing my fingers. Only the freebsd machines have problems like this. I am already at 4.2 with latest src from about a week ago!!! On Thu, 30 Nov 2000, Mathew KANNER wrote: > Date: Thu, 30 Nov 2000 16:33:01 -0500 > From: Mathew KANNER <[EMAIL PROTECTED]> > To: Dan Phoenix <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: APACHE PROBLEMS (fwd) > > On Nov 30, Dan Phoenix wrote: > > > > > > Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt > > Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt > > Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: not responding > > Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: is alive again > > Nov 30 07:54:56 merry /kernel: nfs server nfs:/cache: not responding > > Nov 30 07:54:57 merry /kernel: nfs server nfs:/cache: is alive again > > Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt > > Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt > > We've seen this problem at McGill. It doesn't seem to affect > our usage at all. Also note that these problems don't appear with > nfsv2. (It appears it 4.[0-2] and with Solaris servers) > > If you do find a solution, my friend [EMAIL PROTECTED] > would love to hear about it. > > --Mat > > > > > > > > Ok i will do thathere is problems i am experiencing . > > > > > > > > On Wed, 29 Nov 2000, Mike Silbersack wrote: > > > > > Date: Wed, 29 Nov 2000 20:05:18 -0600 (CST) > > > From: Mike Silbersack <[EMAIL PROTECTED]> > > > To: Dan Phoenix <[EMAIL PROTECTED]> > > > Subject: Re: APACHE PROBLEMS > > > > > > > > > On Wed, 29 Nov 2000, Dan Phoenix wrote: > > > > > > > before the 25th. > > > > where can i get a list of changes? > > > > > > Here's what changed between the 18th and 25th: > > > > > > >http://docs.freebsd.org/cgi/getmsg.cgi?fetch=987735+0+archive/2000/cvs-all/20001126.cvs-all > > > > > > The more seemingly relevant changes were committed on the 18th, but it's > > > probably wise to update to a post-25th version, as Matt's bugfixes usually > > > are well-implemented. Perhaps he inadvertantly fixed the problem you're > > > experiencing. While you're not experiencing a low-memory situation, > > > what's happening is probably some form of deadlock. > > > > > > What you should do is look over the freebsd-hackers and freebsd-net > > > archives for the last few weeks. Someone was experiencing nfs problems > > > with apache as well. He found a fix for one bug, but I'm not sure if it > > > was committed or not. Contacting him and seeing if you're experiencing > > > the same problem would probably help you solve your problem. And if > > > you're able to get good debugging info on what's happening (don't ask me > > > how, I don't know either), you may wish to contact Matt directly, as this > > > type of problem is right up his alley. > > > > > > And yes, his name is Matt Dillon, but he's not the actor. :) > > > > > > Mike "Silby" Silbersack > > > > > > > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-hackers" in the body of the message > > -- > Mathew Kanner <[EMAIL PROTECTED]> SOCS McGill University >Obtuse quote: He [not me] understands: "This field of perception >is void of perception of man." -- The Quintessence of Buddhism > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: APACHE PROBLEMS (fwd)
On Nov 30, Dan Phoenix wrote: > > > Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt > Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt > Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: not responding > Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: is alive again > Nov 30 07:54:56 merry /kernel: nfs server nfs:/cache: not responding > Nov 30 07:54:57 merry /kernel: nfs server nfs:/cache: is alive again > Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt > Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt We've seen this problem at McGill. It doesn't seem to affect our usage at all. Also note that these problems don't appear with nfsv2. (It appears it 4.[0-2] and with Solaris servers) If you do find a solution, my friend [EMAIL PROTECTED] would love to hear about it. --Mat > > > > Ok i will do thathere is problems i am experiencing . > > > > On Wed, 29 Nov 2000, Mike Silbersack wrote: > > > Date: Wed, 29 Nov 2000 20:05:18 -0600 (CST) > > From: Mike Silbersack <[EMAIL PROTECTED]> > > To: Dan Phoenix <[EMAIL PROTECTED]> > > Subject: Re: APACHE PROBLEMS > > > > > > On Wed, 29 Nov 2000, Dan Phoenix wrote: > > > > > before the 25th. > > > where can i get a list of changes? > > > > Here's what changed between the 18th and 25th: > > > > >http://docs.freebsd.org/cgi/getmsg.cgi?fetch=987735+0+archive/2000/cvs-all/20001126.cvs-all > > > > The more seemingly relevant changes were committed on the 18th, but it's > > probably wise to update to a post-25th version, as Matt's bugfixes usually > > are well-implemented. Perhaps he inadvertantly fixed the problem you're > > experiencing. While you're not experiencing a low-memory situation, > > what's happening is probably some form of deadlock. > > > > What you should do is look over the freebsd-hackers and freebsd-net > > archives for the last few weeks. Someone was experiencing nfs problems > > with apache as well. He found a fix for one bug, but I'm not sure if it > > was committed or not. Contacting him and seeing if you're experiencing > > the same problem would probably help you solve your problem. And if > > you're able to get good debugging info on what's happening (don't ask me > > how, I don't know either), you may wish to contact Matt directly, as this > > type of problem is right up his alley. > > > > And yes, his name is Matt Dillon, but he's not the actor. :) > > > > Mike "Silby" Silbersack > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Mathew Kanner <[EMAIL PROTECTED]> SOCS McGill University Obtuse quote: He [not me] understands: "This field of perception is void of perception of man." -- The Quintessence of Buddhism To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: APACHE PROBLEMS (fwd)
Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt Nov 30 02:00:21 merry /kernel: nfs send error 32 for server nfs:/lopt Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: not responding Nov 30 05:37:24 merry /kernel: nfs server nfs:/cache: is alive again Nov 30 07:54:56 merry /kernel: nfs server nfs:/cache: not responding Nov 30 07:54:57 merry /kernel: nfs server nfs:/cache: is alive again Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt Nov 30 08:05:53 merry /kernel: nfs send error 32 for server nfs:/lopt Ok i will do thathere is problems i am experiencing . On Wed, 29 Nov 2000, Mike Silbersack wrote: > Date: Wed, 29 Nov 2000 20:05:18 -0600 (CST) > From: Mike Silbersack <[EMAIL PROTECTED]> > To: Dan Phoenix <[EMAIL PROTECTED]> > Subject: Re: APACHE PROBLEMS > > > On Wed, 29 Nov 2000, Dan Phoenix wrote: > > > before the 25th. > > where can i get a list of changes? > > Here's what changed between the 18th and 25th: > > >http://docs.freebsd.org/cgi/getmsg.cgi?fetch=987735+0+archive/2000/cvs-all/20001126.cvs-all > > The more seemingly relevant changes were committed on the 18th, but it's > probably wise to update to a post-25th version, as Matt's bugfixes usually > are well-implemented. Perhaps he inadvertantly fixed the problem you're > experiencing. While you're not experiencing a low-memory situation, > what's happening is probably some form of deadlock. > > What you should do is look over the freebsd-hackers and freebsd-net > archives for the last few weeks. Someone was experiencing nfs problems > with apache as well. He found a fix for one bug, but I'm not sure if it > was committed or not. Contacting him and seeing if you're experiencing > the same problem would probably help you solve your problem. And if > you're able to get good debugging info on what's happening (don't ask me > how, I don't know either), you may wish to contact Matt directly, as this > type of problem is right up his alley. > > And yes, his name is Matt Dillon, but he's not the actor. :) > > Mike "Silby" Silbersack > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: SKIP port on 4.x (prize offer)
What about it? Anyone with skills in this area interested in figuring out what changed between 4.1 and 4.1.1 probably in the crypto changes that prevents the MD5 authentication of a skip partner. Worth a quick $150 prize for the first solution. Jim Flowers <[EMAIL PROTECTED]> #4 ISP on C|NET, #1 in Ohio On Thu, 30 Nov 2000, Archie Cobbs wrote: > Jim Flowers writes: > > If we provide the funding for a few hours of effort, do you know anyone > > who could take a look at this sooner rather than later? The field of > > view has been narrowed down pretty much and may be no more complicated > > than which of the multiple md5.h header files is being used. > > Somebody on [EMAIL PROTECTED] may be interested in taking a look, > especially if there is a small reward.. I'd ask there. > > -Archie > > PS. isn't there also some web site where you can post projects? > > __ > Archie Cobbs * Packet Design * http://www.packetdesign.com > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Cirrus PD6729/6730 data sheets?
Anyone out there have a set of data sheets for the above chips that they could email me? It looks like all the info pertaining to these has been pulled from the Cirrus web site (?!?). Thanks, --lyndon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: diskless/serial-console
On 30-Nov-00 Danny Braniss wrote: > > }There's no way to really do it right now, but you can use: > }http://people.FreeBSD.org/~jhb/patches/pxekey.patch > } > }This will do the equivalent of -P for pxeboot. > } > thanks, > i added the patches, make BOOT_PXELDR_PROBE_KEYBOARD=1 > removed the keyboard, but zero. > i even commented out the ifdef(`PROBE_KEYBOARD',` > and the test for the keyboard, only left > orb $RBX_SERIAL, (%bx) # enable serial console > and still no output, btw, once the system is running, i can tip and it's ok. > is the serial set to 9600? > > is there a way to tell whoever, to send kernel panics to serial? because > that's > all i want. > > Grrr, all this was to catch a panic that im getting, but now they stopped. > > danny Grr, I found my bug. Please download the updated pxekey.patch and try again. I was setting hte wrong value.. *sigh* -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: diskless/serial-console
On 30-Nov-00 Paul Saab wrote:
> Danny Braniss ([EMAIL PROTECTED]) wrote:
>> hi all,
>> how can I set the equiv of -D/-h in /boot.config in a diskless-pxeboot
>> machine? i think that {rootnfs-server}/boot.config is not read at all.
>>
>> tia,
>> danny
>> PS: 4.2-RELEASE
>
> There's no way to really do it right now, but you can use:
> http://people.FreeBSD.org/~jhb/patches/pxekey.patch
>
> This will do the equivalent of -P for pxeboot.
Let me know if it works. Note that you need to compile pxeldr with an extra
option to make (-DBOOT_PXELDR_PROBE_KEYBOARD). If it does work I'll commit it.
:)
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: i18n extention in sysinstall
At Tue, 28 Nov 2000 18:07:05 +0900, Tatsumi Hosokawa <[EMAIL PROTECTED]> wrote: > >At Tue, 28 Nov 2000 11:01:07 +, >Kaltashkin Eugene <[EMAIL PROTECTED]> wrote: >> >> What dear developers will tell about introduction i18n expansions in sysinstall the >utility? >> It would be convenient for many people to adjust FreeBSD on the native language. > > Latest code is based on 4.2-RELEASE and I'm porting porting it to > -current (maybe it's easy). I wrote Russian support for it. Currently only *.hlp files are provided, so, selecting "Usage" or type F1 from main menu is the easiest way to see russian sysinstall message. Latest binaries and sources can be found at http://people.freebsd.org/~hosokawa/boot-ja/4.2-RELEASE/release-20001201-1/ and it currently support Japanese, Korean, Traditional Chinese, Russian, and English. -- Tatsumi Hosokawa <[EMAIL PROTECTED]> http://www.sm.rim.or.jp/~hosokawa/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: pthreads, semaphores and wait
"Dimitar V. Peikov" wrote: > > I've tryed to make some example on using pthreads and semaphores and found > that process became blocked if inside of critical section use wait, uwait or > nanowait finctions. In the attached file if change line : (#if 0) to (#if 1) > the program hangs. I've tested it even with gdb and the threads were blocked > after wait finction. Semaphores aren't wrapped by the threads library (yes, they can block the whole process). This will be resolved in our future libpthread (for info on that, search -arch and -smp in reference to the KSE project). -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: diskless/serial-console
Danny Braniss ([EMAIL PROTECTED]) wrote: > > }There's no way to really do it right now, but you can use: > }http://people.FreeBSD.org/~jhb/patches/pxekey.patch > } > }This will do the equivalent of -P for pxeboot. > } > thanks, > i added the patches, make BOOT_PXELDR_PROBE_KEYBOARD=1 > removed the keyboard, but zero. > i even commented out the ifdef(`PROBE_KEYBOARD',` > and the test for the keyboard, only left > orb $RBX_SERIAL, (%bx) # enable serial console > and still no output, btw, once the system is running, i can tip and it's ok. > is the serial set to 9600? > > is there a way to tell whoever, to send kernel panics to serial? because that's > all i want. Is a keyboard plugged into the machine? If you want to force serial output, set console="comconsole" in your loader.conf. > Grrr, all this was to catch a panic that im getting, but now they stopped. DDB and BREAK_TO_DEBUGGER or ALT_BREAK_TO_DEBUGGER To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
pthreads, semaphores and wait
I've tryed to make some example on using pthreads and semaphores and found
that process became blocked if inside of critical section use wait, uwait or
nanowait finctions. In the attached file if change line : (#if 0) to (#if 1)
the program hangs. I've tested it even with gdb and the threads were blocked
after wait finction.
#include
#include
#include
#include
/* pThread includes */
#include
/* IPC semaphores includes */
#include
#include
#include
extern int errno;
int common = 0;
int common_shared_id = 0;
char *common_pointer = NULL;
int semaphore_id = 0;
int pthread_semaphores(char *s) {
int internal = common;
struct sembuf sem_buf;
int sem_val = 0;
/* Lock semaphore 0 */
sem_buf.sem_num = 0;
sem_buf.sem_op = -1;
sem_buf.sem_flg = 0;
if ((sem_val = semop(semaphore_id, &sem_buf, 1)) == -1) {
fprintf(stderr, "Error lock semaphore: %s\n", strerror(errno));
return -1;
}
/* Get current value of the first semaphore */
if ((sem_val = semctl(semaphore_id, 0, GETVAL)) == -1) {
fprintf(stderr, "Error allocating semaphore: %s\n", strerror(errno));
return -1;
}
/* Do something ... */
common_pointer = (char *) malloc(strlen(s) + 1);
strcpy(common_pointer, s);
fprintf(stderr, "Enter semaphore %u\n", common++);
#if 0
sleep(1);
#endif
fprintf(stderr, "Leave semaphore %u\n", internal);
sem_buf.sem_num = 0;
sem_buf.sem_op = 1;
sem_buf.sem_flg = 0;
if ((sem_val = semop(semaphore_id, &sem_buf, 1)) == -1) {
fprintf(stderr, "Error lock semaphore: %s\n", strerror(errno));
return -1;
}
return 0;
}
int main(int argc, char **argv) {
pthread_t thr[4];
int retcode = 0;
int sem_val;
/* Example using semaphores */
/* Create semaphore */
if ((semaphore_id = semget(IPC_PRIVATE, 1, SEM_R | SEM_A)) == -1) {
fprintf(stderr, "Error allocating semaphore: %s\n", strerror(errno));
return -1;
}
/* Assign value to the first semaphore */
if ((sem_val = semctl(semaphore_id, 0, SETVAL, 1)) == -1) {
fprintf(stderr, "Error allocating semaphore: %s\n", strerror(errno));
return -1;
}
/* Get current value of the first semaphore */
if ((sem_val = semctl(semaphore_id, 0, GETVAL)) == -1) {
fprintf(stderr, "Error allocating semaphore: %s\n", strerror(errno));
return -1;
}
/* Create pthreads */
pthread_create(&thr[0], NULL, (void *(*)(void *))pthread_semaphores, argv[0]);
pthread_create(&thr[1], NULL, (void *(*)(void *))pthread_semaphores, argv[0]);
pthread_join(thr[0], (void *) &retcode);
/* Remove semaphore */
if (semctl(semaphore_id, IPC_RMID, NULL) == -1) {
fprintf(stderr, "Error removing semaphore: %s\n", strerror(errno));
return -1;
}
fprintf(stderr, "Done!\n");
return 0;
}
Dimitar Peikov
Programmer Analyst
"We Build e-Business"
RILA Solutions
27 Building, Acad.G.Bonchev Str.
1113 Sofia, Bulgaria
home: (+359 2) 595495
phone: (+359 2) 9797320
phone: (+359 2) 9797300
fax: (+359 2) 9733355
http://www.rila.com
Re: diskless/serial-console
}There's no way to really do it right now, but you can use: }http://people.FreeBSD.org/~jhb/patches/pxekey.patch } }This will do the equivalent of -P for pxeboot. } thanks, i added the patches, make BOOT_PXELDR_PROBE_KEYBOARD=1 removed the keyboard, but zero. i even commented out the ifdef(`PROBE_KEYBOARD',` and the test for the keyboard, only left orb $RBX_SERIAL, (%bx) # enable serial console and still no output, btw, once the system is running, i can tip and it's ok. is the serial set to 9600? is there a way to tell whoever, to send kernel panics to serial? because that's all i want. Grrr, all this was to catch a panic that im getting, but now they stopped. danny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: diskless/rc
On Thu, Nov 30, 2000 at 05:56:57PM +0200, Danny Braniss wrote:
> 1) the cmp -s -> BUS ERROR
> 2) cp ${T} /etc/motd-> cp: /etc/motd: Bad address
>
> now only 2 is happening - go figure :-)
> it also used to, after it went multiuser, to panic when i did the
> cmp -s ${T} /etc/motd
>
> any insights?
Bad hardware?
David.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: diskless/rc
make sure the kernel you are booting is the same as the NFS file systems
you are using.
paul
Danny Braniss ([EMAIL PROTECTED]) wrote:
> sorry if this is not the correct list.
>
> this code in rc:
> ...
>
> case ${update_motd} in
> [Nn][Oo] | '')
> ;;
> *)
> if T=`mktemp /tmp/_motd.XX`; then
> uname -v | sed -e 's,^\([^#]*\) #\(.*
>[1-2][0-9][0-9][0-9]\).*/\([^\]*\)
> $,\1 (\3) #\2,' > ${T}
> awk '{if (NR == 1) {if ($1 == "FreeBSD") {next} else {print "\n"$0}}
>else
> {print}}' < /etc/motd >> ${T}
> cmp -s ${T} /etc/motd || {
> cp ${T} /etc/motd
> chmod 644 /etc/motd
> }
> rm -f ${T}
> fi
> ;;
> esac
>
> used to
> 1) the cmp -s -> BUS ERROR
> 2) cp ${T} /etc/motd-> cp: /etc/motd: Bad address
>
> now only 2 is happening - go figure :-)
> it also used to, after it went multiuser, to panic when i did the
> cmp -s ${T} /etc/motd
>
> any insights?
>
> danny
>
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
--
Paul Saab
Technical Yahoo
[EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED]
Do You .. uhh .. Yahoo!?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
diskless/rc
sorry if this is not the correct list.
this code in rc:
...
case ${update_motd} in
[Nn][Oo] | '')
;;
*)
if T=`mktemp /tmp/_motd.XX`; then
uname -v | sed -e 's,^\([^#]*\) #\(.*
[1-2][0-9][0-9][0-9]\).*/\([^\]*\)
$,\1 (\3) #\2,' > ${T}
awk '{if (NR == 1) {if ($1 == "FreeBSD") {next} else {print "\n"$0}}
else
{print}}' < /etc/motd >> ${T}
cmp -s ${T} /etc/motd || {
cp ${T} /etc/motd
chmod 644 /etc/motd
}
rm -f ${T}
fi
;;
esac
used to
1) the cmp -s -> BUS ERROR
2) cp ${T} /etc/motd-> cp: /etc/motd: Bad address
now only 2 is happening - go figure :-)
it also used to, after it went multiuser, to panic when i did the
cmp -s ${T} /etc/motd
any insights?
danny
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Drivers
Dear, Sirs! Where I can read about development of drivers for FreeBSD 4.x? Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: DSM Facility for FreeBSD
On Thu, 30 Nov 2000, Tim Tsai wrote: > > Also, my requirements are significantly more relaxed than a true DSM model > (and much more lightweight is preferred).. I really just need synchronized > views of data on a "reasonable" effort basis (i.e. it's OK if one > client/peer sees slightly older data. Sequence is important though). check out http://www.acl.lanl.gov/~rminnich, see zounds. Worked well for me on clusters. The only DSM I've ever seen that supports IP multicast for updates. ron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: diskless/serial-console
Danny Braniss ([EMAIL PROTECTED]) wrote:
> hi all,
> how can I set the equiv of -D/-h in /boot.config in a diskless-pxeboot
> machine? i think that {rootnfs-server}/boot.config is not read at all.
>
> tia,
> danny
> PS: 4.2-RELEASE
There's no way to really do it right now, but you can use:
http://people.FreeBSD.org/~jhb/patches/pxekey.patch
This will do the equivalent of -P for pxeboot.
--
Paul Saab
Technical Yahoo
[EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED]
Do You .. uhh .. Yahoo!?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
diskless/serial-console
hi all,
how can I set the equiv of -D/-h in /boot.config in a diskless-pxeboot
machine? i think that {rootnfs-server}/boot.config is not read at all.
tia,
danny
PS: 4.2-RELEASE
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
DSM Facility for FreeBSD
http://www.usenix.org/publications/library/proceedings/ana97/full_papers/souto/paper.html Does anybody know if something similar to this is available for modern FreeBSD/Unix? Preferably something in Userland vs. Kernel. Also, my requirements are significantly more relaxed than a true DSM model (and much more lightweight is preferred).. I really just need synchronized views of data on a "reasonable" effort basis (i.e. it's OK if one client/peer sees slightly older data. Sequence is important though). Hope that makes sense. Thanks, Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
