Re: Just how standard is APM?

[Daniel C. Sobral]

"Donald J . Maddox" wrote:
> 
> Yeah, I thought that APM was APM, but the apm device does nothing
> on my desktop with power management hardware...  That is, things like
> 'shutdown -p now' don't work, both 'apm' and 'apmd' just return
> 'device not configured', etc.  Interestingly, at least 'shutdown -p'
> does work with ACPI anyway :)  Of course, maybe I'm just misunder-
> standing the whole thing anyway...  Is power management hardware
> == APM?

If this is still about the Presario laptop, APM works (or did up to
november) on the Compaq Presario 1621. Note the apm and acpi can't be
used together in the same kernel.

-- 
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"The bronze landed last, which canceled that method of impartial
choice."


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

Re: Just how standard is APM?

[Graham Wheeler]

"Daniel C. Sobral" wrote:
> 
> If this is still about the Presario laptop, APM works (or did up to
> november) on the Compaq Presario 1621. Note the apm and acpi can't be
> used together in the same kernel.

It's a 1700; previously I had a 1600 which worked better with everything
(the VIA sound was supported, the APM BIOS worked, etc). It had a flaky
touchpad, so I exchanged it, and took a 1700 because I wanted the CD-RW
drive and lighter weight - but now I have lots of unsupported hardware
(Conexant LANtastic Ethernet/modem, ESS1988 Allegro sound, and, it
seems, ACPI - which is unsupported in -stable, I gather). Fortunately I
have a 3Com PCMCIA EtherNIC, so I have enough working to make it quite
usable with FreeBSD anyway.

-- 
Dr Graham WheelerE-mail: [EMAIL PROTECTED]
Director, Research and Development   WWW:http://www.cequrux.com
CEQURUX Technologies Phone:  +27(21)423-6065
Firewalls/VPN SpecialistsFax:+27(21)424-3656


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

Re: RFC: a CUI controlpanel for FreeBSD

[Pedro F. Giffuni]

AGX wrote:

Antonio, you are welcome to contribute to FreeBSD.
> 
> I would like to know if you think that is usefull or not to do this
> job or if there are more urgents work to do upon the FreeBSD distribution/
> installation process. I've wasted 4 years trying to create my personalized
> GNU/Linux distribution and i'm tired of to remake each time the same job.
> 

FWIW, this all reminds me of FreeBSD's own project:

http://people.FreeBSD.org/~alex/libh/

ciao,

Pedro.


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

Re: RFC: a CUI controlpanel for FreeBSD

[Neil Blakey-Milner]

On Thu 2001-01-04 (23:13), AGX wrote:
> I firstly developed everything using cdialog but them are very buggy
> togheter with somebody i did developed "libgringo" that is a generic
> library that interface both ncurses and Gtk (depending how you
> compiled it) and allow you to write script that can run both in console
> both in X-Window.

Where can I look at this stuff?  What scripting language do you use when
you say 'write scripts'?

> I would like to know if you think that is usefull or not to do this
> job or if there are more urgents work to do upon the FreeBSD distribution/
> installation process. I've wasted 4 years trying to create my personalized
> GNU/Linux distribution and i'm tired of to remake each time the same job.

