date:20011001


SÜren Schmidt wrote:

 It seems Maxim Sobolev wrote:
  Hi Soren,
 
  It seems that after a commit to reduce stack usage in ata driver some CDIO
  ioctl's stopped working. Particularly, CDIOCREADSUBCHANNEL now returns an
  'Invalid argument'. This could be verified by executing `cdcontrol stat'.

 Uhm:

 sos cdcontrol -f acd0 stat
 No current status info available
 No media catalog info available
 Left volume = 255, right volume = 255

 That looks pretty OK to me ...

No it isn't normal. Try to truss(1) it and see the problem which leads to the
first string to be  No current status info available. Alternatively, try to
boot 11 days old kernel and see the difference.

-Maxim


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ACPI: problem with fdc resource allocation


Maxim Sobolev wrote:

 Maxim Sobolev wrote:

  Andrey A. Chernov wrote:
 
   On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote:
Hi,
   
Finally decided to upgrade my current box to the post-ACPI/KSE and found
that I'm having problem with resource allocation for floppy disk controller.
I'm sure somebody already reported this some time ago, but the problems seems
still here, so I would like to see it resolved.
  
fdc0: cannot reserve I/O port range (1 ports)
  
   It seems that here is conflict with your device.hints, try to remove fdc
   from the hints.
  
   As I already write, it is very bad thing that ACPI is in conflicts with
   default hints file correctly describing devices used. ACPI must ignore
   duplicate devices from the hints.
  
   The problem with floppy is harder, because floppy controller present in
   ACPI but the floppy itself not present (on my motherboard at least), so
   in current situation fdc0 must not be in hints, but fd0 must be, it makes
   whole thing even more cryptic.
 
  Doesn't work, exactly the same problem - see attached device.hints.

 Knock, knock... Is anybody home?

Hmm, it is very sad to see that acpi code is totally unsupported, especially in the
spite of recent how to attract people to test -current thread. The problem is still
here, as of today's kernel.

-Maxim


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: reappearance of an old bug again? (microtime went backwards)


In message Pine.BSF.4.21.0109302134440.95162-10@beppo Matthew Jacob writes:
: -current as of the last day or so- anyone else seen?

Do these happen with acpi disabled?

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: cardbus nonfunctional in -current as of 9/24

2001-10-01 Thread Georg-W. Koltermann


At Sun, 30 Sep 2001 02:57:27 -0600,
Warner Losh wrote:
 
 Try disabling acpi and let me know what's what.
 
 Warner

Still the same without acpi.  Last night, undocked:

Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb0: TI1225 PCI-CardBus Bridge at 
device 4.0 on pci0
Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb0: PCI Memory allocated: 1000
Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to 
hard-routed irq 11
Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11
Sep 30 20:22:59 hunter /boot/kernel/kernel: cardbus0: Cardbus bus (newcard) on 
pccbb0
Sep 30 20:22:59 hunter /boot/kernel/kernel: pccard0: 16-bit PCCard bus on pccbb0
Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb1: TI1225 PCI-CardBus Bridge at 
device 4.1 on pci0
Sep 30 20:22:59 hunter /boot/kernel/kernel: pccbb1: PCI Memory allocated: 10001000
Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to 
hard-routed irq 11
Sep 30 20:22:59 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11
Sep 30 20:22:59 hunter /boot/kernel/kernel: cardbus1: Cardbus bus (newcard) on 
pccbb1
Sep 30 20:23:00 hunter /boot/kernel/kernel: pccard1: 16-bit PCCard bus on pccbb1
Sep 30 20:23:00 hunter /boot/kernel/kernel: isab0: PCI-ISA bridge at device 7.0 
on pci0
Sep 30 20:23:00 hunter /boot/kernel/kernel: isa0: ISA bus on isab0
[...]
Sep 30 20:23:00 hunter /boot/kernel/kernel: acd0: DVD-ROM TOSHIBA DVD-ROM 
SD-C2402 at ata1-master PIO4
Sep 30 20:23:00 hunter /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s4a
Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb0: card inserted: 
event=0x, state=
Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected
Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb1: card inserted: 
event=0x, state=
Sep 30 20:23:00 hunter /boot/kernel/kernel: pccbb1: Unsupported card type detected
Sep 30 20:23:00 hunter /boot/kernel/kernel: linprocfs registered

Today, docked:

Oct  1 09:01:16 hunter /boot/kernel/kernel: pccbb0: TI1225 PCI-CardBus Bridge at 
device 4.0 on pci0
Oct  1 09:01:16 hunter /boot/kernel/kernel: pccbb0: PCI Memory allocated: 1000
Oct  1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to 
hard-routed irq 11
Oct  1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11
Oct  1 09:01:16 hunter /boot/kernel/kernel: cardbus0: Cardbus bus (newcard) on 
pccbb0
Oct  1 09:01:16 hunter /boot/kernel/kernel: pccard0: 16-bit PCCard bus on pccbb0
Oct  1 09:01:16 hunter /boot/kernel/kernel: pccbb1: TI1225 PCI-CardBus Bridge at 
device 4.1 on pci0
Oct  1 09:01:16 hunter /boot/kernel/kernel: pccbb1: PCI Memory allocated: 10001000
Oct  1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr_linked: linked (60) to 
hard-routed irq 11
Oct  1 09:01:16 hunter /boot/kernel/kernel: pci_cfgintr: 0:4 INTA routed to irq 11
Oct  1 09:01:16 hunter /boot/kernel/kernel: cardbus1: Cardbus bus (newcard) on 
pccbb1
Oct  1 09:01:16 hunter /boot/kernel/kernel: pccard1: 16-bit PCCard bus on pccbb1
Oct  1 09:01:16 hunter /boot/kernel/kernel: isab0: PCI-ISA bridge at device 7.0 
on pci0
Oct  1 09:01:16 hunter /boot/kernel/kernel: isa0: ISA bus on isab0
[...]
Oct  1 09:01:17 hunter /boot/kernel/kernel: acd0: DVD-ROM TOSHIBA DVD-ROM 
SD-C2402 at ata1-master PIO4
Oct  1 09:01:17 hunter /boot/kernel/kernel: Mounting root from ufs:/dev/ad0s4a
Oct  1 09:01:17 hunter /boot/kernel/kernel: pccbb0: card inserted: 
event=0x, state=
Oct  1 09:01:17 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected
Oct  1 09:01:17 hunter /boot/kernel/kernel: pccbb1: card inserted: 
event=0x, state=
Oct  1 09:01:17 hunter /boot/kernel/kernel: pccbb1: Unsupported card type detected
Oct  1 09:01:17 hunter /boot/kernel/kernel: linprocfs registered
[...]
Oct  1 09:06:03 hunter su: gwk to root on /dev/ttyp2
Oct  1 09:09:58 hunter /boot/kernel/kernel: cstsevent occures, 0xd0d0d0d0
Oct  1 09:10:33 hunter last message repeated 35 times
Oct  1 09:12:34 hunter last message repeated 349 times
Oct  1 09:21:11 hunter last message repeated 3687 times
Oct  1 09:21:11 hunter su: gwk to root on /dev/ttyp4
Oct  1 09:21:11 hunter /boot/kernel/kernel: cstsevent occures, 0xd0d0d0d0
Oct  1 09:21:18 hunter last message repeated 66 times
Oct  1 09:21:19 hunter /boot/kernel/kernel: pccbb0: card inserted: 
event=0x83e58955, state=403d8308
Oct  1 09:21:19 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected
Oct  1 09:21:20 hunter /boot/kernel/kernel: pccbb0: card inserted: 
event=0x83e58955, state=403d8308
Oct  1 09:21:20 hunter /boot/kernel/kernel: pccbb0: Unsupported card type detected
Oct  1 09:21:22 hunter

ACPI and APM interoperability?

2001-10-01 Thread Georg-W. Koltermann


Hi,

I'm wondering how I should handle APM now that ACPI has basically
taken over power management responsibility.

It seems I still need to configure APM so that /dev/apm is there and
battery monitoring utilities like the GNOME battery_applet can work.
I also was able to suspend and resume my machine (DELL Inspiron 7500)
with APM being configured (and ACPI being active by default).  Sound
is dead after a resume, PCMCIA is dead after a couple of resumes, I
have to switch to text mode before suspend or else the LCD will turn
pale, but still, the basic functionality is there.  APM used to lockup
on resume, so this is a definite improvement.

Oh, and I'm wondering why a close of the lid only does a mild
suspend where the laptop still hums (disk?  fan?).  I need to do a
acpiconf -s3 in order to get it to really suspend.  Is this
configurable someplace?

--
Regards,
Georg.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

uucp user shell and home directory

2001-10-01 Thread Kris Kennaway


Can anyone tell me why the uucp user needs to have a default shell and
home directory set?

uucp:*:66:66:UUCP pseudo-user:/var/spool/uucppublic:/usr/libexec/uucp/uucico

Both of those no longer exist by default in FreeBSD, with my changes.
Is there any reason why this can't be changed to:

uucp:*:66:66:UUCP pseudo-user:/:/sbin/nologin

?

Kris
 PGP signature

freebsd-current@freebsd.org

2001-10-01 Thread jingdian


  
·úÂI³Ð·N¥H¦Û¥Ñ©M¦h¤¸ªº®É¶¡ªÅ¶¡³Ð³y¥X³Ì¦hªº¦¨ÁZ¡A¥H¶}µo³Ð·N©Mºc«ä¥ø¹º¬°¥D¡A¨Ã´£¨Ñ¨ä°õ¦æ¯à¤O¡C
  
·úÂI³Ð·Nªº¤u§@¦¨û³£¥H¾Ö¦³¬Û·íªº¤u§@¯à¤O©M¸gÅç¬°³Ì¤jªº¸ê²£¡A¨Ã¥B¬Û¤¬¿EÀy¶}µo³Ð·N¡Aª`·N®É¤U¥«³õ°Ó¾÷¡A¥H±À¼s³Ð·N²z©À¡C
¦UÓ¦¨û¿ì¨Æ®Ä²v©M°t¦X«×°ª¡A¯à¥H³Ìµuªº®É¶¡§¹¦¨³Ìºë½oªº§@«~¡A¤£½×¦b¸ê®Æ»`¶°¡AÁÙ¬O¦b±Ä³XÄá¼v¡B½s¿è³]p¤W§@³Ì·¥¦Üªºµo´§
¡C



---
---
ªA°È¶µ¥Ø¡G¥±³]p¡B¼s§i³]p¡BDM¡B®ü³ø¡B¤½¥q§Î¶HCI¡BÂø»x¼s§i¡B³ø¯È¼s§i¡B«¬¿ý¡B»¡©ú®Ñ¡B¦W¤ù³]p..

¡´®ÑÄy´Á¥Z
³æ¥U´Á¥Z«Ê±¨C¥ó\³]p5000\§¹½Z1500
®ÑÄy¤º¶¨C¶\³]p650\§¹½Z350

¡´Âø»x¼s§i
¸ó¶¡B©Ôªø¶¨C¥ó\³]p4000
¤º¶¨C¥ó\³]p3000

¡´³ø¯È¼s§i
¥þ20§å  ¨C¥ó\³]p5000
¥þ10§å¡B¥b20§å  ¨C¥ó\³]p3000

¡´¶Ç³æ¡BDM
A3  ³æ±\³]p2500  Âù±\³]p4500
A4  ³æ±\³]p1000  Âù±\³]p1500

¡´®ü³ø³]p
¥þ¶}¨C¥ó\³]p8000
µâ¥þ¡B¹ï¶}  ¨C¥ó\³]p4000
µâ¹ï¨C¥ó\³]p3000

¡´¤á¥~¼s§i
¼s§i©ÛµP¨C¥ó\³]p5500
¨®½c¼s§i±ªO\³]p4500
¦|¥¬¼s§i¨C¥ó\³]p3500
ºX¼m³]p¤@¦¡¨â´Ú\³]p2500

¡´±Ä³XÄá¼v¨C¹Ï\300\µ¹¤©¹q¤lÀÉ
---
---
·úÂI¼s§i³Ð·N§{
¦a§}¡G¥x¤¤¥«¥_¤Ù°Ï¤å¤ß¸ô¥|¬q182¸¹15¼Ó¤§7
¹q¸Ü¡G04-2291-2347

¥ø¹º°õ¦æ
ªô±Ò»¨ ¥ý¥Í
0922-789-018

³Ð·Nºô¯¸  http://jingdian.2u.com.tw/




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: uucp user shell and home directory

2001-10-01 Thread Sheldon Hearn




On Mon, 01 Oct 2001 02:02:46 MST, Kris Kennaway wrote:

 uucp:*:66:66:UUCP pseudo-user:/:/sbin/nologin

Please use /nonexistent while it's the prevailing convention, or change
the prevailing convention.

Thanks,
Sheldon.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: lpd: Host name for your address (fe80:....%xl0) unknown

2001-10-01 Thread Alexander Langer


Thus spake Hajimu UMEMOTO ([EMAIL PROTECTED]):

 alex 15329  ??  S  0:00.02 lpd -4
 alex alex@oink ~ $ lpq
 alex lpd: Host name for your address (fe80::250:baff:fed4:a512%xl0) unknown
 Sorry, but I cannot see this message, here.
 Could you please tell me how did you do?

I started lpd on this machine: (with the -4 flag, see above).

alex@oink ~ $ uname -a ; ifconfig -a
FreeBSD oink.cichlids.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sat Sep  1 15:25:41 CEST 
2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386
rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet 192.168.0.19 netmask 0xff00 broadcast 192.168.0.255
inet6 fe80::250:baff:fed4:a512%rl0 prefixlen 64 scopeid 0x1 
ether 00:50:ba:d4:a5:12 
media: Ethernet autoselect (100baseTX)
status: active
lp0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500
faith0: flags=8000MULTICAST mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 ::1 prefixlen 128 
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 
inet 127.0.0.1 netmask 0xff00 
ppp0: flags=8010POINTOPOINT,MULTICAST mtu 1500

This is the printcap from this machine:

lp|local line printer:\
:sh:\
:rm=neutron:\
:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:

Note that neutron has:
alex@oink ~ $ ping6 neutron
PING6(56=40+8+8 bytes) fe80::250:baff:fed4:a512%rl0 -- fe80:1::250:4ff:fe0f:5a27
16 bytes from fe80::250:4ff:fe0f:5a27%rl0, icmp_seq=0 hlim=64 time=2.492 ms
^X^C

(telnet6 works!)

Then I just start lpd (or lpd -4, same effect), and this happens.
when I do rm=192.168.0.1 in the printcap, I get:
root@oink ~ $ lpq
oink.cichlids.com: Warning: no daemon present
Rank   Owner  Job  Files Total Size
1stalex   0(standard input)  419326 bytes

lpd: Host name for your address (192.168.0.19) unknown

So, this MIGHT be the reason:  The IPv4 address is nonexistent,
but it displays the IPv6 address as error address.
However, it's still bad that he uses and IPv6 stuff when I specify -4

BTW, it works if I add a PTR for 192.168.0.19.

Alex

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: lpd: Host name for your address (fe80:....%xl0) unknown

2001-10-01 Thread Alexander Langer



BTW, the lpd server (neutron) is a
FreeBSD neutron.cichlids.com 4.3-STABLE FreeBSD 4.3-STABLE #0: Tue Jun  5 01:38:27 
CEST 2001 [EMAIL PROTECTED]:/storage/obj/storage/src/sys/NEUTRON  i386

I think the problem is on the server-side. (since the error messages
contains a xl0 string, which is the server's NIC).

Alex

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

HEADS UP: UUCP migration to ports

2001-10-01 Thread Kris Kennaway


Hi all,

As discussed on -arch, I've removed the UUCP utilities from the base
system, and they now live in the net/freebsd-uucp port.  I have left
the cu utility behind, because it reportedly has capabilities not
supported by tip at this time.  Ideally, it would be great if we can
get any missing capabilities added to tip so we can complete the
removal of cu, but that's a project for another time and possibly
another person (I've noticed OpenBSD have done some work in this
direction already).

I've verified that cu continues to build, but since I don't use it I
can't test whether it still works.  Please let me know of any problems
with this, or the UUCP port and I'll be happy to fix them.

Kris

P.S.  I'm running a post-commit buildworld now to verify that I
haven't broken the build.

 PGP signature

Some CDIO ioctl's are broken


Hi Soren,

It seems that after a commit to reduce stack usage in ata driver some CDIO
ioctl's stopped working. Particularly, CDIOCREADSUBCHANNEL now returns an
'Invalid argument'. This could be verified by executing `cdcontrol stat'.

