Re: Downloads

2007-03-23 Thread Jerry McAllister
On Thu, Mar 22, 2007 at 06:09:26PM -0700, Jim Priovolos wrote:

 Thanks Jerry. If I double click on the files and allow Easy CD Creator 
 to use it's defaults it works. It made bootable CD's. Easy CD Creator 
 wants to use disk-at-once.

Unfortunately, I have found that different burner software utiliities
use different terminology or the same terminology for different things.
So, it can get confusing.

 
 New question: Windows says I have 45g free but FreeBSD only finds 7meg.

Are you looking at the same thing?

What place is Windows looking at and what place is FreeBSD looking at?
Normally, Windows cannot see FreeBSD disk slices and does not
report them.   So, I am suspecting it is looking at its own space
and not the FreeBSD space.   How did you create the FreeBSD space
on the disk?

jerry

 
 And now I have a boot manager but nothing else.
 
 Any help will be appreciated.
 
 Thanks,
 Jim
 
 - Original Message 
 From: Jerry McAllister [EMAIL PROTECTED]
 To: Jim Priovolos [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Sent: Thursday, March 22, 2007 10:44:07 AM
 Subject: Re: Downloads
 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Downloads

2007-03-23 Thread Jerry McAllister
, you might want to make two new Primary
Partitions.  (remember, you can have up to 4).   Make one rather small
one, maybe a couple of GB or so, right next to the MS NTFS slice and
and make it a FAT32 type.  Then put FreeBSD in the one after that.  It
would make the extra one be slice 2 if no vendor slice and 3 if there
is a vendor diagnostic slice.  FreeBSD would then be in slice 3 if no
vendor slice or 4 if there is a vendor slice.   What this little 
extra slice becomes is a space where both MS and FreeBSD can read and
write and means you can use it to shuffle files back and forth.

OK. Fourth, to check this out and just see what is on that disk,
boot up the disc1 CD and when you get the big menu, choose to
run the fixit.When you get the prompt for the fixit, you will be
in a fairly complete, (but still somewhat limited) version of FreeBSD.
Figure out what your drive name is - probably either ad0 or da0 (run
dmesg and pick through the output looking for the disk identifier - 
don't forget you can do scroll-lock and page up in the console)  and
then run fdisk on the drive with no other parameters,  eg.   fdisk ad0

It will print out the status of the four slices on the disk - how
much space is reserved for them, if any, and the type of the slice
and if it is bootable.   It might also make some blathering whines
about geometry.   Ignore those.That fdisk command will give us
the necessary information to understand what is really available
and what is not.   Then you can go from there.

jerry



 
 Thanks again,
 Jim
 
 - Original Message 
 From: Jerry McAllister [EMAIL PROTECTED]
 To: Jim Priovolos [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Sent: Friday, March 23, 2007 3:14:48 PM
 Subject: Re: Downloads
 
 
 On Thu, Mar 22, 2007 at 06:09:26PM -0700, Jim Priovolos wrote:
 
  Thanks Jerry. If I double click on the files and allow Easy CD Creator 
  to use it's defaults it works. It made bootable CD's. Easy CD Creator 
  wants to use disk-at-once.
 
 Unfortunately, I have found that different burner software utiliities
 use different terminology or the same terminology for different things.
 So, it can get confusing.
 
  
  New question: Windows says I have 45g free but FreeBSD only finds 7meg.
 
 Are you looking at the same thing?
 
 What place is Windows looking at and what place is FreeBSD looking at?
 Normally, Windows cannot see FreeBSD disk slices and does not
 report them.   So, I am suspecting it is looking at its own space
 and not the FreeBSD space.   How did you create the FreeBSD space
 on the disk?
 
 jerry
 
  
  And now I have a boot manager but nothing else.
  
  Any help will be appreciated.
  
  Thanks,
  Jim
  
  - Original Message 
  From: Jerry McAllister [EMAIL PROTECTED]
  To: Jim Priovolos [EMAIL PROTECTED]
  Cc: [EMAIL PROTECTED]
  Sent: Thursday, March 22, 2007 10:44:07 AM
  Subject: Re: Downloads
 
 
 
  
 
 Now that's room service!  Choose from over 150,000 hotels
 in 45,000 destinations on Yahoo! Travel to find your fit.
 http://farechase.yahoo.com/promo-generic-14795097
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Downloads

2007-03-23 Thread Garrett Cooper

Jerry McAllister wrote:


That still, unfortunately does not tell me the whole story.  The reason
is that there are still some places where the word partition is misused
(used unconsistently with the rest of FreeBSD).   In FreeBSD the primary
division of the disk is called a slice.Slices are then subdivided
in to partitions in FreeBSD parlance.   
The hierarchy of terminology goes like this:


 -drive: ad0 (for IDE family including SATA)  da0 (for SCSI family) 
 would designate the first drive.  The second would be

 either ad1 or da1.
 ---slice:   ad0s1..ad0s4 - Up to four slices numbered from 1-4.
 MS is typically installed in slice 1 or 2 (depending if
 the vendor sticks a diagnostic/recovery slice on first.
 Dell likes to do that and I think IBM Lenovo does)
 -partition: ad0s1a..ad0s1h.   Up to 8 partitions per slice but
 partition c is reserved to identify the whole slice
 partition is used for root and traditionally reserved
 for that, though it can be used otherwise on a non-boot
 disk.   partition b is used for swap and is traditionally
 reserved for that.


Hmm I got educated. After doing a bit of research it appears that what I 
once knew as partitions and slices were backwards:


http://www.onlamp.com/pub/a/bsd/2002/06/27/Big_Scary_Daemons.html

The above link contains as much information as Jerry provided, and 
possibly some extra info. I only briefly touched the article by in seems 
pretty complete.


So, what you are supposed to be looking for is a slice in which to 
install FreeBSD.  It may be that you are seeing the word partition where 
it should say slice or it may be that you are seeing partition correctly

used, but you are looking in the wrong place.


Yes, and as I discovered FreeBSD slices are MS(/Linux?) partitions :).

snip


If the MS slice is an NTFS type, then those free utilities can not
handle it and you will have to go get something.   The one I have
successfully used is called 'Partitin Magic' and it tends to run
about $70 give or take, from most retailers, mail order or walkin.
I got mine at Best Buy.   Partition Magic will also handle the FAT
and FAT32 type MS Primary Partitions.


There's also another free utility available on Knoppix I believe that 
resizes partitions. I highly suggest backing up your data before doing 
anything, because although NTFS is marked stable for writing, I question 
whether or not the penguin might run off with your data if something bad 
happens..


In either case, you shrink the MS slice (Primary Partition) enough to 
make room for what you want.  Then you create a slice (Primary Partition)

in the newly made free space.   It needs to be a Primary Partition
and not an Extended Partition.  Partition Magic whines about that and
warns you that you might not be able to boot MS.   But it will do it
and it works just fine.In Partition Magic terminology, create that
new Primary Partition as an 'unknown' type.   The FreeBSD installer
will modify the type during install.


Sidenote: If you do use partition magic after installing Unix, don't let 
it fix your disk. It'll muck up your bootloading scheme.



Just a side note:   FreeBSD can read and write FAT and FAT32.  It can
read, but cannot write NTFS (at the current time).  If you have enough 
room to spare on the disk, you might want to make two new Primary

Partitions.  (remember, you can have up to 4).   Make one rather small
one, maybe a couple of GB or so, right next to the MS NTFS slice and
and make it a FAT32 type.  Then put FreeBSD in the one after that.  It
would make the extra one be slice 2 if no vendor slice and 3 if there
is a vendor diagnostic slice.  FreeBSD would then be in slice 3 if no
vendor slice or 4 if there is a vendor slice.   What this little 
extra slice becomes is a space where both MS and FreeBSD can read and

write and means you can use it to shuffle files back and forth.


Windows can also read (and in some cases) write to Reiserfs, and can 
write to ext2 partitions (after you install some utilities for 
interfacing with the filesystems). Freebsd can read/write with the 
previously mentioned filesystems (albeit with some extra functionality 
built into the kernel). Reiser and ext(n) are both commonly used in the 
linux realm as filesystems of choice. ext(n) doesn't have write based 
journal support, which means that you can lose data if you unproperly 
unmount the filesystems / shut down the machine. Reiser doesn't support 
writing yet either because it's strictly a journaling based filesystem.



OK. Fourth, to check this out and just see what is on that disk,
boot up the disc1 CD and when you get the big menu, choose to
run the fixit.When you get the prompt for the fixit, you will be
in a fairly complete, (but still somewhat limited) version of FreeBSD.
Figure out what your drive 

Re: Downloads

2007-03-22 Thread Jerry McAllister
On Wed, Mar 21, 2007 at 04:57:27PM -0700, Jim Priovolos wrote:

 Hi, I've downloaded the 6.2 files. When I burned a CD with the boot file it 
 didn't make my laptop boot off it after powering up with it in the CD drive.
 
 The *disk1 file burnt to a CD gave the same results.
 
 I tried the *disk1 file using ftp through a browser and also command line 
 ftp set to binary.
 
 I checked the boot order and CD is first. If I put a Windows boot CD in 
 there it will boot off of it.

The most popular problem is to burn the CD incorrectly.
The disc1 file (the one you need for installation) is already an ISO - 
 a burnable image.  It must be burned directly to the CD as that image 
and not converted in any way.   The terminology in different burners varies.   
Some call this burning directly as data and some use data to mean something 
they will convert in to a burnable image.   So, check your particular CD
burning software and make sure what you are doing is just a straight burn.

If that ain't it, the next thing to do is go back over your BIOS again.

jerry

 
 Any ideas?
 
 I've got a Compaq Presario 2500 laptop with XP on it now.
 
 Thanks for the help in advance,
 Jim P.
 
 ___
 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: Downloads

2007-03-22 Thread youshi10

On Wed, 21 Mar 2007, Ray wrote:


On Wednesday 21 March 2007 5:57 pm, Jim Priovolos wrote:

Hi, I've downloaded the 6.2 files. When I burned a CD with the boot file it
didn't make my laptop boot off it after powering up with it in the CD
drive.

The *disk1 file burnt to a CD gave the same results.

I tried the *disk1 file using ftp through a browser and also command line
ftp set to binary.

I checked the boot order and CD is first. If I put a Windows boot CD in
there it will boot off of it.

Any ideas?

I've got a Compaq Presario 2500 laptop with XP on it now.

Hi Jim,
the first question is how did you burn the *disk1 file? You have to burn it as
a disk image, not just a data cd. when you put the *disk one into your
machine when windows is running, do you see just one file on it, or many? If
you are using windows to burn the cd, (windows is good for something ;))
you'll probably have to use a separate burning program like nero and choose
disk image. (I'm just getting started here myself, so if your burning under
something besides windows, ask here again for a how to)
Ray



Thanks for the help in advance,
Jim P.


Ray,
You don't even need to do that in some cases. If you run XP (like most 
people do), there's always ISO Recorder, a free util for burning ISOs (google 
it for more info).
-Garrett

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