There're lots of things you can do on FreeBSD, but it's generally best
to do the stuff you most enjoy and/or are best at.  If you like writing
documentation, there's the documentation project; if you like general
hacking, generally hack, and if you like in-depth kernel stuff, I'm sure
the kernel people will be happy for more of themselves. (:

Neil
-- 
Neil Blakey-Milner
[EMAIL PROTECTED]


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

Re: kernel debugging suggestion needed

[Doug Rabson]

On Tue, 2 Jan 2001, Doug White wrote:

> On Tue, 2 Jan 2001, Zhiui Zhang wrote:
>
> >
> > I have written a KLD and am debugging it. The program often hangs after
> > runs for a while (I guess it enters into some dead loop).  Is there a way
> > to attach to the process and somehow find out which code it is executing
> > (with remote debugging or ddb)?
>
> kld debugging is a bit tricky.  Take a look at the debugging macros and
> bits that Greg Lehey put together for vinum for a starting point. You have
> to calculate the appropriate offset to get to the KLD code in gdb.

Not anymore. You can use GDB's "sharelibrary" command to read the symbols
of all loaded KLDs. You only need to ensure that the exact same pathname
works for both loading the KLD on the target machine and for loading the
symbols on the machine running GDB.

-- 
Doug Rabson Mail:  [EMAIL PROTECTED]
Phone: +44 20 8348 6160




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

Re: Just how standard is APM?

[Josef Karthauser]

On Thu, Jan 04, 2001 at 11:57:37PM -0800, Mike Smith wrote:
> > Warner Losh wrote:
> > > 
> > > APM is standard.  Except when it is broken in some brain damaged ways.
> > > 
> > > However, you likely have your apm device disabled in your kernel and
> > > all you need to do is enable it.
> > > 
> > 
> > Nope - as I said, I added log messages to apm.c to log the BIOS probe
> > and they log a failure (I have "device apm0" in my config file).
> 
> How new is this laptop?  It may be ACPI-only.

Where are we at with ACPI?  Does it do power management yet?

Joe


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

Re: Strange fwrite() behavior in a+ mode

[Joshua Rosen]

Alfred Perlstein writes:

> So in Linux, if you have a "a+" file, you can
> 1) seek somewhere (mid file)
> 2) read some data (not until EOF)
> 3) after the read you are at EOF again?
> 
> this doesn't sound really intuative.

No, it doesn't sound intuitive; luckily, that isn't what happens;)
The issue concerns where the position is after a write (and where ftell
reports it as being).

Under glibc on Linux, you can:
1) fseek somewhere (non-EOF)
2) fwrite some data
3) after the *write*, you are at EOF again (ftell reports this, and any
attempted fread, at this point, will hit EOF. any fseek, after a write,
using SEEK_CUR will seek relative to EOF, also)

I guess that the idea is, `bytes are read/written starting at the current
position in the file', and, in order to do this in a system which always
writes after EOF in append-mode, the current position must be changed
before writing

my findings, under FreeBSD 4.2-STABLE, are
1) fseek somewhere (non-EOF, say 4 in a 50-byte-long file)
2) fwrite some data (say 3 bytes)
3) after the fwrite, ftell will report N + the last value pass'd to fseek
(using our example numbers: 7), and fseek with SEEK_CUR will seek relative
to that point, but fread will immediately hit EOF, and a ftell (or feof)
after an attempted read will indicate that the position *is* EOF.

Chris' findings (I believe) are that, under FreeBSD 4.2-STABLE, if you use
fread before fwrite (say, step `1.1'), it acts just like it does with
glibc/Linux.



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

if_fxp driver???

[Dennis]

Has the issue with the new rev intel parts been resolved yet?

Dennis



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

IEEE 1394/Firewire

[simond]

Does anyone know if any work is being done on this? Especially the TCP/IP
over firewire (rfc2734), which would make it nice and easy to network up
my vaio with my desktop PC :)

-- 
Simon Dick  [EMAIL PROTECTED]


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

Re: Strange fwrite() behavior in a+ mode

[Alfred Perlstein]

* Joshua Rosen <[EMAIL PROTECTED]> [010105 09:31] wrote:
> 
> Alfred Perlstein writes:
> 
> > So in Linux, if you have a "a+" file, you can
> > 1) seek somewhere (mid file)
> > 2) read some data (not until EOF)
> > 3) after the read you are at EOF again?
> > 
> > this doesn't sound really intuative.
> 
> No, it doesn't sound intuitive; luckily, that isn't what happens;)
> The issue concerns where the position is after a write (and where ftell
> reports it as being).
> 
> Under glibc on Linux, you can:
> 1) fseek somewhere (non-EOF)
> 2) fwrite some data
> 3) after the *write*, you are at EOF again (ftell reports this, and any
> attempted fread, at this point, will hit EOF. any fseek, after a write,
> using SEEK_CUR will seek relative to EOF, also)
> 
> I guess that the idea is, `bytes are read/written starting at the current
> position in the file', and, in order to do this in a system which always
> writes after EOF in append-mode, the current position must be changed
> before writing
> 
> my findings, under FreeBSD 4.2-STABLE, are
> 1) fseek somewhere (non-EOF, say 4 in a 50-byte-long file)
> 2) fwrite some data (say 3 bytes)
> 3) after the fwrite, ftell will report N + the last value pass'd to fseek
> (using our example numbers: 7), and fseek with SEEK_CUR will seek relative
> to that point, but fread will immediately hit EOF, and a ftell (or feof)
> after an attempted read will indicate that the position *is* EOF.
> 
> Chris' findings (I believe) are that, under FreeBSD 4.2-STABLE, if you use
> fread before fwrite (say, step `1.1'), it acts just like it does with
> glibc/Linux.

