Re: panic: zone: entry not free

[Matthew Dillon]

:Jos Backus wrote:
:> 
:> > That is, INVARIANTS in kernel incompatible with dynamic loading.
:> 
:> Somehow this strikes me as a Bad Thing...
:
:Invariants is not for the production minded. It is for those who
:work with things likely to get broken. Say, for instance, -current.
::-)
:
:--
:Daniel C. Sobral   (8-DCS)

I would disagree with that.  Invariants are for people who want
their data to be as safe as possible and don't mind eating a little
cpu doing extra sanity checks in the kernel.  It is something I would
almost certainly enable in a production kernel.

DIAGNOSTIC, on the otherhand, is something I would only enable in
an extreme test environment.

:d...@newsguy.com
:d...@freebsd.org

-Matt
Matthew Dillon 



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

RE: Staroffice 5.01?

[Doug Rabson]

On Thu, 25 Feb 1999, Daniel O'Connor wrote:

> 
> On 24-Feb-99 Alok K. Dhir wrote:
> >  Has anyone gotten SO501 to run on -current?
> I have and its quite good, but it hangs occasionally..
> The actual 'officey' stuff is quite good tho (ie WP, spreadsheet etc..)
> 
> What problems are you having?

Hangs sometimes for me too.  It also has problems printing which is
strange. From looking at the output, a stray character creeps into the
postscript near the beginning.  If I fix that by hand the postscript will
print.

--
Doug Rabson Mail:  d...@nlsystems.com
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

RE: Staroffice 5.01?

[Daniel O'Connor]

On 25-Feb-99 Doug Rabson wrote:
>  Hangs sometimes for me too.  It also has problems printing which is
>  strange. From looking at the output, a stray character creeps into the
>  postscript near the beginning.  If I fix that by hand the postscript will
>  print.
Weird stuff..
I haven't used it much, but I did do a Word 97 to Word 95 conversion in it and 
it worked
perfectly which impressed me :)

---
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 majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Promise IDE board docs

[S�ren Schmidt]

It seems Mike Tancsa wrote:
> On 24 Feb 1999 18:39:36 -0500, in sentex.lists.freebsd.current you wrote:
> >
> >Hmm, which suggests that I need to leave the "do it by hand" code in
> >there and recommend removing the BIOS :(
> 
> Are there any plans to support the Promise Fast Trak IDE RAID controller ?

Well, sortof, the FastTrak is AFAIK the exact same HW as the Ultra33, just
with a more "advanced" BIOS that does the RAID stuff. The current planned
support is to use it just as a Ultra33 controller, and then use ccd to
do the RAID magic under FreeBSD.


-Søren


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: please don't check mail for root logins

[Rahul Dhesi]

Good idea, thanks, and I now realize that it won't work, and neither
will changing /bin/login -- because sshd does not seem to honor either
one.

I will have to try re-installing sshd with the --with-login flag.  When
I last tried that flag, the use of a .hushlogin file caused failed
logins for some reason, so I reinstalled sshd without --with-login .

Drat!  I hate it when software bypasses standard system routines.

Rahul

> Date:  Wed, 24 Feb 99 23:26:47 PST
> From:  Matthew Dillon 
> To:Rahul Dhesi 
> Cc:freebsd-current@FreeBSD.ORG
> Message-Id: <199902250726.xaa00...@apollo.backplane.com>
> Subject: Re: please don't check mail for root logins

> :I have a suggestion for the FreeBSD maintainers.
> :
> :In /bin/login, please don't check for mail when the user is root.  And
> :in the case that the mail filesystem is mounted via NFS from a
> :non-responding server, it hangs root logins.
> :
> :Root logins on machine A should never ever ever require machine B
> :to be up.
> :
> :Rahul
> 
> You should be able to fix this trivially in /etc/login.conf.  Look
> at the standard: entry's setenv for MAIL and do something similar for
> root's, pointing MAIL somewhere else.  I haven't tried this myself,
> but it should work.
> 
>   -Matt
>   Matthew Dillon 
>   
> 
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Missing files/directories

[Sheldon Hearn]

On Wed, 24 Feb 1999 23:55:11 EST, Tom Torrance at home wrote:

> I am still very suspicious of those dot files even if I am the
> only one.

Hi Tom,

Since it does indeed look like you _are_ the only one, I'd suggest
putting this discussion on hold until you can come back to the list
with the only thing that will carry the thread forward in a productive
direction.  Namely, come up with an _exact_ set of (preferably
command-line) instructions for reproducing the problem.

Since we're discussing free software, you can be fairly confident that
this isn't a conspiracy to shut you up. It's just difficult for anyone
to comment on symptoms he or she imagines impossible without seeing the
problem you're reporting. If you can produce a step-by-step guide to
reproducing the problem, you're more likely to get some solid answers to
your questions.

Until then, I imagine everyone else is probably thinking the same thing
I am -- "wtf?!" :-)