Please fix.

-Maxim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Some CDIO ioctl's are broken

2001-10-01 Thread Søren Schmidt


It seems Maxim Sobolev wrote:
 Hi Soren,
 
 It seems that after a commit to reduce stack usage in ata driver some CDIO
 ioctl's stopped working. Particularly, CDIOCREADSUBCHANNEL now returns an
 'Invalid argument'. This could be verified by executing `cdcontrol stat'.

Uhm:

sos cdcontrol -f acd0 stat
No current status info available
No media catalog info available
Left volume = 255, right volume = 255

That looks pretty OK to me ...

-Søren

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: lpd: Host name for your address (fe80:....%xl0) unknown

2001-10-01 Thread Dag-Erling Smorgrav


Alexander Langer [EMAIL PROTECTED] writes:
 alex@oink ~ $ lpq
 lpd: Host name for your address (fe80::250:baff:fed4:a512%xl0) unknown

The server is reporting that it can't figure out who you are, and
therefore won't let you access the printer.  See hosts.lpd(5).  The
client is merely repeating the error message it got from the server.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: lpd: Host name for your address (fe80:....%xl0) unknown

2001-10-01 Thread Alexander Langer


Thus spake Dag-Erling Smorgrav ([EMAIL PROTECTED]):

  alex@oink ~ $ lpq
  lpd: Host name for your address (fe80::250:baff:fed4:a512%xl0) unknown
 The server is reporting that it can't figure out who you are, and
 therefore won't let you access the printer.  See hosts.lpd(5).  The
 client is merely repeating the error message it got from the server.

It's still using IPv6 though I told it to do IPv4.

Alex

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: lpd: Host name for your address (fe80:....%xl0) unknown

2001-10-01 Thread Hajimu UMEMOTO


 On Mon, 1 Oct 2001 15:29:43 +0200
 Alexander Langer [EMAIL PROTECTED] said:

alex Thus spake Dag-Erling Smorgrav ([EMAIL PROTECTED]):

  alex@oink ~ $ lpq
  lpd: Host name for your address (fe80::250:baff:fed4:a512%xl0) unknown
 The server is reporting that it can't figure out who you are, and
 therefore won't let you access the printer.  See hosts.lpd(5).  The
 client is merely repeating the error message it got from the server.

alex It's still using IPv6 though I told it to do IPv4.

Still, I cannot understand why it occures, and I cannot reproduce it,
here.

--
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: lpd: Host name for your address (fe80:....%xl0) unknown

2001-10-01 Thread Hajimu UMEMOTO


 On Mon, 1 Oct 2001 14:21:28 +0200
 Alexander Langer [EMAIL PROTECTED] said:

alex BTW, the lpd server (neutron) is a
alex FreeBSD neutron.cichlids.com 4.3-STABLE FreeBSD 4.3-STABLE #0: Tue Jun  5 
01:38:27 CEST 2001 [EMAIL PROTECTED]:/storage/obj/storage/src/sys/NEUTRON  
i386

alex I think the problem is on the server-side. (since the error messages
alex contains a xl0 string, which is the server's NIC).

Yes, lpd has this message, while lpq hasn't.
I'm trying to reproduce it on my 4.4-RELEASE box.

--
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

world broken in src/lib/libedit

2001-10-01 Thread Bernd Walter


[...]
cd /var/d10/FreeBSD-2001-10-01/src/lib/libc;make beforeinstall
cd /var/d10/FreeBSD-2001-10-01/src/lib/libcalendar; make beforeinstall
cd /var/d10/FreeBSD-2001-10-01/src/lib/libcalendar   sh 
/var/d10/FreeBSD-2001-10-01/src/tools/install.sh -C -o root -g wheel -m 444  
calendar.h /usr/obj/var/d10/FreeBSD-2001-10-01/src/i386/usr/include
cd /var/d10/FreeBSD-2001-10-01/src/lib/libcam;  make beforeinstall
cd /var/d10/FreeBSD-2001-10-01/src/lib/libcam   sh 
/var/d10/FreeBSD-2001-10-01/src/tools/install.sh -C -o root -g wheel -m 444  camlib.h 
/usr/obj/var/d10/FreeBSD-2001-10-01/src/i386/usr/include
cd /var/d10/FreeBSD-2001-10-01/src/lib/libdisk; make beforeinstall
cd /var/d10/FreeBSD-2001-10-01/src/lib/libdisk   sh 
/var/d10/FreeBSD-2001-10-01/src/tools/install.sh -C -o root -g wheel -m 444  libdisk.h 
/usr/obj/var/d10/FreeBSD-2001-10-01/src/i386/usr/include
cd /var/d10/FreeBSD-2001-10-01/src/lib/libedit; make beforeinstall
cd /var/d10/FreeBSD-2001-10-01/src/lib/libedit   sh 
/var/d10/FreeBSD-2001-10-01/src/tools/install.sh -C -o root -g wheel -m 444  
histedit.h /usr/obj/var/d10/FreeBSD-2001-10-01/src/i386/usr/include
install: histedit.h: No such file or directory
*** Error code 71

Stop in /var/d10/FreeBSD-2001-10-01/src/lib/libedit.
*** Error code 1

Stop in /var/d10/FreeBSD-2001-10-01/src.
*** Error code 1

Stop in /var/d10/FreeBSD-2001-10-01/src.
*** Error code 1

Stop in /var/d10/FreeBSD-2001-10-01/src.
1345.645u 386.311s 44:38.58 64.6%   1315+1849k 6670+1085io 2417pf+0w
Exit 1
ticso@cicely5# 

-- 
B.Walter  COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup   [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: uucp user shell and home directory

2001-10-01 Thread Joe Kelsey


Lyndon Nerenberg writes:
   Garrett == Garrett Wollman [EMAIL PROTECTED] writes:
  
  Garrett I remember, back in the mists of ancient time, it was
  Garrett common practice to provide ``anonymous UUCP'' service
  Garrett along the lines of anonymous FTP in (what was at that
  Garrett time) ARPANET.  
  
  Yup, I used to run one of those (ncc). osu-cis was probably the
  grandaddy of the anonymous UUCP sites. The convention seemed to be to
  use the login 'nuucp' for anonymous passwordless access. (And I
  wouldn't call it common -- there were only a handful sites that
  provided this type of service.)

The convention was to use ``uucp'' as the default anonymous login
service.  Some people had the mistaken impression that there was some
sort of hole in the uucp system which was caused by using uucp as a
default login for uucp service.  No such hole existed in modern uucico
processes, although there were bugs in early uucico (7th Edition
vintage) which may be the reason that these rumors started.

Of course, it didn't hurt the spread of these rumors that most BSD sites
were stuck in the 7th Edition heritage and never actually caught up to
the modern HoneyDanBer uucp.  With the HoneyDanBer uucp, there were no
security holes in uucico and it was completely safe to use uucp as an
anonymous login service.  However, most university sites mistakenly
perpetuated the nuucp service, mostly for administrative reasons.

That said, for max security it is always useful to have each site have
its own login, up to a point.  Some large uucp sites used to use common
logins simply because there was so little security risk (especially with
HoneyDanBer variety).  Certainly, anonymous uucp is more secure than
anonymous ftp.

/Joe

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: world broken in src/lib/libedit


On Mon, Oct 01, 2001 at 04:29:08PM +0200, Bernd Walter wrote:
 cd /var/d10/FreeBSD-2001-10-01/src/lib/libedit   sh 
/var/d10/FreeBSD-2001-10-01/src/tools/install.sh -C -o root -g wheel -m 444  
histedit.h /usr/obj/var/d10/FreeBSD-2001-10-01/src/i386/usr/include
 install: histedit.h: No such file or directory
 *** Error code 71

Known problem -- working on it.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

broken current

2001-10-01 Thread Gene Raytsin


hi,

44  camlib.h /usr/obj/usr/src/i386/usr/include
cd /usr/src/lib/libdisk;make beforeinstall
cd /usr/src/lib/libdisk   sh /usr/src/tools/install.sh -C -o root -g
wheel -m   444  libdisk.h
/usr/obj/usr/src/i386/usr/include
cd /usr/src/lib/libedit;make beforeinstall
cd /usr/src/lib/libedit   sh /usr/src/tools/install.sh -C -o root -g
wheel -m   444  histedit.h
/usr/obj/usr/src/i386/usr/include
install: histedit.h: No such file or directory


Getting this like 3d time as of today.
Any ideas?


Yevgeniy Raytsin| 
ITSP Extreme Telecom  |  
phone:  +380-44-2391429 |   

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: broken current


On Mon, Oct 01, 2001 at 10:49:16PM +0300, Gene Raytsin wrote:
 hi,

Hi.
 
 /usr/obj/usr/src/i386/usr/include
 install: histedit.h: No such file or directory
 
 Getting this like 3d time as of today.
 Any ideas?

Yeah, do what ever you do to retrieve this mailing list; then read any
new messages before sending out a current is broken email.
If you had done that you would have known I was working on this issue.
 
-- 
-- David  ([EMAIL PROTECTED])

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

oops [was: Re: broken current]

2001-10-01 Thread Gene Raytsin


On Mon, 01 Oct 2001 at 14:37:14 -0700, David O'Brien wrote:
 On Mon, Oct 01, 2001 at 10:49:16PM +0300, Gene Raytsin wrote:
  hi,
 
 Hi.
  
  /usr/obj/usr/src/i386/usr/include
  install: histedit.h: No such file or directory
  
  Getting this like 3d time as of today.
  Any ideas?
 
 Yeah, do what ever you do to retrieve this mailing list; then read any
 new messages before sending out a current is broken email.
 If you had done that you would have known I was working on this issue.
  
sorry man,
my falt :(
didn't mean to piss you off.

and I am sorry for offtopic, ofcourse

regards

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: oops [was: Re: broken current]


On Tue, Oct 02, 2001 at 12:43:50AM +0300, Gene Raytsin wrote:
 and I am sorry for offtopic, ofcourse

It wasn't off topic.  Users of -current just have responsibilities (such
as reading the freebsd-current list) before posting about a problem.
 
-- 
-- David  ([EMAIL PROTECTED])

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: uucp user shell and home directory

2001-10-01 Thread Daniel O'Connor



On 01-Oct-2001 Lyndon Nerenberg wrote:
  UUCP still gets used. It's one of the few sane ways to handle email in
  a laptop environment when you're always connecting through different
  dialups/ISPs. It has mostly fallen out of favour due to ignorance and
  FUD. Which is a shame, as it can still be a useful tool in certain
  situations.

I think a more 'modern' solution is POP or IMAP over SSH, you can also feed
SMTP over an SSH tunnel too (This is what I use).

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: uucp user shell and home directory

2001-10-01 Thread Julian Elischer


NO, 

POP and IMAP (I think) will lose all the envelope information,

UUCP keeps that..

SMTP is a PUSH operation..

so for a PULL operation that can handle envelope information (e.g. BCC)
you need UUCP

On Tue, 2 Oct 2001, Daniel O'Connor wrote:

 
 On 01-Oct-2001 Lyndon Nerenberg wrote:
   UUCP still gets used. It's one of the few sane ways to handle email in
   a laptop environment when you're always connecting through different
   dialups/ISPs. It has mostly fallen out of favour due to ignorance and
   FUD. Which is a shame, as it can still be a useful tool in certain
   situations.
 
 I think a more 'modern' solution is POP or IMAP over SSH, you can also feed
 SMTP over an SSH tunnel too (This is what I use).
 
 ---
 Daniel O'Connor software and network engineer
 for Genesis Software - http://www.gsoft.com.au
 The nice thing about standards is that there
 are so many of them to choose from.
   -- Andrew Tanenbaum
 
 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

Re: uucp user shell and home directory

2001-10-01 Thread Daniel O'Connor



On 02-Oct-2001 Julian Elischer wrote:
  POP and IMAP (I think) will lose all the envelope information,
  
  UUCP keeps that..

What use is it? I don't know what I'm missing...

  SMTP is a PUSH operation..

I meant that I tunnel SMTP back to my work to send email from a foreign
location.

---
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
The nice thing about standards is that there
are so many of them to choose from.
  -- Andrew Tanenbaum

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ACPI and APM interoperability?


In message [EMAIL PROTECTED] Scott Long writes:
: On Mon, Oct 01, 2001 at 10:50:17AM +0200, Georg-W. Koltermann wrote:
:  Hi,
:  
:  I'm wondering how I should handle APM now that ACPI has basically
:  taken over power management responsibility.
: 
: APM and ACPI are mutually exclusive from what I understand.  You should
: remove the apm device from your kernel config.

I've been able to run both with my VAIO.  However, my VAIO hangs
randomly with ACPI enabled (even when i have apm disable).

:  It seems I still need to configure APM so that /dev/apm is there and
:  battery monitoring utilities like the GNOME battery_applet can work.
: 
: Battery, temp, etc, can be monitored via the hw.acpi sysctl tree.
: Someone will have to do the required conversion to the various APM
: utilities is GNOME and whatever else.

Hmmm.  That's good to know.  I didn't know that until now.  I'll have
to reboot my vaio to see how good/bad this information is.

:  I also was able to suspend and resume my machine (DELL Inspiron 7500)
:  with APM being configured (and ACPI being active by default).  Sound
:  is dead after a resume,
: 
: What sound card?
: 
:  PCMCIA is dead after a couple of resumes,
: 
: Resource leak?  Warner?

I don't see this with my Inspiron 8000, so I don't care :-).

Seriously, I'm still running stable on my i8000.  I'll be cutting over
in a little bit (I can dual boot it now), so that will be less of an
issue going forward.

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ACPI and APM interoperability?

In message [EMAIL PROTECTED] Mitsuru IWASAKI writes:
: Generalized power-management interface API to have compatibility with
: APM and ACPI also is suggested long time ago;
:
:http://www.freebsd.org/cgi/getmsg.cgi?fetch=403390+406841+/usr/local/www/db/text/2001/freebsd-current/20010114.freebsd-current

I still have this message in my inbox :-). I liked the API presented
in it.

: Device node for ACPI is discussed bofore too; having only one /dev/acpi
: or having generalized nodes for each device types such as /dev/battery0
: but we couldn't reach the conclusion, now discussion stops...

I like what we do with the sound system. There's only /dev/dsp0 for
people that want blast sound. Under the covers the sound system hooks
up the drivers to that device. I think that doing /dev/battery would
be a good idea. Doing device plumbing like this isn't too bad with
newbus. Just make the battery device attach at either the acpi or apm
devices. I'm doing something similar right now with a FM USB Radio
driver I'm writing. I'm bringing Video 4 Linux API into the tree
(assuming I don't get shot first) because there are so many cool
progrms that work with that which don't work with FreeBSD.

: Any suggestions on it? Once we get the conclusion, we can start developing
: API and convert userland tools.

What other APIs are available? Do they fit our needs? What does
Linux or NetBSD do here? Anything interesting?

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ACPI: problem with fdc resource allocation


Mitsuru IWASAKI wrote:

 Hi,

  Maxim Sobolev wrote:
 
   Maxim Sobolev wrote:
  
Andrey A. Chernov wrote:
   
 On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote:
  Hi,
 
  Finally decided to upgrade my current box to the post-ACPI/KSE and found
  that I'm having problem with resource allocation for floppy disk 
controller.
  I'm sure somebody already reported this some time ago, but the problems 
seems
  still here, so I would like to see it resolved.

  fdc0: cannot reserve I/O port range (1 ports)

 It seems that here is conflict with your device.hints, try to remove fdc
 from the hints.

 As I already write, it is very bad thing that ACPI is in conflicts with
 default hints file correctly describing devices used. ACPI must ignore
 duplicate devices from the hints.

 The problem with floppy is harder, because floppy controller present in
 ACPI but the floppy itself not present (on my motherboard at least), so
 in current situation fdc0 must not be in hints, but fd0 must be, it makes
 whole thing even more cryptic.
   
Doesn't work, exactly the same problem - see attached device.hints.
  
   Knock, knock... Is anybody home?
 
  Hmm, it is very sad to see that acpi code is totally unsupported, especially in the
  spite of recent how to attract people to test -current thread. The problem is 
still
  here, as of today's kernel.

 I'm not sure exactly what's the problem you are having, but it's too
 little information to track it down...
 Could you send [EMAIL PROTECTED] ;
  - acpidump output; like
# acpidump -o your_machine_name.dsdt  your_machine_name.dsdt.asl
   I'll add them to
   http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp
  - dmesg output of kernel boot -v

Just sent it to you privately. After hiting sed button I've realised that machine_name 
that
you have requested != host_name. Since it isn't a brandname model you can identify it 
after
the mainboard name - Tyan-S1590.

-Maxim



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ACPI and APM interoperability?

2001-10-01 Thread Mitsuru IWASAKI

Hi,

On Mon, Oct 01, 2001 at 10:50:17AM +0200, Georg-W. Koltermann wrote:
Hi,

I'm wondering how I should handle APM now that ACPI has basically
taken over power management responsibility.

APM and ACPI are mutually exclusive from what I understand. You should
remove the apm device from your kernel config.

Yes, some older machines w/ ACPI can support both of them at the same time,
but most modern machines don't.

It seems I still need to configure APM so that /dev/apm is there and
battery monitoring utilities like the GNOME battery_applet can work.

Battery, temp, etc, can be monitored via the hw.acpi sysctl tree.
Someone will have to do the required conversion to the various APM
utilities is GNOME and whatever else.

Yes, you can get battery info. in C code like;
sysctlbyname(hw.acpi.battery.time, percent, len, NULL, 0);
Note that these MIBs maybe change in future...

Generalized power-management interface API to have compatibility with
APM and ACPI also is suggested long time ago;
http://www.freebsd.org/cgi/getmsg.cgi?fetch=403390+406841+/usr/local/www/db/text/2001/freebsd-current/20010114.freebsd-current

Device node for ACPI is discussed bofore too; having only one /dev/acpi
or having generalized nodes for each device types such as /dev/battery0
but we couldn't reach the conclusion, now discussion stops...

Any suggestions on it? Once we get the conclusion, we can start developing
API and convert userland tools.

I also was able to suspend and resume my machine (DELL Inspiron 7500)
with APM being configured (and ACPI being active by default). Sound
is dead after a resume,

What sound card?

PCMCIA is dead after a couple of resumes,

Resource leak? Warner?

Is yours similar to any data at there (Dell_I7500*) ?
http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp

I guess CardBus controllers are _SB_.PCI0.CB1_ and _SB_.PCI0.CB2_
but I didn't see any sleep/wakeup hack for them...

Thanks

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Today's -CURRENT buildworld breaks: libedit/Makefile wants histedit.h


On Mon, Oct 01, 2001 at 08:06:20AM -0700, David Wolfskill wrote:
 Today's -CURRENT build breaks:

Thanks for the note.  I'm looking now what is different from my test box
and what everyone else has.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

panic in ipfw code

2001-10-01 Thread Daniel Rock


Hi,

I wondered nobody noticed this bug so far.
The kernel panics if you feed him with unnumbered firewall rules
(like ipfw add allow all from any to any)

Fix is simple. In the code the wrong loop variable was used:

Index: ip_fw.c
===
RCS file: /data/cvs/src/sys/netinet/ip_fw.c,v
retrieving revision 1.170
diff -u -r1.170 ip_fw.c
--- ip_fw.c 27 Sep 2001 23:44:26 -  1.170
+++ ip_fw.c 1 Oct 2001 17:20:39 -
@@ -1654,9 +1654,9 @@
 
/* If entry number is 0, find highest numbered rule and add 100 */
if (ftmp-fw_number == 0) {
-   LIST_FOREACH(ftmp, head, next) {
-   if (ftmp-fw_number != IPFW_DEFAULT_RULE)
-   nbr = ftmp-fw_number;
+   LIST_FOREACH(fcp, head, next) {
+   if (fcp-fw_number != IPFW_DEFAULT_RULE)
+   nbr = fcp-fw_number;
else
break;
}


-- 
Daniel

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ACPI: problem with fdc resource allocation

2001-10-01 Thread Mitsuru IWASAKI


Hi,

  I'm not sure exactly what's the problem you are having, but it's too
  little information to track it down...
  Could you send [EMAIL PROTECTED] ;
   - acpidump output; like
 # acpidump -o your_machine_name.dsdt  your_machine_name.dsdt.asl
I'll add them to
http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp
   - dmesg output of kernel boot -v
 
 Just sent it to you privately. After hiting sed button I've realised that 
machine_name that
 you have requested != host_name. Since it isn't a brandname model you can identify 
it after
 the mainboard name - Tyan-S1590.

Thanks, I've just add them to 
http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/Tyan-S1590.asl?cvsroot=freebsd-jp

The problem is here, right?
 can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_BUFFER_LIMIT

I'm sure _SB_.PCI0.ISA_.FDC0._CRS (Current Resource Settings) have some
problems (not sure in BIOS or ACPICA yet).  I could reproduce the problem
which you reported.  Trace attached in this mail.
I'll try to make a workaround tomorrow or next, sorry.
# Here in Japan, it's midnight...

Thanks

% acpicadb Tyan-S1590.dsdt
Parsing Methods:...
55 Control Methods found and parsed (259 nodes total)
ACPI Namespace successfully loaded at root 0x8087414
- f FDC0
\_SB_.PCI0.ISA_.FDC0 (0x8098da8) - Device
- debug _SB_.PCI0.ISA_.FDC0._CRS
Executing \_SB_.PCI0.ISA_.FDC0._CRS
0 #0008 [00]  Name BUF0  (Path \)
[00]  (
5 #0011 [01]  Buffer
[01]  (
7 #000A [02]  (UINT8)  0x18,
9 #0033 [02]  ByteList  (Length 0x0018)  
[02]  }
[01]  }

% 
ArgObj:0x80acfa8 Obj Integer 0018
00021 #008C [00]  CreateByteField
[00]  (
00022 #002D [01]  BUF0,  (Path 
00026 #000A [01]  (UINT8)  0x02,
00028 #002D [01]  IOLO  (Path 
[01]  }

% 
ArgObj:0x80acf28 NodeName BUF0 Type-Buffer
ArgObj:0x80af1a8 Obj Integer 0002
ArgObj:0x80af0a8 NodeName IOLO Type-BuffField
0002C #008C [00]  CreateByteField
[00]  (
0002D #002D [01]  BUF0,  (Path 
00031 #000A [01]  (UINT8)  0x03,
00033 #002D [01]  IOHI  (Path 
[01]  }

% 
ArgObj:0x80acf28 NodeName BUF0 Type-Buffer
ArgObj:0x80af328 Obj Integer 0003
ArgObj:0x80af228 NodeName IOHI Type-BuffField
00037 #008C [00]  CreateByteField
[00]  (
00038 #002D [01]  BUF0,  (Path 
0003C #000A [01]  (UINT8)  0x04,
0003E #002D [01]  IORL  (Path 
[01]  }

% 
ArgObj:0x80acf28 NodeName BUF0 Type-Buffer
ArgObj:0x80af4a8 Obj Integer 0004
ArgObj:0x80af3a8 NodeName IORL Type-BuffField
00042 #008C [00]  CreateByteField
[00]  (
00043 #002D [01]  BUF0,  (Path 
00047 #000A [01]  (UINT8)  0x05,
00049 #002D [01]  IORH  (Path 
[01]  }

% 
ArgObj:0x80acf28 NodeName BUF0 Type-Buffer
ArgObj:0x80af628 Obj Integer 0005
ArgObj:0x80af528 NodeName IORH Type-BuffField
0004D #008C [00]  CreateByteField
[00]  (
0004E #002D [01]  BUF0,  (Path 
00052 #000A [01]  (UINT8)  0x19,
00054 #002D [01]  IRQL  (Path 
[01]  }

% 
ArgObj:0x80acf28 NodeName BUF0 Type-Buffer
ArgObj:0x80af7a8 Obj Integer 0019
ArgObj:0x80af6a8 NodeName IRQL Type-BuffField
dsopcode-0677 [09] DsEvalBufferFieldOpera: Field size 208 exceeds Buffer size 192 
(bits)
PsExecute: method failed - \_SB_.PCI0.ISA_.FDC0._CRS (0x8098fa8)
Execution of \_SB_.PCI0.ISA_.FDC0._CRS failed with status AE_AML_BUFFER_LIMIT



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: uucp user shell and home directory

2001-10-01 Thread Lyndon Nerenberg


 Ruslan == Ruslan Ermilov [EMAIL PROTECTED] writes:

Ruslan It doesn't really matter what the home directory is set to
Ruslan (IIRC), but the shell must be uucico(8).

No, this is wrong on both counts.

By convention, the home directory of the uucp login has corresponded
to the UUCP PUBDIR. Traditionally this was /usr/spool/uucppublic, and
maps to /var/spool/uucppublic these days. Thus, if I wanted to
copy a file to the public file area on machine b I would incant

 uucp file b!~

and the uucico on the remote end would expand the '~' to
/usr/spool/uucppublic.

This usage predates (and probably inspired) the common behavior of 
current shells handling of '~' expansion. While no modern UUCP I'm
aware of uses the value of pw-pw_dir to derive PUBDIR, POLA would
imply that the interpretation of '~uucp' should be the same for
both the uucp(1) command and for shells that do ~ expansion. Therefore
I would recommend keeping the UUCP home directory as /var/spool/uucppublic.
If you want to be paranoid you make this directory owned by root.wheel
and mode 0555 without breaking anything.

As for the `uucp' account's shell, this should be set to
/sbin/nologin.  The purpose of the uucp entry in /etc/passwd is to
provide a unique runtime uid for the setuid UUCP components. Note that
there are some periodic maintenance scripts that should be run if you
actively use UUCP. These traditionally run under the `uucp' identity,
so you need to make sure that they will continue to function with
/sbin/nologin. (Which they should, otherwise they would have barfed
with uucico as the shell.) The shell for the uucp account should most
certainly NOT be uucico! And you should *never* allow remote site UUCP
logins (those that run uucico) under the `uucp' login, for obvious
security reasons. Instead, create seperate unique logins for each
remote site, just as you would for each of your shell accounts, but
set the login shell to uucico.

