Re: How can I manually turn off the HDD?

2007-02-14 Thread Daniel Rudy
At about the time of 2/13/2007 10:58 AM, Chuck Swiger stated the following:
 On Feb 13, 2007, at 7:47 AM, [EMAIL PROTECTED] wrote:
 How can I turn off the HDD? .. and leave the buffers in the memory,  
 until the RAM is full .. then spin up the drive, write out the  
 data, then it turn off again.
 
 ENOTSUPPORTED, at least with FreeBSD.  Note that Apple has done a lot  
 of work to facilitate drive spindown for power-saving reasons for  
 their laptops, so MacOS X will make a reasonable attempt to spindown  
 the drives until really needed
 

There is a port called ataidle that you may want to look at.  It
programs the HDD to spin down after a specified timeout.

-- 
Daniel Rudy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Newbie--new install on Core 2 Duo?

2007-02-14 Thread Daniel Rudy
At about the time of 2/13/2007 12:07 PM, pete wright stated the following:
 On 2/13/07, Gerard [EMAIL PROTECTED] wrote:
 On Tuesday February 13, 2007 at 01:42:23 (PM) pete wright wrote:


 how would you define correct?  have all systems boot with a SMP
 kernel by default so that machines with multiple processors
 automatically detect all available CPU's?  then what about all the
 users that are using uni-proc systems?

 i think the current state of building a system w/o SMP enabled is
 great.  it's not that hard to do a:

 cd /usr/src
 make buildkernel KERNCONF=SMP
 make installkernel KERNCONF=SMP
 reboot

 this is all covered in the FreeBSD handbook, which all new
 admin's/users should be reading and following closely anyway ;)
 It is also a hugh waste of time. Doing the initial system installation,
 there should be an option at the very least to enable SMP. Installing
 a system, then having to rebuilt and and reinstall it again if counter
 productive.

 The market is moving toward multiple CPUs. The FBSD installation routine
 should embrace that reality and afford it the proper consideration that
 it deserves.

 
 hmm...didn't realize that not loading a SMP kernel by default would
 turn people away from running FreeBSD.  building a kernel is much
 different from reinstalling a system though...
 
 OT, but - I know a fair amount of locations will have a custom kernel,
 and most large sites will script sysinstall to load a custom kernel as
 well.  yet, for junior admins maybe a boot time option allow one to
 load a SMP kernel during the install phase (which would also be the
 kernel the system boot's from after installation) may be helpfull.
 There are currently options to disable ACPI (granted that's a .ko) but
 perhaps there is precedent to do this.
 
 
 anyway, sounds like a good PR :)
 
 -pete
 
 
 

Interesting.

I have a computer here that's a AMD 64 3700 and it's not dual core, but
the board is capable of using a X2 processor, so loads a SMP kernel
anyways.  It seems to work just fine with the single core, single CPU.
The thing is though is that it refers to the CPU as cpu0.  Doing it this
way just might be the future...

Oh, and I didn't tell it to use the SMP kernel.  Sysinstall did that
itself.  So based on this behavior, if the bios reports SMP capable (the
bios shows CPU 0 during the post), then sysinstall loads a SMP kernel?

I have to turn acpi off though otherwise I get dead lock up problems.



-- 
Daniel Rudy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: That Drive Geometry Bug

2005-12-27 Thread Daniel Rudy
At about the time of 12/26/2005 5:45 PM, [EMAIL PROTECTED] stated the
following:
 I am trying to back up the drive I have been using (which is now full)
 onto a 60GB Seagate IDE drive - ST360020A. After a bunch of failures at
 configuring the disk, I did some searching on the web and found some info
 on the drive geometry bug.
 
 I followed the directions I found there - essentially, go into my BIOS at
 boot time, write down the drive geometry that the BIOS thinks I have and
 then plug those numbers into FreeBSD fdisk at the beginning of
 installation.
 
 What happened:
 1. FreeBSD complained that the drive geometry it was seeing was wrong, and
 was using its own best guess: 7297/255/63.
 2. I hit G and edited the C/H/S to that which the BIOS reported:
 28733/16/255.
 3. I hit Enter; the installer said `Nope, you're wrong! I'm going to use
 my best guess instead!'
 
 No matter how many times I try to enter the info, it changes it back to
 whatever it thinks is more correct.
 
 I tried switching the head and sector info (trying 28733/255/16). but no joy.
 
 Is there a way to coax the installer into cooperating?
 
 Thanks -
 -- paz.

I just recently ran into this problem myself.  Just use FreeBSD's best
guess and it will work fine.  If you set the BIOS to LBA mode, you will
find that matches FreeBSD's best guess.

-- 
Daniel Rudy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How do I know if my internal PCI modem works on FreeBSD?

2005-12-06 Thread Daniel Rudy
At about the time of 12/4/2005 7:46 PM, Foo Ji-Haw stated the following:
 Thanks for the good feedback.
 
 Is there a particular modem chipset which if it is spotted on the card, it
 is confirmed that it's more than a WinModem?
 
 

There are various chipsets by both Lucent and Conextent (Formerly known
as Rockwell).  It seems that most of the hardware modems that I have
come across use Conextent chipsets, but that can be hit and miss.  Every
Lucent one that I have seen is a Winmodem.  90 pecent of the time, if
it's a PCI modem, then it's a Winmodem.

-- 
Daniel Rudy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: schedule a script at system startup

2005-12-04 Thread Daniel Rudy
At about the time of 12/3/2005 5:18 PM, Ian Lord stated the following:

 Hi,
 
 I would like to run a shell script at system startup which needs to 
 run under a specific uid...
 
 I don't see anything for this in man cron...
 
 is there a way to do it with cron ? or otherwise is there another way ?
 
 I guess there might be a way to put a script in /etc/rd.d/ but I 
 don't know how to run it under a specifid uid
 
 Any help would be appreciated
 
 Thanks
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

@reboot username command

The @reboot is a BSD extension.

-- 
Daniel Rudy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How do I know if my internal PCI modem works on FreeBSD?

2005-12-04 Thread Daniel Rudy
At about the time of 12/3/2005 7:38 AM, Wojciech Puchar stated the
following:

Basically, it all depends on how much you spent for the modem.  A $15-20
modem is more than likely a WinModem (software modem) which FreeBSD does
*NOT* support without a third party driver.  If the modem cost $70-100,
and it is recongized as a serial port by the sio driver, then it
probably will work.
 
 
 
 externally connected modems (by serial) costs less than $100 anyway and do 
 work for sure.
 
 many external modems does connect by USB port and can be cheaper, but 
 check for hayes compatible label (or similar) as some USB modems are 
 winmodems too.
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

So, some USB modems are winmodems now?  I was not aware of that.
Besides, who wants a USB modem anyways?  I didn't mention the external
modems because the OP was asking specifically about his internal PCI modem.

A good internal PCI hardware (controller based) modem is the Zoom 2920.
 They run about $80 or so at Fry's...If you can find them.  Or talk to
Zoom directly at http://www.zoom.com.

-- 
Daniel Rudy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: How do I know if my internal PCI modem works on FreeBSD?

2005-12-03 Thread Daniel Rudy
At about the time of 11/30/2005 10:50 PM, Foo Ji-Haw stated the following:

 Hello there,
 
 I'm thinking of plugging in a Motorola PCI modem into my
 FreeBSD box to act as a fax server (using HylaFax). I tried to
 look for documentation on the installation or support of such
 a modem on FreeBSD (Google, the Handbook), but found none.
 Can anyone point me in the right direction, or better still:
 tell me if my modem will work in FBSD 5.4?
 
 Thanks.
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 

Please wrap your lines properly.


Basically, it all depends on how much you spent for the modem.  A $15-20
modem is more than likely a WinModem (software modem) which FreeBSD does
*NOT* support without a third party driver.  If the modem cost $70-100,
and it is recongized as a serial port by the sio driver, then it
probably will work.

The reason why I threw the cost of the equipment into the mix was
because the cheap modems don't have the controller, DSP, data pump, or
other required hardware.  All the functions of those components is
emulated in the software of the host system.  This is why that are known
as software modems.  A hardware modem costs much more, but it also has
all the required hardware such as the controller, DSP, data pump, etc.
so it can function independantly of the host system software.

You can also generally tell by looking at the modem itself.  Usually, if
you see a chip that has what looks like version numbers on it, as well
as one or more large square chips and lots of circutry, then you
probably have a hardware modem.  The best way is lookup the model number
on the manufacturer's web site and see what it is.  If it says it's only
compatible with Windows, then more than likely it's a software modem.

-- 
Daniel Rudy
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Spash screen will not come up

2005-10-18 Thread Daniel Rudy

Hello,

I'm running FreeBSD 5.4-RELEASE.  The problem that I have is that the
splash screen will not come up.  I have made sure that the bmp is 256
colors.  I have tried uncompressed and RLE compressed bmps.  The RLE
compressed versions worked in 4.x.  I have also added the approperiate
lines to /boot/loader.conf.  It seems that ever since I upgraded to 5.x,
I have not been able to get a splash screen.  Upon further examination,
I see this in the dmsg when the system boots:

module_register_init: MOD_LOAD (splash_bmp, 0xc06e4810, 0) error 2

Any ideas as to why I am getting this error?

/boot/loader.conf:
strata:/home/dr2867 1026 $$$ -more /boot/loader.conf
# Verbose output from loader
# verbose_loading=YES # Set to YES for verbose loader output

# Show Splash Graphic
splash_bmp_load=YES   # Set this to YES for bmp splash screen!
bmp_load=YES  # Load bitmap
bitmap_name=/boot/splash.bmp  # Set this to the name of the bmp or pcx
file

# Boot Menus and Delay
autoboot_delay=5  # Delay in seconds before autobooting
beastie_disable=NO# Turn the beastie boot menu on and off

# Panic crashdumps go here
dumpdev=ad0s1b# Set swap device for crash dumps

-- 
Daniel Rudy

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Spash screen will not come up

2005-10-18 Thread Daniel Rudy
 --- David Kirchner [EMAIL PROTECTED] wrote:
 On 10/18/05, Daniel Rudy [EMAIL PROTECTED] wrote:
 
  Hello,
 
  I'm running FreeBSD 5.4-RELEASE.  The problem that
 I have is that the
  splash screen will not come up.  I have made sure
 that the bmp is 256
  colors.  I have tried uncompressed and RLE
 compressed bmps.  The RLE
  compressed versions worked in 4.x.  I have also
 added the approperiate
  lines to /boot/loader.conf.  It seems that ever
 since I upgraded to 5.x,
  I have not been able to get a splash screen.  Upon
 further examination,
  I see this in the dmsg when the system boots:
 
  module_register_init: MOD_LOAD (splash_bmp,
 0xc06e4810, 0) error 2
 
 I believe error 2 in this context means No such
 file or directory.
 Maybe it's expecting the bmp to be somewhere else?
 ___
 freebsd-questions@freebsd.org mailing list

http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]
 

That's interesting because I have specified the
absolute path of the bitmap file in /boot/loader.conf.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Controlling init on shutdown/reboot

2003-12-05 Thread Daniel Rudy
Somewhere around the time of 12/02/2003 00:12, the world stopped and
listened as Rob contributed this to humanity:
 I haven't used ppp(8) - I prefer pppd(8) -  so I'm not familiar with
 ppp.linkdown.sh. If this is a shell script, there's a couple of things that
 I've seen cause strange script behaviour: lack of default environment and
 lack of TTY. This usually shows up in scripts that work fine at the command
 line, but fail under other circumstances (such as crontabs).
 
 Does it take more than 2 minutes at the command line?
 
 Have you tried adding
 
 set -x
 
 at the start to see where it's failing? If it's called by rc.shutdown the
 output should be to the console, but I'm not sure what ppp(8) does with
 script output.
 

The script is called by ppp on a link down event.  That is a link down
for ANY reason, including a shutdown.  The problem is that ppp doesn't
differentiate on why the link went down, just that it went down.  Now,
when rc.shutdown executes, it writes a stop file to /tmp that
ppp.linkdown.sh checks for.  If it finds that file, then I have it do
something alittle different.  Does it take long to execute?  Nope, it
runs quite fast, which may be part of the problem.  Because this is
called from ppp and not rc.shutdown, init is killing it before it
finishes because init thinks that it is not part of the system shutdown
sequence.
-- 
Daniel Rudy

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Controlling init on shutdown/reboot

2003-12-01 Thread Daniel Rudy
Hello,

How does one allocate more time for /etc/rc.shutdown?  It seems that
some of my scripts are not being executed when the system shuts down or
reboots.

-- 
Daniel Rudy

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Controlling init on shutdown/reboot

2003-12-01 Thread Daniel Rudy
Somewhere around the time of 12/01/2003 03:32, the world stopped and
listened as Rob contributed this to humanity:

From line 99 of /usr/src/sbin/init/init.c,
 
   #define DEATH_SCRIPT  120  /* wait for 2min for /etc/rc.shutdown */
 
 and on line 1576 it looks like you can change this with the sysctl
 'kern.shutdown_timeout'.
 
 But 2 minutes is a long time for a shell script - are you sure that
 everything is working correctly?

The problem is that a ppp.linkdown.sh script needs to do something and
it's not doing it.  Works fine if I execute the script normally from the
command line though using the approperiate parameters that ppp would
send it.  It seems that init is killing the script before the script can
finish, which is the problem.

BTW, that oid, kern.shutdown_timeout does not exist.  I'm running
4.9-RELEASE.


 - Original Message -
 From: Daniel Rudy [EMAIL PROTECTED]
 Subject: Controlling init on shutdown/reboot
 
 
 
Hello,

How does one allocate more time for /etc/rc.shutdown?  It seems that
some of my scripts are not being executed when the system shuts down or
reboots.

--
Daniel Rudy

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
 
 [EMAIL PROTECTED]
 
 


-- 
Daniel Rudy

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


PPP modem init string

2003-09-24 Thread Daniel Rudy
Hello,

How do I get PPP to send an init string to my modem?  I'm using
different PPP profiles in /etc/ppp/ppp.conf, and each one has a
different requirement for the configuration of the modem such as
outbound ISP and incoming.

Thanks.
-- 
Daniel Rudy


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: PPP modem init string

2003-09-24 Thread Daniel Rudy
Somewhere around the time of 09/24/2003 12:31, the world stopped and
listened as fbsd_user contributed this to humanity:
 The (set dial) option sends Hayes 'AT' commands to the modem only
 for dial out. Totally different situation for dial in to FBSD. In
 that case you have to use the Hayes 'AT' commands to setup and save
 your modem configuration in the modem's nvram. You have to tell the
 modem to go into answer mode when the modem is powered on. That's
 the only way to get it to pick up the inbound call.
 
 Check the questions archives, this question has been answered many
 times before and there are detailed instructions on how to setup you
 modem and PPP to do this. Search for key works 'PPP dial in'  or
 'FBSD answering modem' or 'inbound calls'
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Daniel Rudy
 Sent: Wednesday, September 24, 2003 11:54 AM
 To: [EMAIL PROTECTED]
 Subject: PPP modem init string
 
 Hello,
 
 How do I get PPP to send an init string to my modem?  I'm
 using
 different PPP profiles in /etc/ppp/ppp.conf, and each one has a
 different requirement for the configuration of the modem such as
 outbound ISP and incoming.
 
 Thanks.
 --
 Daniel Rudy
 
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]
 

I think that the mail archive search engine is broken.  No matter what I
try for a search query, it never finds anything.

-- 
Daniel Rudy

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Finding your dynamic external IP

2003-08-03 Thread Daniel Rudy
Somewhere around the time of 08/03/2003 15:13, the world stopped and
listened as David S. Jackson spoke these words of wisdom...:
If your external IP number changes, as with DHCP, is there a way
to find out what it currently is?  I was thinking you could keep
BitchX logged into a chat channel and script a /dns yournick and
email yourself the results from time to time.   

How would you do it?

If you know what interface you are running on, then you can do this to 
get the IP address:

ifconfig interface | head -2 | tail -1 | awk '{print $2}'

to get the IP address.  Then if you want to mail it to yourself, then 
you can do the following:

/usr/bin/printf Current IP address: `ifconfig interface | head -2 | 
tail -1 | awk '{print $2}'`\n | /usr/bin/mail -s IP Address 
Assignment root 

To update your Dynamic DNS, use the following:

ddclient -use=if -if=interface

This will run ddclient in daemon mode so that anytime the IP address 
changes on interface it will update the DDNS provider's servers.
--
Daniel Rudy

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]