Re: Downloads

2007-03-21 Thread Ray
On Wednesday 21 March 2007 5:57 pm, Jim Priovolos wrote:
 Hi, I've downloaded the 6.2 files. When I burned a CD with the boot file it
 didn't make my laptop boot off it after powering up with it in the CD
 drive.

 The *disk1 file burnt to a CD gave the same results.

 I tried the *disk1 file using ftp through a browser and also command line
 ftp set to binary.

 I checked the boot order and CD is first. If I put a Windows boot CD in
 there it will boot off of it.

 Any ideas?

 I've got a Compaq Presario 2500 laptop with XP on it now.
Hi Jim,
the first question is how did you burn the *disk1 file? You have to burn it as 
a disk image, not just a data cd. when you put the *disk one into your 
machine when windows is running, do you see just one file on it, or many? If 
you are using windows to burn the cd, (windows is good for something ;)) 
you'll probably have to use a separate burning program like nero and choose 
disk image. (I'm just getting started here myself, so if your burning under 
something besides windows, ask here again for a how to) 
Ray  


 Thanks for the help in advance,
 Jim P.




 ___
_ Need Mail bonding?
 Go to the Yahoo! Mail QA for great tips from Yahoo! Answers users.
 http://answers.yahoo.com/dir/?link=listsid=396546091
 ___
 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]