Later,
Sheldon

PS: I'd also suggest that you use just _one_ FreeBSD mailing list when
you do follow up.


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Promise IDE board docs

[Mike Tancsa]

At 04:49 AM 2/25/99 , Søren Schmidt wrote:
>It seems Mike Tancsa wrote:
>> On 24 Feb 1999 18:39:36 -0500, in sentex.lists.freebsd.current you wrote:
>> >
>> >Hmm, which suggests that I need to leave the "do it by hand" code in
>> >there and recommend removing the BIOS :(
>> 
>> Are there any plans to support the Promise Fast Trak IDE RAID controller ?
>
>Well, sortof, the FastTrak is AFAIK the exact same HW as the Ultra33, just
>with a more "advanced" BIOS that does the RAID stuff. The current planned
>support is to use it just as a Ultra33 controller, and then use ccd to
>do the RAID magic under FreeBSD.

Interesting.  So the BIOS doesnt actually do the RAID work ? It still needs
to be done in software ?

---Mike
**
Mike Tancsa, Network Admin*  m...@sentex.net
Sentex Communications Corp,   *  http://www.sentex.net/mike
Cambridge, Ontario*  01.519.651.3400
Canada*


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: listproc problem?

[Thomas T. Veldhouse]

>> Also, as a side note, how do I set up my box to use PostFix instead of
>> sendmail?  I heard that it was (or was considered) included in the
>> 3.1-RELEASE, it just wasn't enabled by default.
>
>It was shouted down as unnecessary bloat in favour of a port. However, I
>haven't seen this port submitted yet..until then looks like you'll have to
>install manually.
>

I have done that and it works pretty well.  It is still BETA though.  It is
probably just as well that it isn't in the core distribution.



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Missing files/directories

[Brian Somers]

[.]
> PS: I'd also suggest that you use just _one_ FreeBSD mailing list when
> you do follow up.

Indeed - Tom's using RELENG_3, not -current ;^P

-- 
Brian   
  
Don't _EVER_ lose your sense of humour !




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Missing files/directories

[Brian Somers]

> Hi Brian,
> 
> It was a good thought, but we can't put the blame on bad hardware.
> 
> These tests were done on the RELENG_3 system cvsup'd 
> as of Feb 22 @ 20:00 EST. All tests were run internal to the
> same machine. So that I don't remain the only guy in the world
> to see these test results, Control files are included so you 
> can test locally:-)

Your best test engine would be either -current or using the latest 
ppp from my web site.  The RELENG_3 version doesn't have a lot of 
recent changes.

> "ppp0 -direct" on localhost is started by port 6671.
> 
> I know (now) that setting up the test this way the ppp's were
> communicating via localhost rather than the tunnel, but this way
> was much cleaner as far as verifying exactly how close the results
> were to what I saw running the server under 2.2-stable. There were
> differences, but the main issues are demonstrated.

Hmm, not 100% - see below.

> You will recall our discussion about the server hanging around
> under 2.2-stable after the client is terminated? Required by the
> RFCs you said? Under RELENG_3 the server meekly goes away, which
> makes sense to me.
> 
> Two tests were done. The first involved "kill -KILL clientpid".
> The second was "kill -TERM clientpid".
> In the first test, the server illegally removed the default route.
> In the second test, the server did the same - neither ppp actioned
> the second command in the linkdown scripts.

If a kill -KILL results in your default route disappearing, then that 
conclusively proves that ppp is not to blame :-/  If find this a bit 
strange though - this certainly doesn't happen on my machines - I 
frequently instruct my machine to connect to the 'net and then tunnel 
into an internal machine with something like ``ssh realmachine ssh 
internalmachine ppp -direct in''.  In my setup, internalmachine is 
using realmachine as it's default gateway, and that default has never 
disappeared unexpectedly.

WRT the second command, it looks like you've hit a problem that's 
next on my list to fix - since the radius changes, the interface 
netmasks are a bit faulty, and it's likely that there were some 
not-quite-so-bad problems in RELENG_3 too.  Your commands should 
work ok if you change them to ``add 10.0.1.1/32 127.0.0.1'' and 
``add 10.0.1.2/32 127.0.0.1''.

> I was surprised that the first test ended immediately - I thought
> the LQR packets would cause the server to terminate after 1 minute.

When you specify the device as a tcp link or a program to execute, 
ppp can tell immediately when the peer goes away - the results are 
exactly the same as loosing carrier.  This is why testing via the tcp 
link doesn't always cover all angles (I've suffered from these 
problems myself).

