Re: Invalid partition table after installation

[Fbsd1]

John wrote:

On Thu, Jan 21, 2010 at 10:25:26PM +0800, Fbsd1 wrote:

John wrote:

On Thu, Jan 21, 2010 at 04:38:22PM +0800, Fbsd1 wrote:

John wrote:

I've tried the modern BIOS geometry and the 255 head geometry.
I've ensured that the first slice (boot slice) is smaller than 1.5
Gb.  I've tried to figure out what the BIOS thinks the geometry
is, but it doesn't seem to want to tell me.  At least, I can't find
it in the BIOS menu anywhere.  When I boot from the CD-ROM with
the 255 head geometry, though, it complains about the disk geometry,
saying 16h,63s != 255h,63s or something like that - it flies by
pretty fast (is there a way to go back and see that from the CD-ROM
boot only boot?).

I'm using the Standard boot manager, and the entire disk is devoted
to FreeBSD.

System
BIOS version  PT84510A.86A.2004.P05
Processor Type: Intel Pentium 4
Processor speed: 2.20Ghz

Memory: 512Mb

Disk: Primary IDE Master ST380021A (Seagate Barracuda ATA IV 80Gb)
Primary IDE Slave: IOMega ZIP 250
Secondary IDE Master: Sony CD-RW CRX19 (what I boot from to install)
Secondary IDE Slave: DVD-ROM DDU1621

Boot sequence:
1) ATAPI CD-ROM
2) Hard Drive
3) Removable Dev.

Modern BIOS geometry: 155061/16/63 for ad0
calculated geometry: 9729/255/63 for ad0

ad0s1 start=63, size=2875572
ad0s2 start=2875635, size=10217340
ad0s3 start=13092975, size=143203410
unus  start=156296384, size=5103

ad0s1a / 384Mb
ad0s1d /usr 1Gb
ad0s2b SWAP 1Gb
ad0s2d /tmp 384Mb
ad0s2e /var 512Mb
ad0s2f /var/mail 2Gb
ad0s2g /usr/ports 1Gb
ad0s3d /home/mysql 4Gb
ad0s3e /home 50Gb
ad0s3f /usr/src 3Gb
ad0s3g /usr/obj 3Gb
ad0s3h /extra 8483Mb

Suggestions, please?  I'm making zero headway right now. :(

What version of FreeBSD are you running

Well, yes, I suppose that would be a good bit of information!

What I'm *TRYING* to run is 8.0.  It seems to install successfully
(of course - after doing all that), but then when I try to boot
from the hard drive, I see an otherwise-blank screen that says:


Invalid partition table


and that's as far as it goes!


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
There are reports of this sort of thing caused by 8.0 fdisk when doing a 
install from scratch over a hard drive that all ready has an older 
version of Freebsd installed on it.


The solution is to force the scratching of the MBR on the disk first 
before running sysinstall fdisk.


Boot a LiveFS CD, then at a root prompt do:

sysctl kern.geom.debugflags=16  and:

dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1

where x equals your drive number.


OK.  I did exactly that.  I confirmed that the second 512 bytes were zero
by doing a dd if/dev/ad0 bs=512 count=2 | od -c
and everything from 001000 through 002000 was zero.

But I still got Invalid partition table after the installation.

I guess I should set up one of my other systems as a local mirror.
I've done the installation so many time already, and it looks like
I'm not done yet!


On the 8.0 fdisk/MBR subject.
Doing dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 was the
solution from another post to the list with subject 'SunFire X2100
fails'. Here is another post that gives more details
http://www.freebsd.org/cgi/getmsg.cgi?fetch=322687+326879+/usr/local/
www/db/text/2009/freebsd-questions/20091227.freebsd-questions

It seems in 8.0 gpart was introduced and a change was made to fdisk to
support its sector o mbr format. 8.0 fdisk and disklabel are now broken.

Searching the list archives may shed more light on your problem.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)

[Fbsd1]

Christoph Kukulies wrote:

Fbsd1 schrieb:

Christoph Kukulies wrote:
I installed FreeBSD 8.0 on an USB-stick and was able to boot it on my 
Desktop PC and install 8.0

from it.


DO YOU MEAN YOU INSTALLED THE 8.0 ISO ON A USB STICK. BOOTED FROM IT AS 
INSTALL SOURCE AND INSTALLED 8.0 ON A DESKTOP PC TO THE MOTHERBOARD 
CABLED HARD DRIVE??? OR DO YOU MEAN YOU INSTALLED 8.0 ON A DESKTOP PC TO 
ANOTHER USB STICK???





Now I plugged the same stick into my Dell Inspiron 9400 and the USB 
stick (2GB) is not even listed in the F12 Bios boot menu.


YOU MEAN YOU PLUGGED THE STICK WITH THE ISO INSTALLED ON IT THAT THE 
DESKTOP BOOTED FROM???




Any clues?

--
Christoph



Older pc's have bios which do not have option to boot from USB stick.
I think that is so in your case. Check mfg website for bios update.
If not you are SOL. (shit outof luck)


I can boot USB sticks in general from that notebook/BIOS. That Dell 9400 
isn't that old. Today I tried an another USB stick (16GB) an Ubuntu 9.04 
boot image and it worked fine. I saw the boot device under F12 in the 
bootable device menu.
It's definitely not the BIOS. Could be some partition problem (active 
partition?). 

 Why is it part #4 btw, that FreeBSD resides in and not part #1 ?

LETS NOT GET CONFUSED WITH MSDOS /FREEBSD TERMS. IN FREEBSD A SLICE IS 
WHAT MSDOS CALLS A PARTITION. IN FREEBSD A PARTITION IS A FILE SYSTEM 
SUCH AS /, /USR, /VAR WITH IN THE SLICE. A SLICE IS MARKED AS ACTIVE 
MEANING ITS BOOTABLE. THE MBR (MASTER BOOT RECORD)PARTITION TABLE IS 
REALLY FREEBSD SLICE TABLE. FROM YOUR STATEMENT ABOVE YOU HAVE A 
MOTHERBOARD CABLED HARD DRIVE WITH 4 PARTITIONS/SLICES DEFINED IN THE 
MBR PARTITION TABLE. THE FIRST 3 PARTITIONS COULD BE HOLDING OTHER 
OPERATING SYSTEMS THAT YOU MAY WANT TO BOOT FROM. IS THIS CORRECT?


 I followed some FreeBSD howto, if I'm not wrong, to bring the ISO

to the USB stick. Think it was a tool from HP to write it to the stick.

--
Christoph





Here is some thing for you to check. When you plug your USB stick into a
running freebsd system a bunch of messages are printed on the root
console. One of those messages contain the Revision level of the 2.0
standard used by the micro code in the usb stick. I have found through
testing different non-branded and branded sticks that the Revision level
makes a very large difference in whether you can boot from the stick.
Sticks that show Rev 2.00/0.00 or 2.00/1.00 will never boot. Only sticks
that show Rev 2.00/2.00 are bootable. Now since only one of my 4 pc's is
new enough to have bios option to boot from usb stick I do not know if
these results are dependent on my particular Acer TravelMate 4220 pc bios.

Please let me know what usb stick Revision levels you can boot from on 
both your desktop and laptop. I would think if the stick is bootable on 
desktop it should also boot on the laptop.


Here is the script I use to put the disc-1 iso on usb stick so I can use 
the stick as source media to install from. When booting from usb stick 
as install source and installing onto another usb stack as the target 
you have to have both sticks plugged in before booting. When you are in 
sysinstall fdisk check the stick size to verify you have chosen the 
correct da stick as target. You can find yourself fdisking your source 
stick by mistake. If you don't get prompt to chose da0 or da1 before 
fdisk starts then you have to tell sysinstall to re-probe devices by 
using options rescan (*) off the main menu,  move highlight bar by using 
arrow keys and hit space bar to rescan. Then you should get prompt 
containing both da devices before fdisk.



I have used this command to to write zeros to the usb stick MBR
dd if=/dev/zero of=/dev/da0 count=1
and this command to display the MBR
dd if=/dev/da0 count=1 | od -c

I also notice that fdisk does not allocate space on usb sticks as i 
would expect. It always allocates a free space before and after the full 
stick single slice. It also never get the size of the stick correct. A 
2GB stick is shown as 1.7GB and 4GB stick is shown as 3.7GB. Do you see 
the same thing happening with your usb sticks?



#!/bin/sh
#Purpose = Use to transfer the FreeBSD install cd1 to
#  a bootable 1GB USB flash drive so it can be used to install 
from.

#  First fetch the FreeBSD 7.1-RELEASE-i386-disc1.iso to your
#  hard drive /usr. Then execute this script from the command line
# fbsd2usb /usr/7.1-RELEASE-i386-disc1.iso /usr/7.1-RELEASE-i386-disc1.img
# Change system bios to boot from USB-dd and away you go.

# NOTE: This script has to be run from root and your 1GB USB flash drive
#   has to be plugged in before running this script.

# On the command line enter fbsd2usb iso-path img-path

# You can set some variables here. Edit them to fit your needs.

# Set serial variable to 0 if you don't want serial console at all,
# 1 if you want comconsole and 2 if you want comconsole and vidconsole
serial=0

set -u

if [ $# -lt 2 ]; then
echo

Re: Invalid partition table after installation

[Fbsd1]

John wrote:

On Fri, Jan 22, 2010 at 06:36:14AM -0600, John wrote:

On Fri, Jan 22, 2010 at 08:16:59PM +0800, Fbsd1 wrote:

John wrote:

On Thu, Jan 21, 2010 at 10:25:26PM +0800, Fbsd1 wrote:

John wrote:

On Thu, Jan 21, 2010 at 04:38:22PM +0800, Fbsd1 wrote:

John wrote:

I've tried the modern BIOS geometry and the 255 head geometry.
I've ensured that the first slice (boot slice) is smaller than 1.5
Gb.  I've tried to figure out what the BIOS thinks the geometry
is, but it doesn't seem to want to tell me.  At least, I can't find
it in the BIOS menu anywhere.  When I boot from the CD-ROM with
the 255 head geometry, though, it complains about the disk geometry,
saying 16h,63s != 255h,63s or something like that - it flies by
pretty fast (is there a way to go back and see that from the CD-ROM
boot only boot?).

I'm using the Standard boot manager, and the entire disk is devoted
to FreeBSD.

System
BIOS version  PT84510A.86A.2004.P05
Processor Type: Intel Pentium 4
Processor speed: 2.20Ghz

Memory: 512Mb

Disk: Primary IDE Master ST380021A (Seagate Barracuda ATA IV 80Gb)
Primary IDE Slave: IOMega ZIP 250
Secondary IDE Master: Sony CD-RW CRX19 (what I boot from to install)
Secondary IDE Slave: DVD-ROM DDU1621

Boot sequence:
1) ATAPI CD-ROM
2) Hard Drive
3) Removable Dev.

Modern BIOS geometry: 155061/16/63 for ad0
calculated geometry: 9729/255/63 for ad0

ad0s1 start=63, size=2875572
ad0s2 start=2875635, size=10217340
ad0s3 start=13092975, size=143203410
unus  start=156296384, size=5103

ad0s1a / 384Mb
ad0s1d /usr 1Gb
ad0s2b SWAP 1Gb
ad0s2d /tmp 384Mb
ad0s2e /var 512Mb
ad0s2f /var/mail 2Gb
ad0s2g /usr/ports 1Gb
ad0s3d /home/mysql 4Gb
ad0s3e /home 50Gb
ad0s3f /usr/src 3Gb
ad0s3g /usr/obj 3Gb
ad0s3h /extra 8483Mb

Suggestions, please?  I'm making zero headway right now. :(

What version of FreeBSD are you running

Well, yes, I suppose that would be a good bit of information!

What I'm *TRYING* to run is 8.0.  It seems to install successfully
(of course - after doing all that), but then when I try to boot
from the hard drive, I see an otherwise-blank screen that says:


Invalid partition table


and that's as far as it goes!


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
There are reports of this sort of thing caused by 8.0 fdisk when doing a 
install from scratch over a hard drive that all ready has an older 
version of Freebsd installed on it.


The solution is to force the scratching of the MBR on the disk first 
before running sysinstall fdisk.


Boot a LiveFS CD, then at a root prompt do:

sysctl kern.geom.debugflags=16  and:

dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1

where x equals your drive number.

OK.  I did exactly that.  I confirmed that the second 512 bytes were zero
by doing a dd if/dev/ad0 bs=512 count=2 | od -c
and everything from 001000 through 002000 was zero.

But I still got Invalid partition table after the installation.

I guess I should set up one of my other systems as a local mirror.
I've done the installation so many time already, and it looks like
I'm not done yet!

On the 8.0 fdisk/MBR subject.
Doing dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 was the
solution from another post to the list with subject 'SunFire X2100
fails'. Here is another post that gives more details
http://www.freebsd.org/cgi/getmsg.cgi?fetch=322687+326879+/usr/local/
www/db/text/2009/freebsd-questions/20091227.freebsd-questions

It seems in 8.0 gpart was introduced and a change was made to fdisk to
support its sector o mbr format. 8.0 fdisk and disklabel are now broken.

Searching the list archives may shed more light on your problem.

Hmmm.  This seems to describe a case where fdisk fails to change
the slice table.  That is definitely not my case.  The changes
certainly get made.  The next time I go to retry the installation,
it has the information I gave it the previous time.  I suppose it is
possible that it is putting it (and reading it) in the wrong location,
which is why the MBR throws up.

The problem is that I have a finite (and smallish) amount of time
in which to solve this.  It seems like the most expedient route
forward at this point may be to try to install 7.2 and see how
that goes.


OK - well, I just tried with 7.2.  I got exactly the same results.
After what seems like a successful installation, I try to boot from
the hard disk and get Invalid partition table.  Should I try Boot
Manager?  Could that make a difference?  Is it possible that this
combination of BIOS, processor, disk drive, etc., just isn't going
to to do for me?  I can't just keep throwing hours at this problem.


Something is wrong with the MBR. Do
dd if=/dev/zero of=/dev/ad0 count=1  to blank out the MBR

THEN
Do you have a bootable win98 cd or floppy that contains the msdos fdisk 
pgm. If so boot that and fdisk the hard drive

Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)

[Fbsd1]

Christoph Kukulies wrote:

I don't know why you shout. (?)


Not shouting, just making my inserted comments visible within the old 
post as in different from bottom or top posting.




Fbsd1 schrieb:

Christoph Kukulies wrote:

Fbsd1 schrieb:

Christoph Kukulies wrote:
I installed FreeBSD 8.0 on an USB-stick and was able to boot it on 
my Desktop PC and install 8.0

from it.


DO YOU MEAN YOU INSTALLED THE 8.0 ISO ON A USB STICK. BOOTED FROM IT 
AS INSTALL SOURCE AND INSTALLED 8.0 ON A DESKTOP PC TO THE MOTHERBOARD 
CABLED HARD DRIVE??? OR DO YOU MEAN YOU INSTALLED 8.0 ON A DESKTOP PC 
TO ANOTHER USB STICK???


The former, I copied the 8.0 iso image to an USB stick, booted it and 
installed it to the desktop PCs hard drive.
That was one story. The other point is, that I now wanted to plug this 
USB stick into my Dell inspiron and install FreeBSD in the same manner 
to a free partition on my notebooks hard drive.







Now I plugged the same stick into my Dell Inspiron 9400 and the USB 
stick (2GB) is not even listed in the F12 Bios boot menu.


YOU MEAN YOU PLUGGED THE STICK WITH THE ISO INSTALLED ON IT THAT THE 
DESKTOP BOOTED FROM???


Yes, that same stick booted the desktop but is not recognized in the F12 
menu of my notebook.






Any clues?

--
Christoph



Older pc's have bios which do not have option to boot from USB stick.
I think that is so in your case. Check mfg website for bios update.
If not you are SOL. (shit outof luck)


I can boot USB sticks in general from that notebook/BIOS. That Dell 
9400 isn't that old. Today I tried an another USB stick (16GB) an 
Ubuntu 9.04 boot image and it worked fine. I saw the boot device 
under F12 in the bootable device menu.
It's definitely not the BIOS. Could be some partition problem (active 
partition?). 

 Why is it part #4 btw, that FreeBSD resides in and not part #1 ?

LETS NOT GET CONFUSED WITH MSDOS /FREEBSD TERMS. IN FREEBSD A SLICE IS 
WHAT MSDOS CALLS A PARTITION. IN FREEBSD A PARTITION IS A FILE SYSTEM 
SUCH AS /, /USR, /VAR WITH IN THE SLICE. A SLICE IS MARKED AS ACTIVE 
MEANING ITS BOOTABLE. THE MBR


The FreeBSD fdisk program names it partition.

(MASTER BOOT RECORD)PARTITION TABLE IS REALLY FREEBSD SLICE TABLE. 
FROM YOUR STATEMENT ABOVE YOU HAVE A MOTHERBOARD CABLED HARD DRIVE 
WITH 4 PARTITIONS/SLICES DEFINED IN THE MBR PARTITION TABLE. THE FIRST 
3 PARTITIONS COULD BE HOLDING OTHER OPERATING SYSTEMS THAT YOU MAY 
WANT TO BOOT FROM. IS THIS CORRECT?


Actually, I thought the USB stick had been blanked out before, but I'm 
nit sure and will look at it again.




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

Re: Cannot boot FreeBSD (8.0) from USB stick (Dell Inspiron 9400)

[Fbsd1]

Christoph Kukulies wrote:

Here is some more info:

The file I copied to the USB stick was

ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/8.0/8.0-RELEASE-i386-memstick.img 



Actually, I don't remember how I got the image to the USB stick. I 
believe I used a free tool from HP

from within Windows XP.

I will try out your method below now.


