Re: mounting a .iso image? ... missing man page
Gary Aitken wrote:
> On 10/09/13 21:25, Polytropon wrote:
>> On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote:
>>> Seems like it must be possible to mount a cd9660 image somehow without
>>> burning an actual disc?
>>
>> Of course. :-)
>
> I guess knowing it's possible is a start;
> couldn't figure out where to look to get the magic combination.
>
>> It is possible by using a virtual node "connected" to the
>> ISO file. Without having tested, according to your example:
>>
>> # mdconfig -u 0 -t vnode -f
>> /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso
>
> for the record, that's:
> mdconfig -a -t vnode -u 0 -f
>
>> # mount -o ro -t cd9660 /dev/md0 /mnt/tmp
>> ... do stuff ...
>> # umount /mnt/tmp
>> # mdconfig -u 0 -d
>
> and that one is
> mdconfig -d -u 0
>
> order appears to be important
>
> Thanks again,
>
> Gary
> ___
> 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"
>
>
To avoid having to recall the arguments for mdconfig(8):
#/bin/sh
#start_isofs
#two commands to attach and mount or umount file.iso
#
isofs_stop() {
(umount -f /mnt &&
mdconfig -d -u $NUM)
}
NUM=3
DEV="/dev/md${NUM}"
IMGFS=$1
case $2 in
"start")
# first check whether target mount point is in use
if mount | grep -q "/mnt"; then
printf "Exiting: mount point '/mnt' currently unavailable.\n"
exit 1
fi
(mdconfig -a -t vnode -f "$IMGFS" -u $NUM &&
mount -o ro -t cd9660 $DEV /mnt) ;;
"stop")
isofs_stop ;;
*)
if [ "$IMGFS" = "stop" ]; then
isofs_stop
else
your_script="$(basename $0)"
printf "Usage: %s [isofile] start|stop\n" $your_script
fi
;;
esac
exit
--
c...@sdf.org
SDF Public Access UNIX System - http://sdf.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"
Re: mounting a .iso image? ... missing man page
On Wed, 09 Oct 2013 22:18:41 -0600, Gary Aitken wrote: > for the record, that's: > mdconfig -a -t vnode -u 0 -f Correct, I noticed too late that -a was missing. But "man mdconfig" mentions all parts that are needed. :-) > > # mount -o ro -t cd9660 /dev/md0 /mnt/tmp > > ... do stuff ... > > # umount /mnt/tmp > > # mdconfig -u 0 -d > > and that one is > mdconfig -d -u 0 > > order appears to be important The manpage doesn't seem to explicitely mention this, but if I remember correctly, it actually matters, as you said. By the way, the manpage mentions mount -t cd9660 /dev/`mdconfig -f cdimage.iso` /mnt as an interesting construction in the EXAMPLES section. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: mounting a .iso image? ... missing man page
On 10/09/13 21:25, Polytropon wrote: > On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote: >> Seems like it must be possible to mount a cd9660 image somehow without >> burning an actual disc? > > Of course. :-) I guess knowing it's possible is a start; couldn't figure out where to look to get the magic combination. > It is possible by using a virtual node "connected" to the > ISO file. Without having tested, according to your example: > > # mdconfig -u 0 -t vnode -f > /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso for the record, that's: mdconfig -a -t vnode -u 0 -f > # mount -o ro -t cd9660 /dev/md0 /mnt/tmp > ... do stuff ... > # umount /mnt/tmp > # mdconfig -u 0 -d and that one is mdconfig -d -u 0 order appears to be important Thanks again, Gary ___ 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: mounting a .iso image? ... missing man page
On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote: > Seems like it must be possible to mount a cd9660 image somehow without > burning an actual disc? Of course. :-) It is possible by using a virtual node "connected" to the ISO file. Without having tested, according to your example: # mdconfig -u 0 -t vnode -f /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso # mount -o ro -t cd9660 /dev/md0 /mnt/tmp ... do stuff ... # umount /mnt/tmp # mdconfig -u 0 -d An alternative would be to use tar to extract the files from the image, change whatever you want, and use mkisofs afterwards to rebuild the (new) image, in case you want to modify its content. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: mounting a .iso image? ... missing man page
On 10/09/2013 10:14 pm, Gary Aitken wrote: For some strange reason, my 9.1 system seems to be missing the section 1 man page for tar, although everything else seems to be there. I have an iso9660 image of 9.1 release which I tried to mount to copy the missing file, but that didn't work (can't find the CD I burned...). #mount -t cd9660 -o ro FreeBSD-9.1-RELEASE-amd64-disc1.iso /mnt/tmp mount_cd9660: /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso: Block device required Seems like it must be possible to mount a cd9660 image somehow without burning an actual disc? Gary ___ 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" mdconfig -a -t vnode -f /path/to/file.iso this will create a /dev/md# where # starts at 0 for first one mount it with mount -t cd9660 -o ro /dev/md# /mnt -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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"
mounting a .iso image? ... missing man page
For some strange reason, my 9.1 system seems to be missing the section 1 man page for tar, although everything else seems to be there. I have an iso9660 image of 9.1 release which I tried to mount to copy the missing file, but that didn't work (can't find the CD I burned...). #mount -t cd9660 -o ro FreeBSD-9.1-RELEASE-amd64-disc1.iso /mnt/tmp mount_cd9660: /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso: Block device required Seems like it must be possible to mount a cd9660 image somehow without burning an actual disc? Gary ___ 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: gptid's in fstab while installing FreeBSD using ISO
On Fri, 4 Oct 2013 20:04:09 +0530, varanasi sainath wrote: > Hi All, > > How do I get gptid's as default in fstab while installing using FreeBSD iso > file (Virtual,machine installation) ? > Is this possible currently? As far as I know, the installer "bsdinstall" currently does not have this option included, but it already offers labeling the partitions as desired, so you could change the content of /etc/fstab manually to use labels instead of those device names. You could do this as a post-installation task while leaving the installer for the command shell and using an editor to do this. > if not how do I achieve this? > I use guided partitioning while installing - If I were to tweak in to the > source code which files or drivers I should be focusing on? I haven't looked into the source yet, but I assume you should concentrate on the component doing the partitioning tasks as explained here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall-partitioning.html > which drivers write the contents of fstab? The corresponding installer's component itself which creates the file according to the partitioning layout at installation time. I assume the required data will actually be written when the installer performs the _real_ installation steps (committing to the installation). > PS: any reason why we use device names in the place of gptid's as default > in fstab. Because it's not always wanted or intended. Next to GPT partitioning with GPT labels, UFS partitioning is possible (both MBR and dedicated style), which _may_ have cases where it needs to be applied. Maybe this can happen when you have a very strange combination of striping, mirroring, encryption and other things that require metadata here and there... The different methods have different capabilities regarding labels (UFS labels, UFSIDs to be mentioned). You can find out more about them here: http://www.freebsd.org/doc/handbook/geom-glabel.html And read about the different methods of partitioning itself: http://www.wonkity.com/~wblock/docs/html/disksetup.html Even "hardcoded" device names could also be required, though I can't imagine such a situation at the moment. :-) It highly depends on the toolset you're using (the bsdinstall program, gpart, fdisk & disklabel, newfs only). PS. I've trimmed the CC list to the freebsd-questions@ list for my reply, hope that's okay. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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"
gptid's in fstab while installing FreeBSD using ISO
Hi All, How do I get gptid's as default in fstab while installing using FreeBSD iso file (Virtual,machine installation) ? Is this possible currently? if not how do I achieve this? I use guided partitioning while installing - If I were to tweak in to the source code which files or drivers I should be focusing on? which drivers write the contents of fstab? PS: any reason why we use device names in the place of gptid's as default in fstab. Thanks, Sainath. ___ 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: Custom release ISO questions.
Thank you Paul! > mkisofs ... It is interesting, does the Linux version of mkisofs fit? > slightly different approach. Very nice! Thanks again. On Wed, Sep 4, 2013 at 4:17 PM, Paul Wootton < paul-free...@fletchermoorland.co.uk> wrote: > On 09/04/13 10:27, Sergey wrote: > >> Hi all! >> >> Is there a way to create custom ISO without buildworld? >> I just want to edit some configs and bsdinstall scripts for silent >> automated install - why need to recompile whole world? >> It will be great if you'll share some useful links about this process. >> >> Thanks. >> > > Hi, > > To create a custom ISO, download the ISO you want to use as your base, use > tar to extract the ISO into a new directory, make the changes you want and > then run "mkisofs -V FreeBSD9 -J -R -b boot/cdboot -no-emul-boot -o > ../freebsd_custom.iso ." from the new directory. > That will create a bootable CD. > > What I did when making a custom install CD for my server (it's 1000s of > miles away in a datacenter) was a slightly different approach. > I created a sparse file (sparse to save on disk space) the exact size of > my server harddrive on my running BSD box, used mdconfig to give me a md > device and pointed VirtualBox at it. Within a VBox session, I did a normal > install (manually created the ZFS filing systems), made all the config > changes I wanted, installed the apps I wanted then shut the VBox session > down. I DD-ed in the md device and piped it to bzip2, creating a bz2 file. > Added the bz2 file to the custom BSD install ISO and modified /etc/rc.local > file to un-bzip the bz2 file, pipe it to mbuffer (so the opperator could > see something was happening) and write the output to the harddrive, popping > the reset line when complete. > When the server restarted, it was configured with all the right user > accounts, ip addresses, nameserver settings etc. > > Just my 2 pence worth... > > Paul > ___ 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: Custom release ISO questions.
On 04/09/2013 13:17, Paul Wootton wrote: On 09/04/13 10:27, Sergey wrote: Hi all! Is there a way to create custom ISO without buildworld? I just want to edit some configs and bsdinstall scripts for silent automated install - why need to recompile whole world? It will be great if you'll share some useful links about this process. Thanks. Hi, To create a custom ISO, download the ISO you want to use as your base, use tar to extract the ISO into a new directory, make the changes you want and then run "mkisofs -V FreeBSD9 -J -R -b boot/cdboot -no-emul-boot -o ../freebsd_custom.iso ." from the new directory. That will create a bootable CD. (Found in ports/sysutuls/cdrtools) What I did when making a custom install CD for my server (it's 1000s of miles away in a datacenter) was a slightly different approach. Boggle! ___ 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: Custom release ISO questions.
On 09/04/13 10:27, Sergey wrote: Hi all! Is there a way to create custom ISO without buildworld? I just want to edit some configs and bsdinstall scripts for silent automated install - why need to recompile whole world? It will be great if you'll share some useful links about this process. Thanks. Hi, To create a custom ISO, download the ISO you want to use as your base, use tar to extract the ISO into a new directory, make the changes you want and then run "mkisofs -V FreeBSD9 -J -R -b boot/cdboot -no-emul-boot -o ../freebsd_custom.iso ." from the new directory. That will create a bootable CD. What I did when making a custom install CD for my server (it's 1000s of miles away in a datacenter) was a slightly different approach. I created a sparse file (sparse to save on disk space) the exact size of my server harddrive on my running BSD box, used mdconfig to give me a md device and pointed VirtualBox at it. Within a VBox session, I did a normal install (manually created the ZFS filing systems), made all the config changes I wanted, installed the apps I wanted then shut the VBox session down. I DD-ed in the md device and piped it to bzip2, creating a bz2 file. Added the bz2 file to the custom BSD install ISO and modified /etc/rc.local file to un-bzip the bz2 file, pipe it to mbuffer (so the opperator could see something was happening) and write the output to the harddrive, popping the reset line when complete. When the server restarted, it was configured with all the right user accounts, ip addresses, nameserver settings etc. Just my 2 pence worth... Paul ___ 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"
Custom release ISO questions.
Hi all! Is there a way to create custom ISO without buildworld? I just want to edit some configs and bsdinstall scripts for silent automated install - why need to recompile whole world? It will be great if you'll share some useful links about this process. 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"
9.2-BETA1 iso is available
Just down loaded the 9.2-BETA1 iso. Thought others would be interested to know it is available. ___ 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 NanoBSD iso image to install NanoBSD on vmware machine?
Hi Olivier, Hard Disk is configured as IDE (IDE 1:1), vm settings. When freebsd image is booting in this VM, before getting the above error, following logs are displayed on boost console: ada0: ATA-4 device ... ... ada0: Previously was known as ad3 .. Trying to mount root from cd9660:/dev/iso9660/nanoISO [ro]... Thanks On Mon, Jul 15, 2013 at 3:56 PM, Olivier Nicole wrote: > Ganesh, > > > I am new to Nanobsd and trying to create an iso image which can be > > installed on vmware machine. > > > > I created an iso image using the disk image > > (/usr/obj/nanobsd.full/_.disk.image) generated according to steps > > given in NanoBSD > > How To <http://www.freebsd.org/doc/en/articles/nanobsd/howto.html> . > > > > VM could boot up with this ISO image, but I got an error as below before > I > > could get OS installation prompt: > > > > mount: /dev/ad0s3: No such file or directory > > mount -o ro /dev/ad0s3 /conf/default/etc failed: droppnig into /bin/sh > > What type of disk have you defined on your VMWare virtual server? The > default is SCSI, which corresponds to /dev/da, not ad. > > Olivier > > > Cannot read termcap database; > > using dumb terminal settings. > > # > > > > > > do I need to use different commands or options to create iso image while > > using nanobsd.sh script? > > > > Please help. > > > > Many thanks in advance for your help and time. > > > > Best Regards, > > - ganesh > > ___ > > 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"
Re: How to create NanoBSD iso image to install NanoBSD on vmware machine?
Ganesh, > I am new to Nanobsd and trying to create an iso image which can be > installed on vmware machine. > > I created an iso image using the disk image > (/usr/obj/nanobsd.full/_.disk.image) generated according to steps > given in NanoBSD > How To <http://www.freebsd.org/doc/en/articles/nanobsd/howto.html> . > > VM could boot up with this ISO image, but I got an error as below before I > could get OS installation prompt: > > mount: /dev/ad0s3: No such file or directory > mount -o ro /dev/ad0s3 /conf/default/etc failed: droppnig into /bin/sh What type of disk have you defined on your VMWare virtual server? The default is SCSI, which corresponds to /dev/da, not ad. Olivier > Cannot read termcap database; > using dumb terminal settings. > # > > > do I need to use different commands or options to create iso image while > using nanobsd.sh script? > > Please help. > > Many thanks in advance for your help and time. > > Best Regards, > - ganesh > ___ > 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"
How to create NanoBSD iso image to install NanoBSD on vmware machine?
Dear Friends, I am new to Nanobsd and trying to create an iso image which can be installed on vmware machine. I created an iso image using the disk image (/usr/obj/nanobsd.full/_.disk.image) generated according to steps given in NanoBSD How To <http://www.freebsd.org/doc/en/articles/nanobsd/howto.html> . VM could boot up with this ISO image, but I got an error as below before I could get OS installation prompt: mount: /dev/ad0s3: No such file or directory mount -o ro /dev/ad0s3 /conf/default/etc failed: droppnig into /bin/sh Cannot read termcap database; using dumb terminal settings. # do I need to use different commands or options to create iso image while using nanobsd.sh script? Please help. Many thanks in advance for your help and time. Best Regards, - ganesh ___ 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: difference img \ iso
On Thu, 2 May 2013 19:03:00 +0600, Osinnyy Bogdan wrote: > Hi there. > > I just want to try some freebsd and get stunned by choosing what release I > should to download\install. > > So I ask you: what difference between iso\img, I mean, If I download > dvd1.iso and mount it on USB drive => starting installation, what difference > between this method and by using *.img ? Why am I asking, 'cause dvd1's got > 3 times more weight, but I never faced with .img when installing windows > systems. The difference is "what's in the files". An IMG is an image of basically _any_ kind of media. It _could_ also be for a DVD or a hard disk. In case of the FreeBSD installation media it's intended for a USB stick. The image contains _everything_ that is needed to make the stick usable, like boot mechanism, file systems and so on. It can carry any file system(s) required. It's an exact 1:1 representation of the content that has to go to the media. An ISO (read: ISO 9660) is also an image, but primarily intended to be used with CDs and DVDs. It carries an ISO-9660 file system, typically with a RR (RockRidge) extension, and it can include a boot mechanism. However, it has "less complicated stuff" in it. It can still be used as a basis for _creating_ non-ISO-9660 file systems in memory (memory disks). Both provided installation media data differs in _content_. While the install DVD has lots of prepackaged software that you can install, the "bootonly" media obviously does not have this. The "memstick" file is somewhere in between. So you would first make a choice on what installation media you want to use, for whatever reasons (e. g. no DVD drive, or system cannot boot from USB). Then you would select the appropriate installation media data file: ISO < 650 MB ---> CD ISO < 4,7 GB ---> DVD IMG > USB stick Of course the _tools_ you need to use to deal with them are different! For example, burning a CD or DVD involves the required recording application, such as cdrecord (CD) or growisofs (DVD), while for writing the IMG file you'd simply use dd. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: (fwd) difference img \ iso
> Hi there. > > I just want to try some freebsd and get stunned by choosing what release I > should to download\install. > > So I ask you: what difference between iso\img, I mean, If I download > dvd1.iso and mount it on USB drive => starting installation, what difference > between this method and by using *.img ? Why am I asking, 'cause dvd1's got > 3 times more weight, but I never faced with .img when installing windows > systems. > > Thanks. > You would use the ISO files for burning a CD or DVD to boot and install FreeBSD. The larger DVD1.ISO file has more pre-built software packages on it to install after you get the basic install completed; the other ISO files are smaller because they expect you to be able to connect to the internet to download the needed extra parts during the installation. DISC1.ISO has the basic FreeBSD system parts on it, but optional things must be downloaded from the internet; the BOOTONLY.ISO is very small because it contains just the minimum to boot a machine from a CD/DVD, and everthing else, including the base system, must be downloaded from the internet. The IMG file is basically the same as the DISC1.ISO, but is for loading on a USB memory stick and used in machines that allows you to boot from a USB memory stick. HTH, Jimmy ___ 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"
difference img \ iso
Hi there. I just want to try some freebsd and get stunned by choosing what release I should to download\install. So I ask you: what difference between iso\img, I mean, If I download dvd1.iso and mount it on USB drive => starting installation, what difference between this method and by using *.img ? Why am I asking, 'cause dvd1's got 3 times more weight, but I never faced with .img when installing windows systems. 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: Can an ISO file be mounted from /etc/fstab at boot?
On Fri, Mar 15, 2013 at 04:04:23PM -0400, Lowell Gilbert typed: > Oscar Hodgson writes: > > > I'm pretty sure the answer is "no, just write a local rc script to do > > that", but thought I'd check. > > > > Can't see any hint of that capability in the handbook or fstab(5). > > > > Really just looking for a single point of management for file systems > > I don't see a way offhand. You need to do the mdconfig before you can > mount, and I don't think that can be done inside of fstab. > > I think that adding such a capability to mount(8) as a program option > would be a fairly minor hack. If it was a standard (UFS) filesystem image (not ISO9600) it would be possible to mount from fstab with something like this: /dev/md0 /data/mfs mfs rw,-PF/path/to/some.img,async 0 0 Ruben ___ 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 an ISO file be mounted from /etc/fstab at boot?
Oscar Hodgson writes: > I'm pretty sure the answer is "no, just write a local rc script to do > that", but thought I'd check. > > Can't see any hint of that capability in the handbook or fstab(5). > > Really just looking for a single point of management for file systems I don't see a way offhand. You need to do the mdconfig before you can mount, and I don't think that can be done inside of fstab. I think that adding such a capability to mount(8) as a program option would be a fairly minor hack. ___ 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"
Can an ISO file be mounted from /etc/fstab at boot?
I'm pretty sure the answer is "no, just write a local rc script to do that", but thought I'd check. Can't see any hint of that capability in the handbook or fstab(5). Really just looking for a single point of management for file systems Thanks in advance. Oscar ___ 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: Duplicate files on distro ISO
On Sat, 12 Jan 2013 02:37:49 -0500, Christian Campbell wrote: > I just tried creating a bootable USB stick with UNetbootin > from FreeBSD-9.1-RELEASE-i386-dvd1.iso. The stick was blank (newly > formatted). Formatted with _which_ file system? I'm asking because of this: > 2. The files deposited on the stick had capitalised names, like /usr/bin/CC The UFS file system should be sensitive to case difference, so "cc" and "CC" are different file names. If you have accidentally formatted the stick with some MS-DOS format (fat16, fat32, vfat or other fat stuff) that might be the problem. Try inializing the stick with the newfs command. Attention! If you're intending to boot from that stick, other actions might need to be taken prior to initializing (like creating partition table, setting active partition and so on). Refer to the documentation on what you need to do manually. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: Duplicate files on distro ISO
On Sat, 12 Jan 2013 02:37:49 -0500 Christian Campbell wrote: > I just tried creating a bootable USB stick with UNetbootin > from FreeBSD-9.1-RELEASE-i386-dvd1.iso. The stick was blank (newly > formatted). While UNetbootin worked it asked about overwriting the > following files: Why are you not using FreeBSD-9.1-RELEASE-amd64-memstick.img and just write it with dd to the stick? Not booting? > > /usr/bin/cc > > /usr/bin/cc > > /usr/bin/mail > > [..] > > So, the files seem to be in the ISO twice each. FWIW: e.g: % ls -la /usr/bin/[Mm]ail -r-xr-xr-x 3 root wheel 82196 2 jan 16:18 /usr/bin/Mail -r-xr-xr-x 3 root wheel 82196 2 jan 16:18 /usr/bin/mail % ls -la /usr/bin/[Cc][Cc] -r-xr-xr-x 3 root wheel 176888 2 jan 16:16 /usr/bin/CC -r-xr-xr-x 2 root wheel 395648 2 jan 16:16 /usr/bin/cc Unetbootin is propably creating a FS (VFAT), that is not case-sensitive. -- Herbert ___ 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"
Duplicate files on distro ISO
I just tried creating a bootable USB stick with UNetbootin from FreeBSD-9.1-RELEASE-i386-dvd1.iso. The stick was blank (newly formatted). While UNetbootin worked it asked about overwriting the following files: > /usr/bin/cc /usr/bin/cc /usr/bin/mail /usr/share/man/man1/cc.1.gz /usr/share/man/man1/mail.1.gz /usr/share/man/man3/archive_read_open_file.3.gz /usr/share/man/man3/archive_write_open_file.3.gz /usr/share/man/man3/execvp.3.gz /usr/share/man/man4/altq.4.gz /usr/share/man/man4/cam.4.gz /usr/share/man/man4/fdt.4.gz /usr/share/man/man4/geom.4.gz /usr/share/man/man4/i386/pae.4.gz /usr/share/man/man4/scsi.4.gz /usr/share/man/man4/smp.4.gz /usr/share/man/man8/nis.8.gz /usr/share/man/man8/yp.8.gz /usr/share/man/man9/alq.9.gz /usr/share/man/man9/altq.9.gz /usr/share/man/man9/bus_bind_intr.9.gz /usr/share/man/man9/bus_describe_intr.9.gz /usr/share/man/man9/bus_setup_intr.9.gz /usr/share/man/man9/bus_teardown_intr.9.gz /usr/share/man/man9/eventhandler_deregister.9.gz /usr/share/man/man9/eventhandler_register.9.gz /usr/share/man/man9/m_move_pkthdr.9.gz /usr/share/man/man9/m_prepend.9.gz /usr/share/man/man9/rtfree.9.gz /usr/share/man/man9/sysctl_add_oid.9.gz /usr/share/man/man9/vfs_mount.9.gz /usr/share/man/man9/vref.9.gz /usr/share/openssl/man/man3/bn_print.3.gz /usr/share/openssl/man/man3/hmac.3.gz /usr/share/openssl/man/man3/md5.3.gz /usr/share/openssl/man/man3/mdc2.3.gz /usr/share/openssl/man/man3/pem.3.gz /usr/share/openssl/man/man3/rc4.3.gz /usr/share/openssl/man/man3/ssl.3.gz So, the files seem to be in the ISO twice each. FWIW: 1. I said 'no' to each overwrite. 2. The files deposited on the stick had capitalised names, like /usr/bin/CC . Does the above pose a problem? Thanks, Christian _ 3425 SW 2nd Ave, #239 cell (352) 514-7411 Gainesville, FL 32607-2813 dc...@alumni.ufl.edu On this perfect day / Nothing's standing in my way...-Hoku ___ 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"
making a custom iso
Hi , I have just build a custom iso using cd /usr svn co http://svn.freebsd.org/base/stable/9 src cd src make buildworld buildkernel cd release make release make install DESTDIR=/var/freebsd-snapshot Svn Revision is r244359 (9.1-RELEASE is r243825) but after install when i do uname -a I get 9.1-PRERELEASE I think http://svn.freebsd.org/base/stable/9 should be updated to 9-Stable Regards. ___ 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"
Custom ISO mount script problem
I have a server that I use to host ISO images, and mount them so they are available via network shares. I ran into a problem today, I temporarily made an ISO image accessible via a md device and mounted it under /mnt just to check the data on the ISO image. My ISO mount script ran its updated check while this was there, and hung up because of it. Now the obvious solution is to fix my script, but as I am baffled as to why it hung-up, it does do a query on md devices, and will try to dismount any that are mounted if they don't match its criteria, and delete the md device as well. However as it would have found this one in use, it should have just returned a failure and continued on. However it didn't and then when I tried to manually umount it, my umount command hung as well. What I was left with was two umount commands attempting to umount /dev/md1000 both stuck, they wouldn't respond to a kill -9 I couldn't use mdconfig -d -u 1000 to delete the md device, even with a -o force (had yet another process stuck). After 1 hour all processes were still hung, killing the shell left them zombied, but still hung there, tying up the md device. I was left with rebooting the server, until I can figure out why my script broke and didn't just error and continue the remaining checks in its list. Does anyone have any idea how if this happens again to kill these hung-up umount processes, without rebooting the server? This could be a fun one to fix, because so far attempting to duplicate the problem hasn't worked, think I just have to time something just right, or wrong depended how you look at it. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ 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: Burning .iso DVD's
On Fri, Nov 2, 2012 at 5:12 PM, Al Plant wrote: > > Aloha, > > I am not able to get a successfull burn of .iso DVD's 9.0 or higher > FreeBSD. > > > Chapter 19.7 ... of Handbook says to use growisofs with ATAPI support same > as I do for 7.* 8.* FreeBSD etc. > > I get error of no growisofs ..when I run growisofs -dvd-compat -Z > /dev/cd0=image.iso growisofs is part of the dvd+rw-tools port/package. -- Take care Rick Miller ___ 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: Burning .iso DVD's
On Nov 2, 2012 2:18 PM, "Al Plant" wrote: > > > Aloha, > > I am not able to get a successfull burn of .iso DVD's 9.0 or higher FreeBSD. > > > Chapter 19.7 ... of Handbook says to use growisofs with ATAPI support same as I do for 7.* 8.* FreeBSD etc. > > I get error of no growisofs ..when I run growisofs -dvd-compat -Z /dev/cd0=image.iso > > What has cdrecord home.iso got to do with this ? It seems that to run growisofs some people say you have to use this now. Not clearly defined in handbook pages I printed. > > I would like to make a new burner that works on 9.* up. Any help would be great. Thanks. > > ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 > + http://hawaiidakine.com + http://freebsdinfo.org + > + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + > < 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" Mahalo Al, I have been burning DVD's ok on 9 and 10. I'm not at a place to check this second, but I believe you need to install something like cdtools (?) . Should be listed in handbook. I can check later when I get home. Waitman Gobble San Jose California ___ 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"
Burning .iso DVD's
Aloha, I am not able to get a successfull burn of .iso DVD's 9.0 or higher FreeBSD. Chapter 19.7 ... of Handbook says to use growisofs with ATAPI support same as I do for 7.* 8.* FreeBSD etc. I get error of no growisofs ..when I run growisofs -dvd-compat -Z /dev/cd0=image.iso What has cdrecord home.iso got to do with this ? It seems that to run growisofs some people say you have to use this now. Not clearly defined in handbook pages I printed. I would like to make a new burner that works on 9.* up. Any help would be great. Thanks. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + < 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"
Re: 8.3 stable or 9.0 stable amd64 iso with mfi driver changes of May 18, 2012
Kevin, Thank you for your response. It is great to get confirmation and I will try with 9.1-RC1 I DO have on board Broadcom 5720 NIC. Nice to know what my next problem is likely to be. Hopefully that will be easy to solve if I install another NIC card. Thanks! Jean Jean Christofferson je...@relevantpower.com Relevant Power, Inc. www.relevanttools.com On Sep 14, 2012, at 6:14 PM, kpn...@pobox.com wrote: On Fri, Sep 14, 2012 at 04:45:49PM -0700, Jean Christofferson wrote: I am trying to install FreeBSD stable - either 8.3 or 9.0 - on a Dell 420 with Perc H310 LSI PCI Express SAS Raid controllers. Although the physical disks are present and recognized by the BIOS the sysinstall does not see the disks. I think the issue is mfi driver and was added to the stable release May 18, 2012. Yup, the 12G machines came out when the paint was drying on 8.3. So there isn't a -stable release with the updated driver. The new mfi driver is in 9.1-RC1 if you are OK with a pre-release. I hope you don't have the Broadcom 5720 NIC like the R620. The FreeBSD driver (bge) isn't finished yet. At least, I don't remember seeing it go into the tree. It's known to _not_ work on the R620 and I believe R720. -- Kevin P. Nealhttp://www.pobox.com/ ~kpn/ "Nonbelievers found it difficult to defend their position in \ the presense of a working computer." -- a DEC Jensen paper ___ 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.3 stable or 9.0 stable amd64 iso with mfi driver changes of May 18, 2012
I am trying to install FreeBSD stable - either 8.3 or 9.0 - on a Dell 420 with Perc H310 LSI PCI Express SAS Rain controllers. Although the physical disks are present and recognized by the BIOS the sysinstall does not see the disks. I think the issue is mfi driver and was added to the stable release May 18, 2012. http://www.FreeBSD.org/cgi/man.cgi?query=mfi&sektion=4&manpath=FreeBSD+8.3-RELEASE I do not have an environment to download the source and make my own installation disk. The 8.3 image on the ftp site is dated April 9, 2012 and the 9.0 is Jan 2012. Is there some place I can download an amd63 iso that was includes the mfi driver update done on May 18, 2012? Or perhaps that is not really the issue at all - any help that anyone can provide will be welcome! Thanks, Jean Jean Christofferson je...@relevantpower.com Relevant Power, Inc. www.relevanttools.com 415-472-8400 ___ 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: Virtual FreeBSD9.0 ISO Image Won't Mount Root FS
What option argument did you specify for the -V (volume ID) option when
you created the ISO with the `mkisofs` command? I believe that the root
filesystem lies under /dev/iso9660/ for which the ISO loader's
default configuration specifies as /dev/iso9660/FREEBSD_INSTALL. Thus
you'll need to change the vfs.root.mountfrom loader variable to be
cd9660:/dev/iso9660/
Ryan
On 09/05/2012 09:26 AM, Martin McCormick wrote:
The ISO image is the FreeBSD9.0 bootonly CDROM for amd64
systems. I added loader.conf to /boot in order to activate a
serial console and this along with socat appears to be working
as it should. This is great because remote desktop is not an
option.
The VM boot starts normally with the spinning bars and
normal startup messages until:
cd0: cd present [85585 x 2048 byte records]
Timecounter "TSC" frequency 3368628976 Hz quality 800
Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]...
mountroot: waiting for device /dev/iso9660/FREEBSD_INSTALL ...
Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error 19.
Loader variables:
vfs.root.mountfrom=cd9660:/dev/iso9660/FREEBSD_INSTALL
vfs.root.mountfrom.options=ro
Manual root filesystem specification:
: [options]
Mount using filesystem
and with the specified (optional) option list.
eg. ufs:/dev/da0s1a
zfs:tank
cd9660:/dev/acd0 ro
(which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /)
? List valid disk boot devices
. Yield 1 second (for background tasks)
Abort manual input
mountroot>
I enter a Question Mark.
mountroot> ?
List of GEOM managed disk devices:
iso9660/CDROM cd0 ada0
mountroot>
The host system is a fairly new 64-bit Macintosh which
is using VirtualBox. Here is the script to define the new
machine.
VBoxManage createvm --name "vsys" --ostype FreeBSD_64 --register
VBoxManage modifyvm "vsys" --memory 1000 --vram 128 --acpi on \
--boot2 dvd --boot1 disk --nic1 nat
#setup ttyu0 so the VM can communicate.
VBoxManage modifyvm "vsys" --uart1 0x3F8 4
VBoxManage -q modifyvm "vsys" --uartmode1 server '/tmp/vmx'
VBoxManage createhd --filename "FreeBSD.VMDK" --size 1
VBoxManage storagectl x --name "SATA Controller" --add sata --controller \
IntelAHCI --hostiocache on
VBoxManage storageattach x --storagectl "SATA Controller" \
--port 0 --device 0 --type hdd --medium "FreeBSD.VMDK"
VBoxManage storagectl "vsys" --name "IDE Controller" \
--add ide --controller PIIX4
VBoxManage storageattach "vsys" --storagectl "IDE Controller" \
--port 0 --device 0 --type dvddrive --medium /users/sysbuild/headless.iso
___
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"
Virtual FreeBSD9.0 ISO Image Won't Mount Root FS
The ISO image is the FreeBSD9.0 bootonly CDROM for amd64 systems. I added loader.conf to /boot in order to activate a serial console and this along with socat appears to be working as it should. This is great because remote desktop is not an option. The VM boot starts normally with the spinning bars and normal startup messages until: cd0: cd present [85585 x 2048 byte records] Timecounter "TSC" frequency 3368628976 Hz quality 800 Trying to mount root from cd9660:/dev/iso9660/FREEBSD_INSTALL [ro]... mountroot: waiting for device /dev/iso9660/FREEBSD_INSTALL ... Mounting from cd9660:/dev/iso9660/FREEBSD_INSTALL failed with error 19. Loader variables: vfs.root.mountfrom=cd9660:/dev/iso9660/FREEBSD_INSTALL vfs.root.mountfrom.options=ro Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/acd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input mountroot> I enter a Question Mark. mountroot> ? List of GEOM managed disk devices: iso9660/CDROM cd0 ada0 mountroot> The host system is a fairly new 64-bit Macintosh which is using VirtualBox. Here is the script to define the new machine. VBoxManage createvm --name "vsys" --ostype FreeBSD_64 --register VBoxManage modifyvm "vsys" --memory 1000 --vram 128 --acpi on \ --boot2 dvd --boot1 disk --nic1 nat #setup ttyu0 so the VM can communicate. VBoxManage modifyvm "vsys" --uart1 0x3F8 4 VBoxManage -q modifyvm "vsys" --uartmode1 server '/tmp/vmx' VBoxManage createhd --filename "FreeBSD.VMDK" --size 1 VBoxManage storagectl x --name "SATA Controller" --add sata --controller \ IntelAHCI --hostiocache on VBoxManage storageattach x --storagectl "SATA Controller" \ --port 0 --device 0 --type hdd --medium "FreeBSD.VMDK" VBoxManage storagectl "vsys" --name "IDE Controller" \ --add ide --controller PIIX4 VBoxManage storageattach "vsys" --storagectl "IDE Controller" \ --port 0 --device 0 --type dvddrive --medium /users/sysbuild/headless.iso ___ 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: iso image question
In article you write: >I have a CD that was burned (but not labeled so well). Is is possible to tell >if >this is an i386 or amd64 image? Sure. Mount it, do a "file" on some of the programs in /bin and see whether they're i386 or x86-64 code. R's, John ___ 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"
iso image question
I have a CD that was burned (but not labeled so well). Is is possible to tell if this is an i386 or amd64 image? ___ 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: New iso format on 9.0
On Tue, 21 Feb 2012 11:31:23 -0800, Robison, Dave wrote: On 02/21/2012 10:28, Devin Teske wrote: Why can't you mount the disc on /mnt and then use tar after mounting the disk to copy the files from /mnt to /destdir ... tar cpf - -C /mnt . | tar xvpf - -C /destdir That will preserve hard links, symlinks, permissions, and times (and doesn't require rsync). There are other methods involving cpio, but I find tar to be nice. Just FYI, a trick using cpio which Julian once taught me: find . -depth | cpio -pdmluv /destination/dir/here -- Dave Robison Sales Solution Architect II FIS Banking Solutions 510/621-2089 (w) 530/518-5194 (c) 510/621-2020 (f) da...@vicor.com david.robi...@fisglobal.com _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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" Thanks a lot this one and the previous advice using tar was what I was looking for :) :) Thanks a lot really :) ___ 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: New iso format on 9.0
On 02/21/2012 10:28, Devin Teske wrote: > Why can't you mount the disc on /mnt and then use tar after mounting the disk > to copy the files from /mnt to /destdir ... > > tar cpf - -C /mnt . | tar xvpf - -C /destdir > > That will preserve hard links, symlinks, permissions, and times (and doesn't > require rsync). > > There are other methods involving cpio, but I find tar to be nice. Just FYI, a trick using cpio which Julian once taught me: find . -depth | cpio -pdmluv /destination/dir/here -- Dave Robison Sales Solution Architect II FIS Banking Solutions 510/621-2089 (w) 530/518-5194 (c) 510/621-2020 (f) da...@vicor.com david.robi...@fisglobal.com _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: New iso format on 9.0
> -Original Message- > From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- > questi...@freebsd.org] On Behalf Of ego...@ramattack.net > Sent: Tuesday, February 21, 2012 10:14 AM > To: freebsd-questions@freebsd.org > Subject: RE: New iso format on 9.0 > > > umount /mnt > > vnconfig -u vn99c > > > > Or, you can just download this script which works on both Linux and > > FreeBSD: > > > > > > > http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/src/tools/ > umo > > unt_iso.sh?view=log > > > > Usage: > > ./umount_iso.sh /mnt > > > Hello all, > > And thanks a lot really for you're answers. Yes... I know the way you > can mount an iso image (I have done a couple of times yesterday in > fact)... but I'm really worried about how making a consistent copy of it > like I did with tar... as I said this is for an unattended installation > system... so I cannot be depending on having the cd mounted on the > operating system... with tar the -p option was important for preserving > permissions, flags, and so... perhaps now... should mount like you said > before for example and later having an rsync compiled with file flag > preserving support do an rsync -av /cd-mount-point > /disk-place-to-copy-cd-content ?? > > this last is the real question... I have played previously several > times with memory disks mappings, mdconfig and those staff but how > to make a consistent copy of the cd for the unattended installation > system... Why can't you mount the disc on /mnt and then use tar after mounting the disk to copy the files from /mnt to /destdir ... tar cpf - -C /mnt . | tar xvpf - -C /destdir That will preserve hard links, symlinks, permissions, and times (and doesn't require rsync). There are other methods involving cpio, but I find tar to be nice. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: New iso format on 9.0
Devin Teske fisglobal.com> writes: > > > > -Original Message- > > From: owner-freebsd-questions freebsd.org [mailto:owner-freebsd- > > questions freebsd.org] On Behalf Of jb > > Sent: Tuesday, February 21, 2012 9:53 AM > > To: freebsd-questions freebsd.org > > Subject: Re: New iso format on 9.0 > > > > ramattack.net> writes: > > > > > > > > Good morning, > > > > > > Previously I was doing a : 'tar -C /expert/netboot/freebsd8 -pxvf > > > 8.0-RELEASE-amd64-disc1.iso' for extracting iso files. > > > ... > > > > There is a simple way to access contents of an iso file: > > # mount -o loop some.iso /mnt > > > > That works on FreeBSD? I commonly use that (daily even) on Linux, but was not > aware that would work on FreeBSD. > ... Well, old habits never die :-) But, actually, why not on FreeBSD ? Btw, mdconfig(8) ... To create an md(4) device out of an ISO 9660 CD image file (-a and -t vnode are implied), using the first available md(4) device, and then mount the new memory disk: mount -t cd9660 /dev/`mdconfig -f cdimage.iso` /mnt ... jb ___ 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: New iso format on 9.0
umount /mnt vnconfig -u vn99c Or, you can just download this script which works on both Linux and FreeBSD: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/src/tools/umo unt_iso.sh?view=log Usage: ./umount_iso.sh /mnt Hello all, And thanks a lot really for you're answers. Yes... I know the way you can mount an iso image (I have done a couple of times yesterday in fact)... but I'm really worried about how making a consistent copy of it like I did with tar... as I said this is for an unattended installation system... so I cannot be depending on having the cd mounted on the operating system... with tar the -p option was important for preserving permissions, flags, and so... perhaps now... should mount like you said before for example and later having an rsync compiled with file flag preserving support do an rsync -av /cd-mount-point /disk-place-to-copy-cd-content ?? this last is the real question... I have played previously several times with memory disks mappings, mdconfig and those staff but how to make a consistent copy of the cd for the unattended installation system... Thanks again, Best regards, ___ 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: New iso format on 9.0
> -Original Message- > From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- > questi...@freebsd.org] On Behalf Of jb > Sent: Tuesday, February 21, 2012 9:53 AM > To: freebsd-questions@freebsd.org > Subject: Re: New iso format on 9.0 > > ramattack.net> writes: > > > > > Good morning, > > > > Previously I was doing a : 'tar -C /expert/netboot/freebsd8 -pxvf > > 8.0-RELEASE-amd64-disc1.iso' for extracting iso files. > > ... > > There is a simple way to access contents of an iso file: > # mount -o loop some.iso /mnt > That works on FreeBSD? I commonly use that (daily even) on Linux, but was not aware that would work on FreeBSD. Here's the method I use on [modern] FreeBSD: mdconfig -a -t vnode -u 99 -f $ISOFILE mount -t cd9660 /dev/md99 /mnt And here's the method I would use on LEGACY FreeBSD: cd /dev && sh MAKEDEV vn99 vnconfig -c vn99 $ISOFILE mount -t cd9660 /dev/vn99c /mnt Or, you can just download this script which works on both Linux and FreeBSD: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/src/tools/mou nt_iso.sh?view=log Usage: ./mount_iso.sh $ISOFILE /mnt Don't forget that when you're done, you have to deconfigure the device... On [modern] FreeBSD: umount /mnt mdconfig -d -u 99 And here's the method for LEGACY FreeBSD: umount /mnt vnconfig -u vn99c Or, you can just download this script which works on both Linux and FreeBSD: http://druidbsd.cvs.sourceforge.net/viewvc/druidbsd/druidbsd/druid/src/tools/umo unt_iso.sh?view=log Usage: ./umount_iso.sh /mnt -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: New iso format on 9.0
ramattack.net> writes: > > Good morning, > > Previously I was doing a : 'tar -C /expert/netboot/freebsd8 -pxvf > 8.0-RELEASE-amd64-disc1.iso' for extracting iso files. > ... There is a simple way to access contents of an iso file: # mount -o loop some.iso /mnt jb ___ 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: New iso format on 9.0
On Tue, 21 Feb 2012 13:33:56 +, Matthew Seaman wrote: On 21/02/2012 12:46, ego...@ramattack.net wrote: Previously I was doing a : 'tar -C /expert/netboot/freebsd8 -pxvf 8.0-RELEASE-amd64-disc1.iso' for extracting iso files. Now due to a different way of creating iso files in this new release... have read this is not recommended and in fact it does not work pretty good. The matter because I wanted to make this extraction is for an unattended installation system of FreeBSD (Jumpstart basically) so I need a consistent way of extracting it, preserving the most properties of the iso files content. So, could anyone advice me a proper way of doing what I was doing before, with the new iso files?. Using tar to extract the contents of a .iso should work. You might end up with oddities to do with file ownership and permissions, but you should be able to fix that by suitable application of mtree(1). Alternatively you can grab the actual installation images from the install media -- that's any of the .txz files under /usr/freebsd-dist for 9.0. These are actually rather easier to use than the equivalents under 8.x or earlier: you get about 5 .txz files, not all of which are necessary to boot the new system. For a minimal install on a 64bit platform you'ld need base.txz, lib32.txz and kernel.txz. Just untar those in the root directory of the system you're building (preserving permissions and ownership) and you should be good to go. [Assuming you've already done all the partitioning and creating filesystems and installing boot-blocks stuff required, of course.] Cheers, Matthew Hi all!!, And could be possible... doing something like : mdconfig -a -t vnode -f /tmp/bootable.iso -u 0 # mount -t cd9660 /dev/md0 /mnt And later an rsync -av (rsync compiled preserving file flags) /mnt /expert/netboot/freebsd90... ?? and the most important thing... could this content in /expert/netboot/freebsd90 be consistent for using it for an unattended installation system? Thanks a lot!! Best regards, ___ 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: New iso format on 9.0
On 21/02/2012 12:46, ego...@ramattack.net wrote: > Previously I was doing a : 'tar -C /expert/netboot/freebsd8 -pxvf > 8.0-RELEASE-amd64-disc1.iso' for extracting iso files. Now due to a > different way of creating iso files in this new release... have read > this is not recommended and in fact it does not work pretty good. The > matter because I wanted to make this extraction is for an unattended > installation system of FreeBSD (Jumpstart basically) so I need a > consistent way of extracting it, preserving the most properties of the > iso files content. So, could anyone advice me a proper way of doing what > I was doing before, with the new iso files?. Using tar to extract the contents of a .iso should work. You might end up with oddities to do with file ownership and permissions, but you should be able to fix that by suitable application of mtree(1). Alternatively you can grab the actual installation images from the install media -- that's any of the .txz files under /usr/freebsd-dist for 9.0. These are actually rather easier to use than the equivalents under 8.x or earlier: you get about 5 .txz files, not all of which are necessary to boot the new system. For a minimal install on a 64bit platform you'ld need base.txz, lib32.txz and kernel.txz. Just untar those in the root directory of the system you're building (preserving permissions and ownership) and you should be good to go. [Assuming you've already done all the partitioning and creating filesystems and installing boot-blocks stuff required, of course.] Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
New iso format on 9.0
Good morning, Previously I was doing a : 'tar -C /expert/netboot/freebsd8 -pxvf 8.0-RELEASE-amd64-disc1.iso' for extracting iso files. Now due to a different way of creating iso files in this new release... have read this is not recommended and in fact it does not work pretty good. The matter because I wanted to make this extraction is for an unattended installation system of FreeBSD (Jumpstart basically) so I need a consistent way of extracting it, preserving the most properties of the iso files content. So, could anyone advice me a proper way of doing what I was doing before, with the new iso files?. Best regards, ___ 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"
which media type I must use when booting ISO from grub
HI I want to install freebse and boot it from grub as: title FreeBSD 8.0 (USB) map --mem (hd0,0)/iso/FreeBSD8.iso (hd32) map --hook chainloader (hd32) boot Which media type I must use when choosing 'media type' in menu? as one way to solve problem is extract 8.2-RELEASE and packages directories to root of FlashDrive. but how to skip coping files from .iso? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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 custom CD and extra files to be included in the iso
On Sat, Feb 4, 2012 at 9:46 PM, Devin Teske wrote: > > On Feb 4, 2012, at 1:37 AM, Amitabh Kant wrote: > > On Sat, Feb 4, 2012 at 2:50 PM, Amitabh Kant > wrote: > > I have been able to use the "make release" command to create a custom iso > > for FreeBSD which includes some changes to the various bsdinstall scripts. > > It all works well as the iso / memory stick images / ftp files are > > generated and usable. > > > What I would now like to do is try adding couple of files, scripts and/or > > packages, to this custom iso. I am a little confused on where the files > > should be placed so that it is placed in either root's home directory after > > installation? > > > Amitabh > > > > Sorry for not making it clear in my last mail, I am using FreeBSD 9.0 > RELEASE on amd64 arch. > > > If you use the DRUID (http://druidbsd.sf.net/), this is extremely easy. > > Step-by-step instructions... > > NOTE: Feel free to use ANY operating system you like, so long as it has > (1) /bin/sh (2) cvs (3) mkisofs (4) GNU make. Including (but not limited > to) Mac OS X (with developer tools installed), Cygwin, Linux, and of > course, FreeBSD. > > 1. mkdir druidbsd.sf.net > > 2. cd druidbsd.sf.net > > 3. cvs -d:pserver:anonym...@druidbsd.cvs.sourceforge.net:/cvsroot/druidbsd > login > > NOTE: Press "ENTER" when prompted for "CVS password:" > > NOTE: Ignore warning about "failed to open ~/.cvspass" > > 4. cvs -z3 -d:pserver:anonym...@druidbsd.cvs.sourceforge.net:/cvsroot/druidbsd > co -P druidbsd/druid > > NOTE: The screen will stream information for about 5-10 minutes as it > downloads 510MB of source code to the FreeBSD DRUID installer -- a > sysinstall(8) based custom FreeBSD 9.0 installer capable of installing > *either* i386 or amd64 from the same disc (among many many other things). > > 5. cd druidbsd/druid > > NOTE: The DRUID has a special directory in-which anything placed there > gets copied to the target installation disk automatically after > installation of the Operating System completes (but before any > post-installation scripts are run). This directory is called "sys_custom" > and it lives within the RELEASE directory. Within sys_custom, files are > copied exactly as-is, so since you mentioned that you wanted to copy files > to "/root", let's operate under that assumption below. > > 6. mkdir -p src/freebsd/repos/9.0-RELEASE-amd64/sys_custom/root > > 7. cp myfiles src/freebsd/repos/9.0-RELEASE-amd64/sys_custom/root/ > > NOTE: If you want the same files available for the installation of the > i386 release of 9.0-RELEASE, you should repeat the above steps 6-7 with the > destination directory "src/freebsd/repos/9.0-RELEASE/sys_custom/root" > (remember, the DRUID is a unified installer that supports both the > installation of i386 and amd64 from the same disc). > > 8. ./configure > > 9. make freebsd > > NOTE: Replace "make" with "gmake" if on FreeBSD > > NOTE: If you're using FreeBSD, you may have to first say "pkg_add -r > gmake" followed by "rehash" (if using csh or tcsh as your shell). > > NOTE: Also, if you need to get "mkisofs", it's "pkg_add -r cdrtools" (and > again, "rehash" if using csh or tcsh as your shell). > > 10. You now have a custom "FreeBSD_Druid-9.0b56.iso" that will install > your custom files automatically to /root when either i386 or amd64 is > installed. > > ASIDE: sys_custom is like a "dumping ground" for anything and everything > you simply want to be copied to-disk post-installation of the OS. If > instead you want to write scripts to be run as part of the > post-installation process, see instead "dep/freebsd/run_once/template.sh" > and "src/freebsd/repos/9.0-RELEASE/run_once/*.sh" and > "src/freebsd/repos/9.0-RELEASE-amd64/run_once/*.sh". The "run_once" > directory unlike "sys_custom" is a "dumping ground" for post-installation > scripts (any script ending in ".sh" in that directory will automatically be > executed as part of the post-installation procedure after installing the OS. > > ASIDE: As you can tell, the DRUID is a FreeBSD installer that was designed > to be *easily* extended by anybody/everybody on any OS they like (any OS > that can produce or edit an ISO that is). > -- > Devin > _ > The information contained in this message is proprietary and/or > confidential. If you are not the intended recipient, please: (i) delete the > message and all copies; (ii) do not disclose, distribute or use the message > in any manner; and (iii) notify the sender immediately. In addition, please > be aware that any message addressed to our domain is subject to archiving > and review by persons other than the intended recipient. Thank you. > Thanks Devin. Would take a look at DRUID. Amitabh ___ 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 custom CD and extra files to be included in the iso
On Feb 4, 2012, at 1:37 AM, Amitabh Kant wrote: > On Sat, Feb 4, 2012 at 2:50 PM, Amitabh Kant wrote: > >> I have been able to use the "make release" command to create a custom iso >> for FreeBSD which includes some changes to the various bsdinstall scripts. >> It all works well as the iso / memory stick images / ftp files are >> generated and usable. >> >> What I would now like to do is try adding couple of files, scripts and/or >> packages, to this custom iso. I am a little confused on where the files >> should be placed so that it is placed in either root's home directory after >> installation? >> >> Amitabh >> > > Sorry for not making it clear in my last mail, I am using FreeBSD 9.0 > RELEASE on amd64 arch. > If you use the DRUID (http://druidbsd.sf.net/), this is extremely easy. Step-by-step instructions... NOTE: Feel free to use ANY operating system you like, so long as it has (1) /bin/sh (2) cvs (3) mkisofs (4) GNU make. Including (but not limited to) Mac OS X (with developer tools installed), Cygwin, Linux, and of course, FreeBSD. 1. mkdir druidbsd.sf.net 2. cd druidbsd.sf.net 3. cvs -d:pserver:anonym...@druidbsd.cvs.sourceforge.net:/cvsroot/druidbsd login NOTE: Press "ENTER" when prompted for "CVS password:" NOTE: Ignore warning about "failed to open ~/.cvspass" 4. cvs -z3 -d:pserver:anonym...@druidbsd.cvs.sourceforge.net:/cvsroot/druidbsd co -P druidbsd/druid NOTE: The screen will stream information for about 5-10 minutes as it downloads 510MB of source code to the FreeBSD DRUID installer -- a sysinstall(8) based custom FreeBSD 9.0 installer capable of installing *either* i386 or amd64 from the same disc (among many many other things). 5. cd druidbsd/druid NOTE: The DRUID has a special directory in-which anything placed there gets copied to the target installation disk automatically after installation of the Operating System completes (but before any post-installation scripts are run). This directory is called "sys_custom" and it lives within the RELEASE directory. Within sys_custom, files are copied exactly as-is, so since you mentioned that you wanted to copy files to "/root", let's operate under that assumption below. 6. mkdir -p src/freebsd/repos/9.0-RELEASE-amd64/sys_custom/root 7. cp myfiles src/freebsd/repos/9.0-RELEASE-amd64/sys_custom/root/ NOTE: If you want the same files available for the installation of the i386 release of 9.0-RELEASE, you should repeat the above steps 6-7 with the destination directory "src/freebsd/repos/9.0-RELEASE/sys_custom/root" (remember, the DRUID is a unified installer that supports both the installation of i386 and amd64 from the same disc). 8. ./configure 9. make freebsd NOTE: Replace "make" with "gmake" if on FreeBSD NOTE: If you're using FreeBSD, you may have to first say "pkg_add -r gmake" followed by "rehash" (if using csh or tcsh as your shell). NOTE: Also, if you need to get "mkisofs", it's "pkg_add -r cdrtools" (and again, "rehash" if using csh or tcsh as your shell). 10. You now have a custom "FreeBSD_Druid-9.0b56.iso" that will install your custom files automatically to /root when either i386 or amd64 is installed. ASIDE: sys_custom is like a "dumping ground" for anything and everything you simply want to be copied to-disk post-installation of the OS. If instead you want to write scripts to be run as part of the post-installation process, see instead "dep/freebsd/run_once/template.sh" and "src/freebsd/repos/9.0-RELEASE/run_once/*.sh" and "src/freebsd/repos/9.0-RELEASE-amd64/run_once/*.sh". The "run_once" directory unlike "sys_custom" is a "dumping ground" for post-installation scripts (any script ending in ".sh" in that directory will automatically be executed as part of the post-installation procedure after installing the OS. ASIDE: As you can tell, the DRUID is a FreeBSD installer that was designed to be *easily* extended by anybody/everybody on any OS they like (any OS that can produce or edit an ISO that is). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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 custom CD and extra files to be included in the iso
On Sat, Feb 4, 2012 at 2:50 PM, Amitabh Kant wrote: > I have been able to use the "make release" command to create a custom iso > for FreeBSD which includes some changes to the various bsdinstall scripts. > It all works well as the iso / memory stick images / ftp files are > generated and usable. > > What I would now like to do is try adding couple of files, scripts and/or > packages, to this custom iso. I am a little confused on where the files > should be placed so that it is placed in either root's home directory after > installation? > > Amitabh > Sorry for not making it clear in my last mail, I am using FreeBSD 9.0 RELEASE on amd64 arch. Amitabh ___ 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 custom CD and extra files to be included in the iso
I have been able to use the "make release" command to create a custom iso for FreeBSD which includes some changes to the various bsdinstall scripts. It all works well as the iso / memory stick images / ftp files are generated and usable. What I would now like to do is try adding couple of files, scripts and/or packages, to this custom iso. I am a little confused on where the files should be placed so that it is placed in either root's home directory after installation? Amitabh ___ 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: mkisofs increasing iso size by 100 MB
On Thu, Jan 12, 2012 at 2:48 PM, Amitabh Kant wrote: > On Wed, Jan 11, 2012 at 9:49 PM, Jan Henrik Sylvester wrote: > >> On 01/-10/-28163 20:59, Amitabh Kant wrote: >> >>> I am trying to customise the bsdinstall auto script. I can mount the iso >>> (amd64 arch / 9.0 RELEASE) and change the shell script as per my >>> requirement. Once I try to re-create the iso file using mkisofs utility, >>> the size of the final iso increases by 100 MB if -J (joliet) mode is >>> used. >>> If I remove the joliet mode, it still increases by around 97 MB. Even if >>> no >>> changes are made to any of the files, the result is same. >>> >>> The process I have followed is as follows: >>> # mkdir /usr/iso >>> # cd /usr/iso >>> # dd if=/dev/cd0 of=org.iso bs=2048 >>> # mdconfig -a -t vnode -f org.iso -u 0 >>> # mount_cd9660 /dev/md0 /mnt >>> # mkdir staging >>> # cd staging >>> # rsync -a /mnt/ . >>> With Joliet mode >>> # mkisofs -J -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o >>> /usr/iso/my_custom.iso . >>> Without Joliet mode >>> # mkisofs -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o >>> /usr/iso/my_custom1.iso . >>> >>> The original iso is 612M, custom.iso is 712M and custom1.iso is 709M. >>> >>> System details: FreeBSD amd64 9.0 RELEASE running inside a virtualbox >>> with >>> 2GB RAM. >>> >>> Where am I going wrong? >>> >> >> There are many hardlinked files on the iso images. By the procedure >> above, you have them included multiple times. >> >> From the rsync manpage: "Note that -a does not preserve hardlinks, >> because finding multiply-linked files is expensive. You must separately >> specify -H." >> >> You will probably want "-cache-inodes" for mkisofs as well (and maybe >> other options). Or you could look at src/release/amd64/mkisoimages.**sh >> for the use of "makefs -t cd9660". >> >> Cheers, >> Jan Henrik >> > > Tried -H with rsync and -cache-inodes in mkisofs. Saw the mkisoimages.sh > and used the same parameters (at least to my understanding), still with the > same result. The only thing left to try is to get it running on a dedicated > machine rather than in a virtualbox. > > Amitabh > Same result on a dedicated machine too. Amitabh ___ 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: mkisofs increasing iso size by 100 MB
On Wed, Jan 11, 2012 at 9:49 PM, Jan Henrik Sylvester wrote: > On 01/-10/-28163 20:59, Amitabh Kant wrote: > >> I am trying to customise the bsdinstall auto script. I can mount the iso >> (amd64 arch / 9.0 RELEASE) and change the shell script as per my >> requirement. Once I try to re-create the iso file using mkisofs utility, >> the size of the final iso increases by 100 MB if -J (joliet) mode is used. >> If I remove the joliet mode, it still increases by around 97 MB. Even if >> no >> changes are made to any of the files, the result is same. >> >> The process I have followed is as follows: >> # mkdir /usr/iso >> # cd /usr/iso >> # dd if=/dev/cd0 of=org.iso bs=2048 >> # mdconfig -a -t vnode -f org.iso -u 0 >> # mount_cd9660 /dev/md0 /mnt >> # mkdir staging >> # cd staging >> # rsync -a /mnt/ . >> With Joliet mode >> # mkisofs -J -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o >> /usr/iso/my_custom.iso . >> Without Joliet mode >> # mkisofs -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o >> /usr/iso/my_custom1.iso . >> >> The original iso is 612M, custom.iso is 712M and custom1.iso is 709M. >> >> System details: FreeBSD amd64 9.0 RELEASE running inside a virtualbox with >> 2GB RAM. >> >> Where am I going wrong? >> > > There are many hardlinked files on the iso images. By the procedure above, > you have them included multiple times. > > From the rsync manpage: "Note that -a does not preserve hardlinks, because > finding multiply-linked files is expensive. You must separately specify > -H." > > You will probably want "-cache-inodes" for mkisofs as well (and maybe > other options). Or you could look at src/release/amd64/mkisoimages.**sh > for the use of "makefs -t cd9660". > > Cheers, > Jan Henrik > Tried -H with rsync and -cache-inodes in mkisofs. Saw the mkisoimages.sh and used the same parameters (at least to my understanding), still with the same result. The only thing left to try is to get it running on a dedicated machine rather than in a virtualbox. Amitabh ___ 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: mkisofs increasing iso size by 100 MB
On 01/-10/-28163 20:59, Amitabh Kant wrote: I am trying to customise the bsdinstall auto script. I can mount the iso (amd64 arch / 9.0 RELEASE) and change the shell script as per my requirement. Once I try to re-create the iso file using mkisofs utility, the size of the final iso increases by 100 MB if -J (joliet) mode is used. If I remove the joliet mode, it still increases by around 97 MB. Even if no changes are made to any of the files, the result is same. The process I have followed is as follows: # mkdir /usr/iso # cd /usr/iso # dd if=/dev/cd0 of=org.iso bs=2048 # mdconfig -a -t vnode -f org.iso -u 0 # mount_cd9660 /dev/md0 /mnt # mkdir staging # cd staging # rsync -a /mnt/ . With Joliet mode # mkisofs -J -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o /usr/iso/my_custom.iso . Without Joliet mode # mkisofs -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o /usr/iso/my_custom1.iso . The original iso is 612M, custom.iso is 712M and custom1.iso is 709M. System details: FreeBSD amd64 9.0 RELEASE running inside a virtualbox with 2GB RAM. Where am I going wrong? There are many hardlinked files on the iso images. By the procedure above, you have them included multiple times. From the rsync manpage: "Note that -a does not preserve hardlinks, because finding multiply-linked files is expensive. You must separately specify -H." You will probably want "-cache-inodes" for mkisofs as well (and maybe other options). Or you could look at src/release/amd64/mkisoimages.sh for the use of "makefs -t cd9660". Cheers, Jan Henrik ___ 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"
mkisofs increasing iso size by 100 MB
I am trying to customise the bsdinstall auto script. I can mount the iso (amd64 arch / 9.0 RELEASE) and change the shell script as per my requirement. Once I try to re-create the iso file using mkisofs utility, the size of the final iso increases by 100 MB if -J (joliet) mode is used. If I remove the joliet mode, it still increases by around 97 MB. Even if no changes are made to any of the files, the result is same. The process I have followed is as follows: # mkdir /usr/iso # cd /usr/iso # dd if=/dev/cd0 of=org.iso bs=2048 # mdconfig -a -t vnode -f org.iso -u 0 # mount_cd9660 /dev/md0 /mnt # mkdir staging # cd staging # rsync -a /mnt/ . With Joliet mode # mkisofs -J -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o /usr/iso/my_custom.iso . Without Joliet mode # mkisofs -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o /usr/iso/my_custom1.iso . The original iso is 612M, custom.iso is 712M and custom1.iso is 709M. System details: FreeBSD amd64 9.0 RELEASE running inside a virtualbox with 2GB RAM. Where am I going wrong? Amitabh ___ 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: creating a bootable iso for raid BIOS flash
On Sun, 8 Jan 2012, the wise Polytropon wrote: Does this image boot successfully? Unfortunately this is also a no go. I think Intel has done something special to their iso's, considering that I'm missing 7MB of data. Regards, Marco -- Men have as exaggerated an idea of their rights as women have of their wrongs. -- Edgar W. Howe ___ 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: creating a bootable iso for raid BIOS flash
On Sun, 8 Jan 2012, the wise Polytropon wrote: Does this image boot successfully? I don't know yet because I've used all my cd-r's :-(. Within a few days I'm expecting some new cd-rw's and I'll let you know how things went. If you compare your ISO with the original one, file sizes should be the same for all files; are they? A reason could be that the original one contains some "metadata" that the creating program (which will very probably _not_ be mkisofs as you're using) may have stored there. Things like for example an application ID, copyright information, media name. Maybe the original program did use a different "mechanism" to create the ISO? You can easily add the file sizes inside the original ISO and compare them to your sources (which should be equal) and see where the difference comes from. I think it will be some file system metadata (remember that the ISO-9660 file system occupies "invisible" space within the ISO file). I compared the original iso from Intel with the one generated by me and I really can't see any differences. My generated one is 9MB, and 8 MB of metadata seems a lot to me, or isn't it?. Don't know how Intel makes his iso's. Regards, Marco -- From the moment I picked your book up until I put it down I was convulsed with laughter. Some day I intend reading it. -- Groucho Marx, from "The Book of Insults" ___ 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: creating a bootable iso for raid BIOS flash
On Sun, 8 Jan 2012 01:11:30 +0100 (CET), Marco Beishuizen wrote: > On Sun, 8 Jan 2012, the wise Polytropon wrote: > > > If this is depending on the name "[BOOT]", there are > > two ways to deal with special characters in file names, > > if you need to specify them on the command line: > > > > a) use escape sequences: > > -b \[BOOT\]/Bootable_HardDisk.img > > > > b) use quoting: > > -b "[BOOT]/Bootable_HardDisk.img" > > I used escape sequences and that works. The "no match" error is gone. By using [ and ], the shell tries to expand a regular expression where [BOOT] means "one of the letters B, O, or T; neither B/Bootable_HardDisk.img, O/Bootable_HardDisk.img or T/Bootable_HardDisk.img is present, so the shell fully correctly replies with "no match". (In a similar fashion, * and ? are interpreted by the shell.) > > Also read "man mkisofs" about the boot-related > > options, especially -b, where > > > > If the boot image is not an image of a floppy, you need to add > > one of the options: -hard-disk-boot or -no-emul-boot. If the > > system should not boot off the emulated disk, use -no-boot. > > > > is mentioned. Maybe consider using -G instead of -b? > > I tried the -G option and removed the -hard-disk-boot option and now it > created an iso without errors. The size is still 9MB though. I looked > inside the original iso and the one generated by me but I really can't see > any differences. Does this image boot successfully? If you compare your ISO with the original one, file sizes should be the same for all files; are they? A reason could be that the original one contains some "metadata" that the creating program (which will very probably _not_ be mkisofs as you're using) may have stored there. Things like for example an application ID, copyright information, media name. Maybe the original program did use a different "mechanism" to create the ISO? You can easily add the file sizes inside the original ISO and compare them to your sources (which should be equal) and see where the difference comes from. I think it will be some file system metadata (remember that the ISO-9660 file system occupies "invisible" space within the ISO file). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: creating a bootable iso for raid BIOS flash
On Sun, 8 Jan 2012, the wise Polytropon wrote: If this is depending on the name "[BOOT]", there are two ways to deal with special characters in file names, if you need to specify them on the command line: a) use escape sequences: -b \[BOOT\]/Bootable_HardDisk.img b) use quoting: -b "[BOOT]/Bootable_HardDisk.img" I used escape sequences and that works. The "no match" error is gone. Also read "man mkisofs" about the boot-related options, especially -b, where If the boot image is not an image of a floppy, you need to add one of the options: -hard-disk-boot or -no-emul-boot. If the system should not boot off the emulated disk, use -no-boot. is mentioned. Maybe consider using -G instead of -b? I tried the -G option and removed the -hard-disk-boot option and now it created an iso without errors. The size is still 9MB though. I looked inside the original iso and the one generated by me but I really can't see any differences. -- The future is a race between education and catastrophe. -- H. G. Wells ___ 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: creating a bootable iso for raid BIOS flash
On Fri, 6 Jan 2012 17:22:57 +0100 (CET), Marco Beishuizen wrote: > After that I tried to create the iso with: > root@yokozuna:/data2/tmp# mkisofs -r -J -b [BOOT]/Bootable_HardDisk.img > -hard-disk-boot -o raid.iso /data2/tmp > which gives an error: mkisofs: No match > > First I thought the directory name [BOOT] was weird so I changed this to > BOOT. Running mkisofs -r -J -b BOOT/Bootable_HardDisk.img -hard-disk-boot > -o raid.iso /data2/tmp creates an iso, but when I burn this to a cd it > doesn't boot. If this is depending on the name "[BOOT]", there are two ways to deal with special characters in file names, if you need to specify them on the command line: a) use escape sequences: -b \[BOOT\]/Bootable_HardDisk.img b) use quoting: -b "[BOOT]/Bootable_HardDisk.img" Also read "man mkisofs" about the boot-related options, especially -b, where If the boot image is not an image of a floppy, you need to add one of the options: -hard-disk-boot or -no-emul-boot. If the system should not boot off the emulated disk, use -no-boot. is mentioned. Maybe consider using -G instead of -b? > Strange thing also is the fact that the original iso has the size of > ~17MB, but the created iso by me is ~10MB. So it seems I'm missing some > files. You can mount the ISO you've generated and look inside to find out which files may be missing, or if there are differences in file sizes. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: SSH Access To Live CD? (Was Re: FBSD-9.0-RC3 Disk 1 ISO Bootable?)
Здравствуйте, Drew. Вы писали 6 января 2012 г., 23:44:28: DT> On 1/6/2012 12:07 PM, Al Plant wrote: >> per...@pluto.rain.com wrote: >>> Al Plant wrote: >>> I accessed the sshd from the new install screen as an option when I loaded it on the test box. I had to set up the lan manually to first get it up. Then you should be able to use ssh. >>> >>> I take it you either arranged for ssh to accept a direct root login, >>> or added a non-root username. Does the new installer do one of >>> these automatically, or is there more manual configuration involved? >> >> BSD Installer asks if you want to install sshd and click yes. Later >> you can go to another box on the lan and use the user account to ssh >> into the new box and su to root. This feature has been on the installs >> for a while. I used it on sysinstall on 7.*. DT> OK, so you didn't actually install remotely via ssh. You installed DT> locally and let the installer configure sshd for your new install and it DT> was available after you rebooted into your new install. DT> I'd like to actually be able to install via ssh. Basically I'd like ssh DT> access to the Live CD so I could partition my drives for zfs prior to DT> installing. And I'd like to do it from a computer that's connected to DT> the web so I can read and copy/paste examples. DT> Cheers, DT> Drew mfsBSD - is interesting project, that allow you to install/ reinstall system remotely! -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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"
SSH Access To Live CD? (Was Re: FBSD-9.0-RC3 Disk 1 ISO Bootable?)
On 1/6/2012 12:07 PM, Al Plant wrote: per...@pluto.rain.com wrote: Al Plant wrote: I accessed the sshd from the new install screen as an option when I loaded it on the test box. I had to set up the lan manually to first get it up. Then you should be able to use ssh. I take it you either arranged for ssh to accept a direct root login, or added a non-root username. Does the new installer do one of these automatically, or is there more manual configuration involved? BSD Installer asks if you want to install sshd and click yes. Later you can go to another box on the lan and use the user account to ssh into the new box and su to root. This feature has been on the installs for a while. I used it on sysinstall on 7.*. OK, so you didn't actually install remotely via ssh. You installed locally and let the installer configure sshd for your new install and it was available after you rebooted into your new install. I'd like to actually be able to install via ssh. Basically I'd like ssh access to the Live CD so I could partition my drives for zfs prior to installing. And I'd like to do it from a computer that's connected to the web so I can read and copy/paste examples. Cheers, Drew -- Like card tricks? Visit The Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.com ___ 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-9.0-RC3 Disk 1 ISO Bootable?
per...@pluto.rain.com wrote: Al Plant wrote: I accessed the sshd from the new install screen as an option when I loaded it on the test box. I had to set up the lan manually to first get it up. Then you should be able to use ssh. I take it you either arranged for ssh to accept a direct root login, or added a non-root username. Does the new installer do one of these automatically, or is there more manual configuration involved? ___ 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" Aloha, BSD Installer asks if you want to install sshd and click yes. Later you can go to another box on the lan and use the user account to ssh into the new box and su to root. This feature has been on the installs for a while. I used it on sysinstall on 7.*. -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + < 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"
creating a bootable iso for raid BIOS flash
Hi, I have an Intel SRCU42X raid controller that currently has firmware version 414D. The bios flash was done by a "system update package", from Intel which is an iso file that you can burn to a cd. The upgrade to 414D went fine. But the newest firmware version is 414I and is not available as a bootable iso, only as a 414I.rom file (windows only etc.). So I thought: lets alter the 414D iso to the newest 414I iso, and make a new bootable iso. But this was harder than I thought. I extracted the original iso file with file-roller and replaced the 414D.rom file with 414I.rom, and modified the .bat-files references from 414D to 414I. The files and directories in the original iso are: -rwxr-xr-x 1 marco wheel 7828 Feb 9 2006 LICENSE.TXT drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCS16 drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCS28X drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCU41L drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCU42E drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCU42L drwxr-xr-x 2 marco wheel 512 Jan 6 11:24 SRCU42X drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCZCRX drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SROMB42E -rwxr-xr-x 1 marco wheel 1207 Aug 23 2004 SUP.BAT -rwxr-xr-x 1 marco wheel 3732 Feb 11 2006 SUP.TXT -rwxr-xr-x 1 marco wheel 4350 Mar 10 2006 SUP_Release_note.txt -rwxr-xr-x 1 marco wheel 5479 Feb 10 2006 UPDATE.BAT -rwxr-xr-x 1 marco wheel 244 Jan 6 11:25 VER_LOAD.BAT drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 [BOOT] The SRCU42X directory contains the 414I.rom file, an irflash.exe update utility and a run.bat batch file (running irflash.exe with reference to the .rom file). The [BOOT] directory contains one file: Bootable_HardDisk.img. After that I tried to create the iso with: root@yokozuna:/data2/tmp# mkisofs -r -J -b [BOOT]/Bootable_HardDisk.img -hard-disk-boot -o raid.iso /data2/tmp which gives an error: mkisofs: No match First I thought the directory name [BOOT] was weird so I changed this to BOOT. Running mkisofs -r -J -b BOOT/Bootable_HardDisk.img -hard-disk-boot -o raid.iso /data2/tmp creates an iso, but when I burn this to a cd it doesn't boot. Strange thing also is the fact that the original iso has the size of ~17MB, but the created iso by me is ~10MB. So it seems I'm missing some files. So what am I doing wrong and what is the correct commandline to create a bootable iso for flashing a raid controller bios? Thanks, Marco -- If I promised you the moon and the stars, would you believe it? -- Alan Parsons Project ___ 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-9.0-RC3 Disk 1 ISO Bootable?
Al Plant wrote: > I accessed the sshd from the new install screen as an option when > I loaded it on the test box. I had to set up the lan manually to > first get it up. Then you should be able to use ssh. I take it you either arranged for ssh to accept a direct root login, or added a non-root username. Does the new installer do one of these automatically, or is there more manual configuration involved? ___ 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-9.0-RC3 Disk 1 ISO Bootable?
Drew Tomlinson wrote: On 1/4/2012 8:01 PM, R Skinner wrote: On 01/05/12 13:23, Drew Tomlinson wrote: I downloaded FreeBSD-9.0-RC3-amd64-disc1.iso <ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso> and burned the image to CD. However the CD does not boot. Just wanted to confirm that it is supposed to be bootable. Also, is there a DVD version? I don't have many CDs around my house but plenty of DVDs. :) Hi Drew, and welcome to FreeBSD. How did you 'burn' the disc? As an iso image (in Windows) you can open any burning program and tell it to burn it as is; you don't need to extract any contents. This is the usual problem if it won't boot. I used the Windows image burning tool on the one that didn't work. However I tried on another PC that had Nero Burning ROM. That one worked. Now I just wish the boot disk had an apparent way to enable ssh so I could install from another PC while browsing the web. [snip] Thanks, Drew I accessed the sshd from the new install screen as an option when I loaded it on the test box. I had to set up the lan manually to first get it up. Then you should be able to use ssh. -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + < 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"
Re: FBSD-9.0-RC3 Disk 1 ISO Bootable?
Chris wrote: Can't speak for the 64 bit but the I386 does. As for a DVD, look for that at the release. Chris Sent from my HTC. - Reply message - From: "Drew Tomlinson" Date: Wed, Jan 4, 2012 9:23 pm Subject: FBSD-9.0-RC3 Disk 1 ISO Bootable? To: "FreeBSD Questions" I downloaded FreeBSD-9.0-RC3-amd64-disc1.iso <ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso> and burned the image to CD. However the CD does not boot. Just wanted to confirm that it is supposed to be bootable. Also, is there a DVD version? I don't have many CDs around my house but plenty of DVDs. :) Thanks, Drew <ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso> ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions Aloha Drew, I made a DVD of i386 10.0 and it works fine too. Haven't tried the 64. Even the new install screen worked the first time for me. Amazing. Da guys did a good job. ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + < 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"
Re: FBSD-9.0-RC3 Disk 1 ISO Bootable?
On 1/4/2012 8:01 PM, R Skinner wrote: On 01/05/12 13:23, Drew Tomlinson wrote: I downloaded FreeBSD-9.0-RC3-amd64-disc1.iso <ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso> and burned the image to CD. However the CD does not boot. Just wanted to confirm that it is supposed to be bootable. Also, is there a DVD version? I don't have many CDs around my house but plenty of DVDs. :) Hi Drew, and welcome to FreeBSD. How did you 'burn' the disc? As an iso image (in Windows) you can open any burning program and tell it to burn it as is; you don't need to extract any contents. This is the usual problem if it won't boot. I used the Windows image burning tool on the one that didn't work. However I tried on another PC that had Nero Burning ROM. That one worked. Now I just wish the boot disk had an apparent way to enable ssh so I could install from another PC while browsing the web. [snip] Thanks, Drew -- Like card tricks? Visit The Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.com ___ 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-9.0-RC3 Disk 1 ISO Bootable?
On Thu, Jan 5, 2012 at 8:53 AM, Drew Tomlinson wrote: > I downloaded FreeBSD-9.0-RC3-amd64-disc1.**iso <ftp://ftp.freebsd.org/pub/ > **FreeBSD/releases/amd64/amd64/**ISO-IMAGES/9.0/FreeBSD-9.0-** > RC3-amd64-disc1.iso<ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso>> > and burned the image to CD. However the CD does not boot. Just wanted to > confirm that it is supposed to be bootable. > > Also, is there a DVD version? I don't have many CDs around my house but > plenty of DVDs. :) > > Thanks, > > Drew > <ftp://ftp.freebsd.org/pub/**FreeBSD/releases/amd64/amd64/** > ISO-IMAGES/9.0/FreeBSD-9.0-**RC3-amd64-disc1.iso<ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso>> > > > Yes, it's bootable. I did install a test install couple of days ago using amd64 arch. Amitabh ___ 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-9.0-RC3 Disk 1 ISO Bootable?
On 01/05/12 13:23, Drew Tomlinson wrote: I downloaded FreeBSD-9.0-RC3-amd64-disc1.iso <ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso> and burned the image to CD. However the CD does not boot. Just wanted to confirm that it is supposed to be bootable. Also, is there a DVD version? I don't have many CDs around my house but plenty of DVDs. :) Hi Drew, and welcome to FreeBSD. How did you 'burn' the disc? As an iso image (in Windows) you can open any burning program and tell it to burn it as is; you don't need to extract any contents. This is the usual problem if it won't boot. Alternatively, you can try making an installer on a usb disk. I'd recommend at least a 2Gb stick, preferably 4G. See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall-pre.html section 3.3.5. HTH ___ 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-9.0-RC3 Disk 1 ISO Bootable?
Can't speak for the 64 bit but the I386 does. As for a DVD, look for that at the release. Chris Sent from my HTC. - Reply message - From: "Drew Tomlinson" Date: Wed, Jan 4, 2012 9:23 pm Subject: FBSD-9.0-RC3 Disk 1 ISO Bootable? To: "FreeBSD Questions" I downloaded FreeBSD-9.0-RC3-amd64-disc1.iso <ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso> and burned the image to CD. However the CD does not boot. Just wanted to confirm that it is supposed to be bootable. Also, is there a DVD version? I don't have many CDs around my house but plenty of DVDs. :) Thanks, Drew <ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso> -- Like card tricks? Visit The Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.com ___ 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"
FBSD-9.0-RC3 Disk 1 ISO Bootable?
I downloaded FreeBSD-9.0-RC3-amd64-disc1.iso <ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso> and burned the image to CD. However the CD does not boot. Just wanted to confirm that it is supposed to be bootable. Also, is there a DVD version? I don't have many CDs around my house but plenty of DVDs. :) Thanks, Drew <ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/FreeBSD-9.0-RC3-amd64-disc1.iso> -- Like card tricks? Visit The Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.com ___ 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: torrent file for FreeBSD iso
On Sun, 18 Dec 2011 14:35:55 +0200 Коньков Евгений wrote: > It will be very, very handy to put here .torrent file for download > FreeBSD .iso > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.0/ Torrents can already be found here: http://torrents.freebsd.org:8080/ Regards, Andreas -- GnuPG key : 0x2A573565|http://www.gnupg.org/howtos/de/ Fingerprint: 925D 2089 0BF9 8DE5 9166 33BB F0FD CD37 2A57 3565 pgpYqV9X6HVJx.pgp Description: PGP signature
torrent file for FreeBSD iso
It will be very, very handy to put here .torrent file for download FreeBSD .iso ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.0/ Thank you -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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: get rel 9.0 iso
I could build one kernel that would support the hardware on both computers, or one kernel for each computer. This would be the USB-stick i386 install. I would also have FreeBSD 9.0 amd64 on the new computer hard drive; would put the system source and ports tree on the hard-drive installation. I might put /home together with root and /usr on the main (USB-stick installation) partition. X Window manager would be IceWM. FreeBSD itself can run comfortably in well under 256 MB RAM. Resource hogs are the big applications: KDE, GNOME, bigger web browsers, multimedia, Adobe Flash Player, printers. Servers, not needing all the fancy stuff, can be set up on old computers as long as they're in good condition. By printers, I mean not only CUPS, but hplip which depends on cups. On BETA1, hplip build failed in cups because of undefined variable, I believe. Other failed port was fuse. On the computer from 2001, FreeBSD 8.1 and 8.2 /var got over 800 MB; I became nervous as /var data grew during the freebsd-update from 8.1 to 8.2. Most iso-downloadable (CD or DVD) Linux distributions now require 512 MB RAM or more; I believe PC-BSD requires at least 512 MB RAM. Tom ___ 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: get rel 9.0 iso
On Sun, 11 Sep 2011 04:11:26 + (GMT), Thomas Mueller wrote: > To build FreeBSD 9.0 on USB stick for the old computer, host > computer would be new amd64, cross-compiling for i386. Yes, in this case you would need to cross-compile. > I see default /var partition size for new FreeBSD installations > was to be 4 GB, so I might be safer with 16 GB rather than 8 GB > USB stick, even though there would be no need to install system > source and ports tree on the USB stick. Those would have been installed on the /usr partition, not on /var. I think 8 GB might be a quite huge partition, but that will depend on what you intend to use your server for. In some cases /var won't get bigger than 1 GB, on other cases it might fill up quite quickly. % df -h /var Filesystem SizeUsed Avail Capacity Mounted on /dev/ad4s1e989M133M776M15%/var This is an example from my home system - you can see that /var is hardly used. > But I had already decided that I was not going to have > separate partitions for /tmp, /var and /usr, but would > want a separate partition for /home, except possibly > on a USB stick. That's a good idea, so you can get rid of partition size calculations. But note that some temporary process might fill /tmp and therefore affect the _whole_ partition that also contains /usr. But maybe that won't be a problem as you put /home somewhere else. > Now it looks like FreeBSD 9.0-to-be is pushing the idea > of installing on GPT; even the memstick installation disk, > where traditional MBR partitioning scheme would fit > comfortably, uses GPT. You can easily apply GTP partitions for the same purpose, e. g. da0p1 for / (including /tmp, /var and /usr subtrees) and da0p2 for /home if you want them on _one_ media - or put da0p1 covering the whole stick to be mounted as /, and da1p1 (second USB media) for /home. > I could build one kernel that would support the hardware > on both computers, or one kernel for each computer. One for each, as you probably will use AMD64 kernel on the "bigger" machine. But you still _can_ use i386 on both of them except you intendedly _require_ AMD64 functionality on the "bigger" machine. > FreeBSD itself can run comfortably in well under 256 MB RAM. Yes, the OS has no problem booting fast even on such limited hardware. > Resource hogs are the big applications: KDE, GNOME, bigger > web browsers, multimedia, Adobe Flash Player, printers. Uhm... printers??? Oh, maybe CUPS, yes. :-) You can _still_ build workstation systems on limited hardware, but you have to be _very_ picky about the applications you use. For example, I have a 300 MHz P2 workstation that runs XFCE 3, Opera 8, mplayer (compiled because of getting the best optimization!), OpenOffice 2, xmms and LaTeX. This system runs well and is still quite usable. > Servers, not needing all the fancy stuff, can be set up on > old computers as long as they're in good condition. I completely agree, as I'm following this philosophy myself. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: get rel 9.0 iso
To build FreeBSD 9.0 on USB stick for the old computer, host computer would be new amd64, cross-compiling for i386. I see default /var partition size for new FreeBSD installations was to be 4 GB, so I might be safer with 16 GB rather than 8 GB USB stick, even though there would be no need to install system source and ports tree on the USB stick. But I had already decided that I was not going to have separate partitions for /tmp, /var and /usr, but would want a separate partition for /home, except possibly on a USB stick. Now it looks like FreeBSD 9.0-to-be is pushing the idea of installing on GPT; even the memstick installation disk, where traditional MBR partitioning scheme would fit comfortably, uses GPT. I could build one kernel that would support the hardware on both computers, or one kernel for each computer. FreeBSD itself can run comfortably in well under 256 MB RAM. Resource hogs are the big applications: KDE, GNOME, bigger web browsers, multimedia, Adobe Flash Player, printers. Servers, not needing all the fancy stuff, can be set up on old computers as long as they're in good condition. Tom ___ 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: get rel 9.0 iso
On Fri, 9 Sep 2011 11:29:28 + (GMT), Thomas Mueller wrote: > FreeBSD 8.2 slice on old computer is about 12 GB with 1.3 GB > free; RAM is 256 MB. Depending on your particular software needs, a full FreeBSD installation _with_ programs can fit onto an 8 GB slice (or disk) with 50% free space. :-) > So a better way to upgrade to 9.0 might be to build on the > new computer onto a 16 GB USB stick, I wouldn't even need > to keep the ports tree or system source on the USB stick. You should just pay attention to building parameters (see "man make.conf" and "man src.conf") to keep the system in a minimal state, and make sure not to tie it to the hardware characteristics (especially CPU) of the building system. > I assume booting a USB stick with Plop would work on the > 2001 computer with FreeBSD as it did with NetBSD 4.0.1 > and NetBSD-current. Just try it, it should be possible. > Due to insufficient RAM and insufficient disk space for > the bigger packages/ports, I feel like I'm at the end > of the line with FreeBSD, NetBSD too, on the 2001 > computer; would need to build on my new computer. Yes, even if the system runs flawlessly, upgrading gets more and more complicated, so maybe migrating to a new machine would be better here. Just an addition: I still run a Pentium (yes, no numbers after the name!) with 150 MHz and 128 MB RAM here as a small server, using FreeBSD/x86 8.2. I did install from CD and then via Internet. Packages are fine to use in this case (see "man pkg_add"). Depending on _what_ the server does, even this over-obsoleted configuration might fit perfectly well! So I do _no_ claim it's impossible to run and install FreeBSD on older hardware. In fact, it _IS_ possible, maybe just a bit complicated in special cases (e. g. as the P1 server I mentioned does not even have USB, only a CD-ROM drive), but _POSSIBLE_, which may be fully sufficient in some cases. So "old iron" can still be a valueable citizen of the IT infrastructure. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: get rel 9.0 iso
On Thu, 8 Sep 2011 10:31:57 + (GMT), Thomas Mueller wrote: > Is that pc that can't boot from memstick old? I have an old > PC, dating to July 2001, that can't boot directly from USB, > but can boot from USB with the help of Plop (http://www.plop.at/) > boot manager. If it doesn't boot directly (even my old 2005 PC has problems with that) try to use PLOP to boot the memstick image. You can easily directly copy it to a USB stick which would then be a bootable media. > I think dvd1.iso was < 700 MB and would therefore fit on a CD? No that would have been the CD#1; the traditional set of 4 CDs comes with CD#1 installation, CD#2 Live system (can also be used to install via Internet), CD#3 and CD#4 for packages. Those CD images are named "disc" instead of "dvd". You can find them for the current release at ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/8.2/ FreeBSD-8.2-RELEASE-i386-bootonly.iso 48,108 KB -> CD FreeBSD-8.2-RELEASE-i386-disc1.iso668,928 KB -> CD FreeBSD-8.2-RELEASE-i386-dvd1.iso.xz2,017,993 KB -> DVD FreeBSD-8.2-RELEASE-i386-livefs.iso 258,216 KB -> CD FreeBSD-8.2-RELEASE-i386-memstick.img 936,150 KB -> USB Those set of images is typically generated for a RELEASE, not for CURRENT (and its BETA and RC stages). In your case, the 9.0-BETA2 "bootonly" CD can be used to boot the system and to start the installation via Internet (in case you don't have the option to boot from DVD). > My computer from July 2001 had CD-RW but no DVD. This was > one of the factors pushing me to buy parts for a new computer. In this case, I'd simply use CD because it seems to be less trouble (just in case USB boot via PLOP doesn't work). You can also go the following road: Install 8.2-RELEASE, do a source upgrade to 9.0-BETA and update your system from source. You'll find details in the FreeBSD Handbook and in /usr/src/Makefile's comment header. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: get rel 9.0 iso
> > The dvd1.iso file is less than 700mb and would fit on a standard cd. But >> the point is you do not install from a .iso file. The .iso file is a >> compressed file and when you uncompress it it's way to large to fit on a >> standard cd but will fit on a dvd. Thats why its named dvd1.iso. > > > __**_ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions<http://lists.freebsd.org/mailman/listinfo/freebsd-questions> > To unsubscribe, send any mail to "freebsd-questions-** > unsubscr...@freebsd.org " > I just burned the dvd1.iso to a cd-r this morning and used it to install to a laptop. Worked great. I think there is some confusion about compression on the iso file. There is none on the file in question. Previous DVD iso files have been compressed, which gives it a filename of dvd1.iso.xz. The 9.0BETA2 file is not compressed though. Mike Kelly ___ 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: get rel 9.0 iso
"Thomas Mueller I think dvd1.iso was < 700 MB and would therefore fit on a CD? I just checked, it was < 700 MB: Index of ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/ Up to higher level directory NameSizeLast Modified File:CHECKSUM.MD5 1 KB09/01/1100:00:00 File:CHECKSUM.SHA2561 KB09/01/1100:00:00 File:FreeBSD-9.0-BETA2-amd64-bootonly.iso 142490 KB 08/31/11 18:45:00 File:FreeBSD-9.0-BETA2-amd64-dvd1.iso 621926 KB 08/31/1118:43:00 File:FreeBSD-9.0-BETA2-amd64-memstick.img 666990 KB 08/31/11 18:46:00 (end of quote) My computer from July 2001 had CD-RW but no DVD. This was one of the factors pushing me to buy parts for a new computer. FreeBSD 8.2 slice on old computer is about 12 GB with 1.3 GB free; RAM is 256 MB. So a better way to upgrade to 9.0 might be to build on the new computer onto a 16 GB USB stick, I wouldn't even need to keep the ports tree or system source on the USB stick. I assume booting a USB stick with Plop would work on the 2001 computer with FreeBSD as it did with NetBSD 4.0.1 and NetBSD-current. Due to insufficient RAM and insufficient disk space for the bigger packages/ports, I feel like I'm at the end of the line with FreeBSD, NetBSD too, on the 2001 computer; would need to build on my new computer. Tom The dvd1.iso file is less than 700mb and would fit on a standard cd. But the point is you do not install from a .iso file. The .iso file is a compressed file and when you uncompress it it's way to large to fit on a standard cd but will fit on a dvd. Thats why its named dvd1.iso. ___ 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: get rel 9.0 iso
I think dvd1.iso was < 700 MB and would therefore fit on a CD? I just checked, it was < 700 MB: Index of ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/ Up to higher level directory NameSizeLast Modified File:CHECKSUM.MD5 1 KB09/01/1100:00:00 File:CHECKSUM.SHA2561 KB09/01/1100:00:00 File:FreeBSD-9.0-BETA2-amd64-bootonly.iso 142490 KB 08/31/11 18:45:00 File:FreeBSD-9.0-BETA2-amd64-dvd1.iso 621926 KB 08/31/1118:43:00 File:FreeBSD-9.0-BETA2-amd64-memstick.img 666990 KB 08/31/11 18:46:00 (end of quote) My computer from July 2001 had CD-RW but no DVD. This was one of the factors pushing me to buy parts for a new computer. FreeBSD 8.2 slice on old computer is about 12 GB with 1.3 GB free; RAM is 256 MB. So a better way to upgrade to 9.0 might be to build on the new computer onto a 16 GB USB stick, I wouldn't even need to keep the ports tree or system source on the USB stick. I assume booting a USB stick with Plop would work on the 2001 computer with FreeBSD as it did with NetBSD 4.0.1 and NetBSD-current. Due to insufficient RAM and insufficient disk space for the bigger packages/ports, I feel like I'm at the end of the line with FreeBSD, NetBSD too, on the 2001 computer; would need to build on my new computer. Tom ___ 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: get rel 9.0 iso
> On Wed, 07 Sep 2011 20:43:47 -0400, Fbsd8 wrote:
> > No rel 9.0 i386 disc1.iso anywhere. My pc can not boot from memstick.
Polytropon responded:
> ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/
> ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.0/
> A FreeBSD-9.0-BETA2-{i386|amd64}-bootonly.iso and
> FreeBSD-9.0-BETA2-{i386|amd64}-dvd1.iso are available.
> Note that this is "just" a BETA, _not_ a RELEASE.
> If your system can boot at least from CD, the bootonly should
> be fine (if you can then continue installation via Internet);
> if you don't have a machine connected, the DVD #1 will be a
> good tool (as a DVD-capable drive should be assumed as common
> equipment today).
Is that pc that can't boot from memstick old? I have an old PC, dating to July
2001, that can't boot directly from USB, but can boot from USB with the help of
Plop (http://www.plop.at/) boot manager.
I think dvd1.iso was < 700 MB and would therefore fit on a CD?
My computer from July 2001 had CD-RW but no DVD. This was one of the factors
pushing me to buy parts for a new computer.
Tom
___
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: get rel 9.0 iso
On Wed, 07 Sep 2011 20:43:47 -0400, Fbsd8 wrote:
> No rel 9.0 i386 disc1.iso anywhere. My pc can not boot from memstick.
ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/
ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/i386/ISO-IMAGES/9.0/
A FreeBSD-9.0-BETA2-{i386|amd64}-bootonly.iso and
FreeBSD-9.0-BETA2-{i386|amd64}-dvd1.iso are available.
Note that this is "just" a BETA, _not_ a RELEASE.
If your system can boot at least from CD, the bootonly should
be fine (if you can then continue installation via Internet);
if you don't have a machine connected, the DVD #1 will be a
good tool (as a DVD-capable drive should be assumed as common
equipment today).
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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: get rel 9.0 iso
Polytropon wrote: On Wed, 07 Sep 2011 19:59:05 -0400, Fbsd8 wrote: What is the ftp url to fetch the most current release 9.0 .iso file? FreeBSD-9.0 hasn't been released yet. In order to obtain a current snapshot, check the FTP server: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201107/ You'll find FreeBSD-9.0-CURRENT-201107-ia64-bootonly.iso and FreeBSD-9.0-CURRENT-201107-ia64-release.iso here, as well as a memory stick image. In ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ you'll also find ISO images for amd64 and i386 architectures. The current releases can be found on the FTP server at ftp://ftp.freebsd.org/pub/FreeBS/releases/i386/ISO-IMAGE/ and ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/ as well as ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/ and ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/ respectively. Those are the releases. The current one is 8.2. For details, see: http://www.freebsd.org/relnotes/CURRENT/relnotes/index.html No rel 9.0 i386 disc1.iso anywhere. My pc can not boot from memstick. ___ 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: get rel 9.0 iso
On Wed, Sep 7, 2011 at 4:59 PM, Fbsd8 wrote: > What is the ftp url to fetch the most current release 9.0 .iso file? 9.0-RELEASE is not available yet. 9.0-BETA2 has been annouced today though: http://www.freebsd.org/where.html#helptest this will also be available on mirrors shortly... -pete -- pete wright www.nycbug.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"
Re: get rel 9.0 iso
On Wed, 07 Sep 2011 19:59:05 -0400, Fbsd8 wrote: > What is the ftp url to fetch the most current release 9.0 .iso file? FreeBSD-9.0 hasn't been released yet. In order to obtain a current snapshot, check the FTP server: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201107/ You'll find FreeBSD-9.0-CURRENT-201107-ia64-bootonly.iso and FreeBSD-9.0-CURRENT-201107-ia64-release.iso here, as well as a memory stick image. In ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201105/ you'll also find ISO images for amd64 and i386 architectures. The current releases can be found on the FTP server at ftp://ftp.freebsd.org/pub/FreeBS/releases/i386/ISO-IMAGE/ and ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/ as well as ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/ and ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/ respectively. Those are the releases. The current one is 8.2. For details, see: http://www.freebsd.org/relnotes/CURRENT/relnotes/index.html -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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"
get rel 9.0 iso
What is the ftp url to fetch the most current release 9.0 .iso 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: Scritping sysinstall and custom iso
On Sun, 28 Aug 2011 17:20:34 +0530, Amitabh Kant wrote: > All the commands run fine and I am able to generate an iso. Now, couple of > questions that have confused me: > a) Where do I place install.cfg file for sysinstall to read without any user > intervention? In the root directory of the disc1 layout or inside > 8.2-Release / other sub directory? According to /usr/src/usr.sbin/sysinstall/install.cfg's location from which one would conclude that the sysinstall would be in /usr/sbin of the CD (as well as installed on the disk), I would assume install.cfg to be in the same directory as the sysinstall program itself - /usr/sbin. But it could also be /stand... > b) Is there a place where I can get a sample install.cfg with all the > options explained? All I could find were different examples tailored to > specific situations, most of them towards PXE boot. The file /usr/src/usr.sbin/sysinstall/install.cfg does contain some comments for explaination. Also see "man 8 sysinstall" for the "SCRIPT SYNTAX" section. > c) Is it necessary to define every step in install.cfg? I would like to keep > disk partition / label and network configuration dialogs available (root > password if necessary), while setting values for all other user dialogs and > screens. I don't think it is neccessary (as assumed by the "incomplete" install.cfg mentioned above), but consult the documentation to be sure. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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"
Scritping sysinstall and custom iso
Hello I am trying to create a custom FreeBSD iso which will automate most of the steps asked in a standard installation using sysinstall. While "make release" is available, I was trying to modify disc1 iso, as it seems that I only need to have install.cfg for automating sysinstall. I downloaded the disc1 iso file (8.2 amd64 arch), created a memory disk using mdconfig, and then mounted the disk. The commands that I have run are: mdconfig -a -t vnode -f org.iso -u 0 mount_cd9660 /dev/md0 /mnt mkdir custom_iso cd custom_iso rsync -a /mnt/ . Once I am done with the changes, I plan to run the following command to recreate the iso mkisofs -J -R -V CustomBSD -no-emul-boot -b boot/cdboot -iso-level 3 -o /usr/home/isotest/custom.iso . All the commands run fine and I am able to generate an iso. Now, couple of questions that have confused me: a) Where do I place install.cfg file for sysinstall to read without any user intervention? In the root directory of the disc1 layout or inside 8.2-Release / other sub directory? b) Is there a place where I can get a sample install.cfg with all the options explained? All I could find were different examples tailored to specific situations, most of them towards PXE boot. c) Is it necessary to define every step in install.cfg? I would like to keep disk partition / label and network configuration dialogs available (root password if necessary), while setting values for all other user dialogs and screens. Amitabh Kant ___ 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: ISO images
"Michael Ross" wrote: > Am 17.08.2011, 15:59 Uhr, schrieb Julian H. Stacey : > > > Hi, > > Reference: > >> From: "Michael Ross" > >> Date: Wed, 17 Aug 2011 15:28:41 +0200 > >> Message-id: > > > > "Michael Ross" wrote: > >> Am 17.08.2011, 14:55 Uhr, schrieb Julian H. Stacey : > >> > >> > Lars Eighner wrote: > >> > ftp protocol does not support command du, so one can't see size of > >> > > >>ftp://ftp.freebsd.orgpub/FreeBSD/ports/amd64/packages-8.2-release/All/ > >> > > >> > >> > >> My FTP client shows it at about 32GB total. > > > > Nice to be able to see that. Which client ? > > Do you know it get that ? Maybe it adds size of each file together ? > > > > ( I was using /usr/bin/ftp ) > > > > Cheers, > > Julian > > WinSCP on a Windows desktop. > > In ports there is ftp/lftp, which has a du command. Ah Thanks, building now, will be a luxury :-) > I don't know how they get the value, assume they do just that: ls each > directory and add up. > > Michael Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ 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: ISO images
Am 17.08.2011, 15:59 Uhr, schrieb Julian H. Stacey : Hi, Reference: From: "Michael Ross" Date: Wed, 17 Aug 2011 15:28:41 +0200 Message-id: "Michael Ross" wrote: Am 17.08.2011, 14:55 Uhr, schrieb Julian H. Stacey : > Lars Eighner wrote: > ftp protocol does not support command du, so one can't see size of > ftp://ftp.freebsd.orgpub/FreeBSD/ports/amd64/packages-8.2-release/All/ > My FTP client shows it at about 32GB total. Nice to be able to see that. Which client ? Do you know it get that ? Maybe it adds size of each file together ? ( I was using /usr/bin/ftp ) Cheers, Julian WinSCP on a Windows desktop. In ports there is ftp/lftp, which has a du command. I don't know how they get the value, assume they do just that: ls each directory and add up. Michael ___ 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: ISO images
"Julian H. Stacey" writes: > Hi, > Reference: >> From:"Michael Ross" >> Date:Wed, 17 Aug 2011 15:28:41 +0200 >> Message-id: > > "Michael Ross" wrote: >> Am 17.08.2011, 14:55 Uhr, schrieb Julian H. Stacey : >> >> > Lars Eighner wrote: >> > ftp protocol does not support command du, so one can't see size of >> >ftp://ftp.freebsd.orgpub/FreeBSD/ports/amd64/packages-8.2-release/All/ >> > >> >> >> My FTP client shows it at about 32GB total. > > Nice to be able to see that. Which client ? > Do you know it get that ? Maybe it adds size of each file together ? > > ( I was using /usr/bin/ftp ) ftp/lftp? It has `du' command. lftp ftp.freebsd.org:/pub/FreeBSD/ports/amd64> du -hs packages-8-stable/All 33G packages-8-stable/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: ISO images
Hi, Reference: > From: "Michael Ross" > Date: Wed, 17 Aug 2011 15:28:41 +0200 > Message-id: "Michael Ross" wrote: > Am 17.08.2011, 14:55 Uhr, schrieb Julian H. Stacey : > > > Lars Eighner wrote: > > ftp protocol does not support command du, so one can't see size of > > ftp://ftp.freebsd.orgpub/FreeBSD/ports/amd64/packages-8.2-release/All/ > > > > > My FTP client shows it at about 32GB total. Nice to be able to see that. Which client ? Do you know it get that ? Maybe it adds size of each file together ? ( I was using /usr/bin/ftp ) Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ 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: ISO images
Am 17.08.2011, 14:55 Uhr, schrieb Julian H. Stacey : Lars Eighner wrote: ftp protocol does not support command du, so one can't see size of ftp://ftp.freebsd.orgpub/FreeBSD/ports/amd64/packages-8.2-release/All/ My FTP client shows it at about 32GB total. Michael ___ 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: ISO images
On Wed, Aug 17, 2011 at 10:56:35AM +0100, Rui Silva typed: > Hi, > > I want to install FreeBSD for the first time but I have some doubts > regarding the ISO images. > > I have downloaded an ISO image (FreeBSD-8.2-RELEASE-i386-dvd1.iso) > via torrent, but soon realised that the packages collection was very > poor when compared to "ftp://ftp.freebsd.org/pub/FreeBSD/releases/ > i386/8.2-RELEASE/packages/" > > Is there any complete ISO image that includes all the packages I saw > in "ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.2-RELEASE/ > packages/"? That would be really nice. Not a direct answer, but after installation from the DVD you have, you can easily install any package from the ftp site by running pkg_add -r Ruben ___ 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: ISO images
Lars Eighner wrote: > On Wed, 17 Aug 2011, Rui Silva wrote: > > > Hi, > > > > I want to install FreeBSD for the first time but I have some doubts > > regarding > > the ISO images. > > > > I have downloaded an ISO image (FreeBSD-8.2-RELEASE-i386-dvd1.iso) via > > torrent, but soon realised that the packages collection was very poor when > > compared to > > "ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.2-RELEASE/packages/"; > > > > Is there any complete ISO image that includes all the packages I saw in > > "ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.2-RELEASE/packages/";? > > That > > would be really nice. > > Of course there is not because no media appropriate to an ISO image could > contain such an ISO. Rui, in case that's not clear enough, DVD are too Small Raw media sizes DVD self burnable media : 4.7 G http://www.berklix.com/~jhs/txt/cdroms.html Commercial bulk (film/movie) DVDs : 9 G. Blu ray, (rare expensive) : [2 x] 25 Gig http://en.wikipedia.org/wiki/Blu-ray_Disc ftp protocol does not support command du, so one can't see size of ftp://ftp.freebsd.orgpub/FreeBSD/ports/amd64/packages-8.2-release/All/ Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. ___ 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: ISO images
On Wed, Aug 17, 2011 at 10:56 AM, Rui Silva wrote: > Hi, > > I want to install FreeBSD for the first time but I have some doubts > regarding the ISO images. > > I have downloaded an ISO image (FreeBSD-8.2-RELEASE-i386-**dvd1.iso) via > torrent, but soon realised that the packages collection was very poor when > compared to "ftp://ftp.freebsd.org/pub/**FreeBSD/releases/i386/8.2-** > RELEASE/packages/<ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.2-RELEASE/packages/> > " > > Is there any complete ISO image that includes all the packages I saw in " > ftp://ftp.freebsd.org/pub/**FreeBSD/releases/i386/8.2-**RELEASE/packages/<ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.2-RELEASE/packages/>"? > That would be really nice. > you could fetch the DVD instead (but it will not have all packages bundled on one DVD) ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/8.2/ > > Thank you ;) > > Rui Silva > > > > > __**_ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-**questions<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"
Re: ISO images
On Wed, 17 Aug 2011, Rui Silva wrote: Hi, I want to install FreeBSD for the first time but I have some doubts regarding the ISO images. I have downloaded an ISO image (FreeBSD-8.2-RELEASE-i386-dvd1.iso) via torrent, but soon realised that the packages collection was very poor when compared to "ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.2-RELEASE/packages/"; Is there any complete ISO image that includes all the packages I saw in "ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.2-RELEASE/packages/";? That would be really nice. Of course there is not because no media appropriate to an ISO image could contain such an ISO. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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"
ISO images
Hi, I want to install FreeBSD for the first time but I have some doubts regarding the ISO images. I have downloaded an ISO image (FreeBSD-8.2-RELEASE-i386-dvd1.iso) via torrent, but soon realised that the packages collection was very poor when compared to "ftp://ftp.freebsd.org/pub/FreeBSD/releases/ i386/8.2-RELEASE/packages/" Is there any complete ISO image that includes all the packages I saw in "ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.2-RELEASE/ packages/"? That would be really nice. Thank you ;) Rui Silva ___ 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"