The only problem is when we're using a device that's a character 
special that doesn't support CD (carrier)

> Files:
> test1.netstat0shows routing after boot
> test1.netstat1shows routing after "ppp -background testloop"
> test1.psaxl   show ps results for the executing processes.
> test1.netstat2shows routing after killing the client.
> test1.tun0ifconfig while active.
> test1.tun1ifconfig while active.
> test2.netstat routing tables after terminating the client.
> Logs are supplied for both tests.
> 
> I hope that this is very helpful to you. I really appreciate
> your efforts!!

And I yours - thanks.

> Cheers,
> Tom

-- 
Brian   
  
Don't _EVER_ lose your sense of humour !




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: please don't check mail for root logins

[jcptch]

On Thu, Feb 25, 1999 at 04:15:30AM -0800, Rahul Dhesi wrote:

> Good idea, thanks, and I now realize that it won't work, and neither
> will changing /bin/login -- because sshd does not seem to honor either
> one.

You could try taking a look in sshd_config and setting UseLogin Yes.

-- 
Jon Parise (par...@pobox.com)  .  .: current environment :.
Rochester Inst. of Technology  :  OSF1 grace V4.0 878 alpha
Computer Science House Member  :  user: jcptch  host: grace
https://www.csh.rit.edu/~jon/  :  term: vt100tty: ttysb


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

ELECTRONIC ILLUSIONS FOR MAGICIANS

[magickey]

 
Dear magician:
This letter is to present you my new catalogue, videocatalogue (VHS PAL 
videocassette) AND WEB   
   of electronic equipment for  
magicians. 
I am looking forward to hearing  from you with any questions you have.
Yours faithfully
Eduardo Hernando de Liñán
Director of La Llave Magica



If you wish to be removed from this list please contact
WRITE IN Subject: DELETE
magic...@arrakis.es

AMIGO EN LA MÁGIA: 

ME DIRIJO A TI PARA PRESENTARTE MI COLECCÍÓN DE EFECTOS DE ILUSIONISMO 
ELÉCTRÓNICOS, PODRAS ENCONTRARLOS EN   
JUNTO A ELLOS, TAMBIÉN ENCONTRARAS UN CATÁLOGO DE PIROTÉCNIA, PARA 
ESCENARIOS Y DE EFECTOS DE ILUMINACIÓN DE ÚLTIMA GENERACIÓN. 

EN EL DESEO DE QUE ELLOS TE APORTEN TANTAS SATISFACCIONES COMO ME HAN 
PROPORCIONADO A MÌ, QUEDO ENTERAMENTE A TU DISPOSICIÓN. 
Atentamente 
Eduardo Hernando de Liñan

 PARA NO RECIBIR NUNCA MÁS NUESTRA CIRCULAR, ENVIE UN MAIL INDICANDO EN 
Asunto: DELETE
magic...@arrakis.es




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: IDE CDROM not found with PIIX4 chipset, -current kernel

[Pierre Beyssac]

On Thu, Feb 25, 1999 at 02:09:31PM +1030, Greg Lehey wrote:
> > Wow. Thanks a million! I didn't even have to go so far, I just
> > deleted wd2 and wd3 and acd0 now appears as if by magic. I can't
> > tell you how extremely stupid I now feel...
> 
> You shouldn't do.  What you did shouldn't have any effect on the
> problem.

Yet it definitely has. The CDROM never probed before, now it does
(at least every time I tried: only about half a dozen reboots for
the moment).

So there's probably something strange with the probe code and how
it interacts with wd[0-3] declarations.

So the CDROM now probes correctly, but OTOH I didn't manage to use
it. I get the following message every time:

bofh /kernel: atapi1.0: controller not ready for cmd

The machine then seems to hang, more or less (X11 kindly moves the
mouse pointer, but the network is dead).

> FreeBSD still has difficulties with some ATAPI CD-ROM drives.  If you
> continue to have trouble (and I suspect you will), you should enter a
> PR with send-pr or at http://www.freebsd.org/send-pr.html.  Make sure
> to give exact details of your hardware and software configuration.

I tried to find out why it worked with a Linux kernel by comparing
our IDE code and theirs, but it was way beyond my comprehension.
I'm not trained for the black magic of IDE probing.

I'll try to investigate some more, then I'll try a bug report.
-- 
Pierre Beyssac  p...@enst.fr


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: IDE CDROM not found with PIIX4 chipset, -current kernel

[Pierre Beyssac]

On Thu, Feb 25, 1999 at 04:20:20PM +1100, Bruce Evans wrote:
> doesn't see the slave, and control passes to the atapi probe which does
> support cdrom drives.  It works worst with a cdrom master and no slave.