Can you do a bit more research and let me know if this happens
when using open/read/write/lseek as well?

-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
"I have the heart of a child; I keep it in a jar on my desk."


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

Re: IEEE 1394/Firewire

[Andrew R. Reiter]

Plz search -hackers

On Fri, 5 Jan 2001 [EMAIL PROTECTED] wrote:

> Does anyone know if any work is being done on this? Especially the TCP/IP
> over firewire (rfc2734), which would make it nice and easy to network up
> my vaio with my desktop PC :)
> 
> -- 
> Simon Dick[EMAIL PROTECTED]
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
> 

*-.
| Andrew R. Reiter 
| [EMAIL PROTECTED]
| "It requires a very unusual mind
|   to undertake the analysis of the obvious" -- A.N. Whitehead



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

Re: Just how standard is APM?

[Warner Losh]

In message <[EMAIL PROTECTED]> Graham Wheeler writes:
: Nope - as I said, I added log messages to apm.c to log the BIOS probe
: and they log a failure (I have "device apm0" in my config file).

What's the failure mode?  Is it enabled in the BIOS (I assume it is,
otherwise it wouldn't work in 'Doz).

Warner


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

Re: Just how standard is APM?

[Warner Losh]

In message <[EMAIL PROTECTED]> "Donald J . Maddox" writes:
: Yeah, I thought that APM was APM, but the apm device does nothing
: on my desktop with power management hardware...  That is, things like
: 'shutdown -p now' don't work, both 'apm' and 'apmd' just return
: 'device not configured', etc.  Interestingly, at least 'shutdown -p'
: does work with ACPI anyway :)  Of course, maybe I'm just misunder-
: standing the whole thing anyway...  Is power management hardware
: == APM?

No.  APM is a BIOS interface.  Many BIOSes that have ACPI have legacy
APM support.  Some work, some don't.  Windows (98 and newer) uses ACPI
in preference to APM, so the testing that APM mode gets is usually
meager at best.

Warner


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

Re: Just how standard is APM?

[John Baldwin]

On 05-Jan-01 Josef Karthauser wrote:
> On Thu, Jan 04, 2001 at 11:57:37PM -0800, Mike Smith wrote:
>> > Warner Losh wrote:
>> > > 
>> > > APM is standard.  Except when it is broken in some brain damaged ways.
>> > > 
>> > > However, you likely have your apm device disabled in your kernel and
>> > > all you need to do is enable it.
>> > > 
>> > 
>> > Nope - as I said, I added log messages to apm.c to log the BIOS probe
>> > and they log a failure (I have "device apm0" in my config file).
>> 
>> How new is this laptop?  It may be ACPI-only.
> 
> Where are we at with ACPI?  Does it do power management yet?

Yes.  For the Inspiron that you have you have to hack around a bit to get it to
not hang during boot (and battery status doesn't work as a result I think), but
suspend/resume on lid close work, the power button works, shutdown -p, etc.

> Joe

-- 

John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/


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

open PR WRT syslogd vs. serial consoles

[Brian Reichert]

I'm chasing down a syslogd problem on a 3.4-R box, only to discover
that I'm being bit (still!) by a PR I submitted two years ago:

  

I'm responsible for a wad of machines hanging off of a terminal server.

- I wanted syslog messages reported to the console, for revealing
  critical errors.

- Due to cabling and the terminal server itself, using Big Digi
  hardware, I need to have getty running off of cuaa0, not ttyd0.

Apparently, in three versions of FreeBSD, this is _still_ a problem.

Does anyone have any insight on this?

-- 
Brian 'you Bastard' Reichert<[EMAIL PROTECTED]>
37 Crystal Ave. #303Daytime number: (603) 434-6842
Derry NH 03038-1713 USA Intel architecture: the left-hand path


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

Re: BSD dlopen and such

[David O'Brien]

On Thu, Jan 04, 2001 at 10:19:56AM -0800, Doug White wrote:
> > 1) Can a native binary dlopen a Linux ELF GL, yes or no?
> 
> No.  The linux compatbility is through the image activator.  The syscalls
> have to be translated, otherwise if you were running as root and loaded a
> linux lib into a freebsd binary, then that lib called fcntl(), your system
> would reboot :)

