Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Dec 2005 19:15:18 -0000
From:      "Tony" <tony.xiong@friwo.com>
To:        <freebsd-stable@freebsd.org>
Subject:   Re: (by tony.j.x@163.com)freebsd-stable Digest, Vol 140, Issue 13
Message-ID:  <7BB35345ED22456B89488D42631CC284@Proxyserver>
References:  <20051224120148.8F72116A426@hub.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
hgfd
----- Original Message -----
From: <freebsd-stable-request@freebsd.org>
To: <freebsd-stable@freebsd.org>
Sent: Saturday, December 24, 2005 8:01 PM
Subject: Fw: (by tony.j.x@163.com)freebsd-stable Digest, Vol 140, Issue 13


> Send freebsd-stable mailing list submissions to
> freebsd-stable@freebsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> or, via email, send a message with subject or body 'help' to
> freebsd-stable-request@freebsd.org
>
> You can reach the person managing the list at
> freebsd-stable-owner@freebsd.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of freebsd-stable digest..."
>
>
> Today's Topics:
>
>    1. Making a data DVD with 4.10 and dvd+rw-format (Radoslav Mitov)
>    2. StorageWorks (Anton Nikiforov)
>    3. Re: SSH login takes very long time...sometimes (JoaoBR)
>    4. OpenSSH does not honour WITHOUT_KERBEROS (Alastair D'Silva)
>    5. Re: StorageWorks (Wilko Bulte)
>    6. Re: StorageWorks (Anton Nikiforov)
>    7. sys/compat/linux/linux_socket.c - log() message without
>       trailing \n (Stanislaw Halik)
>    8. ACPI and SC_PIXEL_MODE problems in 6-stable (iwant4x4jeep)
>    9. Re: ACPI and SC_PIXEL_MODE problems in 6-stable (Xin LI)
>   10. Re: SSH login takes very long time...sometimes (James Tanis)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 24 Dec 2005 00:11:29 +0200
> From: Radoslav Mitov <rmitov@interbgc.com>
> Subject: Making a data DVD with 4.10 and dvd+rw-format
> To: freebsd-stable@freebsd.org
> Message-ID: <43AC7611.7040104@interbgc.com>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Did you try with growisofs -dvd-compat -Z /dev/cd0*a* -J -R ?
> I had the same problem but , i tried with this device (cd0_a)_ and it
> worked.
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 24 Dec 2005 02:13:38 +0300
> From: Anton Nikiforov <anton@nikiforov.ru>
> Subject: StorageWorks
> To: stable@freebsd.org,  hardware@freebsd.org
> Message-ID: <43AC84A2.9090804@nikiforov.ru>
> Content-Type: text/plain; charset="us-ascii"
>
> Dear ALL!
> I have a Intel XEON based server and Compaq StorageWorks FC adapter with
> FC disk subsystem.
> I did not found any info about drivers available in
> FreeBSD-5.4-RELEASE-p8 (maybe vendor developed drivers/utilities?).
>
> Could you please help? is there any solution to make this three parts
> (server, FC adapter and disk subsystem) to work under FreeBSD?
>
> Best regards,
> Anton
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/x-pkcs7-signature
> Size: 2218 bytes
> Desc: S/MIME Cryptographic Signature
> Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20051224/5b315
f56/smime-0001.bin
>
> ------------------------------
>
> Message: 3
> Date: Fri, 23 Dec 2005 21:19:58 -0200
> From: JoaoBR <joao@matik.com.br>
> Subject: Re: SSH login takes very long time...sometimes
> To: freebsd-stable@freebsd.org
> Message-ID: <200512232119.58748.joao@matik.com.br>
> Content-Type: text/plain;  charset="iso-8859-1"
>
> On Friday 23 December 2005 20:26, James Tanis wrote:
> > What reason is that? A reverse-lookup is no longer really a valid way
> > of filtering out the undesireable unless your lucky enough to be
> > dealing only with those who have the knowledge and ability to control
> > those entries. Most residential ips either have no reverse-lookup or
>
> I guess you are wrong
>
> you can fake your IP and you can fake your hostname, but exactly for
security
> reasons, since we believe that beeing a a network admin is not because of
> luck but knowledge, and we also believe that this person has a certain
> responsibility and so he will probably not set up false dns reverse data.
>
> so when I check your IP and hostname you send me and when this do not
match
> the reverse info I get I can suppose you do not have good intentions or
you
> do not have the knowledge to set your network up. Both cases may not be
> welcome on my network and you get kicked out. Like you see here the
decision
> is the owner's one who can or not enter his home.
>
> so reverse dns is a absolute valid check - what never was so important as
> today since each newborn already knows how to fake IP's
>
> and when your residential Ip provider do not has a correct reverse DNS get
> yourself a more serious one
>
> anyway, you are mixing things up since you do not need a valid reverse dns
to
> configure your sshd, the server admin can disable this lookup or use the
> local host file - or you may like the "clever way" and forget to set or
> delete your resolv.conf
>
> Joćo
>
>
>
>
>
>
>
> A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada
segura.
> Service fornecido pelo Datacenter Matik  https://datacenter.matik.com.br
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 24 Dec 2005 10:24:09 +1100
> From: "Alastair D'Silva" <alastair@newmillennium.net.au>
> Subject: OpenSSH does not honour WITHOUT_KERBEROS
> To: <stable@freebsd.org>
> Message-ID: <200512232324.jBNNOA15067738@locutus.newmillennium.net.au>
> Content-Type: text/plain; charset="us-ascii"
>
> Building OpenSSH (as part of buildworld) from a RELENG_6 tree (RELENG_5
> works fine from memory) results in binaries linked against the Kerberos
> libraries, even when NO_KERBEROS is set in make.conf.
>
> Although these libraries exist in the host environment, they do not in the
> target environment (because it is being built with NO_KERBEROS set).
>
> --
> Alastair D'Silva            mob: 0423 762 819
> Networking Consultant       fax: 0413 181 661
> New Millennium Networking   web: http://www.newmillennium.net.au
>
>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 24 Dec 2005 00:25:24 +0100
> From: Wilko Bulte <wb@freebie.xs4all.nl>
> Subject: Re: StorageWorks
> To: Anton Nikiforov <anton@nikiforov.ru>
> Cc: stable@freebsd.org, hardware@freebsd.org
> Message-ID: <20051223232523.GA1628@freebie.xs4all.nl>
> Content-Type: text/plain; charset=us-ascii
>
> On Sat, Dec 24, 2005 at 02:13:38AM +0300, Anton Nikiforov wrote..
> > Dear ALL!
> > I have a Intel XEON based server and Compaq StorageWorks FC adapter with
> > FC disk subsystem.
> > I did not found any info about drivers available in
> > FreeBSD-5.4-RELEASE-p8 (maybe vendor developed drivers/utilities?).
> >
> > Could you please help? is there any solution to make this three parts
> > (server, FC adapter and disk subsystem) to work under FreeBSD?
>
> *What* Compaq StorageWorks adapter?  There are lots of different
> adapters, both from own Compaq production as well as QLogic and Emulex
> OEM origin.  Only the Qlogics have a driver in FreeBSD, isp(4).
>
> --
> Wilko Bulte wilko@FreeBSD.org
>
>
> ------------------------------
>
> Message: 6
> Date: Sat, 24 Dec 2005 02:46:18 +0300
> From: Anton Nikiforov <anton@nikiforov.ru>
> Subject: Re: StorageWorks
> To: Wilko Bulte <wb@freebie.xs4all.nl>
> Cc: stable@freebsd.org, hardware@freebsd.org
> Message-ID: <43AC8C4A.6090707@nikiforov.ru>
> Content-Type: text/plain; charset="us-ascii"
>
> Wilko Bulte wrote:
> > On Sat, Dec 24, 2005 at 02:13:38AM +0300, Anton Nikiforov wrote..
> >
> >>Dear ALL!
> >>I have a Intel XEON based server and Compaq StorageWorks FC adapter with
> >>FC disk subsystem.
> >>I did not found any info about drivers available in
> >>FreeBSD-5.4-RELEASE-p8 (maybe vendor developed drivers/utilities?).
> >>
> >>Could you please help? is there any solution to make this three parts
> >>(server, FC adapter and disk subsystem) to work under FreeBSD?
> >
> >
> > *What* Compaq StorageWorks adapter?  There are lots of different
> > adapters, both from own Compaq production as well as QLogic and Emulex
> > OEM origin.  Only the Qlogics have a driver in FreeBSD, isp(4).
> >
> It is now working under windows and Device manager saying only the
> following:
> Compaq Storage Works 64/66 Fibre host Bus adapter
> Tomorrow i'll try to open my HP box and see what is on the board.
>
> Best regards,
> Anton
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/x-pkcs7-signature
> Size: 2218 bytes
> Desc: S/MIME Cryptographic Signature
> Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20051224/b4811
6d0/smime-0001.bin
>
> ------------------------------
>
> Message: 7
> Date: Sat, 24 Dec 2005 03:14:55 +0100
> From: Stanislaw Halik <weirdo@tehran.lain.pl>
> Subject: sys/compat/linux/linux_socket.c - log() message without
> trailing \n
> To: stable@freebsd.org
> Message-ID: <20051224021455.GA55140@tehran.lain.pl>
> Content-Type: text/plain; charset="iso-8859-2"
>
> hello,
>
> I got such entry mailed to me in last periodic run:
>
> obsolete pre-RFC2553 sockaddr_in6 rejectedarplookup 62.21.28.103 failed:
host is not on local network
>
> I've grepped through sys/compat/linux/linux_socket.c and looks like
> there should be an \n on line 157.
>
> regards,
>
> --
> Stanis³aw Halik, http://tehran.lain.pl
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 187 bytes
> Desc: not available
> Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20051224/a7aeb
2d9/attachment-0001.bin
>
> ------------------------------
>
> Message: 8
> Date: Sat, 24 Dec 2005 07:41:52 +0300 (MSK)
> From: "iwant4x4jeep" <iwant4x4jeep@yandex.ru>
> Subject: ACPI and SC_PIXEL_MODE problems in 6-stable
> To: stable@freebsd.org
> Message-ID: <43ACD190.000004.31939@webmail11.yandex.ru>
> Content-Type: text/plain;  charset="US-ASCII"
>
> I'm upgrade my FreeBSD5.4 system to 6.0-STABLE. Now ACPI suspend-to-ram
(sleepstate #3) don't work ( before upgrade all works fine)
>
> Processor - Pentium 4 2.4Ghz
> Mother Board - ASUS P4PE
>
> # dmesg | grep -i acpi
> ACPI APIC Table: <ASUS   P4PE    >
>
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
,C
> MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> acpi0: <ASUS P4PE> on motherboard
> acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 22
> acpi0: Power Button (fixed)
> pci_link0: <ACPI PCI Link LNKA> irq 5 on acpi0
> pci_link1: <ACPI PCI Link LNKB> irq 9 on acpi0
> pci_link2: <ACPI PCI Link LNKC> irq 9 on acpi0
> pci_link3: <ACPI PCI Link LNKD> irq 9 on acpi0
> pci_link4: <ACPI PCI Link LNKE> irq 10 on acpi0
> pci_link5: <ACPI PCI Link LNKF> on acpi0
> pci_link6: <ACPI PCI Link LNKG> on acpi0
> pci_link7: <ACPI PCI Link LNKH> irq 11 on acpi0
> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
> acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
> cpu0: <ACPI CPU> on acpi0
> acpi_throttle0: <ACPI CPU Throttling> on cpu0
> acpi_button0: <Power Button> on acpi0
> pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
> pci0: <ACPI PCI bus> on pcib0
> pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
> pci1: <ACPI PCI bus> on pcib1
> pcib2: <ACPI PCI-PCI bridge> at device 30.0 on pci0
> pci2: <ACPI PCI bus> on pcib2
> fdc0: <floppy drive controller> port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on
acpi0
> ppc0: <ECP parallel printer port> port 0x378-0x37f,0x778-0x77b irq 7 drq 3
on ac
> pi0
> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
> sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
> atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
>
> When I (as usually before) enter in console 'acpiconf -s 3' (Really I use
sudo, so type 'sudo acpiconf -s 3', computer suspends, but don't resume
after power on.
>
> I have problem with hi-ressolution modes in console ( Using pathes from
DragonFlyBSD project, which is allready included with freebsd since 6.0).
> I'm enabled VESA and SC_PIXEL_MODE options in kernel, when I enter
'vidcontrol -i mode' - all modes(what i need) displays, but if I use
vidcontrol MODE_279 (for example), monitor enter 1024x768 mode, but I can't
see anything.
> First time I think that I do something wrong (Don't load needed fonts for
example), but when I try it on another computer-  I can't believe my eyes..
It was real 1024x768 in FreeBSD Console !!!
>
> P.S.
> I am not think that you'll help me, but I tried...
>
>
> ------------------------------
>
> Message: 9
> Date: Sat, 24 Dec 2005 15:34:21 +0800
> From: Xin LI <delphij@gmail.com>
> Subject: Re: ACPI and SC_PIXEL_MODE problems in 6-stable
> To: iwant4x4jeep@yandex.ru
> Cc: stable@freebsd.org
> Message-ID:
> <a78074950512232334h177cc0e7n825e866adf64baa4@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Hi,
>
> On 12/24/05, iwant4x4jeep <iwant4x4jeep@yandex.ru> wrote:
> > I'm upgrade my FreeBSD5.4 system to 6.0-STABLE. Now ACPI suspend-to-ram
(sleepstate #3) don't work ( before upgrade all works fine)
> >
> > Processor - Pentium 4 2.4Ghz
> > Mother Board - ASUS P4PE
> >
> > # dmesg | grep -i acpi
> > ACPI APIC Table: <ASUS   P4PE    >
> >
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
,C
> > MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
> > acpi0: <ASUS P4PE> on motherboard
> > acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 22
> > acpi0: Power Button (fixed)
> > pci_link0: <ACPI PCI Link LNKA> irq 5 on acpi0
> > pci_link1: <ACPI PCI Link LNKB> irq 9 on acpi0
> > pci_link2: <ACPI PCI Link LNKC> irq 9 on acpi0
> > pci_link3: <ACPI PCI Link LNKD> irq 9 on acpi0
> > pci_link4: <ACPI PCI Link LNKE> irq 10 on acpi0
> > pci_link5: <ACPI PCI Link LNKF> on acpi0
> > pci_link6: <ACPI PCI Link LNKG> on acpi0
> > pci_link7: <ACPI PCI Link LNKH> irq 11 on acpi0
> > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
> > acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
> > cpu0: <ACPI CPU> on acpi0
> > acpi_throttle0: <ACPI CPU Throttling> on cpu0
> > acpi_button0: <Power Button> on acpi0
> > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
> > pci0: <ACPI PCI bus> on pcib0
> > pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
> > pci1: <ACPI PCI bus> on pcib1
> > pcib2: <ACPI PCI-PCI bridge> at device 30.0 on pci0
> > pci2: <ACPI PCI bus> on pcib2
> > fdc0: <floppy drive controller> port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on
acpi0
> > ppc0: <ECP parallel printer port> port 0x378-0x37f,0x778-0x77b irq 7 drq
3 on ac
> > pi0
> > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
> > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
> > atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
> >
> > When I (as usually before) enter in console 'acpiconf -s 3' (Really I
use sudo, so type 'sudo acpiconf -s 3', computer suspends, but don't resume
after power on.
> >
> > I have problem with hi-ressolution modes in console ( Using pathes from
DragonFlyBSD project, which is allready included with freebsd since 6.0).
> > I'm enabled VESA and SC_PIXEL_MODE options in kernel, when I enter
'vidcontrol -i mode' - all modes(what i need) displays, but if I use
vidcontrol MODE_279 (for example), monitor enter 1024x768 mode, but I can't
see anything.
> > First time I think that I do something wrong (Don't load needed fonts
for example), but when I try it on another computer-  I can't believe my
eyes.. It was real 1024x768 in FreeBSD Console !!!
>
> Are you sure that your configuration cacn support MODE_279?  Will
> other modes work?
>
> Cheers,
> --
> Xin LI <delphij@delphij.net> http://www.delphij.net
>
> ------------------------------
>
> Message: 10
> Date: Sat, 24 Dec 2005 03:11:30 -0500
> From: James Tanis <jtanis@pycoder.org>
> Subject: Re: SSH login takes very long time...sometimes
> To: JoaoBR <joao@matik.com.br>
> Cc: freebsd-stable@freebsd.org
> Message-ID:
> <65dcde740512240011y7c9e324esb3ceee331c5992c6@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> > you can fake your IP and you can fake your hostname, but exactly for
security
> > reasons, since we believe that beeing a a network admin is not because
of
> > luck but knowledge, and we also believe that this person has a certain
> > responsibility and so he will probably not set up false dns reverse
data.
> >
> > so when I check your IP and hostname you send me and when this do not
match
> > the reverse info I get I can suppose you do not have good intentions or
you
> > do not have the knowledge to set your network up. Both cases may not be
> > welcome on my network and you get kicked out. Like you see here the
decision
> > is the owner's one who can or not enter his home.
>
> If you truly believe one can easily fake their IP then a
> reverse-lookup is even more irrelevant because it doesnt take a genius
> to choose an ip and hostname that match. From what your saying
> falsifying the actual reverse-lookup record need not even be
> considered. I don't pretend to be any kind of hacker or security
> professional, I have no idea how involved spoofing a valid (not
> local-only) ip is or if it is indeed possible, but it seems to me that
> this ability would only make the reverse-lookup less reliable.
>
> >
> > so reverse dns is a absolute valid check - what never was so important
as
> > today since each newborn already knows how to fake IP's
> >
> > and when your residential Ip provider do not has a correct reverse DNS
get
> > yourself a more serious one
>
> A good many large ips do not assign a reverse lookup as that would
> also require a hostname. Since most residential users do not need a
> host name it isn't necessarily standard procedure to give them one.
>
> Isp that assign reverse lookup cause an even bigger problem because no
> one want to name their computers according to their isp,  for instance
> Charter likes to assign hostnames like:
> xxx-xxx-xxx-xxx.dhcp.xxx.xx.charter.com
>
> Which is very basically a hyphen delimited ip followed by an
> abbreviated city and state. Nothing wrong with the scheme but I don't
> really care to name my firewall that, I much prefer loki.pycoder.org.
> This in itself is not a sign of ill intent. Most residential users,
> whether they are knowledgeable or not will not all make sure to have
> their computers all reporting the hostname
> xxx-xxx-xxx-xxx.dhcp.xxx.xx.charter.com yet they have no ill intent.
> Clearly then reverse dns lookup is only desireable in specific
> situations where you know exactly where you'll be getting remote
> connections from and can accomodate if they do not have properly set
> reverse-lookup entries.
>
> >
> > anyway, you are mixing things up since you do not need a valid reverse
dns to
> > configure your sshd, the server admin can disable this lookup or use the
> > local host file - or you may like the "clever way" and forget to set or
> > delete your resolv.conf
>
> Exactly the point I was trying to argue. I've been using FreeBSD long
> enough to know my way around /etc as well as hold my own with BIND.. I
> was more than able to diagnose/fix the problem. That does not change
> the fact though that not everyone is able to administer their own dns,
> not because they do not know how, but because they do not have the
> right. How does this affect FreeBSD? Not at all, I'd just wish it
> didn't have to be in the default setup, but I've already lost interest
> in the subject as its really just an insignificant point that really
> didn't deserve this long of an email :P.
>
>
> >
> > Joćo
> >
> >
> >
> >
> >
> >
> >
> > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada
segura.
> > Service fornecido pelo Datacenter Matik  https://datacenter.matik.com.br
> > _______________________________________________
> > freebsd-stable@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org"
> >
>
>
> --
> James Tanis
> jtanis@pycoder.org
> http://pycoder.org
>
>
> ------------------------------
>
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>
> End of freebsd-stable Digest, Vol 140, Issue 13
> ***********************************************
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7BB35345ED22456B89488D42631CC284>