Sadly, that's exactly the out-of-the-box Dell configuration: 2
disks on the first IDE, just a CDROM on the second IDE.

I'd have changed the hardware configuration to swap the second disk
with the CDROM, but I thought it would be much better if it could
be made to work, since it apparently can...
-- 
Pierre Beyssac  p...@enst.fr


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: IDE CDROM not found with PIIX4 chipset, -current kernel

[Sheldon Hearn]

On Thu, 25 Feb 1999 17:16:53 +0100, Pierre Beyssac wrote:

> I tried to find out why it worked with a Linux kernel by comparing
> our IDE code and theirs, but it was way beyond my comprehension.
> I'm not trained for the black magic of IDE probing.

I used this particular issue for the launch of my first adventure into
serial console kernel debugging. Multo fun.

I can offer you two interesting points:

1) I have an ATAPI drive that FreeBSD 2.2-STABLE won't detect on boot if
   it contains a disc.

2) I found that stepping through the kernel caused exactly the same
   problems I was having with accessing my one ATAPI drive that I
   experience just running normally with my other drive. So it looks
   like at least one problem regarding ATAPI has to do with timings.

So far, the conversations I've had with clueful FreeBSD hackers have led
me to accept the following:

A) The ATAPI standard is weak and the variety of implimentations thereof
   is even worse.

B) The odds that your ATAPI CDROM drive will behave predictably in
   accordance with said standards are directly proportional to its age.
   It seems that newer (24xspeed+) drives suck.

C) The ATAPI code in FreeBSD is about as good as our hackers care to
   make it, given the demotivating impact of A and B above.

I spent a good few days stepping around my kernel over serial
connection, using a "working" 4xspeed drive and a "broken" 36xspeed
drive and testing a reproducible fault with cdcontrol. I'm a pretty
stubborn guy, but I gave up.

Ciao,
Sheldon.


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: IDE CDROM not found with PIIX4 chipset, -current kernel

[Sheldon Hearn]

On Thu, 25 Feb 1999 17:26:14 +0100, Pierre Beyssac wrote:

> I'd have changed the hardware configuration to swap the second disk
> with the CDROM, but I thought it would be much better if it could
> be made to work, since it apparently can...

Nope, it's almost certainly better to have your random access disks on
two different controllers.

Ciao,
Sheldon.


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

RE: IDE CDROM not found with PIIX4 chipset, -current kernel

[Ladavac Marino]

> -Original Message-
> From: Sheldon Hearn [SMTP:sheld...@iafrica.com]
> Sent: Thursday, February 25, 1999 5:40 PM
> To:   Pierre Beyssac
> Cc:   Greg Lehey; freebsd-current@FreeBSD.ORG
> Subject:  Re: IDE CDROM not found with PIIX4 chipset, -current
> kernel 
> 
> 
> 
> On Thu, 25 Feb 1999 17:16:53 +0100, Pierre Beyssac wrote:
> 
> > I tried to find out why it worked with a Linux kernel by comparing
> > our IDE code and theirs, but it was way beyond my comprehension.
> > I'm not trained for the black magic of IDE probing.
> 
> I used this particular issue for the launch of my first adventure into
> serial console kernel debugging. Multo fun.
> 
> I can offer you two interesting points:
> 
> 1) I have an ATAPI drive that FreeBSD 2.2-STABLE won't detect on boot
> if
>it contains a disc.
> 
> 2) I found that stepping through the kernel caused exactly the same
>problems I was having with accessing my one ATAPI drive that I
>experience just running normally with my other drive. So it looks
>like at least one problem regarding ATAPI has to do with timings.
> 
> So far, the conversations I've had with clueful FreeBSD hackers have
> led
> me to accept the following:
> 
> A) The ATAPI standard is weak and the variety of implimentations
> thereof
>is even worse.
> 
> B) The odds that your ATAPI CDROM drive will behave predictably in
>accordance with said standards are directly proportional to its
> age.
>It seems that newer (24xspeed+) drives suck.
> 
> C) The ATAPI code in FreeBSD is about as good as our hackers care to
>make it, given the demotivating impact of A and B above.
> 
> I spent a good few days stepping around my kernel over serial
> connection, using a "working" 4xspeed drive and a "broken" 36xspeed
> drive and testing a reproducible fault with cdcontrol. I'm a pretty
> stubborn guy, but I gave up.
[ML]  Heh, it would seem that the prevailing OS is not really
ATAPI
compliant and the manufacturers try to make their hardware more
easily detectable for the prevailing OS family.

How about this "brilliant" idea: put a logic analyzer on the IDE
cable
and measure the timings the prevailing OS family/BIOS uses?

