unbloating {tcp,tcp6,udp,udp6}_getcred()
The tcp_getcred(), tcp6_getcred(), udp_getcred(), udp6_getcred() look
like a bad example of mostly duplicated code caused by cut and paste
programming. By passing a pointer to the inpcbinfo structure as an
argument to the sysctl hander it is possible to combine the use a common
handler for the TCP and UDP cases, and the IPv4 and IPv6 handlers can
use a common back end once the PCB has been looked up.
To switch tcp_getcred() to use this new handler, you would make the
following change:
SYSCTL_PROC(_net_inet_tcp, OID_AUTO, getcred,
-CTLTYPE_OPAQUE|CTLFLAG_RW|CTLFLAG_PRISON, 0, 0,
-tcp_getcred, S,xucred, Get the xucred of a TCP connection);
+CTLTYPE_OPAQUE|CTLFLAG_RW|CTLFLAG_PRISON, tcbinfo, 0,
+in_pcbgetcred_handler, S,xucred, Get the xucred of a TCP connection);
The pcblist sysctl handlers look like another case of cut and paste
programming ...
===Cut Here===
#include opt_inet6.h
#include sys/param.h
#include sys/systm.h
#include sys/proc.h
#include sys/jail.h
#include sys/sysctl.h
#include sys/socket.h
#include sys/socketvar.h
#include sys/ucred.h
#include netinet/in.h
#include netinet/in_pcb.h
#include netinet/in_pcbgetcred.h
#ifdef INET6
#include netinet/ip6.h
#include netinet6/in6_pcb.h
#endif /* INET6 */
/*
* Convert the socket credential for inp to external format, unlock pcbinfo,
* and return the credential info using SYSCTL_OUT().
*/
static int
in_getcred(struct sysctl_req *req, struct inpcbinfo *pcbinfo, struct inpcb *inp,
int s)
{
struct xucred xuc;
int error;
if (inp == NULL) {
error = ENOENT;
goto out;
}
/*
* XXX - It should not be necessary to lock the PCB or
* test inp_socket, since inp_socket is static
* for the life of the PCB.
*/
INP_LOCK(inp);
if (inp-inp_socket == NULL) {
error = ENOENT;
goto outlocked;
}
error = cr_canseesocket(req-td-td_ucred, inp-inp_socket);
if (error == 0)
cru2x(inp-inp_socket-so_cred, xuc);
outlocked:
INP_UNLOCK(inp);
out:
INP_INFO_RUNLOCK(pcbinfo);
splx(s);
if (error == 0)
error = SYSCTL_OUT(req, xuc, sizeof(struct xucred));
return (error);
}
/*
* Socket credential sysctl handler.
* The pcbinfo pointer should be passed as arg1.
*/
int
in_pcbgetcred_handler(SYSCTL_HANDLER_ARGS)
{
struct inpcbinfo *pcbinfo = arg1;
struct sockaddr_in addrs[2];
struct inpcb *inp;
int error, s;
error = suser_cred(req-td-td_ucred, PRISON_ROOT);
if (error)
return (error);
error = SYSCTL_IN(req, addrs, sizeof(addrs));
if (error)
return (error);
s = splnet();
INP_INFO_RLOCK(pcbinfo);
inp = in_pcblookup_hash(pcbinfo, addrs[1].sin_addr, addrs[1].sin_port,
addrs[0].sin_addr, addrs[0].sin_port, 0, NULL);
return (in_getcred(req, pcbinfo, inp, s));
}
#ifdef INET6
int
in6_pcbgetcred_handler(SYSCTL_HANDLER_ARGS)
{
struct inpcbinfo *pcbinfo = arg1;
struct sockaddr_in6 addrs[2];
struct inpcb *inp;
int error, s, mapped = 0;
error = suser_cred(req-td-td_ucred, PRISON_ROOT);
if (error)
return (error);
error = SYSCTL_IN(req, addrs, sizeof(addrs));
if (error)
return (error);
if (IN6_IS_ADDR_V4MAPPED(addrs[0].sin6_addr)) {
if (IN6_IS_ADDR_V4MAPPED(addrs[1].sin6_addr))
mapped = 1;
else
return (EINVAL);
}
s = splnet();
INP_INFO_RLOCK(pcbinfo);
if (mapped == 1)
inp = in_pcblookup_hash(pcbinfo,
*(struct in_addr *)addrs[1].sin6_addr.s6_addr[12],
addrs[1].sin6_port,
*(struct in_addr *)addrs[0].sin6_addr.s6_addr[12],
addrs[0].sin6_port,
0, NULL);
else
inp = in6_pcblookup_hash(pcbinfo, addrs[1].sin6_addr,
addrs[1].sin6_port,
addrs[0].sin6_addr, addrs[0].sin6_port,
0, NULL);
return (in_getcred(req, pcbinfo, inp, s));
}
#endif
===Cut Here===
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: VESA 800x600 console not working
David Xu wrote: Yes, this is a known problem. I have a patch for this, you may download it from here: http://opensource.zjonline.com.cn/freebsd/vm86patch.tgz Any ideas why it isn't committed yet? -Maxim David Xu - Original Message - From: Rob [EMAIL PROTECTED] To: Current [EMAIL PROTECTED] Sent: Saturday, July 27, 2002 6:46 AM Subject: VESA 800x600 console not working Having a laptop here, I wanted to get the same 800x600 console that I have in -stable. I built my kernel with OPTIONS VESA and OPTIONS SC_PIXEL_MODE. I have tried two methods. The first was to put 0x0080 in the device.hints file for SC. That gave me a blank screen upon startup. I also tried putting into /usr/local/etc/rc.d the vidcontrol command vidcontrol -g 100x37 VESA_800x600. That gave me a blank screen at the end of the bootup. Is this functionality broken in -current, or am I doing something wrong? Thanks, Rob. -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message __ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
MSc student, needs help from OS contributor! - 2nd request
Hello again,
I uploaded a newer version of my online questionnaire
(http://www.lse-students.ac.uk/tzouris/oss), and I am searching for Open
Source contributors who might be interested in answering it.
The questionnaire is designed in a way that it won't require more than 10 minutes to
be answered.
My previous request didn't have the expected responce, so you are kindly asked to
answer this one. It will take you for sure less than 10 minutes!
My MPhil/PhD which is commencing in the upcoming October, will be based
on my current research. So as you can understand your help is really
important to me.
If you are a contributor, you are kindly requested to fill in this questionnaire
http://www.lse-students.ac.uk/tzouris/oss
Thank you very much in advance for your help,
Menelaos.
PS: my background:
I am an MSc student at the London School of Economics, department of
Information Systems, London, U.K. (http://is.lse.ac.uk) I am currently
writing my summer dissertation (MSc thesis) on Open Source. This is
where I need your help!
I received my Bsc in Computer Science fro the Athens University of
Economics and Business (http://www.cs.aueb.gr http://www.cs.acueb.gr )
Some of the issues that have been covered in my BSc are published here:
http://www.geocities.com/tzmnlaos
=
Menelaos G. Tzouris
Graduate Student
Department of Information Systems
London School of Economics and Political Science
èR{.nÇ+·¬zwfj)m¢f£¢·hkyàRàÂ+aº{.nÇ+·ç±×.®·§¶)í
æèw* ¶¦zË
Re: A fix of recent bugs in swapping in/out a process
Hi, Just want to let you know that this patch fixes the 'fault on nofault entry' panics I had. It was very easily reproducable with: --- char *buf; int n=0; buf=(char *)malloc(1); for(;;) buf=(char *)realloc(buf,n++*1024*1024); --- Ran some tests now and as said it didn't happen again. Thanks alot. Mark On Sun, Jul 28, 2002 at 09:51:57PM +0900, Seigo Tanimura wrote: If you are having a trouble of a broken thread state (eg a thread with TDS_RUNQ on no run queue) or a mysterious page fault on a kernel memory (probably in mi_switch()), you may want to try my patch at: http://people.FreeBSD.org/~tanimura/patches/procswap.diff.gz In a nutshell, this patch fixes three bugs: 1. a thread with TDS_RUNQ on no run queue. This is due to wakeup() and wakeup_one() setting the state to a thread to TDS_RUNQ even if the thread has been swapped out. As a thread being or having been swapped out cannot be scheduled immediately, introduce a new thread state TDS_SWAPPED to note that. 2. a possible race condition for multiple threads to swap in a single process. Since faultin() may block (and likely to do so) without leaving any flags for a process being swapped in, more than one threads can call faultin() for the same process. Avoid this by adding a new process state flag PS_SWAPPINGIN to a process being swapped in. 3. a running thread being swapped out. Swapout_procs() and swapout() do not check the states of the threads in a process about to be swapped out. This causes the pcb and the kernel stack of a running thread being unmapped, resulting in a page fault in cpu_switch(). Do not swap out a process unless all of its threads are either in a run queue or sleeping. Eventually, it may become our option to swap out only threads that are safe to do so. -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: firewall support?
On (2002/07/28 09:49), Szilveszter Adam wrote: is firewall support built into the -current kernel or does it need to be compiled in? It is not in GENERIC, but you can always either compile it in, or load it from a module by editing /boot/loader.conf. Beware! AFAIK, the kernel-loadable version of IPFW (ipfw.ko) defaults to deny! Enable with care on remotely managed systems for which you do not have serial console access. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VESA 800x600 console not working
Maxim Sobolev wrote: David Xu wrote: Yes, this is a known problem. I have a patch for this, you may download it from here: http://opensource.zjonline.com.cn/freebsd/vm86patch.tgz Any ideas why it isn't committed yet? -Maxim BTW, the VESA mode doesn't work on -stable now either. I knew I shouldn't have cvsup'd, with all the problem reports I'm seeing on the lists. Dohh! But I just ordered a Dell 8200, so maybe my problems will become different Rob. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Be careful mounting -stable partitions on -current
I mounted my -stable /usr partition on -current /mnt to copy over a kernel config file, and when I finally fired up -stable, the /usr partition was borked. Fsck couldn't fix it manually. Luckily I had backups. It said that the master record didn't match the alternate. I might have rebooted without unmounting the -stable partition. On my laptop (Sony FX290), each type of reboot has different consequences. reboot works as expected. CTRL-ALT-DEL does not- it syncs disks and then freezes. Shutdown -p now shuts down, but when you turn the laptop back on it freezes and you have to take the batteries out to get it working right again. Rob. (ps. this is the message I was trying to send that ended up as dozens of QUIT messages- sorry again) -- - The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VESA 800x600 console not working
What do you mean? VESA mode works like a charm here on a very fresh STABLE. FreeBSD stable 4.6-STABLE FreeBSD 4.6-STABLE #0: Mon Jul 29 10:19:35 EDT 2002 root@stable:/usr/src/sys/compile/KAN i386 On Mon, 29 Jul 2002 06:57:13 -0700 rob [EMAIL PROTECTED] wrote: BTW, the VESA mode doesn't work on -stable now either. I knew I shouldn't have cvsup'd, with all the problem reports I'm seeing on the lists. Dohh! But I just ordered a Dell 8200, so maybe my problems will become different Rob. -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing INET6 does stop the crashes.
Maxim Konovalov wrote:
On 18:19-0700, Jul 28, 2002, walt wrote:
After reading Scott Long's recent post I tried removing INET6
from my kernel config and the crashes due to mozilla are now
definitely gone.
[...]
Please try the next patch.
Index: sys/netinet/tcp_usrreq.c
===
RCS file: /home/ncvs/src/sys/netinet/tcp_usrreq.c,v
retrieving revision 1.78
diff -u -r1.78 tcp_usrreq.c
--- sys/netinet/tcp_usrreq.c 25 Jul 2002 18:10:04 - 1.78
+++ sys/netinet/tcp_usrreq.c 28 Jul 2002 14:34:09 -
@@ -407,8 +407,10 @@
if (IN6_IS_ADDR_V4MAPPED(sin6p-sin6_addr)) {
struct sockaddr_in sin;
- if ((inp-inp_flags IN6P_IPV6_V6ONLY) != 0)
- return(EINVAL);
+ if ((inp-inp_flags IN6P_IPV6_V6ONLY) != 0) {
+ error = EINVAL;
+ goto out;
+ }
in6_sin6_2_sin(sin, sin6p);
inp-inp_vflag |= INP_IPV4;
%%%
Yes, it stops the crashes. If I set v6only = 0 then the machine
works normally; if set to 1 then I get connection refused from
any server I try to connect to. Is that normal v6only behavior?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Be careful mounting -stable partitions on -current
rob wrote: I mounted my -stable /usr partition on -current /mnt to copy over a kernel config file, and when I finally fired up -stable, the /usr partition was borked. Fsck couldn't fix it manually... I'm told that the fsck on -stable has been updated to fix this problem. Have you updated your -stable machine recently? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing INET6 does stop the crashes.
On 29-Jul-2002 walt wrote:
Maxim Konovalov wrote:
On 18:19-0700, Jul 28, 2002, walt wrote:
After reading Scott Long's recent post I tried removing INET6
from my kernel config and the crashes due to mozilla are now
definitely gone.
[...]
Please try the next patch.
Index: sys/netinet/tcp_usrreq.c
===
RCS file: /home/ncvs/src/sys/netinet/tcp_usrreq.c,v
retrieving revision 1.78
diff -u -r1.78 tcp_usrreq.c
--- sys/netinet/tcp_usrreq.c 25 Jul 2002 18:10:04 - 1.78
+++ sys/netinet/tcp_usrreq.c 28 Jul 2002 14:34:09 -
@@ -407,8 +407,10 @@
if (IN6_IS_ADDR_V4MAPPED(sin6p-sin6_addr)) {
struct sockaddr_in sin;
-if ((inp-inp_flags IN6P_IPV6_V6ONLY) != 0)
-return(EINVAL);
+if ((inp-inp_flags IN6P_IPV6_V6ONLY) != 0) {
+error = EINVAL;
+goto out;
+}
in6_sin6_2_sin(sin, sin6p);
inp-inp_vflag |= INP_IPV4;
%%%
Yes, it stops the crashes. If I set v6only = 0 then the machine
works normally; if set to 1 then I get connection refused from
any server I try to connect to. Is that normal v6only behavior?
Let's get this patch committed then. :)
--
John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve! - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Removing INET6 does stop the crashes.
[...] Let's get this patch committed then. :) Already done, sys/netinet/tcp_usrreq.c rev. 1.79 -- Maxim Konovalov, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Panic with KSE
Hi Julian, Thanks for the pointer. It does seems fix my panic problem. Haro From: Julian Elischer [EMAIL PROTECTED] Date: Sun, 28 Jul 2002 21:36:09 -0700 (PDT) ::I think this has just been found and fixed by: ::Seigo Tanimura [EMAIL PROTECTED], (CC'd) :: his fix is at: ::http://people.FreeBSD.org/~tanimura/patches/procswap.diff.gz :: ::please try it! ::let us know if it fixes your problem. :: ::On Mon, 29 Jul 2002, Munehiro Matsuda wrote: :: :: Hi, :: :: I sometimes get a panic with KSE. :: :: panic: KSE not on run queue :: :: syncing disks... panic: bremfree: bp 0xc4014908 not locked :: Uptime: 53m5s :: Terminate ACPI :: :: :: This usally happends when I try to build two differnt kernels, :: one based on OLDCARD and the other on NEWCARD, concurrently on :: differnt xterms sessions. :: :: I've attached dmesg file. :: :: Hope this helps, :: Haro =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: firewall support?
On Mon, Jul 29, 2002 at 02:44:50PM +0200, Sheldon Hearn wrote: On (2002/07/28 09:49), Szilveszter Adam wrote: is firewall support built into the -current kernel or does it need to be compiled in? It is not in GENERIC, but you can always either compile it in, or load it from a module by editing /boot/loader.conf. Beware! AFAIK, the kernel-loadable version of IPFW (ipfw.ko) defaults to deny! Correct. But we also have ipfilter, which is also loadable... but I did not want to be specific. If there are other questions, I will. Enable with care on remotely managed systems for which you do not have serial console access. It's not for nothing that the first rule of firewall configuration: Show up! (at the console). Many a surprise can be averted this way...:-) -- Regards: Szilveszter ADAM Szombathely Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Removing INET6 does stop the crashes.
Hi,
On Mon, 29 Jul 2002 08:11:50 -0700
walt [EMAIL PROTECTED] said:
After reading Scott Long's recent post I tried removing INET6
from my kernel config and the crashes due to mozilla are now
definitely gone.
Thank you for fixing it. I tried to fix as the same way as you did,
then during committing my fix, I found that it was already fixed by
you. :-)
wa1ter Yes, it stops the crashes. If I set v6only = 0 then the machine
wa1ter works normally; if set to 1 then I get connection refused from
wa1ter any server I try to connect to. Is that normal v6only behavior?
It is expected behaivior. However, I realized that Mozilla still has
the problem that IPv4-mapped IPv6 address is used to connect to IPv4
site. It should be fixed by Mozilla side. I heared that NetBSD
pkgsrc has a workaround to this problem:
http://cvsweb.no.netbsd.org/bsdweb.cgi/pkgsrc/www/mozilla/patches/patch-be?rev=1.8content-type=text/x-cvsweb-markup
Our port should have it, too.
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: A fix of recent bugs in swapping in/out a process
great.. looks like it's a commit... On Mon, 29 Jul 2002, Mark Santcroos wrote: Hi, Just want to let you know that this patch fixes the 'fault on nofault entry' panics I had. It was very easily reproducable with: --- char *buf; int n=0; buf=(char *)malloc(1); for(;;) buf=(char *)realloc(buf,n++*1024*1024); --- Ran some tests now and as said it didn't happen again. Thanks alot. Mark On Sun, Jul 28, 2002 at 09:51:57PM +0900, Seigo Tanimura wrote: If you are having a trouble of a broken thread state (eg a thread with TDS_RUNQ on no run queue) or a mysterious page fault on a kernel memory (probably in mi_switch()), you may want to try my patch at: http://people.FreeBSD.org/~tanimura/patches/procswap.diff.gz In a nutshell, this patch fixes three bugs: 1. a thread with TDS_RUNQ on no run queue. This is due to wakeup() and wakeup_one() setting the state to a thread to TDS_RUNQ even if the thread has been swapped out. As a thread being or having been swapped out cannot be scheduled immediately, introduce a new thread state TDS_SWAPPED to note that. 2. a possible race condition for multiple threads to swap in a single process. Since faultin() may block (and likely to do so) without leaving any flags for a process being swapped in, more than one threads can call faultin() for the same process. Avoid this by adding a new process state flag PS_SWAPPINGIN to a process being swapped in. 3. a running thread being swapped out. Swapout_procs() and swapout() do not check the states of the threads in a process about to be swapped out. This causes the pcb and the kernel stack of a running thread being unmapped, resulting in a page fault in cpu_switch(). Do not swap out a process unless all of its threads are either in a run queue or sleeping. Eventually, it may become our option to swap out only threads that are safe to do so. -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
unkillable process :-\
KOffice's kword is stuck here... Can not be killed even with -9. Sits idle, with its window open, but not updating: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 1042 88248 1 0 96 0 119296 28105 - WWs pm0:00,00 kword /tmp/k Machine is otherwise fine, uptime 12 days -- my work desktop. -current of Tue Jul 16 13:14:05 EDT 2002 vintage. Any clues? -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A fix of recent bugs in swapping in/out a process
I committed your patch. Thankyou for doing this work. I a very pleased that other people are looking at this system and code. I could get almost no-one to review before I committed so I am pleased that people do look at it and try understand it after I committed! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
AMD low power hacks
I've been wondering lately why my AthlonTB runs at a quite high idle-temperature and I came across this page: http://vcool.occludo.net/VC_Theory.html Does someone feel like getting something similar into our kernel? Regards, -- Michael Nottebrock msg41473/pgp0.pgp Description: PGP signature
Re: unkillable process :-\
ddb
ps (find address of proc)
cont
cd /sys/i386/compile/MYKERNEL
gdb -k kernel.debug /dev/mem
print *(struct proc *){address}
go to the thread..
do the same.
maybe others can tell you other things to look at while you are in
there
(if you can not get to ddb you may neet to traverse the allproc list
to find your process.)
On Mon, 29 Jul 2002, Mikhail Teterin wrote:
KOffice's kword is stuck here... Can not be killed even with -9.
Sits idle, with its window open, but not updating:
UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND
1042 88248 1 0 96 0 119296 28105 - WWs pm0:00,00 kword
/tmp/k
Machine is otherwise fine, uptime 12 days -- my work desktop. -current
of Tue Jul 16 13:14:05 EDT 2002 vintage. Any clues?
-mi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
[no subject]
Many thanks to everybody that send their feedback on this matter. I have now uploaded a text based questionnaire that can be found at: http://www.geocities.com/tzmnlaos/oss/txtquestionnaire.txt there is also a link to it from the web based one (http://www.lse-students.ac.uk/tzouris/oss/). If you prefer, you can feel in this questionnaire and email it or mail it to me instead. Thank you all again, Menelaos. ¡Iì¹» ®Þ±éݨ¥¶Ý¢jçH:+éì¹» ®Þ~·nÇ\ººÞا¶¡Ü¨~Ø^ë,j
TXT based questionnaire now available [MSc student, needs help from OS contributor! - 2ndrequest]
Many thanks to everybody that send their feedback on this matter. I have now uploaded a text based questionnaire that can be found at: http://www.geocities.com/tzmnlaos/oss/txtquestionnaire.txt there is also a link to it from the web based one (http://www.lse-students.ac.uk/tzouris/oss/). If you prefer, you can feel in this questionnaire and email it or mail it to me instead. Thank you all again, Menelaos. ¡Iì¹» ®Þ±éݨ¥¶Ý¢jçH:+éì¹» ®Þ~·nÇ\ººÞا¶¡Ü¨~Ø^ë,j
Re: your mail
On Mon, 29 Jul 2002, Tzouris,M wrote: ?? can read questions fine, but won't allow me to answer any of them Bob Many thanks to everybody that send their feedback on this matter. I have now uploaded a text based questionnaire that can be found at: http://www.geocities.com/tzmnlaos/oss/txtquestionnaire.txt there is also a link to it from the web based one (http://www.lse-students.ac.uk/tzouris/oss/). If you prefer, you can feel in this questionnaire and email it or mail it to me instead. Thank you all again, Menelaos. ASCII Ribbon CampaignaccessBob NO HTML/PDF/RTF in e-mail [EMAIL PROTECTED] NO MSWord docs in e-mailAccess Systems, engineers NO attachments in e-mail, *LINUX powered* access is a civil right *#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*# THIS message and any attachments are CONFIDENTIAL and may be privileged. They are intended ONLY for the individual or entity named above. If you are not the intended recipient, Please notify the sender as soon as possible. Please DO NOT READ, COPY, USE, or DISCLOSE this communication to others and DELETE it from your computer systems. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Re: Be careful mounting -stable partitions on -current
At 7:18 PM + 7/29/02, [EMAIL PROTECTED] wrote: I cvsup'd on Friday of last week, after I restored /usr. Did the fix come later than that? I'm kind of afraid to try it again :) Thanks, Rob. The fix in question was to -stable, not -current (I am not sure if that was mentioned earlier). I think the change was committed to -stable sometime in early July, iirc. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: VESA 800x600 console not working
Alexander Kabaev wrote: What do you mean? VESA mode works like a charm here on a very fresh STABLE. A: What's that? B: It's my luck rabbit's foot. A: What's it for? B: It keeps dragons from swooping out of the sky and eating me. A: Really?!? B: Yeah. A: And how does it work? B: It works like a charm. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: AMD low power hacks
Michael Nottebrock wrote: I've been wondering lately why my AthlonTB runs at a quite high idle-temperature and I came across this page: http://vcool.occludo.net/VC_Theory.html Does someone feel like getting something similar into our kernel? Note that this can not be made to be reliable without the confidential errata for A4, A5, A6, A7, and A9. Otherwise, you can/will get spurious system hangs. I rather expect that this is the reason it's off by default, on most systems, and why there is a BIOS override that disables it, on others. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
for UPDATING
to upgrade from FreeBSD-current previous to GCC3.1 (circa April, May) to the current top of tree, a 'make -k world' may be necessary to skip over an (apparently unnecessary) broken gperf build. This has been confirmed twice for alpha and once for i386. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Subscribe
Title: Subscribe O'Keeya Singleton Multimedia Analyst National Health Foundation 515 S. Figueroa St., Suite 1300 Los Angeles, CA 90071 (213) 538-0700 (213) 639-4272 fax www.nationalhealthfoundation.org
minor OPIE + telnet nit
telnet -X sra currentbox Trying -- Connected to curentbox Escape character is '^]'. FreeBSD/i386 (currentbox) (ttypq) login: obrien otp-md5 16 dr8821 ext Password: otp-md5 16 dr8821 ext Password [echo on]: What I type for the password is not echoed. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
make buildworld crashing
I just updated my source and running make buildworld crashes here: cd /usr/src/usr.bin/makewhatis; make DIRPRFX=usr.bin/makewhatis/ obj; make DIRPRFX=usr.bin/makewhatis/ depend; make DIRPRFX=usr.bin/makewhatis/ all; make DIRPRFX=usr.bin/makewhatis/ DESTDIR=/usr/obj/usr/src/i386 install /usr/obj/usr/src/i386/usr/src/usr.bin/makewhatis created for /usr/src/usr.bin/makewhatis make: don't know how to make bsd.README. Stop *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
i386 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/i386/obj/local0/scratch/des/src/i386/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Mon Jul 29 22:35:00 PDT 2002 -- === xe cc1: warnings being treated as errors /local0/scratch/des/src/sys/kern/kern_mac.c:54: warning: `struct __mac_get_proc_args' declared inside parameter list /local0/scratch/des/src/sys/kern/kern_mac.c:54: warning: its scope is only this definition or declaration, which is probably not what you want /local0/scratch/des/src/sys/kern/kern_mac.c:55: warning: no previous prototype for `__mac_get_proc' /local0/scratch/des/src/sys/kern/kern_mac.c:61: warning: `struct __mac_set_proc_args' declared inside parameter list /local0/scratch/des/src/sys/kern/kern_mac.c:62: warning: no previous prototype for `__mac_set_proc' /local0/scratch/des/src/sys/kern/kern_mac.c:68: warning: `struct __mac_get_fd_args' declared inside parameter list /local0/scratch/des/src/sys/kern/kern_mac.c:69: warning: no previous prototype for `__mac_get_fd' /local0/scratch/des/src/sys/kern/kern_mac.c:75: warning: `struct __mac_get_file_args' declared inside parameter list /local0/scratch/des/src/sys/kern/kern_mac.c:76: warning: no previous prototype for `__mac_get_file' /local0/scratch/des/src/sys/kern/kern_mac.c:82: warning: `struct __mac_set_fd_args' declared inside parameter list /local0/scratch/des/src/sys/kern/kern_mac.c:83: warning: no previous prototype for `__mac_set_fd' /local0/scratch/des/src/sys/kern/kern_mac.c:89: warning: `struct __mac_set_file_args' declared inside parameter list /local0/scratch/des/src/sys/kern/kern_mac.c:90: warning: no previous prototype for `__mac_set_file' *** Error code 1 Stop in /local0/scratch/des/obj/local0/scratch/des/src/sys/GENERIC. *** Error code 1 Stop in /local0/scratch/des/src. *** Error code 1 Stop in /local0/scratch/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make buildworld crashing
On Mon, Jul 29, 2002 at 08:15:06PM -0700, karl agee wrote: I just updated my source and running make buildworld crashes here: cd /usr/src/usr.bin/makewhatis; make DIRPRFX=usr.bin/makewhatis/ obj; make DIRPRFX=usr.bin/makewhatis/ depend; make DIRPRFX=usr.bin/makewhatis/ all; make DIRPRFX=usr.bin/makewhatis/ DESTDIR=/usr/obj/usr/src/i386 install /usr/obj/usr/src/i386/usr/src/usr.bin/makewhatis created for /usr/src/usr.bin/makewhatis make: don't know how to make bsd.README. Stop *** Error code 2 Stop in /usr/src. *** Error code 1 World builds fine, here. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Be careful mounting -stable partitions on -current
rob [EMAIL PROTECTED] writes: I mounted my -stable /usr partition on -current /mnt to copy over a kernel config file, and when I finally fired up -stable, the /usr partition was borked. Fsck couldn't fix it manually. Luckily I had backups. It said that the master record didn't match the alternate. I might have rebooted without unmounting the -stable partition. There's nothing wrong with your partition, but there's a bug in your version of fsck. You can fix your partition with 'fsck -b 32 -y', but you really should update your system. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Re: Be careful mounting -stable partitions on -current
I cvsup'd on Friday of last week, after I restored /usr. Did the fix come later than that? I'm kind of afraid to try it again :) Thanks, Rob. - Original Message - From: Dag-Erling Smorgrav [EMAIL PROTECTED] To: rob [EMAIL PROTECTED] Sent: 29 Jul 2002 18:26:23 rob [EMAIL PROTECTED] writes: I mounted my -stable /usr partition on -current /mnt to copy over a kernel config file, and when I finally fired up -stable, the /usr partition was borked. Fsck couldn't fix it manually. Luckily I had backups. It said that the master record didn't match the alternate. I might have rebooted without unmounting the -stable partition. There's nothing wrong with your partition, but there's a bug in your version of fsck. You can fix your partition with 'fsck -b 32 -y', but you really should update your system. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: unkillable process :-\
In the last episode (Jul 29), Mikhail Teterin said: KOffice's kword is stuck here... Can not be killed even with -9. Sits idle, with its window open, but not updating: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 1042 88248 1 0 96 0 119296 28105 - WWs pm0:00,00 kword /tmp/k The W in STAT means it's been swapped out. I don't know what WW means, though. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Mike Barcroft [EMAIL PROTECTED] writes: Thanks. Do you want to increase the tinderbox to run twice a day? Sure, done. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: install -d -C (was: Re: cvs commit: src/share/man/man5 make.conf.5 src/share/examples/etc make.conf)
On Fri, Jul 19, 2002 at 10:55:56PM +1000, Bruce Evans wrote:
On Fri, 19 Jul 2002, Ruslan Ermilov wrote:
On Fri, Jul 19, 2002 at 03:05:37PM +0300, Ruslan Ermilov wrote:
...
On Fri, Jul 19, 2002 at 09:21:14PM +1000, Bruce Evans wrote:
On Thu, 18 Jul 2002, Ruslan Ermilov wrote:
ru 2002/07/18 05:07:49 PDT
Modified files:
etc Makefile
[...]
usr.sbin/ypserv Makefile
Log:
s/${INSTALL} -c/${INSTALL} ${COPY}/
Strongly unapproved by: bde.
This change is to help work around the foot-shooting of making -d
incompatible with -C and -p in install(1)'s flags. It abuses the old
...
Since its first revision (install.1,v 1.7 and install.c,v 1.16 they
were incompatible). Later on, in rev. 1.26, it was made a no-op,
I think this makes -c vs -d moot.
just to support INSTALL=install -C in /etc/make.conf.
-C is not really like -c. It really means unbreak the default of !-c,
and preserve certain metadata. Preserving the metadata is the main
point of this option, but IIRC it was made as much like -c as possible
just as a first attempt to kill -c.
OpenBSD merged these changes and since then they still have them
incompatible.
That was probably a mistake. Certainly merging it all back was. -C
is our (half my) flag, so we should know its intended use :-).
There are two ways to proceed:
1. Rename COPY to INSTALL_COPY (that was my plan), optionally giving
it by default an empty value. This shouldn't harm third-party
makefiles as -c is now an effective no-op. But this would make
us even more compatible with OpenBSD that has:
: INSTALL_COPYThe old usage of this flag is obsolescent since install(1)
: now copies by default. However, it can also be used to
: specify that a file not be copied unless it is different
: (via the -p option). See install(1) for details. This
: is to be used when building our own install script so
: that the entire system can either be installed with copies,
: or copy-if-different using a single knob. [-c]
OTOH, if we go this way we can get rid of ugly ${COPY} completely.
I'd like to get rid of it too. But not in RELENG_4. -c has been the default
for long enough now in -current. As you know, there are various problems
in using the correctly named variable for install(1)'s flags (INSTALLFLAGS)
to actually hold install's flags in a general way (mainly, this variable
already exists and is used in a non-general way). However, the old hack
of putting the flags in the same variable as the command still works well
except for the -[Cp] vs -d conflict. This depends on the flags not being
order-dependent.
OK, -[CpS] are now ignored with -d, and I've dropped support for COPY.
I have a question. Why COPY can't be removed from RELENG_4 as well?
Ports that use COPY (there are many of them) will see it as an empty
string.
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
[EMAIL PROTECTED] Sunbay Software AG,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.512.251Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
msg41506/pgp0.pgp
Description: PGP signature