Acutally you should have said "YES", with a limitation that the Linux
object cannot make syscalls.  On the Alpha we use a Linux library with
the Compaq ccc comiler.



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

Re: FreeBSD + Mylex DAC960 (RAID 1) + DEC Prioris HX 6000 Serverwill not recognize boot record for some reason

[Gordon Tetlow]

On Thu, 4 Jan 2001, Mike Smith wrote:

> This is a FAQ; you have a geometry mismatch.
>
> Make sure the BIOS on the card is set for 2GB mode, make sure sysinstall
> detects a */128/32 geometry.  8GB mode doesn't work (my fault, will be
> fixed once I get my lab set up and some free time).

Hmm, I just installed it using 8GB mode (4.2-RELEASE) and it booted no
problem. I then tried 4.0-RELEASE and it worked. In my previous experience
it hadn't. I'm going to revisit the boxes that don't boot and play with
them a bit.

-gordon



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

encrypt h/w for FreeBSD?

[Len Conrad]

Sorry, got no answer in -questions.

Just my quarterly check to see whether there's support coming up for 
hardware assisted IPsec, SSL, whatever?

In addition to SSL on web servers, we'd recently have found some need 
like to run TLS for SMTP and postfix.

Thanks,
Len



http://BIND8NT.MEIway.com : Binary for ISC BIND 8.2.3 T9B for NT4 & W2K
http://IMGate.MEIway.com  : Build free, hi-perf, anti-spam mail gateways



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

Re: OT: silence as an answer? (was: how to test out cron.c changes?)

[Doug Barton]

Gerhard Sittig wrote:
> 
> [ this message is no personal affront against you, Doug, but an
> expression of what feeling this kind of behaviour causes for
> those who want to share and find themselves ignored ]

Actually, I wouldn't care if it were, but thanks for the clarification.
FYI, you will get a faster response if you cc: the person who wrote you.
I'm currently behind on list mail. 

> On Mon, Jan 01, 2001 at 18:06 -0800, Doug Barton wrote:
> > Gerhard Sittig wrote:
> > >
> > > [ ... reminder after two weeks of silence ... ]
> >
> > Two weeks of silence is generally enough to let you know that
> > no one is interested in this modification. If someone was,
> > they'd generally have said something by now.
> 
> Well, I don't come to the same conclusion here as you do and I'm
> not so sure about it as you are. :)  Silence as I see it is just
> a sign for "nobody answered", without a reason to see why.

Sometimes that's true. I think that my point could have been better
stated as, "No one was excited enough about your proposal to take
further action on it." This may be because no one wants it, or it may be
because no one has had time to deal with it... or lots of other reasons.
The fact is however, that things that people really ARE interested in
get done. So, silence can be, and usually is rejection, even if that's
not really the answer you wanted. 

> BTW is rejection much more the kind of reaction I had expected in
> the case you describe (nobody wants it).  This would have been at
> least *some* reaction. 

The problem is that no one person can state conclusively that the
project doesn't want something. One person CAN step in and make
something happen, so acceptance is easy, whereas rejection is almost
always a case of slow death by apathy. 

> Getting ignored is definitely a fine way
> of discouraging future contributions. 

You may find this hard to believe, but I sympathize with your plight. I
was there for years. That's why I tend to make the kinds of replies I
did in this case so that at least the person will have some assurance
that their suggestion was seen, and considered. 