Sadly, I don't have access to a logic analyzer :(  Anyone with
(good) connections to a (university) hardware lab?

/Marino

> Ciao,
> Sheldon.
> 
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: IDE CDROM not found with PIIX4 chipset, -current kernel

[Sheldon Hearn]

On Thu, 25 Feb 1999 18:07:39 +0100, Ladavac Marino wrote:

>   How about this "brilliant" idea: put a logic analyzer on the IDE
> cable and measure the timings the prevailing OS family/BIOS uses?

My understanding from previous conversations is that the situation
you're often faced with is that you'll break support for one set of
drives by fixing support for another.

Ciao,
Sheldon.

PS: It's not usually necessary to quote back the entire content of a
message you reply to when you're replying less than 30 minutes after
the original was posted. :)


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: IDE CDROM not found with PIIX4 chipset, -current kernel

[Pierre Beyssac]

On Thu, Feb 25, 1999 at 06:40:35PM +0200, Sheldon Hearn wrote:
> > I'd have changed the hardware configuration to swap the second disk
> > with the CDROM, but I thought it would be much better if it could
> > be made to work, since it apparently can...
> 
> Nope, it's almost certainly better to have your random access disks on
> two different controllers.

Oh yes, I won't try to argue against that since I quite agree. I'll
try this once I get tired trying my current config :-). I was just
considering that the more configurations that work, the better for
FreeBSD's ease of installation/configuration. The problem is bound
to happen again since this is a configuration (CDROM by itself on
a second IDE controller) currently sold by Dell.

Don't ask me why, Dell always tends to make weird choices regarding
how they install IDE devices and controllers. I suspect this has
to do with this weird, differently abled stuff sold by a major
company which lost the source code for it, arrogant enough to call
it an OS.
-- 
Pierre Beyssac  p...@enst.fr


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Promise IDE board docs

[Jake]

> >Well, sortof, the FastTrak is AFAIK the exact same HW as the Ultra33, just
> >with a more "advanced" BIOS that does the RAID stuff. The current planned
> >support is to use it just as a Ultra33 controller, and then use ccd to
> >do the RAID magic under FreeBSD.
> 
> Interesting.  So the BIOS doesnt actually do the RAID work ? It still needs
> to be done in software ?

I think what he means is that if the OS supports it, the RAID stuff is
done in the BIOS.  We don't yet support it, so it has to be done with software.

as an aside, I'd suggest vinum over ccd for the software part.
I have two 4 gig drives, and the performance is on par with what 
I've seen from single 8 and even 12 gig drives.

Cheers,
-- 
obfuscate v.t. darken; obscure; bewilder.