kernel messages at the time usb stick is inserted:
ugen4.3: USB 2.0 at usbus4
umass0: USB 2.0 Flash Disk, class 0/0, rev 2.00/1.10, addr 3 on usbus4
umass0:  SCSI over Bulk-Only; quirks = 0x
umass0:1:0:-1: Attached to scbus1
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have 
changed

(probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
da0 at umass-sim0 bus 0 target 0 lun 0
da0: USB 2.0 Flash Disk PMAP Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 1921MB (3935000 512 byte sectors: 255H 63S/T 244C)
GEOM: da0: media size does not match label.
#
#
# fdisk /dev/da0
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl)

/tmp/l12: unmodified, readonly: line 1
kernel messages at the time usb stick is inserted:
ugen4.3: USB 2.0 at usbus4
umass0: USB 2.0 Flash Disk, class 0/0, rev 2.00/1.10, addr 3 on usbus4
umass0:  SCSI over Bulk-Only; quirks = 0x
umass0:1:0:-1: Attached to scbus1
(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
(probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
(probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have 
changed

(probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
da0 at umass-sim0 bus 0 target 0 lun 0
da0: USB 2.0 Flash Disk PMAP Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 1921MB (3935000 512 byte sectors: 255H 63S/T 244C)
GEOM: da0: media size does not match label.
#
#
# fdisk /dev/da0
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=244 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
UNUSED
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
   start 0, size 5 (24 Meg), flag 80 (active)
   beg: cyl 0/ head 0/ sector 1;
   end: cyl 1023/ head 254/ sector 63
#
--
Christoph



The dd command is what is used to copy the memstick.img to USB stick.

The memstick.img is created with the dd command so no compression done. 
It has fixit included and is 3 times larger than the disc-1 iso file. 
Thats why I download the disc-1 iso and run the script to build the img 
on USB stick. So much faster this way.


So I see that both usb sticks you are using are revision rev 2.00/1.10. 
But the stick that boots on your desktop will not boot on the laptop. 
And the stick that boots on the laptop will not boot on the desktop. 
Very strange indeed. This indicates that the pc bios are playing a big 
part in which USB stick it recognizes as bootable.


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

Re: Invalid partition table after installation (GOOD NEWS!)

[Fbsd1]

John wrote:

On Fri, Jan 22, 2010 at 04:35:21PM -0600, John wrote:

On Fri, Jan 22, 2010 at 11:01:02AM -0600, John wrote:

On Fri, Jan 22, 2010 at 08:09:50AM -0600, John wrote:

On Fri, Jan 22, 2010 at 07:27:56AM -0600, John wrote:

On Fri, Jan 22, 2010 at 06:36:14AM -0600, John wrote:

On Fri, Jan 22, 2010 at 08:16:59PM +0800, Fbsd1 wrote:

John wrote:

On Thu, Jan 21, 2010 at 10:25:26PM +0800, Fbsd1 wrote:

John wrote:

On Thu, Jan 21, 2010 at 04:38:22PM +0800, Fbsd1 wrote:

John wrote:

I've tried the modern BIOS geometry and the 255 head geometry.
I've ensured that the first slice (boot slice) is smaller than 1.5
Gb.  I've tried to figure out what the BIOS thinks the geometry
is, but it doesn't seem to want to tell me.  At least, I can't find
it in the BIOS menu anywhere.  When I boot from the CD-ROM with
the 255 head geometry, though, it complains about the disk geometry,
saying 16h,63s != 255h,63s or something like that - it flies by
pretty fast (is there a way to go back and see that from the CD-ROM
boot only boot?).

I'm using the Standard boot manager, and the entire disk is devoted
to FreeBSD.

System
BIOS version  PT84510A.86A.2004.P05
Processor Type: Intel Pentium 4
Processor speed: 2.20Ghz

Memory: 512Mb

Disk: Primary IDE Master ST380021A (Seagate Barracuda ATA IV 80Gb)
Primary IDE Slave: IOMega ZIP 250
Secondary IDE Master: Sony CD-RW CRX19 (what I boot from to install)
Secondary IDE Slave: DVD-ROM DDU1621

Boot sequence:
1) ATAPI CD-ROM
2) Hard Drive
3) Removable Dev.

Modern BIOS geometry: 155061/16/63 for ad0
calculated geometry: 9729/255/63 for ad0

ad0s1 start=63, size=2875572
ad0s2 start=2875635, size=10217340
ad0s3 start=13092975, size=143203410
unus  start=156296384, size=5103

ad0s1a / 384Mb
ad0s1d /usr 1Gb
ad0s2b SWAP 1Gb
ad0s2d /tmp 384Mb
ad0s2e /var 512Mb
ad0s2f /var/mail 2Gb
ad0s2g /usr/ports 1Gb
ad0s3d /home/mysql 4Gb
ad0s3e /home 50Gb
ad0s3f /usr/src 3Gb
ad0s3g /usr/obj 3Gb
ad0s3h /extra 8483Mb

Suggestions, please?  I'm making zero headway right now. :(

What version of FreeBSD are you running

Well, yes, I suppose that would be a good bit of information!

What I'm *TRYING* to run is 8.0.  It seems to install successfully
(of course - after doing all that), but then when I try to boot
from the hard drive, I see an otherwise-blank screen that says:


Invalid partition table


and that's as far as it goes!


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
There are reports of this sort of thing caused by 8.0 fdisk when doing a 
install from scratch over a hard drive that all ready has an older 
version of Freebsd installed on it.


The solution is to force the scratching of the MBR on the disk first 
before running sysinstall fdisk.


Boot a LiveFS CD, then at a root prompt do:

sysctl kern.geom.debugflags=16  and:

dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1

where x equals your drive number.

OK.  I did exactly that.  I confirmed that the second 512 bytes were zero
by doing a dd if/dev/ad0 bs=512 count=2 | od -c
and everything from 001000 through 002000 was zero.

But I still got Invalid partition table after the installation.

I guess I should set up one of my other systems as a local mirror.
I've done the installation so many time already, and it looks like
I'm not done yet!

On the 8.0 fdisk/MBR subject.
Doing dd if=/dev/zero of=/dev/adx oseek=1 bs=512 count=1 was the
solution from another post to the list with subject 'SunFire X2100
fails'. Here is another post that gives more details
http://www.freebsd.org/cgi/getmsg.cgi?fetch=322687+326879+/usr/local/
www/db/text/2009/freebsd-questions/20091227.freebsd-questions

It seems in 8.0 gpart was introduced and a change was made to fdisk to
support its sector o mbr format. 8.0 fdisk and disklabel are now broken.

Searching the list archives may shed more light on your problem.

Hmmm.  This seems to describe a case where fdisk fails to change
the slice table.  That is definitely not my case.  The changes
certainly get made.  The next time I go to retry the installation,
it has the information I gave it the previous time.  I suppose it is
possible that it is putting it (and reading it) in the wrong location,
which is why the MBR throws up.

The problem is that I have a finite (and smallish) amount of time
in which to solve this.  It seems like the most expedient route
forward at this point may be to try to install 7.2 and see how
that goes.

OK - well, I just tried with 7.2.  I got exactly the same results.
After what seems like a successful installation, I try to boot from
the hard disk and get Invalid partition table.  Should I try Boot
Manager?  Could that make a difference?  Is it possible that this
combination of BIOS, processor, disk drive, etc., just isn't going
to to do for me?  I can't just keep throwing hours at this problem

8.0 and floppy support

[Fbsd1]

When booting release 8.0 i no longer get the fd0 floppy device prob 
message. This pc has run freebsd 6.4 7.0 7.2 which all supported the 
floppy drive.


Has floppy drive support been dropped in 8.0?

I know the floppy drive works because i can boot win98 floppy disk ok.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Server compromised Zen-Cart record company Exploit

[Fbsd1]

Bogdan Webb wrote:

try php's safe_mode but it is likely to keep the hackers off, indeed they
can get in and snatch some data but they would be kept out of a shell's
reach... but sometimes safe_mode is not enough... try considering Suhosin
but the addon not the patch... and define the
suhosin.executor.func.blacklist witch will deny use of certain php commands
that allow shell execution... but keep in mind it's impossible to prevent
all breaches... this php patch will only keep the hacker kiddos off but
there's still a good chance it can be broken... stay safe !

ref's:
http://www.hardened-php.net/suhosin.127.html
http://beta.pgn.ro/phps/phpinfo.php

2010/1/31 James Smallacombe u...@3.am


Whoever speculated that my server may have been compromised was on to
something (see bottom).  The good news is, it does appear to be contained to
the www unpriveleged user (with no shell).  The bad news is, they can
still cause a lot of trouble.  I found the compromised customer site and
chmod 0 their cart (had php binaries called core(some number).php that gave
the hacker a nice browser screen to cause all kinds of trouble)

Not sure if this is related to the UDP floods, but if not, it's a heck of a
coincidence.  At times, CPU went through the roof for the www user, mostly
running some sort of perl scripts (nothing in the suexec-log).  I would kill
apache, but couldn't restart it as it would show port 80 in use.  I would
have to manually kill processes like these:

www  70471  1.4  0.1  6056  3824  ??  R  4:21PM   0:44.75 [eth0] (perl)
www  70470  1.2  0.1  6060  3828  ??  R  4:21PM   0:44.50 [bash] (perl)
www  64779  1.0  0.1  6056  3820  ??  R 4:07PM   2:24.34
/sbin/klogd -c 1 -x -x (perl)
www   70472  1.0  0.1  6060  3828  ??  R 4:21PM   0:44.84

I could not find ANY file named klogd on the system, let alone in /sbin.
Clues as to how to dig myself out of this are appreciated

I found this in /tmp/bx1.txt:

--More--(5%)#!/usr/bin/php
?php

#
# --- Zen Cart 1.3.8 Remote Code Execution
# http://www.zen-cart.com/
# Zen Cart Ecommerce - putting the dream of server rooting within reach of
anyone!
# A new version (1.3.8a)  is avaible on http://www.zen-cart.com/
#
# BlackH :)
#

error_reporting(E_ALL ^ E_NOTICE);
if($argc  2)
{
echo 
=___ Zen Cart 1.3.8 Remote Code Execution Exploit  =

|  BlackH bl4c...@gmail.com  |

|  |
| \$system php $argv[0] url|
| Notes: url  ex: http://victim.com/site (no slash)  |
|  |

;exit(1);

---  snipped --

It is dated from two nights ago, after these issues started, but it's
nonetheless larming.  Security Focus is aware of the issue and refers you to
Zen for the fix.  Only problem is, this is an old version of Zen cart, and
the

James Smallacombe PlantageNet, Inc. CEO and Janitor
u...@3.am http://3.am
=
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org


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





check out port mod_security for apache31 and mod_security2 for apache22
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

FTP using .netrc

[Fbsd1]

Goal is to download the install source directory tree so I can use it as
 an target for local ftp sysinstall.

The problem is that the FreeBSD ftp server keeps timing out before
everything is downloaded. This is the error message ftp gives me.

421 Service not available, remote server timed out. Connection closed

This is the command line command used to launch the ftp session
ftp -v ftp.FreeBSD.org

It defaults to using /root/.netrc which is shown below


machine ftp.FreeBSD.org
login anonymous
password f...@home.com
macdef init
prompt off
cd /pub/FreeBSD/releases/i386/8.0-RELEASE
epsv4 off
mget  ERRATA.HTM ERRATA.TXT HARDWARE.HTM HARDWARE.TXT README.HTM
mget  README.TXT RELNOTES.HTM RELNOTES.TXT cdrom.inf docbook.css
$ getdir base catpages dict doc games info kernels manpages ports
proflibs src
quit

macdef getdir
! mkdir $i
mget $i/*


Question is how can I make FTP resume the download at the place it timed
out. IE not start at the beginning and re-download all the same files
all ready received. ftp -vR ftp.FreeBSD.org just starts downloading from
the beginning again.

I tried testing using fetch -avrpAF ftp://ftp.FreeBSD.org but the
/.netrc file is not being defaulted to like when using plan ftp as above.

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

Installing FreeBSD on a USB stick.

[Fbsd1]

Hello list.
I wrote this article on the different ways to install Freebsd on a USB 
stick. It covers a large range of related subjects dealing with 
installing Freebsd and the use of an USB stick. It's way to large to 
post here so the link below will take you to the article. Looking for 
feedback, errors, corrections, your thoughts in general.



http://www.a1poweruser.com/usb.info.htm


Thanks in advance.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Installing FreeBSD on a USB stick.

[Fbsd1]

Christer Solskogen wrote:

On Mon, Feb 15, 2010 at 4:55 AM, Fbsd1 fb...@a1poweruser.com wrote:


http://www.a1poweruser.com/usb.info.htm



Why does Websence think your site contains Potentially Unwanted Software?



Have no idea what you are talking about. Since your using their software 
maybe you should be asking them this question.

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

Re: Installing FreeBSD on a USB stick.

[Fbsd1]

Christer Solskogen wrote:

On Mon, Feb 15, 2010 at 6:26 PM, Tim Judd taj...@gmail.com wrote:


And I agree with this 'Fbsd1' user (I wish 'Fbsd1' would update his
MTA with a real name) that since Christer is who uses the product, he
should look into it.


I'm probably a bit paranoid, but when someone who is not using their
real name, post a email saying something like CLIK ON DIS LINK PLZ
/and/ Websense kicks in, my paranoia takes over :)

Yea like Christer Solskogen is your real name. Are you that naive that 
you believe a name used on a email address has any truth in who really 
is using it. If you have nothing to say about the article you should 
have kept your paranoia to your self instead of questioning the 
integrity of the writer. There was no reason to make your first reply. 
And even after being told your websence software is in error you still 
continue mouthing nonsense.


Once again YOU SHOULD BE ASKING YOUR WEBSENSE SOFTWARE VENDOR WHAT ARE 
THE EXACT REASONS THEY FLAGGED THIS SITE. OTHER POSTERS HAVE ALL READY 
TOLD YOU THAT FALSE POSITIVES ARE COMMON FROM VENDORS OF SUCH SCAM 
SERVICES AS WEBSENSE. NOBODY HAS A GUN TO YOUR HEAD TO CLICK ON A LINK. 
THAT IS YOUR CHOOSE OR NOT AND NOBODY HERE ON THE LIST HAS THE LEAST 
INTEREST IN WHAT YOU CHOOSE TO CLICK ON SO KEPT IT TO YOUR SELF.


Any reply from this point on just marks you as a flamer.


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

Re: Can't boot off the USB image

[Fbsd1]

rocwhite168 wrote:

My computers (Dell SX280 PCs or Dell D600 laptop) seem

to refuse to boot off the USB disk with non-Windows images are
written to it (I have also tried OpenSolaris images).
I've tried using dd to write the .img files, or using unetbootin to
write either .img or .iso images, or using UltraISO to write the iso
files to my USB disk, but all the methods failed. But if the image was 
a Windows boot disk, it did work. Does anyone know what the problem 
could be? Is it simply because the computers are to old? Or do I
have to do anything special for the FreeBSD images to make the 
computers boot off a USB device?



Thank you very much!
___



When you say USB disk, you do mean an USB cabled external disk hard 
drive correct? That being the case, you have to download the FreeBSD 
disc1.iso file and burn it to a cdrom disk and then boot off that to 
start the sysinstall process to populate your USB cabled external disk 
hard drive with the FreeBSD operating system. Reading the FreeBSD manual 
on the install process or the Freebsd install guide should help you a lot.


http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/
or
http://www.a1poweruser.com


Now if on the other hand you are really talking about a (USB memory 
stick, flash drive, key disk, stick disk, or pen) which all mean the 
same thing, then you should read this article Everything you want to 
know about Installing FreeBSD on a USB stick 
http://www.a1poweruser.com/30.00-USB_installing_article.php


If none of this helps you then repost with an more detailed description 
of just what you did and what the result was.




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

Handbook Index

[Fbsd1]

I find it very hard to find the subject I am looking for in the 
handbook. The index only gets me to the general area in the handbook and 
then I have to (next page) through it looking for what I hope is there.


The Index really needs to be expanded to display each and every 
sub-section of all the major sections now in the index.


For example Installing from a ms/dos partition or splash screen usage.

These are both subjects in the handbook but are not in the index.
What good is am index that does not index its content?

The purpose of the index is to list all subjects documented in the 
handbook so the reader can skim through the index and click on the exact 
subject they want to read. Can not do that with the current handbook index.


So what do other people think?
Should I submit a Doc bug on this??
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Loader.conf mfs statements

[Fbsd1]

Tyring to understand what mfsbsd is doing.
In its loader.conf file i see these statements
geom_uzip_load=YES
mfs_load=YES
mfs_type=mfs_root
mfs_name-/mfsroot
tmpfs_laod=YES
vfs.root.mountfrom=ufs:/dev/mdo

Where do I find documentation on the meaning of these statements?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: Loader.conf mfs statements

[Fbsd1]

Daniel Bye wrote:

On Thu, Mar 04, 2010 at 09:48:27PM +0800, Fbsd1 wrote:

Tyring to understand what mfsbsd is doing.
In its loader.conf file i see these statements
geom_uzip_load=YES
mfs_load=YES
mfs_type=mfs_root
mfs_name-/mfsroot
tmpfs_laod=YES
vfs.root.mountfrom=ufs:/dev/mdo

Where do I find documentation on the meaning of these statements?


loader.conf(5) and /boot/defaults/loader.conf



All ready checked those sources before posting with no joy.
IE: your are wrong. Those sources have no info on the mfs* statements.

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

Re: Booting MFS from Secondary Partition

[Fbsd1]

Martin McCormick wrote:

I have hit one of these impenetrable walls in which nothing
seems to work but I know it should. I have tried several
versions of /boot.config to no avail. The idea is exactly the
same principle as described in depenguinator which is software
that lets one use grub in Linux to install FreeBSD on a working
Linux system. The idea is to steal the swap partition, put mfsboot
there, and then tell grub to boot from that partition rather than the
normal active one.

The manual for boot.config makes me think I should be
able to just put in the information describing the secondary
partition and it should cause a boot from that one but:

/boot.config: 1:ad(0,b)/boot/loader -P

FreeBSD/i386 boot
Default: 1:ad(0,b)/boot/loader
boot:
error 1 lba 0
No /boot/loader

The mfsboot image works when started from the primary
partition so I am stuck as to why boot.config is not starting
from that secondary partition.
The present boot.config is:

1:ad(0,b)/boot/loader -P

If mfsbsd was starting, shouldn't it see its boot
loader?

Is there a mfsbsd discussion list? Surely, somebody else
has hit this brick wall, also.




From what I read in this freebsd.org article
http://www.freebsd.org/doc/en/articles/remote-install/index.html

There is hard coded logic that is stopping you from doing what you want.
Looks like you are SOL.

Booting mfsBSD
Now that the mfsBSD image is ready, it must be uploaded to the remote 
system running a live rescue system or pre-installed Linux® 
distribution. The most suitable tool for this task is scp:


# scp disk.img r...@192.168.0.2:.
To boot mfsBSD image properly, it must be placed on the first (bootable) 
device of the given machine. This may be accomplished using this example 
providing that sda is the first bootable disk device:


# dd if=/root/disk.img of=/dev/sda bs=1m
If all went well, the image should now be in the MBR of the first device 
and the machine can be rebooted. Watch for the machine to boot up 
properly with the ping(8) tool. Once it has came back on-line, it should 
be possible to access it over ssh(1) as user root with the configured 
password.



The mfsbsd process has new maintainer,  Martin Matuska m...@freebsd.org
Email him for help.

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

Re: Booting MFS from Secondary Partition

[Fbsd1]

Martin McCormick wrote:

Fbsd1 writes:

There is hard coded logic that is stopping you from doing what you want.
Looks like you are SOL.


Me thinks you are absolutely correct. I was only hoping
I was doing something wrong and a slight syntax change would
make it work. Thank you and thanks to Maciej Milewski m...@dat.pl
for his suggestion.

I have one last trick up my sleve before giving up
completely on this idea. Maybe I can hijack one of the rc.x
scripts to cause it to spew a memory disk image of the mfsboot
code on to the freshly-unmounted /dev/ad0 device during a
reboot. Since the goal is to completely rebuild the system
anyway, this would be the last gasp of the present system as it
gets ready to reboot, hopefully with mfsbsd and all hard drives
dismounted.

Martin McCormick
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org



just dd the image to what ever drive you want
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: [ fbsd_questions ] tar(1) vs. msdos_fs: a death_spiral ?

[Fbsd1]

spellberg_robert wrote:

greetings, all ---

i confess that this one has me flummoxed.
the short question:  does tar(1) spit_up when extracting onto an 
msdos_fs hard_drive ?


[ i tried the mailing_list archives tar AND msdos, for -questions, 
-chat, -bugs, -newbies, -performance ]

[ other research as indicated ]



i have no problem using tar(1) on ufs.
large files, small files; if i am on ufs, everything is fine.

i have been creating tarballs from medium_size msdos_fs drives, also.
this worked fine.
i would check them by extracting into a ufs root_point.
no problem.

this week, i tried to do something new.
i wanted to take a tarball, already on ufs, that was created from an 
msdos_fs drive and

  extract it onto an msdos_fs drive.
this, to me, actually seems like a reaasonable idea; but, what do i know ?

well, it starts out just fine, but, it rapidly degenerates into what is, 
normally, infinite_loop land.

when ps(1) says cpu_% of 1%, 2%, 5%; ok, it is an active process.
in about ten minutes, tar(1) enters 90% cpu.
after 20 minutes, 99%.

i does not matter if X_windows is running.
foreground or background process, no difference.

it seems to be working correctly because the error_file is always of 
zero_size.

i suspect that if i left it alone, after a few days, it would finish.



some details
  [ everything is ufs, using 8kB/1kB, except /mnt, which is clustered 
as indicated;

of course, the tarball is not named ball,
nor is the path, to the tarball, named path, but, then, you knew that
  ].


mkdir /path_c
mkdir /path_c/88_x

mkdir /path_d
mkdir /path_d/88_x


mount -v -t msdos /dev/ad1s1 /mnt   [ fat_32, about 
6_GB, 4_KB cluster, the c:\ drive, primary partition. ]

cd /mnt
( tar cvplf /path_c/99_ball.tar .
   /path_c/90_cvpl.out   )
  /path_c/91_cvpl.err[ real time 16m 07s, 
exit_status 0 ]

cd / ; umount /mnt


mount -v -t msdos /dev/ad1s5 /mnt   [ fat_32, about 
12_GB, 8_KB cluster, the d:\ drive, extended partition. ]

cd /mnt
( tar cvplf /path_d/99_ball.tar .
   /path_d/90_cvpl.out   )
  /path_d/91_cvpl.err[ real time 20m 15s, 
exit_status 0 ]

cd / ; umount /mnt


cd /path_c/88_x
( tar xvplf ../99_ball.tar
   ../92_xvpl.out )
  ../93_xvpl.err [ real time 08m 11s; 
exit_status 0 ]
diff ../9[02]*  [ exit_status 0; the 
tables_of_contents are the same ]
ls -l ..[ visually inspect 
the error_files to be of zero_size - verified ]



cd /path_d/88_x
( tar xvplf ../99_ball.tar
   ../92_xvpl.out )
  ../93_xvpl.err [ real time 12m 37s; 
exit_status 0 ]
diff ../9[02]*  [ exit_status 0; the 
tables_of_contents are the same ]
ls -l ..[ visually inspect 
the error_files to be of zero_size - verified ]



[ note that this approach works; it is a good excuse to refill my 
coffee_cup. ]



[ physically replace the source hard_drive w/ 80_GB capacity, 32_KB 
cluster, primary_partition only, virgin hard_drive.
  this destination hard_drive was fdisked and formated 
yesterday_morning;
  this drive was scandisked yesterday for 12 hours, using the 
thorough option,
  it has zero bad clusters [ i wanted to eliminate the drive as the 
problem ]

].


mount -v -t msdos /dev/ad1s1 /mnt

mkdir /mnt/path_cc
cd/mnt/path_cc

( tar xvplf /path_c/99_ball.tar
../92_xvpl.out )
   ../93_xvpl.err[ started this at 
18:05_utc, it is now about 21:35_utc;
  the toc_file, from 
the 8_minute extraction above, has 87517 lines in it;
  the current 
toc_file has only 12667 lines.

]

[ this is the second hard_drive i have tried this on, this week;
  i will probably kill the process as xterm is being updated about 8 
seconds apart, now.

]


on the first hard_drive [ i have not done this on the second drive, yet ]
  i noted that i had a successful extraction on the ufs drive.
not being the smartest person around, i had, what i thought to be, a 
--brilliant-- idea,

  what if i try a recursive copy of the successful extraction ?

this is interesting;
  the recursive copy started_out like gang_busters, then, just like the 
extraction, slowly bogged_down to 99%_cpu.


hmmm..., two different msdos_fs hard_drives, two different 
normally_reliable utilities, same progressive_hogging of the cpu.
this makes me wonder about the msdos_fs hard_drive, which is, rapidly, 
becoming the only remaining common factor.




ok.
i tried the mailing lists.
right now, i am web_page searching;
  tar(1) seems to be slow in some situations, but, i have not, yet, 

/boot.config

[Fbsd1]

During the boot process I want to change the device used to boot from.
From the default 0:ad(0,a)/boot/loader
to 0:da(0,a)/boot/loader forcing the boot to continue from usb stick.

Here is the problem, the bios have no option to boot from USB device.
So thinking let the bios point to first drive to start the boot process 
and have a /boot.config file to redirect to booting from the USB stick.

I am assuming the '0' zero will mean the first USB device.

Is there any command i can use to verify the single USB stick is the 0 
device?


Is this concept valid?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

How to make man pages

[Fbsd1]

Where can I find documentation on the procedure to create man pages 
for a port?

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

Re: /boot.config

[Fbsd1]

Dan Nelson wrote:

In the last episode (Mar 30), Fbsd1 said:

During the boot process I want to change the device used to boot from.
 From the default 0:ad(0,a)/boot/loader
to 0:da(0,a)/boot/loader forcing the boot to continue from usb stick.

Here is the problem, the bios have no option to boot from USB device.  So
thinking let the bios point to first drive to start the boot process and
have a /boot.config file to redirect to booting from the USB stick.  I am
assuming the '0' zero will mean the first USB device.

Is there any command i can use to verify the single USB stick is the 0 
device?


If you boot DOS from a floppy, can you see the USB stick as B: or C: ?  If
not, then the BIOS probably has no USB support at all, and you'll need to
put a small boot partition somewhere on your hard drive to pull the kernel
from.  128MB is large enough for a /boot directory, and you can set
vfs.root.mountfrom=ufs:/dev/da0s1a in loader.conf to make it mount its
root filesystem from the USB stick (since at that point the kernel has
loaded its own USB drivers).

If you do see the USB drive from a DOS boot floppy, try entering
1:da(0,a)? at the boot block prompt and see if it lists the files in your
USB filesystem.  If it does, then 1:da(0,a)/boot/loader should let you
boot FreeBSD.




The USB stick is plugged in before booting. During boot I select option 
6 from Freebsd menu to go direct to the loader prompt. I have ok on 
command line. I enter
 vfs.root.mountfrom=ufs:/dev/da0s1a and get not found after hitting 
enter key.
At the ok prompt I enter ? for list of available boot devices and only 
have ad0 listed.


It seems the da0 device USB stick is not recognized yet.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How to make man pages

[Fbsd1]

On 31/03/2010 04:00:15, Fbsd1 wrote:
Where can I find documentation on the procedure to create man pages
for a port?


If you want to write a man page from scratch, probably the best way to
get started is to just copy a man page from the base system and edit it
to taste.  See groff(1) for documentation on the command used to format
man pages from source, and groff_mdoc(7) for details on the groff macro
syntax.  groff+mdoc might be a markup language, but it's nothing at all
like HTML.

If you're after how to install man pages for a port, then look at:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-manpages.html

Note that the MANX and other ports Macros only affect the pkg-list and
compressing the man pages /after/ installation. You'll still have to put
in some code to copy your self-written man page into place.

Cheers,

Matthew


OK i want to write a man page from scratch. So lets say i want to use
/usr/share/man/man2/jail.2.gz as my starting sample. How do I convert 
this .gz file to a plain text file so I can edit it with ee? And how do 
I turn the edited text file back in to a man page .gz file?


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

Re: /boot.config

[Fbsd1]

krad wrote:

On 31 March 2010 04:53, Fbsd1 fb...@a1poweruser.com wrote:


Dan Nelson wrote:


In the last episode (Mar 30), Fbsd1 said:


During the boot process I want to change the device used to boot from.
 From the default 0:ad(0,a)/boot/loader
to 0:da(0,a)/boot/loader forcing the boot to continue from usb stick.

Here is the problem, the bios have no option to boot from USB device.  So
thinking let the bios point to first drive to start the boot process and
have a /boot.config file to redirect to booting from the USB stick.  I am
assuming the '0' zero will mean the first USB device.

Is there any command i can use to verify the single USB stick is the 0
device?


If you boot DOS from a floppy, can you see the USB stick as B: or C: ?  If
not, then the BIOS probably has no USB support at all, and you'll need to
put a small boot partition somewhere on your hard drive to pull the kernel
from.  128MB is large enough for a /boot directory, and you can set
vfs.root.mountfrom=ufs:/dev/da0s1a in loader.conf to make it mount its
root filesystem from the USB stick (since at that point the kernel has
loaded its own USB drivers).

If you do see the USB drive from a DOS boot floppy, try entering
1:da(0,a)? at the boot block prompt and see if it lists the files in
your
USB filesystem.  If it does, then 1:da(0,a)/boot/loader should let you
boot FreeBSD.



The USB stick is plugged in before booting. During boot I select option 6
from Freebsd menu to go direct to the loader prompt. I have ok on command
line. I enter
 vfs.root.mountfrom=ufs:/dev/da0s1a and get not found after hitting
enter key.
At the ok prompt I enter ? for list of available boot devices and only have
ad0 listed.

It seems the da0 device USB stick is not recognized yet.

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




try legacy usb in the bios, it may help



My bios have no reference to USB at all.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How to make man pages

[Fbsd1]

Matthew Seaman wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 31/03/2010 08:54:25, Fbsd1 wrote:

OK i want to write a man page from scratch. So lets say i want to use
/usr/share/man/man2/jail.2.gz as my starting sample. How do I convert
this .gz file to a plain text file so I can edit it with ee?


   % cp /usr/share/man/man2/jail.2.gz .
   % gunzip jail.2.gz
   % mv jail.2 myname.2
   % ee myname.2


And how do
I turn the edited text file back in to a man page .gz file?


To compress the groff source:

   % gzip myname.2

To render the groff source as ascii text (what the man(1) command does):

   % groff -mdoc -Tascii myname.2 | less

or

   % gzcat myname.2.gz | groff -mdoc -Tascii | less

In general though, you should keep the man page source uncompressed
while you're working on it and within the port; install it uncompressed
and leave it to the ports machinery to compress it after installation.





Getting closer but not there yet. Selected man jail to be my example of 
macro commands used. Did  [gunzip jail.8.gz] and now I have jail.8 file.

How to I convert this file to native macro file that I can edit with ee?

After editing the macro file how to I convert it to format ready to 
compress? I want to test it with the man command.


When I do groff -mdoc -Tascii jail.8  | less
I get loads of  this message mdoc warning: Empty input line #xxx.
If I look at man jail screen output I see each message corresponds to a 
blank line in the man page. Is this suppose to happen?








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

Re: How to make man pages

[Fbsd1]

Matthew Seaman wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 01/04/2010 09:41:59, Fbsd1 wrote:

Getting closer but not there yet. Selected man jail to be my example of
macro commands used. Did  [gunzip jail.8.gz] and now I have jail.8 file.
How to I convert this file to native macro file that I can edit with ee?


Ah -- did you copy the right file?  /usr/share/man/man8/jail.8.gz should
contain mdoc source, which looks like this:


.\
.\ Copyright (c) 2000, 2003 Robert N. M. Watson
.\ Copyright (c) 2008 James Gritton
.\ All rights reserved.
.\
.\ Redistribution and use in source and binary forms, with or without
.\ modification, are permitted provided that the following conditions
.\ are met:
.\ 1. Redistributions of source code must retain the above copyright
.\notice, this list of conditions and the following disclaimer.
.\ 2. Redistributions in binary form must reproduce the above copyright
.\notice, this list of conditions and the following disclaimer in the

[... copyright statements elided for reasons of space ...]

.\ $FreeBSD: src/usr.sbin/jail/jail.8,v 1.97.2.3 2010/01/23 16:40:35 bz
Exp $
.\
.Dd January 17, 2010
.Dt JAIL 8
.Os
.Sh NAME
.Nm jail
.Nd create or modify a system jail
.Sh SYNOPSIS
.Nm
[...etc...]

No blank lines there.  Don't confuse this with the preprocessed version
in /usr/share/man/*cat8*/jail.8.gz

Cheers,

Matthew



Yep that is the problem. I have no source. I did minimum install.
Is there any way to convert the preprocessed version in 
/usr/share/man/*cat8*/jail.8.gz to native macro file.

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

Re: FreeBSD splash screen - freezes my Dell Inspiron 9400

[Fbsd1]

Christoph Kukulies wrote:

I'm observing the following with 8.0 Release:

Just for fun I installed a FreeBSD splash screen The Power to Serve 
with the abstracted little demon.
As long as the vidcontrol screen saver (not X11, I'm not running X11 at 
present) has not fired the first time,

everything  is fine - I can work in alphanumeric mode.

But when I leave the computer unattended for a while so that the 
screensaver switches to darken/blank the screen
the first time, the machine freezes or at least cannot be woken up again 
so that the character screen shows up again.


Anyone seen this or having a clue?

Also not sure whether it is a splash screen issue at all, butr I thought 
so, since it would have come up earlier otherwise.


--
Christoph Kukulies





Have you read the handbook section 12.3.3.4 Boot Time Splash Screens?
The splash screen has its own screen saver. Or are you talking about the 
screen saver enabled in rc.conf?

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

usage of /usr/bin

[Fbsd1]

Why are there RELEASE base files in /usr/bin. I thought /usr was to only 
contain binaries installed from ports or packages.

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

Re: usage of /usr/bin

[Fbsd1]

Polytropon wrote:

On Wed, 07 Apr 2010 15:24:51 +0800, Fbsd1 fb...@a1poweruser.com wrote:
Why are there RELEASE base files in /usr/bin. I thought /usr was to only 
contain binaries installed from ports or packages.


No. The /usr/local subtree (LOCAL) is for local additions (ports
and packages), while things outside this structure usually belong
to the system itself; I'm excluding mounted filesystem and other
things here for a moment.

 /usr/  contains the majority of user utilities and applications

bin/  common utilities, programming tools, and applica-
  tions

But:

   local/local executables, libraries, etc.  Also used as the
  default destination for the FreeBSD ports framework.
  Within local/, the general layout sketched out by
  hier for /usr should be used.  Exceptions are the
  man directory (directly under local/ rather than
  under local/share/), ports documentation (in
  share/doc/port/), and /usr/local/etc (mimics
  /etc).

Because we are on FreeBSD, there's excellent documentation
that shows how and why the system tree has a well intended
layout. :-)

The command

% man hier

will explain everything in detail.




But that is not true. The postfix port populates /usr/bin. And I am sure 
postfix is not the only port to do this also. This intermingling of 
RELEASE binaries and port binaries in /usr/bin is a really big problem 
when trying to build jails. Any past ports which have been included into 
the base release should not be in /usr period.
Saying system user utilizes are in /user/bin then why is fdisk or 
sysinstall not there also. That don't make sense. It time to modernize 
the directory layout keeping all RELEASE binaries out of /usr.
I would think moving the /usr RELEASE binaries by the RELEASE 
development team is a far smaller task then reviewing all 21,500 ports 
for the bad ones that don't target /usr/local/bin and then correcting 
their make files. Before jails this problem was not a problem, But with 
the growing usage of jails this is becoming a major incentive to not use 
jails at all.

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

Re: usage of /usr/bin

[Fbsd1]

Lowell Gilbert wrote:

Fbsd1 fb...@a1poweruser.com writes:


But that is not true. The postfix port populates /usr/bin.


By default, it does not.  You have to enable the Install into /usr and
/etc/postfix configuration option for it to do so.  I don't recommend
that anyone do it without a *really* good reason.  Turn that option back
off and you'll be fine.


Your wrong. I installed the package of postfix and it installed it self 
into /usr/bin with out any help from me.


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

Re: usage of /usr/bin

[Fbsd1]

Jonathan McKeown wrote:

On Wednesday 07 April 2010 11:13:13 Fbsd1 wrote:

Polytropon wrote:

On Wed, 07 Apr 2010 15:24:51 +0800, Fbsd1 fb...@a1poweruser.com wrote:

Why are there RELEASE base files in /usr/bin. I thought /usr was to only
contain binaries installed from ports or packages.

No. The /usr/local subtree (LOCAL) is for local additions (ports
and packages), while things outside this structure usually belong
to the system itself; I'm excluding mounted filesystem and other
things here for a moment.

[snip]

But that is not true. The postfix port populates /usr/bin.


I haven't installed postfix, but is this possibly related to the recently 
(2010-03-22) added option to install postfix into the base?


In which case the commit six days later claims to correct a problem with the 
default (non-base) install.


Jonathan

I installed the package of postfix and it installed is self into 
/usr/bin with out any help from me. Packages are frozen some time before 
the RELEASE is distributed to the public. The change you question would 
have never made it into the RELEASE 8.0 package.


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

Re: usage of /usr/bin

[Fbsd1]

Chuck Swiger wrote:

On Apr 7, 2010, at 4:06 PM, Fbsd1 wrote:

Your wrong. I installed the package of postfix and it installed it self into 
/usr/bin with out any help from me.


Unless you or whoever built the package changed $PREFIX:

% pkg_info -Lx postfix
Information for postfix-2.7.0,1:

Files:
/usr/local/man/man1/postalias.1.gz
/usr/local/man/man1/postcat.1.gz
/usr/local/man/man1/postconf.1.gz
/usr/local/man/man1/postdrop.1.gz
[ ... ]
/usr/local/share/doc/postfix/tlsmgr.8.html
/usr/local/share/doc/postfix/generic.5.html
/usr/local/etc/rc.d/postfix

...every file is under /usr/local.  Perhaps you set INST_BASE option?

[ ] INST_BASE  Install into /usr and /etc/postfix

Regards,



I installed the package of postfix and it installed is self into 
/usr/bin with out any help from me.


This is now I know that. I swapped a empty drive with my live system 
drive. Installed the sysinstall kern developer option to get full 
binaries and sources. After the install I set chflags schg /dir/ and 
/dir/* for these dir. /bin /boot /lib /libexec /sbin /usr/bin 
/usr/include /usr/lib /usr/libexec /usr/sbin. This should have protected 
all those RELEASE base directors and all the files in then. With the dir 
also having schg on, no files should have been able to be added to it. I 
then did a ls -lo /dir  file to save copy of their content. Then I did 
pkg_add -r postfix-current. After which i did another ls -lo /dir  file 
and to my surprise i see all these new files have been added to /usr/bin.


What am I to think? How else would you explain this?

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

Re: USB Powered Speakers

[Fbsd1]

Antonio Olivares wrote:

On 4/8/10, Programmer In Training p...@joseph-a-nagy-jr.us wrote:

I have acquired a pair of Compaq USB /powered/ speakers. On my parents
XP machine they don't seem to cause any problems, but when I hook it up
to listen on my FreeBSD box I have absolutely nothing but problems with
the speakers (even when turned off but still plugged in) interrupting
the normal operation of my keyboard (basically it seems that power is
cut to my keyboard at random). I have a beefy power supply (650W) so I
really shouldn't be having any power distribution issues.

I've tried the speakers in both the on-board USB ports and the USB
expansion card (PCI) with the same results.

Any ideas?


You really need to explain in detail the problem.
Without these new speakers plugged in does wall powered speakers work?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How to make man pages

[Fbsd1]

For the questions list archives:
I wrote an How To  Creating a manpage from scratch.

You can read it here.

http://www.daemonforums.org/showthread.php?t=4602

Thanks to all the people who replied to my post.

Joe

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

Re: installation problem

[Fbsd1]

Александров Иван wrote:
Hellow,my name is Ivan,i have installation problem 
configuration:

intel seleron Dual-core e3300 2.5/800/1mb BOX LGA775 BX80571E3300
ASUS P5KPL-AM SE Soket 775/iG31/DDR II/PCI-Ex16/Video/mAXT
DDR II 1024Mb PC-6400,800MHz Crucial (Micron)
160Gb Hitachi HDS721016LA386(0A39261)8MB SATA-II
Codegen Q3337-A2 ATX 400W
CD-ROM TOSHIBA (don't know 3 years old , HHD)

problem:
In various places errors occur when installing
8.0-RELEASE-i386-disc1.iso
8.0-RELEASE-i386-dvd1.iso.gz
and
FreeBSD-7.3-RELEASE-i386-disc1.iso
everywhere timeout
in 8.0-RELEASE-i386-dvd1.iso.gz for example:
ums0: 3 buttons and [XYZ] coordinates ID=0
acd0: TIMEOUT - READ_BIG retryin (1 retry left )
acd0: TIMEOUT - READ_BIG retryin (0 retries left )
acd0: FAILURE - READ_BIG timed out
cd0: TIMEOUT - READ_BIG retryin (1 retry left )
acd0: TIMEOUT - READ_BIG retryin (0 retries left )
acd0: FAILURE - READ_BIG timed out
cd0: TIMEOUT - READ_BIG retryin (1 retry left )
acd0: TIMEOUT - READ_BIG retryin (0 retries left )
acd0: FAILURE - READ_BIG timed out

I would like to begin the study with nix feeBSD very disappointing
Help please,bootable flash don't work too.
can you help me?
thanks


Make sure the cdrom drive in cabled on the second motherboard ata port 
as master with nothing on the slave nipple. Your sata drive should be on 
the first motherboard port as master and the slave nipple empty.


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

Host firewall and jails

[Fbsd1]

Just where do jails fall in reference to the host firewall?
Do jails see the inbound packets before the host's firewall does?


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

apache Perl CGI programs

[Fbsd1]

I have Perl and apache installed on my system. Do I have to do anything 
additional to get apache to run Perl CGI programs?
Is putting the perl script in the cgi-bin directory at 
/usr/local/www/data all it takes to make things work?


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

ezjail and dmsg -a command

[Fbsd1]

I have a directory tree type of ezjail up and running. When in jail 
console I enter dmesg -a and i get the hosts last boot messages not the 
jails. Why is this dmesg command issued from within the jail have access 
to the host world? Something wrong here!

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

How To create msdosfs on HD?

[Fbsd1]

I have an old IDE 3.5 hard drive with FBSD Release 7.0 on it. I want to 
use it for USB disk space on XP. I bought a 'CD-r king' hard drive to 
USB cable. It will work with 2.5  3.5 IDE drives and sata drives. When 
I plug the USB end of the cable into a FBSD system I can mount the 3.5 
IDE 7.0 HD's da0s1a, da0s1d, da0s1e and da0s1f file systems with no 
problem. But when I plug the same drive into a XP system the USB drive 
shows in system/devices/hard drives as there but windows explorer does 
not assign a drive letter for it. I'm thinking this is because the hard 
drive has UFS format and maybe it I reformat it to fat format xp will 
assign a drive letter to it.


I know mount_msdosfs command is used to mount a HD formated with fat, 
but I could not find a FBSD command to create a msdos file system on a 
hard drive. Native dos fdisk/format is no good because it's not USB 
aware. Is there any FBSD command or port I can use to reformat the UFS 
hard drive with msdosfs?

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

Re: How To create msdosfs on HD?

[Fbsd1]

Rod Person wrote:

On Thu, 29 Apr 2010 09:29:35 -0300, Fbsd1 fb...@a1poweruser.com wrote:
I know mount_msdosfs command is used to mount a HD formated with fat, 
but I could not find a FBSD command to create a msdos file system on a 
hard drive. Native dos fdisk/format is no good because it's not USB 
aware. Is there any FBSD command or port I can use to reformat the UFS 
hard drive with msdosfs?

___


Why can't you format it in XP since you connected it to XP?

Because like I say in the first part of post you snipped out that xp 
does not assign a drive letter to it.

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

Re: How To create msdosfs on HD?

[Fbsd1]

Adam Vande More wrote:

On Thu, Apr 29, 2010 at 6:36 AM, Rod Person rodper...@rodperson.com wrote:


On Thu, 29 Apr 2010 09:29:35 -0300, Fbsd1 fb...@a1poweruser.com wrote:


I know mount_msdosfs command is used to mount a HD formated with fat, but
I could not find a FBSD command to create a msdos file system on a hard
drive. Native dos fdisk/format is no good because it's not USB aware. Is
there any FBSD command or port I can use to reformat the UFS hard drive with
msdosfs?



dd if=/dev/zero of=/dev/da0 bs=512k count=10
fdisk -i /dev/da0
newfs_msdos -F32 /dev/da0s1



Thank you very much.
Thats the answer I was hoping for.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: How To create msdosfs on HD?

[Fbsd1]

Fbsd1 wrote:

On Thu, 29 Apr 2010 09:29:35 -0300, Fbsd1 fb...@a1poweruser.com wrote:

I know mount_msdosfs command is used to mount a HD formated with 
fat, but

I could not find a FBSD command to create a msdos file system on a hard
drive. Native dos fdisk/format is no good because it's not USB 
aware. Is
there any FBSD command or port I can use to reformat the UFS hard 
drive with

msdosfs?



dd if=/dev/zero of=/dev/da0 bs=512k count=10
fdisk -i /dev/da0
newfs_msdos -F32 /dev/da0s1



Thank you very much.
Thats the answer I was hoping for.





For the archives here is a detailed explanation.

Create MS/Windows file system on a Hard Drive so it will be recognized 
on an MS/Windows system.


The goal here is to initialize a hard drive that was previous 
initialized with a non-Microsoft Windows file system, with a single 
active partition populated with Microsoft Windows 32 bit FAT (LBA) file 
system. So this hard drive will be recognized as containing a valid 
MS/Windows file system when used on a Microsoft Windows system.


I have an old IDE 3.5” hard drive with FBSD Release 7.0 on it. I want to 
use it as external USB attached disk on XP. I bought a 'CD-r king' hard 
drive to USB adapter cable. It will work with 2.5”  3.5” IDE drives and 
SATA drives. When I plug the USB end of the cable into a FBSD system I 
can mount the 3.5” IDE 7.0 HD's da0s1a, da0s1d, da0s1e and da0s1f  file 
systems with no problem. But when I plug the same drive into a XP system 
the USB drive shows in “control panel/system/hardware/devices/hard 
drives” as there, but “windows explorer” does not assign a drive letter 
for it so I can not reformat it.


All PC’s running a MS/Windows system inspect sector 0 of the hard drive 
for the partition/slice table to determine the sysid of each 
partition/slice. If the sysid value is 12 then it’s a valid Microsoft 
Windows file system and gets assigned a drive letter in “windows 
explorer”. Any other sysid value means non-Microsoft Windows file system 
and the device is seen in  “control panel/system/hardware/devices/hard 
drives” as there but “windows explorer” does not assign a drive letter 
to it.


There are 2 ways to initialize ((2.5” or 3.5”) (IDE or SATA)) hard 
drives with a valid MS/Windows file system. Using the Microsoft “fdisk” 
program or the FreeBSD “fdisk” program. The Microsoft “fdisk” program 
defaults to sysid =12. The FreeBSD “fdisk” program defaults to sysid = 
165, but has alternate way to assign any sysid value you want.


Microsoft method. Replace the 2.5” hard drive in your laptop with the 
2.5” hard drive containing the FreeBSD system. If 3.5” hard drive then 
open your desktop PC, remove the data cable ribbon and power connection 
from the existing hard drive and attach them to the 3.5” hard drive 
containing the FreeBSD system. Put the Microsoft XP, Vista, or Windows7 
install CD in the cdrom drive and boot. Select fdisk option from the 
install menu to populate the hard drive with official ntfs file system. 
No need to continue with the install after fdisk complete.


FreeBSD method. You need a PC with a running FreeBSD system and USB 
hardware to attach the 2.5” or 3.5” IDE or SATA hard drives with. A USB 
external hard drive housing will work fine for 3.5” IDE and SATA drives. 
For 2.5” IDE or SATA drives you will need a USB adapter cable. The 'CD-r 
king' hard drive to USB cable I purchased works with 2.5”  3.5” IDE 
drives and SATA drives, cost $10 USA. If you have a 3.5” IDE or SATA 
hard drive and FreeBSD is running on a desktop PC, you could open it up 
and add it as a second hard drive on the data ribbon.


Attach the hard drive to the USB equipment and plug into USB port on the 
PC running FreeBSD. Best if you are logged in as “root”. You will see 
the USB console messages as the USB hard drive is connected. In most 
cases the USB drive will be assigned da0 as the device name. The 
following instructions are for initializing the hard drive as a single 
MS/Windows partition occupying the whole hard drive.



 Wipe clean the sector 0 slice table
# dd if=/dev/zero of=/dev/da0 count=2


The following is what you would do if the initialized msdosfs hard drive 
will only be used on a FreeBSD system. The slice table is populated with 
the sysid of 165, which means FreeBSD is using this slice, but the slice 
contains a MSDOS FAT32 file system. The newfs_msdos command is really 
acting like the msdos format command. The larger your hard drive the 
longer this command will take to complete.


#fdisk -BI /dev/da0
#newfs_msdos -F32 /dev/da0s1
This creates the sector 0 slice table and loads the default bios boot 
code and activates a single slice covering the entire disk.



If at this point you un-plugged the USB cable from the FreeBSD system 
and plugged it into a Microsoft Windows PC. The USB drive would be 
un-accessible by “windows explorer” because no drive letter gets 
assigned. That’s because Window’s see this hard drive as a non-windows 
drive. Which

source for sysinstall

[Fbsd1]

How can i just download the source for sysinstall?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

7.2 disc1 bootonly cds not recognized as bootable

[Fbsd1]

Running 7.1 and trying to do clean install of 7.2. Downloaded both disc1 
and bootonly iso files because the 7.2 release announcement says this.


Note: late in the testing cycle it was discovered some machines do not 
recognize


the i386 disc1 as bootable (they just fall through to booting off the 
next boot device).


All affected machines did see the other discs as bootable. If you have a 
machine


with that problem booting off either bootonly or livefs and then 
swapping in disc1


once sysinstall starts should work.

In my case I have the described booting problem with both disc1 and the 
bootonly disk.


Disc1 and bootonly cd are bootable on different computer so know they 
are good.


Dead in the water, Help

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

no pkg for apache13 in 7.2

[Fbsd1]

In 7.1 and previous  pkg_add -r apache  fetched apache13.
Now in release 7.2  pkg_add -r apache  installs apache22.
Looks like someone made apache22 the default pkg and did not
point this out in the release notes or bother to create a
named package for apace13 in the Latest directory.
Is apache13 at end-of-life??
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: no pkg for apache13 in 7.2

[Fbsd1]

Ltcddata wrote:

On Mon, 18 May 2009 20:22:34 +0800
Fbsd1 fb...@a1poweruser.com wrote:


In 7.1 and previous  pkg_add -r apache  fetched apache13.
Now in release 7.2  pkg_add -r apache  installs apache22.
Looks like someone made apache22 the default pkg and did not
point this out in the release notes or bother to create a
named package for apace13 in the Latest directory.
Is apache13 at end-of-life??
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org

using apache13 here on 7.2.. just build it from ports  



Building from port does not address the posted problem.
Can also get pkg from 7.1.


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

Re: Win4BSD 1.1 on 7.1

[Fbsd1]

Polytropon wrote:

On Fri, 22 May 2009 23:53:09 +0200 (CEST), Ronny Mandal 
ronn...@volatile-norway.com wrote:
I'm experiencing problems when attempting to install Win4BSD 1.1. I've 
downloaded the most recent .tbz of W4B, it installs but fails while 
building kqemu.


You downloaded sources manually? Why not use the ports system, or
even install from a precompiled package? This would install any
needed dependencies (kqemu) as well. The ports collection contains
version 1.1.


From the port:


# cd /usr/ports/emulators/win4bsd
# make install clean


From the package:


pkg_add -r win4bsd

It will install run dependencies as well.




Here is the error-msg:

kqemu-freebsd.c: In function 'kqemu_schedule':
kqemu-freebsd.c:211: error: 'sched_lock' undeclared (first use in this 
function)
kqemu-freebsd.c:211: error: (Each undeclared identifier is reported only 
once


I'm not sure, but are you trying to compile Linux sources on
a FreeBSD system?



All sources are installed. Suggestions are very welcome and will be 
appreciated!


Try the port, if you want to compile it yourself, or try pkg_add.
I have to admit that I haven't tried it, so it's a dry advice. :-)






There is no package for win4bsd on the pkg ftp servers for releases 7.0, 
7.1, 7.2, or 8.0.
Looks like the release build team has been missed this one for some time 
now.



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

Re: Win4BSD 1.1 on 7.1

[Fbsd1]

Polytropon wrote:

On Fri, 22 May 2009 23:53:09 +0200 (CEST), Ronny Mandal 
ronn...@volatile-norway.com wrote:
I'm experiencing problems when attempting to install Win4BSD 1.1. I've 
downloaded the most recent .tbz of W4B, it installs but fails while 
building kqemu.


You downloaded sources manually? Why not use the ports system, or
even install from a precompiled package? This would install any
needed dependencies (kqemu) as well. The ports collection contains
version 1.1.


From the port:


# cd /usr/ports/emulators/win4bsd
# make install clean


From the package:


pkg_add -r win4bsd

It will install run dependencies as well.




Here is the error-msg:

kqemu-freebsd.c: In function 'kqemu_schedule':
kqemu-freebsd.c:211: error: 'sched_lock' undeclared (first use in this 
function)
kqemu-freebsd.c:211: error: (Each undeclared identifier is reported only 
once


I'm not sure, but are you trying to compile Linux sources on
a FreeBSD system?



All sources are installed. Suggestions are very welcome and will be 
appreciated!


Try the port, if you want to compile it yourself, or try pkg_add.
I have to admit that I haven't tried it, so it's a dry advice. :-)





The port build of win4bsd will not build on 7.2 because you have first 
to rebuild the freebsd kernel with option SCHED_4BSD. win4bsd-1.1_3 
requires the traditional 4bsd scheduler. Good possibility this is also 
true for 7.0, 7.1 and 8.0


Gave up on testing win4bsd because of performance impact on server from 
using traditional 4bsd scheduler. OMHO this port needs to be updated to 
function using the new scheduler.

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

Software creating karaoke from mp3 files

[Fbsd1]

Been unable to purchase karaoke of rock and roll greats like AC/DC, THE 
ROLLING STONES, THE DOORS, LED ZEPPELIN. Looking for advice on software 
that will allow me to edit out the singing voice tracks from a mp3 file 
and write the resulting music as a avi file so I can have the song words 
show on tv.


If any one has done this type of thing, sure would like to hear about 
how they did it.


Thanks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: pkg_deinstall: delete all packages installed, except for X, Y and Z

[Fbsd1]

Wojciech Puchar wrote:

Hello list.

I am trying to clean up a system with a LOT of cruft. Is there some
argument I could pass to pkg_deinstall that would result in delete
all packages installed, except for X, Y and Z (and obviously their
dependancies)?


just do

pkg_info |cut -f 1 -d   /tmp/pkglist
edit pkglist and delete lines X, Y and Z

do

pkg_delete `cat /tmp/pkglist`
rm /tmp/pkglist

ignore errors about package can't be deleted because X, Y or Z requires 
it. it's exactly what you want.



pkg_delete `cat /tmp/pkglist`  gives error 'no such package `cat 
/tmp/pkglist` installed

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

Re: pkg_deinstall: delete all packages installed, except for X, Y and Z

[Fbsd1]

Wojciech Puchar wrote:
ignore errors about package can't be deleted because X, Y or Z 
requires it. it's exactly what you want.



pkg_delete `cat /tmp/pkglist`  gives error 'no such package `cat 
/tmp/pkglist` installed




for sure you used ' instead of `

  Yet that was the error. I did not know there was another type of 
quote key on the keyboard. The one used in the example is below the Esc key.

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

Re: it is about installing FreeBSD on USB stick

[Fbsd1]

Eric Hsieh wrote:

hello, this is my first time to ask a help from FreeBSD.
I have a question about installing FreeBSD on USB stick.
There are so many informations about how to install FreeBSD on USB
stick from Internet, but I can not find out any information about
follow :
first, if i install FreeBSD on USB stick. Could I operate it on any computer.
if not, how to reach this issue ?
second, if i install FreesBIE on USB stick, i know i can operate it on
any computer.
but i don't know how to store my setting and installed software on USB
stick directly instead of copy my setting to another store device.
thanks, good luck for you.
___





Your statement of any computer is too undefined. The answer to your 
first question as you wrote it is NO. But if we define any computer as
any 386 type of computer then the answer is yes. Note: Not all PC's 
manufactured have option to boot from USB stick or use the 386 type of CPU.


Your second question is wrong. FreesBie has same limitation as Freebsd.
any 386 type of computer with USB stick boot option then the answer is 
yes.


There are other versions of Freebsd for the other CPU types of Pc's. If 
you use one of those other versions for CPU type then your USB stick can 
only run on PC's of the same CPU type.


All of Freebsd run time configuration files are in /etc
/etc will be on your USB stick Freebsd system and will be the ones you 
are modifying.







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

Re: FreeBSD 7.2 o/s on a flash stick

[Fbsd1]

Al Plant wrote:

Aloha Gurus.

All the gogle-ing I did does not give a current status on or how-to on 
installing FreeBSD 7.2 on a flash stick on one slice with the default 
partions.  I want to boot from it on a mini lap top ( no CD ) and use it 
like the hd inside.


I see plenty of how-to's on loading Flash sticks for installing on other 
boxes and using a 2 slice flash to load FreeBSD onto other duplicate 
boxes again.


All I need is to have a FreeBSD  o/s on the stick so I can use it 
instead of the OS on the existing laptop.


I'm sure I saw on this list where somebody did this successfully but I 
cant find it.


Any help is appreciated. Thanks.

~Al Plant - Honolulu, Hawaii -  Phone:  808-284-2740
  + http://hawaiidakine.com + http://freebsdinfo.org +
  + http://aloha50.net   - Supporting - FreeBSD 6.* - 7.* - 8.* +
   email: n...@hdk5.net 
All that's really worth doing is what we do for others.- Lewis Carrol

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




Hi Al

The way i have done this in 7.0 7.1 and 7.2 is to boot off the cd1 
install cd and do a normal install to my 1gb flash stick. A 1gb flash 
stick is to small for the default slice sizes. You will have to manually 
allocate the / /usr /var /swap sizes. I also found it usefully to set 
the boot flag when allocating the whole flash stick. A 2gb or larger 
flash stick allows you to take the auto-allocate option for / /usr /var 
/swap sizes. Keep in mind that your /var log files can fill up you flash 
stick real quick and lock up your system. If your running this flash 
stick 7/24 then rotate them more often deleting the oldest one. It's as 
simple as that.

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

Re: Install from a USB Pen

[Fbsd1]

Mark Wallbank wrote:

OK I know this has probably been done to death by know and I keep
hitting the same problems with the methods I have tried to find on
google and I know I could just sacrifice a laptop and do a build to
create the image or do a net (pxe) install from another NIX serverbut
it does seem to be a bit over the top. Does any body know of an easy
way to create a bootable USB install media for 7.2 using either linux
or vista (or using an option from the install dvd). I have tried some
of the tricks from openBSD and linux to no avail.
Any help appreciated...
Cheers
Mark
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org





If your asking how to put the cd1 install contents onto a usb stick and 
use the sysinstall program to perform the install on the target box then 
check the archive.
It has a post with a script to convert the cd1 install disk to usb 
stick. But the show stopper is the sysinstall program does not have 
option for usb stick as install source. There was a bug report submitted 
2 years ago pointing out this oversight, but as of 7.2 it has not been 
corrected.
If you think the sysinstall program should have install source option 
for usb stick them file your own bug report. The more people who file 
bug reports the more attention this problem will get from the developers.





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

Re: Install from a USB Pen

[Fbsd1]

... or you could just download an official image instead of going to all 
of that trouble. Check the FTP site, there's a memstick.img if you're 
down for using with 8 instead of 7. There are currently three PRs about 
this, and I recently took ownership of them. Filing duplicate bug 
reports doesn't get attention, it's just annoying and it makes trying 
to improve sysinstall that much more difficult because I'll have to 
spend more time closing these duplicates and less time fixing problems. 
There has been an email that stated there is USB install support in 
sysinstall as of 8.0 BETA1, and USB livefs support as of 8.0 BETA2. The 
PRs for USB support in sysinstall will be updated and closed soon. Don't 
open new ones.


You're welcome! :D

-- randi


What are the instructions for using this 8.0 memstick.img?
What raw size memstick is needed?
Is the 8.0 memstick.img the same content as the cd1 disk?


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

Re: Install from a USB Pen

[Fbsd1]

Randi Harper wrote:

On 7/14/09, Fbsd1 fb...@a1poweruser.com wrote:

What are the instructions for using this 8.0 memstick.img?
What raw size memstick is needed?
Is the 8.0 memstick.img the same content as the cd1 disk?


Sigh. Reply-to-all fail. Resending.

It's all in the email about the 8.0 BETA(s). Use dd, a memstick that
 is of equal to or greater size than the memstick.img, and no, it's
 different from disc1. It currently lacks packages, but it does include
 livefs.

 -- randi


The email about 8.0 BETA(s) was not posted to the questions list that is 
why I did not see it.


This is what I tried

 Plugging in the stick auto generated these messages

# /root umass0: vendor 0x0930 USB Flash Memory, class 0/0, rev 
2.00/2.00, addr  2 on uhub1

da0 at umass-sim0 bus 0 target 0 lun 0
da0:  USB Flash Memory 6.50 Removable Direct Access SCSI-0 device
da0: 1.000MB/s transfers
da0: 1905MB (3903487 512 byte sectors: 255H 63S/T 242C)
GEOM_LABEL: Label for provider da0s1 is msdosfs/ço¤¿òÚktñ

 I have to hit enter key to get prompt
 of=da0  or of=da0s1 resulted in same thing, no img on stick

# /usr dd if=8.0-BETA1-i386-memstick.img of=da0 bs=10240 conv=sync
57412+0 records in
57412+0 records out
587898880 bytes transferred in 192.035793 secs (3061403 bytes/sec)

Can not mount with (mount /dev/da0s1 /mnt)
But (mount_msdosfs /dev/da0s1 /mnt) does work but
stick still contains the original data.
Has not been overwritten by the 8.0-BETA1-i386-memstick.img

What is the problem here?



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

Re: Install from a USB Pen

[Fbsd1]

Randi Harper wrote:

On Wed, Jul 15, 2009 at 6:50 PM, Fbsd1 fb...@a1poweruser.com wrote:


Randi Harper wrote:


On 7/14/09, Fbsd1 fb...@a1poweruser.com wrote:


What are the instructions for using this 8.0 memstick.img?
What raw size memstick is needed?
Is the 8.0 memstick.img the same content as the cd1 disk?


Sigh. Reply-to-all fail. Resending.

It's all in the email about the 8.0 BETA(s). Use dd, a memstick that
 is of equal to or greater size than the memstick.img, and no, it's
 different from disc1. It currently lacks packages, but it does include
 livefs.

 -- randi


 The email about 8.0 BETA(s) was not posted to the questions list that is

why I did not see it.

This is what I tried

 Plugging in the stick auto generated these messages

# /root umass0: vendor 0x0930 USB Flash Memory, class 0/0, rev 2.00/2.00,
addr  2 on uhub1
da0 at umass-sim0 bus 0 target 0 lun 0
da0:  USB Flash Memory 6.50 Removable Direct Access SCSI-0 device
da0: 1.000MB/s transfers
da0: 1905MB (3903487 512 byte sectors: 255H 63S/T 242C)
GEOM_LABEL: Label for provider da0s1 is msdosfs/ço¤żňÚktń

 I have to hit enter key to get prompt
 of=da0  or of=da0s1 resulted in same thing, no img on stick

# /usr dd if=8.0-BETA1-i386-memstick.img of=da0 bs=10240 conv=sync
57412+0 records in
57412+0 records out
587898880 bytes transferred in 192.035793 secs (3061403 bytes/sec)

Can not mount with (mount /dev/da0s1 /mnt)
But (mount_msdosfs /dev/da0s1 /mnt) does work but
stick still contains the original data.
Has not been overwritten by the 8.0-BETA1-i386-memstick.img

What is the problem here?



You're writing to a file called da0 inside /usr instead of /dev/da0.

-- randi
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org




dd if=8.0-BETA1-i386-memstick.img of=/dev/da0   worked

I used my laptop to boot from the usb memstick. The 8.0 sysinstall 
started right up but it has problems. In this test i am booting off a 
2gb usb memstick containing the 8.0-BETA1-i386-memstick.img and 
installing on a second 8gb memstick.


While trying to do a [STANDARD/KERNEL DEVELOPER] distribution 
sysinstall issues error msg saying package index not on current media 
them gos on to tell me that docproj, manpages, proflibs, dict, info, 
sbace, ssys and srce are not on the media.


I take this to mean that they are missing from the 
8.0-BETA1-i386-memstick.img.


So I tried to install again this time doing a minimal selection. This 
when through to completion but the resulting memstick was not bootable.


I'll try this test again when BETA2 is released.


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

Re: Install from a USB Pen

[Fbsd1]

Fbsd1 wrote:




dd if=8.0-BETA1-i386-memstick.img of=/dev/da0   worked

I used my laptop to boot from the usb memstick. The 8.0 sysinstall 
started right up but it has problems. In this test i am booting off a 
2gb usb memstick containing the 8.0-BETA1-i386-memstick.img and 
installing on a second 8gb memstick.


While trying to do a [STANDARD/KERNEL DEVELOPER] distribution sysinstall 
issues error msg saying package index not on current media them gos on 
to tell me that docproj, manpages, proflibs, dict, info, sbace, ssys and 
srce are not on the media.


I take this to mean that they are missing from the 
8.0-BETA1-i386-memstick.img.


So I tried to install again this time doing a minimal selection. This 
when through to completion but the resulting memstick was not bootable.


I'll try this test again when BETA2 is released.




OK used the 8.0-BETA2-i386-memstick.img.

Took 3 times longer to download the 8.0-BETA1-i386-memstick.img that to 
download the 8.0-BETA1-i386-disc1.iso. I suggest you look into another 
method of creating the memstick.img so it downloads faster. dd does no 
compression of the data.


dd the memstick.img to my 2gb memstick ok. It booted ok.

Using a 8gb memstick as the target to install 8.0 on took 2 times longer 
than disc1 cd installing to same 8gb memstick.


Selected the [STANDARD/KERNEL DEVELOPER] distribution, It completed 
successfully, but the new 8.0 8gb memstick was not recognized as bootable.


Here is a script i have used in the past to convert the disc1.iso to 
bootable memstick. Maybe its better to add this script to the place 
where 8.0-BETA1-i386-disc1.iso is located in place of the memstick.img.

That way the 3 times larger memstick.img is not needed any more.



#!/bin/sh
#Purpose = Use to transfer the FreeBSD install cd1 to
#  a bootable 1GB USB flash drive so it can be used to install 
from.

#  First fetch the FreeBSD 7.1-RELEASE-i386-disc1.iso to your
#  hard drive /usr. Then execute this script from the command line
# fbsd2usb /usr/7.1-RELEASE-i386-disc1.iso /usr/7.1-RELEASE-i386-disc1.img
# Change system bios to boot from USB-dd and away you go.

# NOTE: This script has to be run from root and your 1GB USB flash drive
#   has to be plugged in before running this script.

# On the command line enter fbsd2usb iso-path img-path

# You can set some variables here. Edit them to fit your needs.

# Set serial variable to 0 if you don't want serial console at all,
# 1 if you want comconsole and 2 if you want comconsole and vidconsole
serial=0

set -u

if [ $# -lt 2 ]; then
echo Usage: $0 source-iso-path output-img-path
exit 1
fi

isoimage=$1; shift
imgoutfile=$1; shift

# Temp  directory to be used later
#export tmpdir=$(mktemp -d -t fbsdmount)
export tmpdir=$(mktemp -d /usr/fbsdmount)

export isodev=$(mdconfig -a -t vnode -f ${isoimage})

ISOSIZE=$(du -k ${isoimage} | awk '{print $1}')
SECTS=$((($ISOSIZE + ($ISOSIZE/5))*4))
#SECTS=$((($ISOSIZE + ($ISOSIZE/5))*2))

echo  
echo ### Initializing image File started ###
echo ### This will take about 4 minutes ###
date
dd if=/dev/zero of=${imgoutfile} count=${SECTS}
echo ### Initializing image File completed ###
date

echo  
ls -l ${imgoutfile}
export imgdev=$(mdconfig -a -t vnode -f ${imgoutfile})

bsdlabel -w -B ${imgdev}
newfs -O1 /dev/${imgdev}a

mkdir -p ${tmpdir}/iso ${tmpdir}/img

mount -t cd9660 /dev/${isodev} ${tmpdir}/iso
mount /dev/${imgdev}a ${tmpdir}/img

echo  
echo ### Started Copying files to the image now ###
echo ### This will take about 15 minutes ###
date

( cd ${tmpdir}/iso  find . -print -depth | cpio -dump ${tmpdir}/img )

echo ### Completed Copying files to the image ###
date

if [ ${serial} -eq 2 ]; then
echo -D  ${tmpdir}/img/boot.config
echo 'console=comconsole, vidconsole'  
${tmpdir}/img/boot/loader.conf

elif [ ${serial} -eq 1 ]; then
echo -h  ${tmpdir}/img/boot.config
echo 'console=comconsole'  ${tmpdir}/img/boot/loader.conf
fi

echo  
echo ### Started writing image to flash drive now ###
echo ### This will take about 30 minutes ###
date
dd if=${imgoutfile} of=/dev/da0 bs=1m
echo ### Completed writing image to flash drive at ###
date

cleanup() {
umount ${tmpdir}/iso
mdconfig -d -u ${isodev}
umount ${tmpdir}/img
mdconfig -d -u ${imgdev}
rm -rf ${tmpdir}
}

cleanup

ls -lh ${imgoutfile}

echo ### Script finished ###




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

USB Flash Memory stick not bootable

[Fbsd1]

Have problem with being able to boot off an new 8GB USB Flash Memory 
stick. When I load the 8.0 disc1.iso to an 2GB USB Flash Memory stick it 
will boot fine. But when I do the same thing to the new 8GB USB Flash 
Memory stick it’s not recognized as bootable. I can access the installed 
partitions manually by mounting then on the 7.2 system. So I know the 
8GB stick has been loaded correctly. I am doing this on a 7.2 release.


Below are the console messages that get displayed when I plug in each of 
the USB Flash Memory stick. You can see a great difference between the 
first set of messages for the 8GB stick versus the 2GB stick that 
follows. I want to boot off the 8GB stick just like I do with the 2GB 
stick.


What is going on here? They should be handled the same way.


Brand new 8GB Kingston DataTraveler 120 purchased 7/16/09

 umass0: Kingston DataTraveler 120, class 0/0, rev 2.00/1.00, addr 2 
on uhub1

 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
 (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
 (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have 
changed

 (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
 da0 at umass-sim0 bus 0 target 0 lun 0
 da0: Kingston DataTraveler 120 1.00 Removable Direct Access SCSI-2 
device

 da0: 1.000MB/s transfers
 da0: 7643MB (15654848 512 byte sectors: 255H 63S/T 974C)
 GEOM_LABEL: Label for provider da0a is ufsid/4a615a2cc673eb3d.


# 3 year old 2GB Kingston DataTraveler
umass1: vendor 0x0930 USB Flash Memory, class 0/0, rev 2.00/2.00,
 addr 3 on uhub1
da1 at umass-sim1 bus 1 target 0 lun 0
da1:  USB Flash Memory 6.50 Removable Direct Access SCSI-0 device
da1: 1.000MB/s transfers



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

Re: Install from a USB Pen

[Fbsd1]

Randi Harper wrote:

On Fri, Jul 17, 2009 at 8:41 PM, Fbsd1 fb...@a1poweruser.com wrote:


Took 3 times longer to download the 8.0-BETA1-i386-memstick.img that to
download the 8.0-BETA1-i386-disc1.iso. I suggest you look into another
method of creating the memstick.img so it downloads faster. dd does no
compression of the data.



-rw-r--r--1 110  1002 346845184 Jul 16 02:04
8.0-BETA2-i386-disc1.iso
-rw-r--r--1 110  1002 917391360 Jul 16 02:00
8.0-BETA2-i386-memstick.img

Note the filesize. This may be the reason it took 3 times longer. Just a
guess.



Using a 8gb memstick as the target to install 8.0 on took 2 times longer
than disc1 cd installing to same 8gb memstick.



Might have something to do with the amount of data being written. Again,
just a guess. Are you sure it wasn't 3 times longer?



Selected the [STANDARD/KERNEL DEVELOPER] distribution, It completed
successfully, but the new 8.0 8gb memstick was not recognized as bootable.



I don't know why that's the case as I am unable to reproduce this problem,
but if the memstick.img is 1GB, why are you using an 8GB memstick instead
of the 2GB?



Here is a script i have used in the past to convert the disc1.iso to
bootable memstick. Maybe its better to add this script to the place where
8.0-BETA1-i386-disc1.iso is located in place of the memstick.img.
That way the 3 times larger memstick.img is not needed any more.



No. If you took a look at the contents of the memstick, you'd realize it's
not just a copy of disc1. It also includes livefs. This is probably why the
memstick.img is so much bigger. :D

-- randi
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org




Instead of combining disc1 and livefs into a single memstick.img would't 
it be better to make 2 memstick images. One of disc1 and one of livefs. 
This matches the standard all ready in place.



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

Are all USB Flash Memory sticks bootable?

[Fbsd1]

Have problem with being able to boot off an new 8GB USB Flash Memory 
stick. When I load the 8.0 disc1.iso to an 2GB USB Flash Memory stick it 
will boot fine. But when I do the same thing to a new 8GB USB Flash 
Memory stick it’s not recognized as bootable. I can access the installed 
partitions manually by mounting then on the 7.2 system. So I know the 
8GB stick has been loaded correctly. I am doing this on a 7.2 release.


Below are the console messages that get displayed when I plug in each of 
the USB Flash Memory stick. You can see a great difference between the 
first set of messages for the 8GB stick versus the 2GB stick that 
follows. I want to boot off the 8GB stick just like I do with the 2GB stick.


What is going on here? They should be handled the same way.


Brand new 8GB Kingston DataTraveler 120 purchased 7/16/09

 umass0: Kingston DataTraveler 120, class 0/0, rev 2.00/1.00, addr 2 
on uhub1

 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
 (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
 (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have 
changed

 (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
 da0 at umass-sim0 bus 0 target 0 lun 0
 da0: Kingston DataTraveler 120 1.00 Removable Direct Access SCSI-2 
device

 da0: 1.000MB/s transfers
 da0: 7643MB (15654848 512 byte sectors: 255H 63S/T 974C)
 GEOM_LABEL: Label for provider da0a is ufsid/4a615a2cc673eb3d.


# 3 year old 2GB Kingston DataTraveler
umass1: vendor 0x0930 USB Flash Memory, class 0/0, rev 2.00/2.00,
 addr 3 on uhub1
da1 at umass-sim1 bus 1 target 0 lun 0
da1:  USB Flash Memory 6.50 Removable Direct Access SCSI-0 device
da1: 1.000MB/s transfers



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

Re: Are all USB Flash Memory sticks bootable?

[Fbsd1]

Randi Harper wrote:

On Thu, Jul 23, 2009 at 6:27 AM, Sergio de Almeida Lenzi 
lenzi.ser...@gmail.com wrote:


Em Qui, 2009-07-23 às 12:52 +0800, Fbsd1 escreveu:
Hello

I found here that some bios does have problem with booting
from partitions they do not know

So first I initialize the USB stick with
==
dd count=100 if=/dev/zero of=/dev/da0
fdisk -BI da0
sade
==
than edit the partitions...
ls /dev/da* should show da0s1 da0s2
than
disklabel -wB da0s1
disklabel -wB da0s2
newfs -L Freebsd7 da0s1a
newfs -L Freebsd8 da0s2a
boot0cfg -vB da0

mount the partitions, copy the files
boot from the usb...  it will show you the F1 F2 chooser

for me, this worked


Sergio



Just to clarify, are you trying to boot from a USB stick that you've
installed FreeBSD onto, or is this a USB stick that you've dd'ed the
memstick.img to?

You should NOT use disklabel on a usb stick that you're dd'ing the
memstick.img to.

-- randi
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org




Here I will try to re-state the problem.

I have two USB Flash Memory sticks. One is a 2GB stick and the other is 
a 8GB stick. I can install Freebsd 8.0 from disc1 cd onto the 2GB stick 
or dd the memstick.img to the 2GB stick and in both cases it will boot 
just fine.


When I repeat the same procedure using the 8GB stick it will not boot. 
AS a test I have fdisk'ed the 8GB stick under MS/XP and loaded files to 
it ok.


The only thing I see different between the 2 memsticks is in the 
messages 7.2 issues when the sticks get plugged in.


Take note of the revision level differences between them.
2.00/1.00 versus  rev 2.00/2.00

The only other guess I have is that the usb code in 7.2 has
am error in it.

Brand new 8GB Kingston DataTraveler 120 purchased 7/16/09

 umass0: Kingston DataTraveler 120, class 0/0, rev 2.00/1.00, addr 2 
on uhub1

 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
 (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
 (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0
 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have 
changed

 (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
 da0 at umass-sim0 bus 0 target 0 lun 0
 da0: Kingston DataTraveler 120 1.00 Removable Direct Access SCSI-2 
device

 da0: 1.000MB/s transfers
 da0: 7643MB (15654848 512 byte sectors: 255H 63S/T 974C)
 GEOM_LABEL: Label for provider da0a is ufsid/4a615a2cc673eb3d.


# 3 year old 2GB Kingston DataTraveler
umass1: vendor 0x0930 USB Flash Memory, class 0/0, rev 2.00/2.00,
 addr 3 on uhub1
da1 at umass-sim1 bus 1 target 0 lun 0
da1:  USB Flash Memory 6.50 Removable Direct Access SCSI-0 device
da1: 1.000MB/s transfers




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

Burncd 700MB rw/cd

[FBSD1]

Been using burncd since Freebsd 4.0 with 650MB rw/cd's just fine. My local
computer store had a sale on 700MB rw/cd's and I picked up a few. Burncd
gives msg (Failure - read_big illegal request) on these 700MB rw/cd's. The
Freebsd 7.0 man burncd has no info on large sized rw/cd's?

Does burncd need a programming update to handle these newer larger sized
rw/cd's?

What other (built in with the release) program can be used to burn 700 MB
rw/cd's?

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

ssh

[FBSD1]

On FreeBSD 7.0 how do I tell ssh to allow login from root and also to listen
on port 9922 instead of port 22?

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

RE: switching discs during install

[FBSD1]

All this talk about changing the order of the ports on the install cd's is
just so much hot air because cd's install media belong to the legacy world.
They are fast becoming obsolete just like floppy drives are. Can't even buy
a computer these days with a floppy drive and still FreeBSD distributes
floppy install images. How absurd is that?

FreeBSD needs to come of age in the 21st century and be changed to install
using USB memory flash stick technology. Just a little tweaking of the
sysinstall program to add USB stick as an option for source of install
source would do it.

Here is a little script to populate a USB flash stick with the cd1.iso that
you may find interesting. This way you can combine the cd1  cd2 install
cd's to a 4GB USB stick and install the system and all the ports you want
without switching any install media. You could even use a USB flash stick as
the target to install FreeBSD on giving you an mobile FreeBSD system you can
plug into any computer and boot from.


#!/bin/sh
#Purpose = Use to transfer the FreeBSD install cd1 to
#  a bootable 1GB USB flash drive so it can be used to install from.
#  First fetch the FreeBSD 6.2-RELEASE-i386-disc1.iso to your
#  hard drive /usr. Then execute this script from the command line
# fbsd2usb /usr/6.2-RELEASE-i386-disc1.iso /usr/6.2-RELEASE-i386-disc1.img
# Change system bios to boot from USB-dd and away you go.

# NOTE: This script has to be run from root and your 1GB USB flash drive
#   has to be plugged in before running this script.

# On the command line enter fbsd2usb iso-path img-path

# You can set some variables here. Edit them to fit your needs.

# Set serial variable to 0 if you don't want serial console at all,
# 1 if you want comconsole and 2 if you want comconsole and vidconsole
serial=0

set -u

if [ $# -lt 2 ]; then
echo Usage: $0 source-iso-path output-img-path
exit 1
fi

isoimage=$1; shift
imgoutfile=$1; shift

# Temp  directory to be used later
#export tmpdir=$(mktemp -d -t fbsdmount)
export tmpdir=$(mktemp -d /usr/fbsdmount)

export isodev=$(mdconfig -a -t vnode -f ${isoimage})

ISOSIZE=$(du -k ${isoimage} | awk '{print $1}')
SECTS=$((($ISOSIZE + ($ISOSIZE/5))*4))
#SECTS=$((($ISOSIZE + ($ISOSIZE/5))*2))

echo  
echo ### Initializing image File started ###
echo ### This will take about 4 minutes ###
date
dd if=/dev/zero of=${imgoutfile} count=${SECTS}
echo ### Initializing image File completed ###
date

echo  
ls -l ${imgoutfile}
export imgdev=$(mdconfig -a -t vnode -f ${imgoutfile})

bsdlabel -w -B ${imgdev}
newfs -O1 /dev/${imgdev}a

mkdir -p ${tmpdir}/iso ${tmpdir}/img

mount -t cd9660 /dev/${isodev} ${tmpdir}/iso
mount /dev/${imgdev}a ${tmpdir}/img

echo  
echo ### Started Copying files to the image now ###
echo ### This will take about 10 minutes ###
date

( cd ${tmpdir}/iso  find . -print -depth | cpio -dump ${tmpdir}/img )

echo ### Completed Copying files to the image ###
date

if [ ${serial} -eq 2 ]; then
echo -D  ${tmpdir}/img/boot.config
echo 'console=comconsole, vidconsole' 
${tmpdir}/img/boot/loader.conf
elif [ ${serial} -eq 1 ]; then
echo -h  ${tmpdir}/img/boot.config
echo 'console=comconsole'  ${tmpdir}/img/boot/loader.conf
fi

echo  
echo ### Started writing image to flash drive now ###
echo ### This will take about 20 minutes ###
date
dd if=${imgoutfile} of=/dev/da0 bs=1m
echo ### Completed writing image to flash drive at ###
date

cleanup() {
umount ${tmpdir}/iso
mdconfig -d -u ${isodev}
umount ${tmpdir}/img
mdconfig -d -u ${imgdev}
rm -rf ${tmpdir}
}

cleanup

ls -lh ${imgoutfile}

echo ### Script finished ###

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

Exiting Gnome

[FBSD1]

Started Gnome for first time. Can not figure how to exit (stop) gnome and
return to the FreeBSD command line. The System/logout option just hangs.

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

Is the freesbie project dead????????

[FBSD1]

I can't reach http://www.freesbie.org/ to official site for the project.

Has this project disbanded? 

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

RE: My unqualified host name

[FBSD1]

Simple solution is to add
hostname=nyana.com
to rc.conf  then everything is happy

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dánielisz László
Sent: Wednesday, September 24, 2008 2:40 PM
To: freebsd-questions@freebsd.org
Subject: Re: My unqualified host name

True, the system boots without any problem but its annoying to wait for that
failure.



- Original Message 
From: [EMAIL PROTECTED] [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: freebsd-questions@freebsd.org
Sent: Wednesday, September 24, 2008 7:05:16 AM
Subject: Re: My unqualified host name

  nyana sm-mta[803]: My unqualified host name (nyana) unknown;
  sleeping for retry

 ... sendmail expects your machine to have working DNS and for
 the machine to have a valid FQDN.  Either set that up, or add
 sendmail_enable=NONE to /etc/rc.conf to disable sendmail ...

There is another approach, which is to ignore the message.  After
something like 3 repetitions, at something like a minute apart,
it will give up on qualifying its name.  Everything seems to work
just fine thereafter until the next boot, when the entire sequence
repeats.

This leads to the question of how to get sendmail -- or whatever
-- into the state where it will eventually land after the 3-miunte
delay, without the delay and the messages.  It seems as if this
ought not be all that difficult.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]




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

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

RE: nat and firewall

[FBSD1]

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of fire jotawski
Sent: Wednesday, September 24, 2008 12:13 PM
To: freebsd-questions@freebsd.org
Subject: nat and firewall

hi sirs,

i am confused now that what is the difference between nat and firewall_nat
in /etc/rc file

natd_enable=YES
firewall_nat_enable=YES

just one question per asking.  there will be another more questions about
this but for this moment only this one first.

thanks in advance for any helps and hints

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


natd_enable=YES  This statement in rc.conf enables ipfw nated function.
firewall_nat_enable=YES  This is an invalid statement. No such thing as
you have here.
FreeBSD has 3 different built in firewall for you to chose from. IPFW,
Ipfilter, and PF
Review /etc/defaults/rc.conf for their statements.
It would do you good to read the firewall section of the FreeBSD Handbook
for a complete explanation of the 3 firewalls and the differences between
them.
In my option the PF firewall has the easiest to use rule set and built in
table functions for automated black listing attacking IP address. Its major
weakness is it has very poorly designed logging function that results in
very cumbersome usage.
IPFilter comes next. It has easy logging and rules usage. It lacks the auto
black listing table building of PF. These two firewalls were ported to
FreeBSD from other Unix flavored operating systems. Both have teams
supporting and maintaining them.
The final firewall is IPFW that is the first firewall included in FreeBSD
many years ago and was developed by the FreeBSD team. IPFW also lacks the
auto black listing table building of PF, and its nated rules are much harder
to get working using all stateful rules. IPFW had a major coding overhaul a
few years back but the inhered design flaw of how nated rules are handled
was not touched. Grape vine says IPFW nated code is a messed up can of worms
and no one wants to touch it.
I have used all 3 firewalls at one time or another to learn about them. I
found IPFilter to be the easiest to use and get logging out put in standard
format like all the other FreeBSD logs are.  But you should ready the
handbook and decide for your self what best satisfies your firewall needs.



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

Xorg/kde startup errors

[FBSD1]

I am new user to xorg/kde.
Installed xorg and kde using port system. Followed instructions in handbook
for Freebsd 7.0
The following is the startx log from when I enter startx command. Have no
idea what is wrong since I expected the xorg and kde port to be completely
functional. Kde seems to run ok except for all the repeating warnings about
missing mimetypes and the invalid Window parameter error for every screen I
navigate through using KDE.

Any help is welcomed



Script started on Tue Oct  7 19:13:25 2008
# /root startx
xauth:  creating new authority file /root/.serverauth.1236


X.Org X Server 1.4.0
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 7.0-RELEASE i386
Current Operating System: FreeBSD 7.0-RELEASE-p4 FreeBSD 7.0-RELEASE-p4 #0:
Tue Sep  2 19:32:35 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
Build Date: 13 February 2008  05:50:12PM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Tue Oct  7 19:13:31 2008
(==) Using config file: /etc/X11/xorg.conf
(II) Module i2c already built-in
(II) Module ddc already built-in
(II) Module ramdac already built-in
Warning: kbuildsycoca is unable to register with DCOP.
kbuildsycoca running...
kbuildsycoca running...
Reusing existing ksycoca
kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop'
specifies undefined mimetype/servicetype 'application/x-tbz2'
kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop'
specifies undefined mimetype/servicetype 'application/zip'
kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop'
specifies undefined mimetype/servicetype 'application/x-7z'
kbuildsycoca: WARNING: 'ark_part.desktop' specifies undefined
mimetype/servicetype 'application/x-tbz2'
kbuildsycoca: WARNING: 'ark_part.desktop' specifies undefined
mimetype/servicetype 'application/x-7z'
kbuildsycoca: WARNING: 'karm_part.desktop' specifies undefined
mimetype/servicetype 'text/english'
kbuildsycoca: WARNING: 'karm_part.desktop' specifies undefined
mimetype/servicetype 'text/x-c'
kbuildsycoca: WARNING: 'karm_part.desktop' specifies undefined
mimetype/servicetype 'text/x-c++'
kbuildsycoca: WARNING:
'/usr/local/share/applications/kde/kpovmodeler.desktop' specifies undefined
mimetype/servicetype 'KPovModeler/Document'
kbuildsycoca: WARNING: 'kfile_ooo.desktop' specifies undefined
mimetype/servicetype 'application/vnd.sun.xml.writer.global'
kbuildsycoca: WARNING: 'kfile_ooo.desktop' specifies undefined
mimetype/servicetype 'application/vnd.sun.xml.writer.math'
kbuildsycoca: WARNING: 'klinkstatus_part.desktop' specifies undefined
mimetype/servicetype 'text/english'
kbuildsycoca: WARNING: 'klinkstatus_part.desktop' specifies undefined
mimetype/servicetype 'text/x-c'
kbuildsycoca: WARNING: 'klinkstatus_part.desktop' specifies undefined
mimetype/servicetype 'text/x-c++'
kbuildsycoca: WARNING: 'kchartpart.desktop' specifies undefined
mimetype/servicetype 'application/vnd.oasis.opendocument.chart-template'
kbuildsycoca: WARNING: '/usr/local/share/applications/firefox.desktop'
specifies undefined mimetype/servicetype 'text/mml'
kbuildsycoca: WARNING: '/usr/local/share/applications/kde/kvoctrain.desktop'
specifies undefined mimetype/servicetype 'application/x-kvoctrain'
kbuildsycoca: WARNING: '/usr/local/share/applications/kde/kvoctrain.desktop'
specifies undefined mimetype/servicetype 'text/x-kvtml'
kbuildsycoca: WARNING: '.hidden/krita_magick.desktop' specifies undefined
mimetype/servicetype 'image/x-xcf'
kbuildsycoca: WARNING: 'kcertpart.desktop' specifies undefined
mimetype/servicetype 'application/binary-certificate'
kbuildsycoca: WARNING: '/usr/local/share/applications/kde/kmid.desktop'
specifies undefined mimetype/servicetype 'audio/midi'
kbuildsycoca: WARNING: 'kformulapart.desktop' specifies undefined
mimetype/servicetype 'application/vnd.oasis.opendocument.formula-template'
kbuildsycoca: WARNING: 'kxsldbg_part.desktop' specifies undefined
mimetype/servicetype 'text/english'
kbuildsycoca: WARNING: 'kxsldbg_part.desktop' specifies undefined
mimetype/servicetype 'text/x-c'
kbuildsycoca: WARNING: 'kxsldbg_part.desktop' specifies undefined
mimetype/servicetype 'text/x-c++'
kbuildsycoca: WARNING: 'knotify.desktop' specifies undefined
mimetype/servicetype 'KNotify'
kbuildsycoca: WARNING: 'ksvgplugin.desktop' specifies undefined
mimetype/servicetype 'image/svg'
kbuildsycoca: WARNING: '/usr/local/share/applications/kde/kexi.desktop'
specifies undefined mimetype/servicetype 'application/x-kexiproject-sqlite'
startkde: Starting up...
kdeinit: Shutting down running client.
kbuildsycoca running...
X Error: BadValue (integer parameter out of 

RE: cannot install from existing UFS thumb drive with sysinstall

[FBSD1]

There is a outstanding PR on sysinstall from usb flash drive which is now
over a year old. The sysinstall install program needs to be updated to use
usb drives as the source of the install media. You could always edit the
sysinstall program source code and make a patch to allow usb sysinstall
media.  Other than that you are S.O.L.

I use this script to build my bootable 1GB USB flash drive

#!/bin/sh
#Purpose = Use to transfer the FreeBSD install cd1 to
#  a bootable 1GB USB flash drive so it can be used to install from.
#  First fetch the FreeBSD 6.2-RELEASE-i386-disc1.iso to your
#  hard drive /usr. Then execute this script from the command line
# fbsd2usb /usr/6.2-RELEASE-i386-disc1.iso /usr/6.2-RELEASE-i386-disc1.img
# Change system bios to boot from USB-dd and away you go.

# NOTE: This script has to be run from root and your 1GB USB flash drive
#   has to be plugged in before running this script.

# On the command line enter fbsd2usb iso-path img-path

# You can set some variables here. Edit them to fit your needs.

# Set serial variable to 0 if you don't want serial console at all,
# 1 if you want comconsole and 2 if you want comconsole and vidconsole
serial=0

set -u

if [ $# -lt 2 ]; then
echo Usage: $0 source-iso-path output-img-path
exit 1
fi

isoimage=$1; shift
imgoutfile=$1; shift

# Temp  directory to be used later
#export tmpdir=$(mktemp -d -t fbsdmount)
export tmpdir=$(mktemp -d /usr/fbsdmount)

export isodev=$(mdconfig -a -t vnode -f ${isoimage})

ISOSIZE=$(du -k ${isoimage} | awk '{print $1}')
SECTS=$((($ISOSIZE + ($ISOSIZE/5))*4))
#SECTS=$((($ISOSIZE + ($ISOSIZE/5))*2))

echo  
echo ### Initializing image File started ###
echo ### This will take about 4 minutes ###
date
dd if=/dev/zero of=${imgoutfile} count=${SECTS}
echo ### Initializing image File completed ###
date

echo  
ls -l ${imgoutfile}
export imgdev=$(mdconfig -a -t vnode -f ${imgoutfile})

bsdlabel -w -B ${imgdev}
newfs -O1 /dev/${imgdev}a

mkdir -p ${tmpdir}/iso ${tmpdir}/img

mount -t cd9660 /dev/${isodev} ${tmpdir}/iso
mount /dev/${imgdev}a ${tmpdir}/img

echo  
echo ### Started Copying files to the image now ###
echo ### This will take about 15 minutes ###
date

( cd ${tmpdir}/iso  find . -print -depth | cpio -dump ${tmpdir}/img )

echo ### Completed Copying files to the image ###
date

if [ ${serial} -eq 2 ]; then
echo -D  ${tmpdir}/img/boot.config
echo 'console=comconsole, vidconsole' 
${tmpdir}/img/boot/loader.conf
elif [ ${serial} -eq 1 ]; then
echo -h  ${tmpdir}/img/boot.config
echo 'console=comconsole'  ${tmpdir}/img/boot/loader.conf
fi

echo  
echo ### Started writing image to flash drive now ###
echo ### This will take about 30 minutes ###
date
dd if=${imgoutfile} of=/dev/da0 bs=1m
echo ### Completed writing image to flash drive at ###
date

cleanup() {
umount ${tmpdir}/iso
mdconfig -d -u ${isodev}
umount ${tmpdir}/img
mdconfig -d -u ${imgdev}
rm -rf ${tmpdir}
}

cleanup

ls -lh ${imgoutfile}

echo ### Script finished ###



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Carl Voth
Sent: Friday, October 10, 2008 6:52 PM
To: freebsd-questions@freebsd.org
Subject: Re: cannot install from existing UFS thumb drive with sysinstall

Is there no one out there that can help?

I've dug into NFS a little more and that does not appear to support
mounting a local filesystem under sysinstall.

In the following thread, Richard Tobin makes an assertion that suggests
that I might be able to mount my thumb drive's existing UFS partition in
the disk labelling step.

http://unix.derkeiler.com/Newsgroups/comp.unix.bsd.freebsd.misc/2004-10/0920
.html
[ http://tinyurl.com/3mknq7 ]

The first problem I ran into was that there is no way to add a second
drive (ie. target drive is SATA hard disk, thumb drive is install drive)
to the disk labelling step. The only way that that can be achieved is by
first adding it to the fdisk partitioning step. I'm willing to believe
that *maybe* there's no risk to my thumb drive in rewriting it's disk
label if I'm very careful not to newfs it. But nothing about the fdisk
partition editor gives me a sense that it will hold off of rewriting my
thumb drive's slice table even though I'm not trying to change anything.
It just seems perverse to have to reslice and relabel just to mount an
existing filesystem. If the only way one can mount a local filesystem in
sysinstall is using the disk label editor, can someone explain to me the
actual consequences and risks of this procedure? I did not proceed to
Write or Commit in this little experiment yet because of the unknown risks.

I have to say that I cannot believe how horribly unfriendly sysinstall
is for anyone wanting to use a USB thumb drive as an install medium. In
fact, it's looking totally unusable.

Clearly sysinstall is utilizing 'mount' functionality for it's own
purposes. Surely there's some way for me to access it too?!?

Carl   

Re: Making bootable USB keys

[Fbsd1]

Samuel Martín Moro wrote:

Hello

I'm having some troubles, trying to create bootable USB keys.
I found (freebsd-hackers ML archives) a script, supposed to create the
bootable image from my iso file.
But, it still don't boot... (I may do it wrong)

In details:
-We distribute a FreeBSD (4.7, 5.4, 6.2 and 7.2) custom server.
-We burn our install CD (and, in a few, our USB sticks) on a Ferdora 9
(sorry...)
-USB sticks must contain a FAT32 partition (we'ld like to provide doc for
windows users)

Well, my english isn't so great... so I'll post my code (more
understandable)



clip 

I have same problem with getting a usb stick to boot. After much testing 
with different sticks and PC combinations have come to this conclusion.


When usb hardware first can out they were created for usb 1.0 standard 
and at that same period PC's where using software drivers for usb 
support and the PC's bio's boot selection did not include option to boot 
from usb disk. As usb devices became more popular PC manufactures 
started adding USB firmware to their motherboards for usb 2.0 standard. 
From my research into usb 2.0 it only supports data recording and does 
not support booting function. About 2007 usb 2.2 standard came out and 
it supports an usb memory stick as bootable. In 2008 some manufactures 
of motherboards added usb 2.2 standard to their motherboards and bio's 
selection to boot from memory stick.


To be bootable the first file on the the stick has to be the boot image. 
 Haveing a ms fat partition first on the stick will never work unless 
you fill it with an bootable ms/windows or ms/dos system or the same 
kind of setup found on the cdrom1 release cd.


Only usb 2.2 memory sticks are bootable on newer PC's that have usb 2.2 
firmware on their motherboards and matching Bio's with selection for 
booting from usb 2.2 memory sticks. Please note that bio's booting 
selection for booting from USB disk is different than booting selection 
for booting from usb memory stick. I have posted many posts on this list 
about this subject and have not received any posts contrary to the above 
statement.


The pending 8.0 release has a complete rewrite of the USB code and a new 
  stick.img is being generated as part of the release install 
distribution's. I can dd the 8.0-stick.img file to an 2.0 stick and it 
never boots, but do the same thing to a 2.2 stick and it boots on all 3 
of my PC manufactured since June 2008.


Final Conclusion: Booting from a USB memory stick successfully is 
totally dependent on using new start-of-the-art hardware.








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

Re: Making bootable USB keys

[Fbsd1]

Samuel Martín Moro wrote:

In fact, we provide the servers and the keys.
So we're sure everything will work.

And also, our install CD is already able to create this kind of USB stick.


I am just curious.
What manufacture / model and GB size of USB stick are you using?
When you plug the USB stick into a FreeBSD system what version of the 
USB standard is used in the firmware on the USB stick (1.0, 2.0 or 2.2)?
The firmware USB version standard used by the stick is displayed when 
the stick is first plugged into a Freebsd release 7.2

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

8.0 release serial mouse not working

[Fbsd1]

Been using the same serial mouse since release 7.0 through 7.1 and 7.2.
Just installed release 8.0 and the rc.conf statements
dont work any longer.


# serial port radioshack 2 button mouse
moused_port=/dev/cuad0
moused_type=intellimouse
moused_enable=YES

Nothing has changed on the box hardware.
Mouse worked in 7.2 but not in 8.0

I even tried sysinstall/configure/mouse to test other options and none 
worked.


Has serial mouse support been dropped in release 8.0 and not removed 
from sysinstall?

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

Re: 8.0 release serial mouse not working

[Fbsd1]

Polytropon wrote:

On Thu, 26 Nov 2009 11:43:17 +0800, Fbsd1 fb...@a1poweruser.com wrote:

Been using the same serial mouse since release 7.0 through 7.1 and 7.2.
Just installed release 8.0 and the rc.conf statements
dont work any longer.


# serial port radioshack 2 button mouse
moused_port=/dev/cuad0
moused_type=intellimouse
moused_enable=YES

Nothing has changed on the box hardware.
Mouse worked in 7.2 but not in 8.0

I even tried sysinstall/configure/mouse to test other options and none 
worked.


Has serial mouse support been dropped in release 8.0 and not removed 
from sysinstall?


I'm not sure about the moused_port, it's some time ago that
I've used a serial mouse, but I had

moused_enable=YES
moused_port=/dev/cuaa0
moused_type=mousesystems
moused_flags=-r 300 -a 2.0

in /etc/rc.conf - cuaa0 instead of cuad0.

For some checking, why not use

moused -f -i all -p /dev/cuad0

and

moused -f -d -t auto -p /dev/cuad0

for some checking?




I checked /dev and there are no cuaa* or cuad*
In 7.2 used the sysinstall/configur/mouse menu and it was the one that 
crated the moused_port=/dev/cuad0 rc.conf statment as showen in first 
post.


/dev does have cuau0  cuau1 for uucp dialer. could this be the names of 
the serial ports in 8.0?


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

Re: MUA questions

[Fbsd1]

Rem Roberti wrote:
I just installed FreeBSD 7.2 on a new box and am having trouble getting 
either fetchmail or getmail to talk to the ISP. Is this a question that 
can can be answered here, or is there another more appropriate forum. I 
thought it best to ask that question first before going any further.


Thanks...

Rem
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org



I have fetchmail working on 7.2. describe your problem in detail and 
post you control statements.

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

Re: 8.0 release serial mouse not working

[Fbsd1]

Polytropon wrote:

On Thu, 26 Nov 2009 14:06:56 +0800, Fbsd1 fb...@a1poweruser.com wrote:

I checked /dev and there are no cuaa* or cuad*


Confirmed, 8.0-RC1 with GENERIC kernel (my toyaround machine).

In 7.2 used the sysinstall/configur/mouse menu and it was the one that 
crated the moused_port=/dev/cuad0 rc.conf statment as showen in first 
post.


That should have been the correct setting. On version 7, I
have /dev/cuad0, /dev/cuad0.init and /dev/cuad0.lock. On
version 8, there's /dev/cuau0, /dev/cuau0.init and
/dev/cuau0.lock instead.

Maybe loading a kernel module is required to have the
serial ports available again?



/dev does have cuau0  cuau1 for uucp dialer. could this be the names of 
the serial ports in 8.0?


It seems that they don't work for the mouse because they're
something different.

I think there's another problem rising: Assume you want to
have a serial dialin line (e. g. for a serial terminal), then
you would have something like

ttyd0 /usr/libexec/getty std.115200 vt320 on secure

in /etc/ttys. The question would be: If /dev/ttyd0 does not
exist anymore, how to make this work again?





From the 8.0 release notes is the following
http://www.freebsd.org/releases/8.0R/relnotes-detailed.html

[amd64, i386] The uart(4) is now the default driver for serial port 
devices in favor of the sio(4) driver. Note that the device nodes have 
been renamed with /dev/cuauN and /dev/ttyuN.


tested these rc.conf statements

moused_port=/dev/cuau0
moused_type=intellimouse
moused_enable=YES

serial mouse works again

This means sysinstall mouse config needs to be changed to reflect the 
new dev names.

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

Re: 8.0 release serial mouse not working

[Fbsd1]

Polytropon wrote:

On Thu, 26 Nov 2009 14:57:32 +0800, Fbsd1 fb...@a1poweruser.com wrote:

 From the 8.0 release notes is the following
http://www.freebsd.org/releases/8.0R/relnotes-detailed.html

[amd64, i386] The uart(4) is now the default driver for serial port 
devices in favor of the sio(4) driver. Note that the device nodes have 
been renamed with /dev/cuauN and /dev/ttyuN.


tested these rc.conf statements

moused_port=/dev/cuau0
moused_type=intellimouse
moused_enable=YES

serial mouse works again


Can confirm.



This means sysinstall mouse config needs to be changed to reflect the 
new dev names.


That's correct. The handbook sec. 2.10.10 and fig. 2-44 would
need an update, too.

http://www.freebsd.org/doc/en/books/handbook/install-post.html





submitted PR
http://www.freebsd.org/cgi/query-pr.cgi?pr=140887
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

8.0 release php5 port not working

[Fbsd1]

Have a clean install of 8.0 and trying to do cvs make install of port 
php5 just to turn on apache module. The php5 make install is complaining 
that autoconf262, pkg-config and libxml2 as non-existent -- dependency 
list incomplete. I installed these as packages and they show up in 
pkg_info.
Only thing i can think of is the php5 make file is looking for the port 
make files of these so call non-existent ports to check that dependent 
is there when it should be checking the pkg-db to check if dependent is 
installed.


Question is how do I force the port make install of php5 to accept the 
package versions of the dependents so the compile will start?

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

8.0 MYSQL50 denying access to user root no password

[Fbsd1]

For many releases of Freebsd going back to 4.3 I have all ways used the 
default mysql user root localhost with no password which has been the 
default.

With 8.0/mysql-server-5.0.86 I am denied access now.
The mysql manual still says the normal install defaults to allowing
access to user root with no password are in effect.

After a fresh clean install of mysql
Tried  mysqladmin -u root drop test   to delete the test db.
Received this msg
connect to srver at localhost failed
access denied for user 'r...@localost (using password: no)
This in not suppose to happen.

Is anyone else having this problem?
Has the package for mysql50-server been changed to force securing user 
root with a password?

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

Re: 8.0 MYSQL50 denying access to user root no password

[Fbsd1]

Tim Judd wrote:

On 11/29/09, Fbsd1 fb...@a1poweruser.com wrote:

For many releases of Freebsd going back to 4.3 I have all ways used the
default mysql user root localhost with no password which has been the
default.
With 8.0/mysql-server-5.0.86 I am denied access now.
The mysql manual still says the normal install defaults to allowing
access to user root with no password are in effect.

After a fresh clean install of mysql
Tried  mysqladmin -u root drop test   to delete the test db.
Received this msg
connect to srver at localhost failed
access denied for user 'r...@localost (using password: no)
This in not suppose to happen.



Two issues, mysqladmin tries to connect to the mysql server -- i see
in your message above it can't connect
if it can't connect, how can it authorize?


Read the post again. says access denied not connection refused.



second, the undocumented mysql_install_db must be run to install the
default database.  But if you run this as root, you should change
ownership of everything in /var/db/mysql to allow the mysql server
access to the files.


mysql_install_db is documented in the mysql manual. After re-reading the
section about using mysql_install_db many times I finally saw my 
problem. mysql_install_db has to be run direct from the root command 
line. I was doing script capture.console.msg.rpt and them running 
another script which had the mysql_install_db command buried in it. The 
mysql manual says mysql_install_db will hose up the user account table
locking out all access. I rm -rf /var/db/mysql to delete the hosed up 
mysql user db and then ran mysql_install_db from the root command line 
and the default root/nopassword worked again.


Thanks for your pointer as to where to look.



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

Re: tty problem after upgrade to 8.0

[Fbsd1]

Jay Hall wrote:

Ladies and Gentlemen,

I completed the upgrade to FreeBSD 8.0 this afternoon and have an error 
plaguing me that I cannot solve.


When the system is booted, I am receiving the following error.

Dec  5 20:43:30  getty[902]: open /dev/ttyd0: No such file or directory

However, when I run ps -ax | grep ttyd0, I see the following entry.

  902  ??  I  0:00.00 /usr/libexec/getty std.9600 ttyd0

I have a modem connected to cuau0 for dial-in purposes.  The /etc/ttys 
file contains the following entry to allow for dial-in access.


# The 'dialup' keyword identifies dialin lines to login, fingerd etc.
ttyd0   /usr/libexec/getty std.9600   dialup  on

Any suggestions would be greatly appreciated.

Thanks,


Jay


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




this will point you in the correct direction
http://www.freebsd.org/cgi/query-pr.cgi?pr=140918


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

what ports to open in firewall for bitlord

[Fbsd1]

Want to allow the bitlord progran to pass through my firewall. Does 
anyone know the port numbers it uses for out bound and inbound packets.


Thanks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

ipfilter nat redirect udp packets

[Fbsd1]

Have this nat rule
rdr rl0 0.0.0.0/0 port 6355 - 10.0.10.3 port 6355

I can see in the log that tcp packets are being redirected but udp 
packets are not. Can not find any verbiage in man 5 0r 8 ipnat that 
states rdr rule only matches on tcp packets. I thought tcp/udp packets 
should be redirected?  Can anyone clarify this?

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

is this booting info correct?

[Fbsd1]

Users with Microsoft/Windows knowledge of how a hard drive is configured
may have a terminology issue with FreeBSD. Microsoft/Windows and FreeBSD
use the word partition to mean different (but related) things.

FreeBSD and Microsoft/Windows have primary-partitions, but they call
them different things. FreeBSD calls the Microsoft/Windows
primary-partition a slice.

The number of hard drive primary-partitions/slices is determined by the
motherboard BIOS (Basic input output system), not the operating system.
Standard motherboard BIOS limits hard-drives to 4 main divisions

Each of those are called primary-partitions in Microsoft/Windows
terminology and slices in FreeBSD terminology.

Each primary-partition/slice can be sub-divided into smaller chunks. In
Microsoft/Windows, they are called extended-partitions. They are
implemented very differently and are not compatible with FreeBSD. In
FreeBSD the sub-divisions are called partitions.

Each one of the 4 max primary-partitions/slices can be made bootable.
The first physical track of the allocated space of each
primary-partition/slice has an initial sector (512 byte block) that is
called the boot sector. If it contains boot up code the motherboard BIOS
considers it to be bootable.

Each physical hard drive in the PC has it's own MBR (Master Boot
Record). The MBR is located in sector-0 of the first physical track on
the hard drive. The standard MBR in Microsoft/Windows and FreeBSD
defaults to booting the first primary-partition/slice allocated on the
first hard drive cabled to the PC.

There are MBR booting programs that you can load into the MBR on the
first physical cabled hard drive to scan for other bootable
primary-partitions/slices on this hard drive and any other hard drives
cabled to the PC. It displays a menu giving you the option to choose
which one you want to boot from. This gives you the ability to have more
that one operating system installed on your PC at one time.








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

ipfilter nat redirect udp packets

[Fbsd1]

Have this nat rule
rdr rl0 0.0.0.0/0 port 6355 - 10.0.10.3 port 6355

I can see in the log that tcp packets are being redirected but udp
packets are not. Can not find any verbiage in man 5 0r 8 ipnat that
states rdr rule only matches on tcp packets. I thought tcp/udp packets
should be redirected?  Can anyone clarify this?

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

Re: Addition to BSDstats

[Fbsd1]

Steve Bertrand wrote:

Marc, et-al,

I wasn't originally going to post this to the list, but I thought that
it would be useful to do so in order to try to solicit feedback.

There's a suggestion that I have for the server-side of bsdstats. I
would find it very useful if the server could track the % of the
reporting connections that come in over IPv6, and include that on the
website front page.

Of course, this would require that rpt.bsdstats.org reside on a reliable
IPv6 network, and code changes to the server-side software. (if the code
is Perl, I'll gladly take a look at it ;)

I'm not interested in the actual addresses of the sending hosts, just
whether the address contains a '.' or ':'.

Cheers,

Steve




BSDSTATS is dead. Don't waste your time.

I am a retired American who is now living in the Philippines. All during 
RELEASE 7.0, 7.1, 7.2, and now 8.0 I have been running the bsdstats port 
on my single system. Yesterday I checked the http://bsdstats.org website 
by country and to my great surprise there are no Freebsd systems listed 
in the Philippines. Also the previous months reports are no longer shown 
on the website and the port stats don't show at all. This is not the 
results talked about on this list when the bsdstats project was trying 
to get Freebsd participation 3 years ago.


The bsdstats website has been un-supported, un-updated for over 2 years 
 and nobody noticed until I  showed up in a country with out any 
Freebsd counts, but knowing I was reports regularly.


What good is participation if there are no real-time results.
I removed bsdstats from my system and the port should be removed from 
the ports system.
I also emailed Marc G. Fournier scra...@hub.org the author and never 
received a reply. That is the best sign that bsdstats is dead.


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

Re: Addition to BSDstats

[Fbsd1]

Marc G. Fournier wrote:

On Tue, 4 May 2010, Marc G. Fournier wrote:

Don't worry about it, found and fixed that bug ... it had to do with 
trying to masquarade behind haproxy, so it looked like all systems were 
coming in from Panama if they were running the newest code ... which 
means alot of ppl out there were running *old* code ...


Basically, by setting up haproxy to load balance, all IPs hitting the 
backend were, as mentioned before, masquaraded ... but, of course, that 
means that when Geo::IP trying to determine country of origin, it always 
reports for the country of origin of the haproxy IP (Panama) ...


I've fixed this ... still not recording IP, but at least the PHP script 
determing country basis it on the proper IP, not the haproxy IP ...


No changes required on the client side, as things will normalize over 
the course of the next month as ppl report in ...


If anyone on FreeBSD wishes to 'force an update':

  /usr/local/etc/periodic/monthly/300.statistics -nodelay

will push it through ...





Just did pkg_add -r bsdstats followed by
/usr/local/etc/periodic/monthly/300.statistics -nodelay

Still don't see any Freebsd systems listed for the Philippines on the 
website.


What is YOUR definition of REAL-TIME.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

BSDstats website displaying data incorrectly

[Fbsd1]

Why does this page show PCBSD has count of 387
http://www.bsdstats.org/bt/home.html?os=

And this page shows PCBSD has count of 1307
http://www.bsdstats.org/bt/home.html?os=PC-BSD

Why is this? I would think both should show the same value, or you 
better add explanation to the web page why the count is different.



And that little selection box on the home page should have some 
explanation of its function. Just sticking it there on the right side of 
the page above the titles hoping someone will fall into it is not user 
friendly.


What is going on with the release stats? What are you showing there?
Is that just for Freebsd? If so then the count is incorrect. This should 
be showing the count for each release under each operating system. IE. 
what release are in use for freebsd, netbsd, openbsd ect.


Website also needs explanation of the time frame being reported. Are the 
values shows as of the the first day of the current month? In general 
the website does not explain much of anything about what is being shown. 
 Put a lot more text describing the overall process and the reporting 
cycle. Also think some kind of operating system monthly growth chart 
over time is needed. Say going back 3 years to current.


The current website is way to passive in the way things are worded. Try 
to inspire people to show their loyalty, allegiance, and devotion by 
running the bsdstats client to anonymously report their usage to the 
benefit of everyone. Developers donate large amounts of their personal 
free time working on the operating systems, the least the users can do 
is fulfill their obligation to demonstrate their gratitude to the 
developers by running bsdstats. Emphasize the reporting is anonymously. 
Website needs to promote it self more. Get on the home page of all the 
different BSD systems. Try to become a default part of the BSD systems 
basic release. Like PCbsd does. Not option to go get it and turn it on, 
but all ready there with option to turn off if desired. This is only 
self promotion of the individual operating systems and should be 
something they should be interested in doing.



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

Re: Accessing file from windows or to windows

[Fbsd1]

Jean-Paul Natola wrote:

Hi all,

I have a file I need in my bsd box, would it be easier, or is it possible, to mount an 
NTFS share , or should I try to map a directory from the windows box.


TIA,

I have 


Xp
Win7
Win2003 
Win2008 
Freebsd 6.4


thanx   





Sounds like all your PCs are on a private LAN and this file you want 
access to will only be accessed from the LAN. I have the same setup and 
exchange files between Windows PCs and Freebsd using FTP. I enable the 
builtin FTP server in /etc/inetd.conf. Close FTP's ports to the public 
internet in the firewall. Then run a free shareware FTP client on the 
windows PC or just use the windows internet browser to target the 
Freebsd ftp server. The shareware FTP client method lets me exchange 
both ways, (move a file from win to fbsd and fbsd to win) The windows 
internet browser method is one direction only, (from fbsd to win). I set 
the FTP server up as anonymous so all LAN PCs can download and upload to 
each other using the FTP server as a post and forward service.

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

Re: Addition to BSDstats

[Fbsd1]

Marc G. Fournier wrote:

On Thu, 6 May 2010, Robert Huff wrote:



 The problem with not including bsdstats in sysinstall or some
 other means of bringing it to peoples attention is that it gets
 forgotten and loses its effectiveness. Maybe it could go in the 

  monthly subscription list reminder.





I think everyone agrees that bsdstats needs more visibility right from 
the virgin install. Since its not appropriate to include bsdstats in the 
sysinstall program. How about getting the RELEASE team to change the 
content of the default logon message of the day /etc/motd, to advocacy 
installing the bsdstats package. What do you think about this idea?

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

port pkg-plist

[Fbsd1]

In a port I am creating I have some files that are not in the /usr/local 
directory tree. There in /var/log  /var/db. What is the correct format 
of the statement in ports pkg-plist file to have these files deleted 
when the port is deleted with pkg_delete command.

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

Re: port pkg-plist

[Fbsd1]

Yuri Pankov wrote:

On Mon, May 10, 2010 at 07:46:09AM +0800, Fbsd1 wrote:

In a port I am creating I have some files that are not in the
/usr/local directory tree. There in /var/log  /var/db. What is the
correct format of the statement in ports pkg-plist file to have
these files deleted when the port is deleted with pkg_delete
command.



@cwd /var
db/dbfile
log/logfile

HTH,
Yuri



Thanks that worked. Have another question.
During the install of the port it adds a enable=YES statement to 
/etc/rc.conf. It there some pre-canned way to auto remove that statement 
when the port is deleted with pkg_delete command?


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

Re: port pkg-plist

[Fbsd1]

Yuri Pankov wrote:

On Mon, May 10, 2010 at 08:19:35AM +0800, Fbsd1 wrote:

Yuri Pankov wrote:

On Mon, May 10, 2010 at 07:46:09AM +0800, Fbsd1 wrote:

In a port I am creating I have some files that are not in the
/usr/local directory tree. There in /var/log  /var/db. What is the
correct format of the statement in ports pkg-plist file to have
these files deleted when the port is deleted with pkg_delete
command.


@cwd /var
db/dbfile
log/logfile

HTH,
Yuri



Thanks that worked. Have another question.
During the install of the port it adds a enable=YES statement to
/etc/rc.conf. It there some pre-canned way to auto remove that
statement when the port is deleted with pkg_delete command?


You shouldn't directly modify rc.conf to enable some service, put
instructions on how to enable it in pkg-message instead.

Having said that, check @unexec command, which is run on package
deinstallation.

Yuri


Where do I find doc on this @unexec command?

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

Re: port pkg-plist

[Fbsd1]

Yuri Pankov wrote:

On Mon, May 10, 2010 at 08:32:26AM +0800, Fbsd1 wrote:

Yuri Pankov wrote:

On Mon, May 10, 2010 at 08:19:35AM +0800, Fbsd1 wrote:

Yuri Pankov wrote:

On Mon, May 10, 2010 at 07:46:09AM +0800, Fbsd1 wrote:

In a port I am creating I have some files that are not in the
/usr/local directory tree. There in /var/log  /var/db. What is the
correct format of the statement in ports pkg-plist file to have
these files deleted when the port is deleted with pkg_delete
command.


@cwd /var
db/dbfile
log/logfile

HTH,
Yuri



Thanks that worked. Have another question.
During the install of the port it adds a enable=YES statement to
/etc/rc.conf. It there some pre-canned way to auto remove that
statement when the port is deleted with pkg_delete command?

You shouldn't directly modify rc.conf to enable some service, put
instructions on how to enable it in pkg-message instead.

Having said that, check @unexec command, which is run on package
deinstallation.

Yuri


Where do I find doc on this @unexec command?


All these commands are documented in pkg_create(1).



Thanks I read that. It will launch what I want to do at deinstall time.
But I still need code to parse through a config file looking for a match 
to the desired literal and then delete that line from the config file 
and save it. I dont know how to do that in a .sh script. I need a sample 
doing that using the @unexec command and then I will be able to tweak it 
to my needs.

Can you help me out?

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

how to find literal in file and them delete that line

[Fbsd1]

I want to search every line in the specified file for a literal and if 
found then delete that line from the file and save the file all from 
within a sh type of shell script.


Does anyone have a example they would share with me?

Thanks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: how to find literal in file and them delete that line

[Fbsd1]

Alberto Mijares wrote:

On Sun, May 9, 2010 at 11:08 PM, Fbsd1 fb...@a1poweruser.com wrote:

I want to search every line in the specified file for a literal and if found
then delete that line from the file and save the file all from within a sh
type of shell script.



man(1) sed

Regards


That makes no sense to me.
need example

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

Re: how to find literal in file and them delete that line

[Fbsd1]

Sahil Tandon wrote:

On Mon, 10 May 2010, Fbsd1 wrote:


Alberto Mijares wrote:

On Sun, May 9, 2010 at 11:08 PM, Fbsd1 fb...@a1poweruser.com wrote:

I want to search every line in the specified file for a literal and if found
then delete that line from the file and save the file all from within a sh
type of shell script.

man(1) sed


That makes no sense to me.
need example


What makes no sense?  The sed(1) man page?  Which section in particular
is confusing?  And please, explain the rationale for making your port
automatically edit /etc/rc.conf.


editing /etc/rc.conf was just given as a example for the post.
Yes the whole man sed reads like Greek. For a neophyte programmer I can 
not even begin to comprehend what its saying. That man page needs 
examples of use. You have forgotten that those man pages are for 
reference for people who all ready know how to use it. Its not intended 
for novices. So yes it's useless to me.

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

Re: how to find literal in file and them delete that line

[Fbsd1]

b. f. wrote:

Alberto Mijares wrote:

snip


It would make sense if you read the sed(1) and re_format(7) manpages.
They may be a pain at first, but they are used often and can make your
life a lot easier.  There are also a lot of tutorial on the web, with
many useful examples, e.g.:

http://sed.sourceforge.net/grabbag/

He is suggesting that, rather than using sh(1), you should use sed(1),
which is typically used for this sort of task, and is also part of the
base system, in some fashion like, for example:

sed -e '/literal/d' file

If you insist on doing this with sh(1), which will probably be less
efficient, then you can cobble something together with a 'case'
statement, or parameter expansion with substring processing.  See the
sh(1) manpage.

I hope that you are not intending to use this for a FreeBSD Port in
the context of your earlier message.  As someone else has already told
you, ports should _not_ be automatically editing configuration files
like rc.conf.  Instead they should just indicate what should be added
by the user or administrator in a pkg-message. Although you are free
to do whatever you want on your own system, if you submit a port that
attempts to tamper with such files to FreeBSD Ports, it is likely that
that part of your submission will be rejected.

Thank you for your kind in-sight. Using sh was again just comments to 
help explain what I needed help with. A list reader replied offline with 
examples and now I have what I needed to proceed.

Thanks to all who replied.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

how to force end-of-line in man page source

[Fbsd1]

I don't like the way some lines in the man page have the last word in 
the sentence broken in 2 and hyphenated. Is there some escape code I can 
put at the end of the line in the source code to suppress this?

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