> Some "we don't like the
> approach, since ..." or a simple "Nope" or even a serious
> "PLONK!" would have been great and as much appreciated as an
> "yes, we like it"!  It had saved time and work for _everyone_
> involved (me as being the originator as well as those I had to
> annoy repeatedly when they could have stopped me right in the
> beginning).

As above, this just doesn't happen very often, unless it's a truly
horrible idea. This is the nature of working on this kind of project.
You will simply have to develop a thicker skin if you are going to
survive in this environment. 
 
> > Speaking only for myself, I don't think your proposed changes
> > are a good idea, which is why I refrained from offering any
> > suggestions on how you can test them.

You stated in another post that you wished I had elaborated more. I was
in a hurry when I wrote that post, so here are more details. While this
is, as you say, "an eternal problem," it is not a problem entirely
without remedy. The proper solution is simply to avoid scheduling
mission/time critical events during the DST change period for your time
zone. Without improperly revealing sources, I can say that I did a lot
of research on this topic in a past life, and it is by no means clear
that your proposed solution is the best one. 

Consider the following. We are in the spring and DST is "springing
forward" at 2am. We have a job scheduled at 2:15 that takes one hour to
run. There is another job scheduled at 3:20 that ABSOLUTELY POSITIVELY
cannot run unless the first job finishes. Aside from the fact that this
is bad design, how should cron handle this situation? You can (and
probably should) respond that this is not cron's responsibility, and
come up with all kinds of ways to ameliorate this situation. My response
will then be that if you can "fix" this situation without "fixing" cron,
then cron doesn't really need to be "fixed." 

With very little imagination you could easily come up with other
situations where your proposed changes will cause more harm than good.
On the other hand, the "damage" that cron is doing in these situations
can easily be repaired by proper system design. Therefore your changes
should not be incorporated. 

Doug


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

RE: encrypt h/w for FreeBSD?

[Charles Randall]

nCipher's nFast card supports FreeBSD 3.3 and 3.4.

http://www.ncipher.com/products/nfast_specs.html

-Charles

-Original Message-
From: Len Conrad [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 05, 2001 3:12 PM
To: [EMAIL PROTECTED]
Subject: encrypt h/w for FreeBSD?


Sorry, got no answer in -questions.

Just my quarterly check to see whether there's support coming up for 
hardware assisted IPsec, SSL, whatever?

In addition to SSL on web servers, we'd recently have found some need 
like to run TLS for SMTP and postfix.

Thanks,
Len



http://BIND8NT.MEIway.com : Binary for ISC BIND 8.2.3 T9B for NT4 & W2K
http://IMGate.MEIway.com  : Build free, hi-perf, anti-spam mail gateways



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


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

RE: encrypt h/w for FreeBSD?

[Daniel O'Connor]

On 05-Jan-01 Charles Randall wrote:
>  nCipher's nFast card supports FreeBSD 3.3 and 3.4.
>  
>   http://www.ncipher.com/products/nfast_specs.html

I think Mike Smith is 'sort of' working on support for HW crypto cards.. No idea
how far he has got. 

---
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-hackers" in the body of the message

Diskless

[Rachmat Hidajat]

Hi All,
I want to try to boot the diskless system, so I compile nb8390.com with
NE2000 support. But I got the following error during the process. Did I
make a mistake?

# make
Warning: Object directory not changed from original
/usr/src/sys/i386/boot/netboot
cc -O2 -DNFS -DROMSIZE=16384 -DRELOC=0x9 -DPCI -DPCI_VENDOR=0x10ec
-DPCI_DEV
ICE=0x8029 -DPCI_CLASS=0x02,0x00,0x00 -DASK_BOOT -aout -nostdinc
-I/usr/src/sys/
i386/boot/netboot/../../../../include
-I/usr/src/sys/i386/boot/netboot/../../..
-I/usr/src/sys/i386/boot/netboot   -DROMSIZE=16384  -static -o makerom
/usr/src
/sys/i386/boot/netboot/makerom.c
ld: scrt0.o: No such file or directory
*** Error code 1
Stop in /usr/src/sys/i386/boot/netboot.
---

PS: Please cc your response to my private address whenever possible.

Regards,
Rachmat Hidajat <[EMAIL PROTECTED]>
Kobe, JAPAN




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