int i;main(){for(;i["]

Re: Staroffice 5.01?

[Ollivier Robert]

According to Daniel O'Connor:
> unzip -L the setup.zip file in the inst directory.
> cd into the inst directory and run setup

You don't even need this with 5.01. I installed it today on my 4.0-CURRENT
machine and everything went fine. I'used the same method as described on
.
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: please don't check mail for root logins

[Ollivier Robert]

According to Rahul Dhesi:
> Good idea, thanks, and I now realize that it won't work, and neither
> will changing /bin/login -- because sshd does not seem to honor either
> one.

The sshd in ports should honor the login.conf stuff. One of the patches
adds FreeBSD as a target with login_cap.h.

Look into patch-af in sshd/patches.
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Staroffice 5.01?

[Alok K. Dhir]

Thanks all - I finally got it to work.  It still stops and asks me to
"insert StarOffice 5.01, yes, no, cancel".  Hitting cancel a few times
allows the installation to continue.

I had gotten this far before, but didn't try hitting cancel.

Does anyone's installation allow them to use the web browsing or 
email component?

Al

On Thu, 25 Feb 1999, Ollivier Robert wrote:

> 
> According to Daniel O'Connor:
> > unzip -L the setup.zip file in the inst directory.
> > cd into the inst directory and run setup
> 
> You don't even need this with 5.01. I installed it today on my 4.0-CURRENT
> machine and everything went fine. I'used the same method as described on
> .
> --
> Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr
> FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999
> 
> 
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
> 
> 

 \||/_
Alok K. Dhir Phone: +1.202.473.2446   oo \
S11-151, ISGMC   Email:  ad...@worldbank.org  L_
The World Bank Group   Washington, DC  \/
|
"Unix _is_ user friendly - it just chooses friends selectively..."



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: mount -o union broken recently?

[John Polstra]

In article ,
Tony Finch   wrote:
> I have been experimenting with union mounts today with a recent
> -stable (cvsupped yesterday), and I haven't had much luck.
> 
> Because cvsup likes to obliterate local changes,

You might wish to CVSup the repository itself (not use checkout
mode), and then apply the techniques described in the CVSup FAQ
to maintain your local changes.  You can find the CVSup FAQ at
.

I've never messed with "mount -o union" before.  But looking at the
tests you did, I'm not so sure you've drawn the right conclusions.
Here's your test that failed:

> # mount
> /dev/da0s1a on / (local, writes: sync 420 async 3185)
> procfs on /proc (local)
> /dev/da0s1e on /www (local, writes: sync 2 async 0)
> # mount /dev/da0s1f /srcdelta
> # ls -l /srcdelta
> total 1
> drwxr-xr-x   6 root wheel 512 Feb 18 10:32 sys
> # umount /srcdelta
> # ls /usr/src
> COPYRIGHT UPDATING  include   share
> CVS   bin   kerberosIVsys
> Makefile  contrib   lib   tools
> Makefile.inc0 cryptolibexec   usr.bin
> Makefile.inc1 etc   release   usr.sbin
> Makefile.upgrade  games sbin
> READMEgnu   secure
> # mount -o union /dev/da0s1f /usr/src
> # ls -l /usr/src
> total 1
> drwxr-xr-x   6 root wheel 512 Feb 18 10:32 sys
> # umount /usr/src
> # uname -a
> FreeBSD shirt.www.demon.net 3.1-STABLE FreeBSD 3.1-STABLE #6: Thu Feb 18 
> 02:26:59 GMT 1999 r...@shirt.www.demon.net:/usr/src/sys/compile/SHIRT  
> i386
> #

OK, in that test, you did the union mount onto "/usr/src", which was
_not_ a mount point.  But you did something different in the test
that succeeded:

> However, on another machine running 3.0-RELEASE mount -o union works
> as expected:
> 
> # ls -l
> total 6
> drwxr-xr-x   2 root wheel 512 Feb 18 16:36 da1
> drwxr-xr-x   2 root wheel 512 Dec 11 11:06 da2
> # mount /dev/da1s1e da1
> # mount /dev/da2s1e da2
> # ls -l da?/*
> -rw-r--r--   1 root wheel   0 Feb 18 16:36 da1/this_is_da1
> -rw-r--r--   1 root wheel   0 Feb 18 16:36 da2/this_is_da2
> # umount da2
> # mount -o union /dev/da2s1e /www/da1
> # ls -l da?/*
> -rw-r--r--   1 root wheel   0 Feb 18 16:36 da1/this_is_da1
> -rw-r--r--   1 root wheel   0 Feb 18 16:36 da1/this_is_da2
> #

Here, you did the union mount on top of an existing mount point (da1).
I don't know for sure, but I suspect that this is the only case in
which union mounts are designed to work.

John
-- 
  John Polstra   j...@polstra.com
  John D. Polstra & Co., Inc.Seattle, Washington USA
  "Nobody ever went broke underestimating the taste of the American public."
-- H. L. Mencken


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: mount -o union broken recently?

[Julian Elischer]

On Thu, 25 Feb 1999, John Polstra wrote:

[...]
> 
> Here, you did the union mount on top of an existing mount point (da1).
> I don't know for sure, but I suspect that this is the only case in
> which union mounts are designed to work.

I was led to believe (last time I read the code) that any directory should
be ok for a union mount

julian



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: panic: aha0 Invalid CCB or SG list

[Warner Losh]

In message <36d4b092.8b076...@partitur.se> Palle Girgensohn writes:
: I've seen three crashes in the last couple of weeks, with a server
: box that's been running stable as a rock for two years, at least. It
: has an adaptec 2940UW with six disks, and an adaptec 1542CP that's
: connected to a seagate travan tape driver.

OK.  This card is known to be good.  At least I've not had any
problems with it.

: It's running STABLE-3.1 from Feb 19 1999, and since the last
: upgrade, I've seen three crashes, all related to dumping to
: tape. Since I got no info on what happened, I decided to sit down
: with the machine, run a backup sequence to tape, and wait for it to
: possibly crash. After 90 minutes, I was about to give up when
: suddenly, poof:
:   panic: aha0  Invalid CCB or SG list.
: 
: So, it's probably the 1540 driver (or hardware)?

Ah.  OK.  I'm not doing tape stuff on my machine.  How fast is that
seagate tr-4 that you are doing?

: Can anybody shed some light on what to do? Is it software? That's my
: guess, since the machine never ONCE has crashed until the upgrade to
: 3.x. I had one crash when running current form beginning of January
: (soon after moving to 3.x), and now theese three in a week. The 1540
: has been in the machine for about six months.

Chances are really good that this is software.  The invalid ccb or sg
list is due to either a race condition or something taht corrupts
these things.

: If there's anything I can do to help debug I'll do it, but device
: drivers are a little above my level of expertise.

If you can wait a day or three, I might be able to find something that
will help.  However, I don't have a tape drive right now to test it
with.  I'll see what I can beg, borrow or steal.

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: please don't check mail for root logins

[Rahul Dhesi]

UserLogin is just a flag that is needed to enable --with-login at runtime.
It doesn't prevent failed logins when a .hushlogin file is present --
that's a bug in sshd that will need to be fixed first.

Rahul

> Date:  Thu, 25 Feb 99 10:51:01 EST
> From:  jcp...@osfmail.isc.rit.edu
> To:freebsd-current@FreeBSD.ORG
> Message-Id: <19990225105101.a15...@osfmail.isc.rit.edu>
> Subject: Re: please don't check mail for root logins

> On Thu, Feb 25, 1999 at 04:15:30AM -0800, Rahul Dhesi wrote:
> 
> > Good idea, thanks, and I now realize that it won't work, and neither
> > will changing /bin/login -- because sshd does not seem to honor either
> > one.
> 
> You could try taking a look in sshd_config and setting UseLogin Yes.
> 
> -- 
> Jon Parise (par...@pobox.com)  .  .: current environment :.
> Rochester Inst. of Technology  :  OSF1 grace V4.0 878 alpha
> Computer Science House Member  :  user: jcptch  host: grace
> https://www.csh.rit.edu/~jon/  :  term: vt100tty: ttysb
> 
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Staroffice 5.01?

[Ollivier Robert]

According to Alok K. Dhir:
> Thanks all - I finally got it to work.  It still stops and asks me to
> "insert StarOffice 5.01, yes, no, cancel".  Hitting cancel a few times
> allows the installation to continue.

I haven't seen this.
 
> Does anyone's installation allow them to use the web browsing or 
> email component?

The web browing part works beautifully (although SO5 is by itself more
memory hungry than Netscape :-)) and I haven't tried the mail part. I don't 
even plan to test it, Mutt is working perfectly.
-- 
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: panic: zone: entry not free

[Mike Smith]

If you thought you could follow the code around a bit and work out why 
it's happening, that would be very helpful...

> This occurs almost immediately after copying a file to an msdos fs. I can
> provide more info if that is deemed useful.
> 
> FreeBSD jos.mp-c.com 4.0-CURRENT FreeBSD 4.0-CURRENT #3: Sat Feb 20 19:31:56
> CET 1999 j...@jos.mp-c.com:/usr/src/sys/compile/JOS  i386
> 
> Thanks,
> -- 
> Jos Backus  _/  _/_/_/"Reliability means never
>_/  _/   _/ having to say you're 
> sorry."
>   _/  _/_/_/   -- D. J. Bernstein
>  _/  _/  _/_/
> jos.bac...@nl.origin-it.com  _/_/   _/_/_/use Std::Disclaimer;
> 
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
\\  Sometimes you're ahead,   \\  Mike Smith
\\  sometimes you're behind.  \\  m...@smith.net.au
\\  The race is long, and in the  \\  msm...@freebsd.org
\\  end it's only with yourself.  \\  msm...@cdrom.com




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: please don't check mail for root logins

[Matthew Dillon]

:UserLogin is just a flag that is needed to enable --with-login at runtime.
:It doesn't prevent failed logins when a .hushlogin file is present --
:that's a bug in sshd that will need to be fixed first.
:
:Rahul

There is a 'CheckMail' option.  You should be able to set it to NO.

-Matt


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: [...@off.to: freebsd low kernel expert...]

[Mike Smith]

> 
> i'm looking for someone who can answer some questions about
> interrupt processing code in freebsd 3.0... not the stuff
> after the SMP processors get to C code, but the glue between
> the hardware and the C code...

Bruce Evans (b...@freebsd.org) and Steve Passe (f...@freebsd.org) are 
probably your best contacts.

> i want to find the `pc' of the interrupting processor... i can
> find the pc of the other processors, but don't yet know how
> to get the previous-pc for the processor which fielded the
> interrupt.

If you're referring to the pc at which the processor running the 
interrupt handler was interrupted, I expect that you'll have to unwind 
the stack to find it.  Note that AFAIK we support multiple interrupt 
entry, so you may have one handler interrupted by another.

It may be easier if you have a specific context in which you need to 
get at the suspended PC.
-- 
\\  Sometimes you're ahead,   \\  Mike Smith
\\  sometimes you're behind.  \\  m...@smith.net.au
\\  The race is long, and in the  \\  msm...@freebsd.org
\\  end it's only with yourself.  \\  msm...@cdrom.com




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Staroffice 5.01?

[Daniel O'Connor]

On 25-Feb-99 Alok K. Dhir wrote:
>  Does anyone's installation allow them to use the web browsing or 
>  email component?
It hangs when I try to use IMAP..

---
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 majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

how to set the ne2000 pci network card in the config file

[Chan Yiu Wah]

Hello,

I recently found that my pci network card didn't work  for me any more.  It 
was recognized by the system but I could config it. This didn't  happen before
and I didn't why.  I had tried to config it as ed1  in my config file.
Then it was probed by the system as ed2   When I tried to config it as ed2
in the config file. It was probed by the system as ed3.  Can anyone tell me
how to solve it.  Thanks.c

Clarence



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Really! strange uid value

[John W. DeBoskey]

Hi,

   I have some machines running 3.0-19981209-SNAP. I have seen
some core dumps from pdksh (which I haven't figured out yet)
that have some really strange uid values.

-rw-r--r--1 4294967294  wheel  389120 Feb 14 23:54 pdksh.core.xclink

   Well, I must say I'm impressed that FreeBSD can support a user
base that is so large! :-) :-)


   Has anyone else run into this?


Thanks!
John



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: how to set the ne2000 pci network card in the config file

[Scot W. Hetzel]

From: Chan Yiu Wah 
> I recently found that my pci network card didn't work  for me any more.
It
> was recognized by the system but I could config it. This didn't  happen
before
> and I didn't why.  I had tried to config it as ed1  in my config file.
> Then it was probed by the system as ed2   When I tried to config it as
ed2
> in the config file. It was probed by the system as ed3.  Can anyone tell
me
> how to solve it.  Thanks.c
>
If you could show us how you were configuring ed[1,2] in your config file we
would probably be able to help you.

You possibly are using:

device ed1 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr

This sets up ed1 for a ed* ISA card.  Thus when the system probe finds your
card, it assigns it as ed2, since PCI devices are automatically assigned to
the next ed* interface.

You should change you config file so that the device line looks as follows:

deviceed1

This will set it up so that the first ed* PCI card found is assigned to the
ed1 interface.

Scot




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: Really! strange uid value

[Chris Costello]

On Thu, Feb 25, 1999, John W. DeBoskey put this into my mailbox:
> Hi,
> 
>I have some machines running 3.0-19981209-SNAP. I have seen
> some core dumps from pdksh (which I haven't figured out yet)
> that have some really strange uid values.
> 
> -rw-r--r--1 4294967294  wheel  389120 Feb 14 23:54 pdksh.core.xclink
> 
>Well, I must say I'm impressed that FreeBSD can support a user
> base that is so large! :-) :-)
> 
> 
>Has anyone else run into this?

   Tried running fsck?

> 
> 
> Thanks!
> John
> 
> 
> 
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-current" in the body of the message
> 

-- 
"In order to make an apple pie from scratch, you must first create the
universe."
-- Carl Sagan, Cosmos


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

New mpd release available

[Archie Cobbs]

FYI,
A new release of mpd is available in ports/net/mpd, or at:

  ftp://ftp.whistle.com/pub/archie/mpd

New features:

 - Support for netgraph: PPP over synchronous lines, frame relay, etc.

 - Includes much more complete chat script (eg, auto-programs
   your Bitsurfr, incoming ring dial-back, etc)

 - Complete user/reference manual included

Next step: using netgraph ppp and interface nodes instead of /dev/tun*
so IP packets never leave the kernel (developers welcome!)

-Archie

___
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message

Re: IDE CDROM not found with PIIX4 chipset, -current kernel

[Daniel C. Sobral]

Sheldon Hearn wrote:
> 
> 2) I found that stepping through the kernel caused exactly the same
>problems I was having with accessing my one ATAPI drive that I
>experience just running normally with my other drive. So it looks
>like at least one problem regarding ATAPI has to do with timings.

FreeBSD code has had it share of bugs due to spec violation,
generally showing up as "timing" problems. One can search the PR for
"HITACHI" or "ATAPI" (I can't quite recall what subject I choose)
PRs from me. First time, someone found the bug, I incorporated it in
my code, sent PR, and distributed the patch to anyone who complained
about it (on the lists I read). Then, the code was changed (the
whole code), and my PR was closed because it did not apply anymore.
Alas, the new code had the same bug. I don't quite recall if I
opened a new PR or just sent the patch to (probably) Soren.

It was somehow distressing, though, that the new code had the exact
same bug as the old, even though it was quite different code.

This was ages ago, though.

--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@freebsd.org

"To make it absolutely clear: you stand on the wrong end of my
blasters, so you better get lost before I start target practice!"




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message