--lyndon

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: uucp user shell and home directory

2001-10-01 Thread Garrett Wollman


On Mon, 01 Oct 2001 11:51:32 -0600, Lyndon Nerenberg [EMAIL PROTECTED] 
said:

 And you should *never* allow remote site UUCP logins (those that run
 uucico) under the `uucp' login, for obvious security reasons.

I remember, back in the mists of ancient time, it was common practice
to provide ``anonymous UUCP'' service along the lines of anonymous FTP
in (what was at that time) ARPANET.  I find it hard to imagine anyone
doing so today, but OTOH I find it hard to imagine anyone using UUCP
at all today, so it is obviously my imagination which has failed
rather than reality.

-GAWollman


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: uucp user shell and home directory

2001-10-01 Thread Lyndon Nerenberg


 Garrett == Garrett Wollman [EMAIL PROTECTED] writes:

Garrett I remember, back in the mists of ancient time, it was
Garrett common practice to provide ``anonymous UUCP'' service
Garrett along the lines of anonymous FTP in (what was at that
Garrett time) ARPANET.  

Yup, I used to run one of those (ncc). osu-cis was probably the
grandaddy of the anonymous UUCP sites. The convention seemed to be to
use the login 'nuucp' for anonymous passwordless access. (And I
wouldn't call it common -- there were only a handful sites that
provided this type of service.)

Garrett I find it hard to imagine anyone doing so
Garrett today, but OTOH I find it hard to imagine anyone using
Garrett UUCP at all today, so it is obviously my imagination
Garrett which has failed rather than reality.

UUCP still gets used. It's one of the few sane ways to handle email in
a laptop environment when you're always connecting through different
dialups/ISPs. It has mostly fallen out of favour due to ignorance and
FUD. Which is a shame, as it can still be a useful tool in certain
situations.

--lyndon

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Today's -CURRENT buildworld breaks: libedit/Makefile wants histedit.h

2001-10-01 Thread David Wolfskill


Today's -CURRENT build breaks:

 stage 4: populating /usr/obj/usr/src/i386/usr/include
--
...
cd /usr/src/lib/libcam; make beforeinstall
cd /usr/src/lib/libcam   sh /usr/src/tools/install.sh -C -o root -g wheel -m 444  
camlib.h /usr/obj/usr/src/i386/usr/include
cd /usr/src/lib/libdisk;make beforeinstall
cd /usr/src/lib/libdisk   sh /usr/src/tools/install.sh -C -o root -g wheel -m 444  
libdisk.h /usr/obj/usr/src/i386/usr/include
cd /usr/src/lib/libedit;make beforeinstall
cd /usr/src/lib/libedit   sh /usr/src/tools/install.sh -C -o root -g wheel -m 444  
histedit.h /usr/obj/usr/src/i386/usr/include
install: histedit.h: No such file or directory
*** Error code 71
1 error
*** Error code 2
1 error
*** Error code 2


Looks as if histedit.h has been in src/include (vs.  src/lib/libedit) for
a while, now

(Ref. src/lib/libedit/Makefile 1.22, line 33.)

Cheers,
david
-- 
David H. Wolfskill  [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: uucp user shell and home directory

2001-10-01 Thread Ruslan Ermilov


On Mon, Oct 01, 2001 at 02:02:46AM -0700, Kris Kennaway wrote:
 Can anyone tell me why the uucp user needs to have a default shell and
 home directory set?
 
 uucp:*:66:66:UUCP pseudo-user:/var/spool/uucppublic:/usr/libexec/uucp/uucico
 
 Both of those no longer exist by default in FreeBSD, with my changes.
 Is there any reason why this can't be changed to:
 
 uucp:*:66:66:UUCP pseudo-user:/:/sbin/nologin
 
As already was told on that channel, this comes from the times
when ``uucp'' user didn't have password and the account was used
for UUCP communication over serial lines.  Any dialup UUCP user
should have a passwd(5) entry built like the ``uucp''.

It doesn't really matter what the home directory is set to (IIRC),
but the shell must be uucico(8).

It doesn't make any sense though to enable the ``uucp'' account.
Moreover, doing so may have a bad impact on system's security,
as many UUCP related files are owner by the user ``uucp''.

Having said that, I'm with Sheldon on how this change should be
done, i.e., change home directory to /nonexistent and shell to
/sbin/nologin.


Cheers,
-- 
Ruslan Ermilov  Oracle Developer/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

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

HEADS UP kernel burncd change..

2001-10-01 Thread Søren Schmidt



Kernel and burncd must be in sync again, a make kernel followed
by a make world should do it.

-Søren

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ACPI and APM interoperability?

2001-10-01 Thread Søren Schmidt


It seems Scott Long wrote:
 On Mon, Oct 01, 2001 at 10:50:17AM +0200, Georg-W. Koltermann wrote:
  I also was able to suspend and resume my machine (DELL Inspiron 7500)
  with APM being configured (and ACPI being active by default).  Sound
  is dead after a resume,
 
 What sound card?
 
  PCMCIA is dead after a couple of resumes,
 
 Resource leak?  Warner?

It has been like that on -current for about a month or so on my 
Latitude as well, try to use slot1 instead of slot0, that makes
it work better here...

-Søren

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

microtime

2001-10-01 Thread Matthew Jacob



yes, with acpi timer disabled this seems to have gone away



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ACPI: problem with fdc resource allocation

2001-10-01 Thread Mitsuru IWASAKI


Hi,

 Maxim Sobolev wrote:
 
  Maxim Sobolev wrote:
 
   Andrey A. Chernov wrote:
  
On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote:
 Hi,

 Finally decided to upgrade my current box to the post-ACPI/KSE and found
 that I'm having problem with resource allocation for floppy disk controller.
 I'm sure somebody already reported this some time ago, but the problems seems
 still here, so I would like to see it resolved.
   
 fdc0: cannot reserve I/O port range (1 ports)
   
It seems that here is conflict with your device.hints, try to remove fdc
from the hints.
   
As I already write, it is very bad thing that ACPI is in conflicts with
default hints file correctly describing devices used. ACPI must ignore
duplicate devices from the hints.
   
The problem with floppy is harder, because floppy controller present in
ACPI but the floppy itself not present (on my motherboard at least), so
in current situation fdc0 must not be in hints, but fd0 must be, it makes
whole thing even more cryptic.
  
   Doesn't work, exactly the same problem - see attached device.hints.
 
  Knock, knock... Is anybody home?
 
 Hmm, it is very sad to see that acpi code is totally unsupported, especially in the
 spite of recent how to attract people to test -current thread. The problem is still
 here, as of today's kernel.

I'm not sure exactly what's the problem you are having, but it's too
little information to track it down...
Could you send [EMAIL PROTECTED] ;
 - acpidump output; like
   # acpidump -o your_machine_name.dsdt  your_machine_name.dsdt.asl
  I'll add them to
  http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/?cvsroot=freebsd-jp
 - dmesg output of kernel boot -v

Mike, anything add to this?

Thanks

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ACPI and APM interoperability?

2001-10-01 Thread Mike Smith


 : APM and ACPI are mutually exclusive from what I understand.  You should
 : remove the apm device from your kernel config.
 
 I've been able to run both with my VAIO.  However, my VAIO hangs
 randomly with ACPI enabled (even when i have apm disable).

You shouldn't be able to do this. 8)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: ACPI and APM interoperability?