floppy boot hangs
Hello, I am a new user trying to install freebsd 7.2 using floppies and ftp. I have reached the part where I should start getting an ftp download but it couldn't find the server I had selected. Now, the Options Editor tells me that Media Type is not yet set and I am not able to set it. It seems that Media Type cannot be set once you have buggered up the ftp download. My question: Is something I can do that will allow me to set the Media Type from the Options Editor or must I go through the whole boot process all over again? Regards, Dave. ___ 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: 5.25 floppy drive
Thanks to all. Solved. It was a multiple cause issue: 1st: BIOS Setting was incorrect (had to enable 1.2MB 5.25 rather than 3.5 which was it set to - an oversight in the firts place, that occured to me). 2nd: Cable issue: I had a combined cable (3.5 connector at the end and edge connector second but last. 3rd: in combination with 2nd: DS0 jumper issue. Anyway, I found a cable that had two edge connectors. In the end it turns out that the floppies that were lying in a drawer for 19 years, are producing read errors. I also learnt about fdcontrol. Floppy interface has changed significantly since Joerg Wunsch and Bruce Evans worked on them in the early FreeBSD days back in 1995 :) -- Christoph Am 01.10.2010 19:18, schrieb Warren Block: On Fri, 1 Oct 2010, Christoph Kukulies wrote: I'm in the need of reading some data from old 5.25 floppy media (1.2MB). I lent 2 drives from neighbour institutes at the university and after having recalled that the floppies have to be enabled in the BIOS I'm now seeing the fd0 device in dmesg (FreeBSD 8.0 RELEASE). I can do a dd if=/dev/fd0 of=/root/fd0.dmp The select light is lit, the head motor seems to get power but the spindle doesn't spin. Possibly a drive select issue. Some drives had jumpers or switches, some cables have flipped-around wires so the connectors are specific to one drive or another. If your cabling is straight-through with no funny business at the connectors, set the drive to DS0. If the cable has split out and flipped-over sections, DS1 should be set in the jumpers --but then it depends on which connector is used. ...I think, anyway, it's been a few years since I've had to use a 5.25. I tried that with two TEAC drives to no avail. Any clues what I may have forgotten? The drive is connected with the edge connector and the end is open. Does it need to be terminated? None that I've seen. ___ 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: 5.25 floppy drive
from Christoph Kukulies k...@kukulies.org: Thanks to all. Solved. It was a multiple cause issue: 1st: BIOS Setting was incorrect (had to enable 1.2MB 5.25 rather than 3.5 which was it set to - an oversight in the firts place, that occured to me). 2nd: Cable issue: I had a combined cable (3.5 connector at the end and edge connector second but last. 3rd: in combination with 2nd: DS0 jumper issue. Anyway, I found a cable that had two edge connectors. In the end it turns out that the floppies that were lying in a drawer for 19 years, are producing read errors. I also learnt about fdcontrol. Floppy interface has changed significantly since Joerg Wunsch and Bruce Evans worked on them in the early FreeBSD days back in 1995 :) -- Christoph Congratulations on solving your floppy problem, but I can understand your problems with floppies. They've gone bad with age for me too. I can read but not write, then I can't read and in most cases can't even reformat. FreeBSD installation sets structure (base.aa, base.ab, base.ac etc.) suggests that one could install from a big set of floppies, but there's no way I could get such a good set of floppies together. I think my 5.25 floppies and drive hold out better than the 3.5 floppies and drives. 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: 5.25 floppy drive
On Sat, 02 Oct 2010 10:50:00 + Thomas Mueller mueller6...@bellsouth.net articulated: from Christoph Kukulies k...@kukulies.org: Thanks to all. Solved. It was a multiple cause issue: 1st: BIOS Setting was incorrect (had to enable 1.2MB 5.25 rather than 3.5 which was it set to - an oversight in the firts place, that occured to me). 2nd: Cable issue: I had a combined cable (3.5 connector at the end and edge connector second but last. 3rd: in combination with 2nd: DS0 jumper issue. Anyway, I found a cable that had two edge connectors. In the end it turns out that the floppies that were lying in a drawer for 19 years, are producing read errors. I also learnt about fdcontrol. Floppy interface has changed significantly since Joerg Wunsch and Bruce Evans worked on them in the early FreeBSD days back in 1995 :) -- Christoph Congratulations on solving your floppy problem, but I can understand your problems with floppies. They've gone bad with age for me too. I can read but not write, then I can't read and in most cases can't even reformat. FreeBSD installation sets structure (base.aa, base.ab, base.ac etc.) suggests that one could install from a big set of floppies, but there's no way I could get such a good set of floppies together. I think my 5.25 floppies and drive hold out better than the 3.5 floppies and drives. I had a similar problem last year on a Windows platform when a local municipality asked to move the data from nearly 500 5.25 disks to CD. The disks were in storage since mid 1990. I located an external 5.25 disk drive, they are dirt cheap, and attempted to copy the data. Like you pointed out, the majority of the disks were severely damaged. I finally settled on Spin-Rite http://www.grc.com/spinrite.htm to repair the disks. I had used it before and was familiar with its workings. It took nearly a week for us to get the disks repaired and copied; however, with only a couple of exceptions, the job ended successfully. I cannot comment on 3.5 vs 5.25 disks, except to say good riddance to both formats. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: 5.25 floppy drive
Hi Christoph, In the end it turns out that the floppies that were lying in a drawer for 19 years, are producing read errors. Do NOT throw them out. I have a tool that can rescue near all data. http://berklix.com/~jhs/src/bsd/jhs/bin/public/valid/ Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text; Not HTML, quoted-printable base 64 spam formats. Avoid top posting, It cripples itemised cumulative responses. ___ 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
5.25 floppy drive
I'm in the need of reading some data from old 5.25 floppy media (1.2MB). I lent 2 drives from neighbour institutes at the university and after having recalled that the floppies have to be enabled in the BIOS I'm now seeing the fd0 device in dmesg (FreeBSD 8.0 RELEASE). I can do a dd if=/dev/fd0 of=/root/fd0.dmp The select light is lit, the head motor seems to get power but the spindle doesn't spin. I tried that with two TEAC drives to no avail. Any clues what I may have forgotten? The drive is connected with the edge connector and the end is open. Does it need to be terminated? -- Christoph ___ 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: 5.25 floppy drive
On Fri, 01 Oct 2010 15:04:40 +0200, Christoph Kukulies k...@kukulies.org wrote: I'm in the need of reading some data from old 5.25 floppy media (1.2MB). I lent 2 drives from neighbour institutes at the university and after having recalled that the floppies have to be enabled in the BIOS I'm now seeing the fd0 device in dmesg (FreeBSD 8.0 RELEASE). Similat to this? % dmesg | grep ^fd fdc0: floppy drive controller port 0x3f2-0x3f3,0x3f4-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: 1440-KB 3.5 drive on fdc0 drive 0 This is for a 3.5 drive of course, the 5.25's message should read similar. FreeBSD 7 here. I can do a dd if=/dev/fd0 of=/root/fd0.dmp The select light is lit, the head motor seems to get power but the spindle doesn't spin. I tried that with two TEAC drives to no avail. Strange, I would suspect drive electronics first... do you have a low end PC (DOS) to check the drives? The lowest level diagnosis tools are often the best. :-) Any clues what I may have forgotten? The drive is connected with the edge connector and the end is open. Sounds correct. Does it need to be terminated? No. The position on the cable selects which drive letter will be associated to a given drive; the one on the end is A:, the one on the middle is B:. A single drive is usually connected to the end of the cable. As the connector for 5.25 drive does have a gap, you can't wrongly connect it. The connector to the main board should also have a nose that prevents wrong cabling. Wrong cabling is indicated by a permanent (!) activity light on the drive. Instead of using dd, can you maybe access the drive using mount or the mtools (from ports)? If you encounter further problems, I can get a working drive and check here. I'm in a kind of working museum. :-) -- 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: 5.25 floppy drive
On Fri, 1 Oct 2010, Christoph Kukulies wrote: I'm in the need of reading some data from old 5.25 floppy media (1.2MB). I lent 2 drives from neighbour institutes at the university and after having recalled that the floppies have to be enabled in the BIOS I'm now seeing the fd0 device in dmesg (FreeBSD 8.0 RELEASE). I can do a dd if=/dev/fd0 of=/root/fd0.dmp The select light is lit, the head motor seems to get power but the spindle doesn't spin. Possibly a drive select issue. Some drives had jumpers or switches, some cables have flipped-around wires so the connectors are specific to one drive or another. If your cabling is straight-through with no funny business at the connectors, set the drive to DS0. If the cable has split out and flipped-over sections, DS1 should be set in the jumpers --but then it depends on which connector is used. ...I think, anyway, it's been a few years since I've had to use a 5.25. I tried that with two TEAC drives to no avail. Any clues what I may have forgotten? The drive is connected with the edge connector and the end is open. Does it need to be terminated? None that I've seen. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting from floppy to install 8.1
Thomas Mueller mueller6...@bellsouth.net wrote: Should I be able to do a network install of 8.1 using a 7.3 boot floppy set? (I'm not planning to set up zfs, at least initially.) ... I once net-installed FreeBSD using a boot CD from an earlier version; I think it was a disk one rather than boot-only ... If you use boot floppies, use only the two (or is it three?) needed to boot the install system. If I've understood the 7.3 set correctly it's now up to five: the initial boot, plus 3 for the kernel and one for the mfsroot image. I never used zfs, don't have big enough hard drive or enough RAM to justify zfs. Ditto, at least as to RAM (512MB, which I tend to think of as _huge_ -- after all, no one should ever need more than 640KB :) I still have a couple of _hard drives_ that are only 10MB each sitting around somewhere. You could look into PLoP (http://www.plop.at/) boot manager: may be able to boot CD or USB even when BIOS does not support booting from CD or USB ... THANK YOU!! It does indeed boot the machine from the 8.1-RELEASE USB memstick, solving the problem entirely. This deserves to be better known. If I were in your situation, my first choice would be net install, assuming you have cable or DSL; dialup would be awful slow. Even dialup would be faster (or at least a lot easier) than installing the whole system from floppies. By boot floppy set I was referring to just the boot, kernel, and mfsroot needed to get started. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting from floppy to install 8.1
I once net-installed FreeBSD using a boot CD from an earlier version; I think it was a disk one rather than boot-only ... If you use boot floppies, use only the two (or is it three?) needed to boot the install system. If I've understood the 7.3 set correctly it's now up to five: the initial boot, plus 3 for the kernel and one for the mfsroot image. I just browsed ftp.freebsd.org, not to download anything: I see the number of boot floppies is up to five for 7.3, and there is also a fixit.flp (i386). For amd64, there are four floppies for the kernel, making six needed to boot, but no fixit.flp For FreeBSD 8.1 i386 and amd64, I could find no boot floppies. Maybe they could see the number of floppies was becoming too unreasonable, added to the great unreliability of old floppies. I see that the sets are still broken into 1392 KB chunks as base.aa, base.ab and so on, wonder why they chose 1392 KB rather than 1440 KB. Maybe to allow for bad sectors revealed when formatting floppies? You could look into PLoP (http://www.plop.at/) boot manager: may be able to boot CD or USB even when BIOS does not support booting from CD or USB ... THANK YOU!! It does indeed boot the machine from the 8.1-RELEASE USB memstick, solving the problem entirely. This deserves to be better known. Glad to know it worked for you, and convinces me that my successful boot of NetBSD 4.0.1 from a USB stick was no fluke. 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
Booting from floppy to install 8.1
I'm trying to solve a chicken-egg problem. I need to boot from floppy to install 8.1, and I don't already have a running 8.1 system on which to build a set of 8.1 floppy images. (The machine in question is an oldish Pentium-III that only boots from its hard drive or from floppy -- the BIOS claims it can also boot from its ATAPI Zip-250 drive but that capability doesn't seem to be working.) By comparing the contents of the 7.3 bootonly ISO and the corresponding floppy images, I've figured out how to construct _almost_ everything on the floppies from the contents of the bootonly ISO. The exception is the boot floppy's boot/loader, which is not the same as or obviously derivable from any file on the bootonly ISO including the ISO's boot/loader (which has changed between 7.3 and 8.1, else I'd feel reasonably safe about trying to use the 7.3 boot floppy's boot/loader file). So, in order of simplicity: Should I be able to do a network install of 8.1 using a 7.3 boot floppy set? (I'm not planning to set up zfs, at least initially.) If not, are the 7.3 and 8.1 boot/loader files similar enough that the boot/loader from a 7.3 boot floppy should work when all else in the floppy set is from 8.1? Is there a reasonable way to build the proper boot/loader file for an 8.1 boot floppy using a 6.x or 7.x system? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting from floppy to install 8.1
Should I be able to do a network install of 8.1 using a 7.3 boot floppy set? (I'm not planning to set up zfs, at least initially.) If not, are the 7.3 and 8.1 boot/loader files similar enough that the boot/loader from a 7.3 boot floppy should work when all else in the floppy set is from 8.1? Is there a reasonable way to build the proper boot/loader file for an 8.1 boot floppy using a 6.x or 7.x system? I once net-installed FreeBSD using a boot CD from an earlier version; I think it was a disk one rather than boot-only. You have to specify the version to install as 8.1-RELEASE exactly as the ftp servers do; exactly as you would do with freebsd-update. If you use boot floppies, use only the two (or is it three?) needed to boot the install system. I never used zfs, don't have big enough hard drive or enough RAM to justify zfs. You could look into PLoP (http://www.plop.at/) boot manager: may be able to boot CD or USB even when BIOS does not support booting from CD or USB. My computer BIOS supports booting from CD but not USB; however NetBSD 4.0.1 installed on a USB stick booted from PLoP. There are various ways of running/installing PLoP, including installing on a floppy. You might possibly then be able to boot from CD or ATAPI Iomega Zip-250. If I were in your situation, my first choice would be net install, assuming you have cable or DSL; dialup would be awful slow. I have problems finding errorfree floppies: might be able to find two or three to boot, if I'm lucky, but no way could I find enough good floppies to accommodate all those .aa, .ab, .ac ... files. 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: Booting from floppy to install 8.1
On Thu, Jul 29, 2010 at 12:50:12AM -0700, per...@pluto.rain.com wrote: I'm trying to solve a chicken-egg problem. snip Is there a reasonable way to build the proper boot/loader file for an 8.1 boot floppy using a 6.x or 7.x system? Install 8.1 in an emulator like qemu or virtualbox to create the floppy images? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpdF7IcU2Wrp.pgp Description: PGP signature
Re: Booting from floppy to install 8.1
On 29 July 2010 10:17, Roland Smith rsm...@xs4all.nl wrote: On Thu, Jul 29, 2010 at 12:50:12AM -0700, per...@pluto.rain.com wrote: I'm trying to solve a chicken-egg problem. snip Is there a reasonable way to build the proper boot/loader file for an 8.1 boot floppy using a 6.x or 7.x system? Install 8.1 in an emulator like qemu or virtualbox to create the floppy images? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/http://www.xs4all.nl/%7Ersmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) as long as the version of the os supports the file system you want and the disk layout eg gpt you in theory can install any version of bsd from any other version of bsd. After all the main os install is just and extract of some tar balls. The only issue I can see might be the boot loader. But then you could chroot into the installed os and use the boot loader from there. I have definately installed a higher version of bsd than berfore but the versions numbers escape me ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd install from floppy
On Sun, 7 Mar 2010 13:58:07 -0800, Walt Pawley w...@wump.org wrote: At 1:28 PM -0500 3/6/10, Chuck Swiger wrote: While I think floppy drives are still useful for BIOS updates and the like, it's not just Apple that isn't selling machines with floppy drives any more. Go to HP or Dell and try to buy a new machine with a floppy drive-- they don't sell them anymore, either... I certainly can't argue that modern machines typically have floppy drives ... even if the motherboard supports one. So what? I think he wanted to point out that even if motherboards today still support floppy disk drives, the computer itself often does omit one. Instead, a blank cover is used for the intended slot, or a SD + CF + who knows what reader comes built-in. This, of course, doesn't stop you from building one (or two) into your box. But manufacturers seem to have agreed that - especially in the home consumer market, which is their most important playing field - floppies aren't used anymore. But soon, the ability to connect a floppy will disappear. First, the connectors will vanish, followed by the functionality within the hardware (e. g. BIOS) to access them. You find such a situation in notebooks. They don't have floppy drives for many years now, and the only way to access floppies with them is to buy (!) an external drive, usually USB based. (I had such a situation with a customer who needs floppy support, but had to buy a new notebook. Imagine his surprise! While home customers already have accepted that there are no floppies anymore, corporate customers that work in a specific field still rely on their presence.) Not everyone in the world throws their three year old computer in the trash so they can stay up to date. Average home consumers do. In fields where it is important to have access to data and programs for much longer time, you often don't find PCs, e. g. in the (still alive) mainframe area, notably IBM's. I, for one, find it very annoying that new versions of software which once worked just fine on equipment I still use every day no longer work in their current incarnations. That's a feeling I had, too, when upgrading my home system from a perfectly working (until the total crash) 5.4 to 7.0, from XFree86 to X.org. Lots of things had to be done, and the observation that if you update things on FreeBSD, they get better and faster, doesn't seem to be confirmed this time (except for the OS) - speed down, usability down, overhead up. But that, what we mostly call bloat, be it in hardware or in software, seems to be a needed motor for development, at least I have been told that. :-) It's a bit scary that the 300 MHz P2 (FreeBSD 5 and apps) works much faster than my 2000 MHz P4 (FreeBSD 7 and apps). Delving into several such cases, I've found comments to the effect that functions are removed because no one uses the old stuff (ie. three years old) any more. THere are still situations where you depend on three (or thirteen) years old stuff, especially in data analytics and forensics. The common situation, especially with home users, is to constantly migrate data from one format to another (again, this may mean file format as well as storage media), to keep them accessible. By the way, I have floppies older than twenty (20!) years that work perfectly - that's much longer as a modern DVD driver works. :-) This leads me to my conclusion again: The older something is, the longer it lasts. Mostly. -- 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: freebsd install from floppy
At 1:28 PM -0500 3/6/10, Chuck Swiger wrote: While I think floppy drives are still useful for BIOS updates and the like, it's not just Apple that isn't selling machines with floppy drives any more. Go to HP or Dell and try to buy a new machine with a floppy drive-- they don't sell them anymore, either... I certainly can't argue that modern machines typically have floppy drives ... even if the motherboard supports one. So what? Not everyone in the world throws their three year old computer in the trash so they can stay up to date. I, for one, find it very annoying that new versions of software which once worked just fine on equipment I still use every day no longer work in their current incarnations. Delving into several such cases, I've found comments to the effect that functions are removed because no one uses the old stuff (ie. three years old) any more. -- Walter M. Pawley w...@wump.org Wump Research Company 676 River Bend Road, Roseburg, OR 97471 541-672-8975 ___ 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 install from floppy
Piotr Lukawski plukaw...@googlemail.com wrote: ... I really cannot understand why nobody can change just one parameter and put the file in a proper place in ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/ I seem to remember something about the floppy images being dropped because few current (or even recent) systems have a floppy drive at all, much less a bootable one. I sure hope they don't start applying the same reasoning to drivers for old-ish devices. Some of us do not rush out and acquire the latest/greatest whiz-giz every few months just because it's 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: freebsd install from floppy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/03/2010 09:26:22, per...@pluto.rain.com wrote: I seem to remember something about the floppy images being dropped because few current (or even recent) systems have a floppy drive at all, much less a bootable one. Yeah, but the floppy disk drive was already obsolete 10 years ago. It's just taken this long for it to fall down dead. Good riddance to it. Why would anyone want an unreliable, slow and tiny capacity device when you can get GiB capacity USB sticks everywhere nowadays? Not providing floppy disk installation images doesn't imply dropping kernel support for floppy drives. My ancient system has a floppy, and if I blew the dust out of it and could find some media it should work just fine with FreeBSD 8.0. In fact, if you need to support older equipment, free OSes like FreeBSD are really your only choice. Drivers for old devices tend to stick around in the source tree for much longer than in any commercial offering. They might suffer from bit-rot due to lack of developer access to samples of kit, but if you really need something like that fixed you probably could get patches. In fact, I think the primary reason for dropping old device drivers is usually because they don't receive any attention during the occasional code refactoring that occurs: no one complains, and the device sits around unusable or needing special backwards compatibility shims for a while, then gets quietly deleted. - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuSJl4ACgkQ8Mjk52CukIxSWACfSkJ6k09ig0sR5lctO7tooF1k NnUAnRrWUeDMssvWDx7rvzMgPWb3fHSw =3zRd -END PGP SIGNATURE- ___ 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 install from floppy
In many situations, especially for and old or non standard equipment floppies are the best or even the only solution. Actually if I haven't found the solution to use floppy to install FreeBSD, I would be forced to use another system eg. OpenBSD instead, even if I prefer FreeBSD. The decision to make floppies obsolete is very bad, because it is still needed by many people. On 6 March 2010 10:54, Matthew Seaman m.sea...@infracaninophile.co.ukwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/03/2010 09:26:22, per...@pluto.rain.com wrote: I seem to remember something about the floppy images being dropped because few current (or even recent) systems have a floppy drive at all, much less a bootable one. Yeah, but the floppy disk drive was already obsolete 10 years ago. It's just taken this long for it to fall down dead. Good riddance to it. Why would anyone want an unreliable, slow and tiny capacity device when you can get GiB capacity USB sticks everywhere nowadays? Not providing floppy disk installation images doesn't imply dropping kernel support for floppy drives. My ancient system has a floppy, and if I blew the dust out of it and could find some media it should work just fine with FreeBSD 8.0. In fact, if you need to support older equipment, free OSes like FreeBSD are really your only choice. Drivers for old devices tend to stick around in the source tree for much longer than in any commercial offering. They might suffer from bit-rot due to lack of developer access to samples of kit, but if you really need something like that fixed you probably could get patches. In fact, I think the primary reason for dropping old device drivers is usually because they don't receive any attention during the occasional code refactoring that occurs: no one complains, and the device sits around unusable or needing special backwards compatibility shims for a while, then gets quietly deleted. - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuSJl4ACgkQ8Mjk52CukIxSWACfSkJ6k09ig0sR5lctO7tooF1k NnUAnRrWUeDMssvWDx7rvzMgPWb3fHSw =3zRd -END PGP SIGNATURE- ___ 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 install from floppy
On Sat, 6 Mar 2010 12:24:30 +0100, Piotr Lukawski plukaw...@googlemail.com wrote: In many situations, especially for and old or non standard equipment floppies are the best or even the only solution. [...] The decision to make floppies obsolete is very bad, because it is still needed by many people. Sometimes you simply stick with systems that just work, even if they are 10 years old - and older. So a machine with no USB support can likely exist. It gets even more interesting if you need to read and write floppies to keep computer systems alive for a museum (see 5,25 floppies). Sometimes, a floppy is completely sufficient and easy to use, e. g. when transfering some config files to a system without network and USB; the tar utility can be used to directly operate on floppies, which is very useful, and maybe even faster than using USB (device detection, mounting etc.). So when booting via CD, USB or network isn't possible, what are the options? Okay, with FreeBSD, you can extract the hard disk, place it into a different computer and then install the OS there; retransfer the hard disk to the original computer and everything should work from now on. (Special hardware may require additional configuration, but the base system doesn't care on what kind of hardware it is running, basically.) The reason to still use such old systems can be very different, for example just works is one of the main reasons. Others may include accurate and reliable working, or less power consumption. (One thing that I could observe over the years: The older hardware is, the longer it works - mostly.) Another reason could be the idea of resisting to buy something new that does the same as the old stuff, an action that costs money and creates electronic waste. I still have such a system which I keep for nostalgia mostly: It introduced me to FreeBSD: A 150MHz P1 with 128 MB SDR-SDRAM, SCSI CD (which I can't boot from), no USB, but Ethernet (which I also can't boot from), and it's in a perfect condition, still usable as a workstation. It does nearly everything my current workstation (P4, 2GHz) can do, and some of the things even faster. I'm sure most of you can't even imagine that. :-) FreeBSD has always impressed me by providing working (!) drivers for older stuff that still works, e. g. SCSI PCI cards, SCSI scanners and PD drives. Most hardware works out of the box, and for very special cases, there are modules or kernel options. And why use FreeBSD? Because it runs faster on the same hardware with every new release. That's something other operating systems can't do. Settings where you update your software, then need to update your hardware, and then still don't feel that anything is faster at all, are known. If floppy images aren't included on the install CD / DVD or via FTP, then at least there should be a simple means to generate them, e. g. make floppies. I wouldn't like to see floppies disappear for, let's say, the next 10 years, as much as I dislike floppy media per se. By the way, their form factor is superior to CDs and DVDs in every concern! Give the world a rewritable optical media the size of a Minidisc and the world is yours. I don't like the idea that I need a drive with the size of a full-featured computer to use media that dissolves chemically and gets unreadable if touched with the finger on the wrong side. :-) -- 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: freebsd install from floppy
Date: Sat, 06 Mar 2010 09:54:38 + From: Matthew Seaman m.sea...@infracaninophile.co.uk Subject: Re: freebsd install from floppy To: per...@pluto.rain.com Cc: questi...@freebsd.org, plukaw...@gmail.com Message-ID: 4b92265e.5030...@infracaninophile.co.uk Content-Type: text/plain; charset=UTF-8 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/03/2010 09:26:22, per...@pluto.rain.com wrote: I seem to remember something about the floppy images being dropped because few current (or even recent) systems have a floppy drive at all, much less a bootable one. Yeah, but the floppy disk drive was already obsolete 10 years ago. It's just taken this long for it to fall down dead. Good riddance to it. Why would anyone want an unreliable, slow and tiny capacity device when you can get GiB capacity USB sticks everywhere nowadays? Correction: Apple stopped selling computers with floppy drives about 10 years ago. The floppy drive is not obsolete because there is still no viable replacement that has the same (or better) functionality. The problem with USB sticks is that they don't have user-accessible write-protect tabs. If you plug a USB stick into a compromised system, it is tainted. Secure Digital Cards have a write-protect tab, but Secure means secure against copying (Copy Protection for Recordable Media), making them inappropriate for known good filesystem images. I have started using CD-ROM booting to install FreeBSD. The problem with CD-R images is that any tweaks to the disk image require burning a new disk. Regards, James Phillips Recent Slashdot exchange about exactly this issue: http://slashdot.org/comments.pl?sid=1565678cid=31302916 __ Make your browsing faster, safer, and easier with the new Internet Explorer® 8. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ ___ 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 install from floppy
On Mar 6, 2010, at 12:44 PM, James Phillips wrote: Correction: Apple stopped selling computers with floppy drives about 10 years ago. The floppy drive is not obsolete because there is still no viable replacement that has the same (or better) functionality. While I think floppy drives are still useful for BIOS updates and the like, it's not just Apple that isn't selling machines with floppy drives any more. Go to HP or Dell and try to buy a new machine with a floppy drive-- they don't sell them anymore, either... The problem with USB sticks is that they don't have user-accessible write-protect tabs. If you plug a USB stick into a compromised system, it is tainted. Some USB flash drives have write-protect switches: http://www.newegg.com/Product/Product.aspx?Item=N82E16820141486 Regards, -- -Chuck ___ 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 install from floppy
On Wed, Mar 03, 2010 at 01:33:52PM +0100, Piotr Lukawski wrote: Dears, I need to install Freebsd 8.0 using floppy and then ftp, but there are no floppy images in +ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/mentioned in http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html I tried so install Freebsd 7 using availiable floppy (successful) and update it to 8.0 (after 3 days finally error and now now whole /usr directory so I am stacked). Could you please produce install floppy images for Freebsd 8.0? Please please please. I have no power to do the install of 7, upgrade and fail again :-( Thanks in adavance. Piotr ___ Yes, I definitly vote for the release of floppy images too! In my case its the SCSI-CD drives what do not allow me to boot from a CD. It might be old fashioned, but its very easy just to boot the floppy and then install all over ftp! I guess there are still a couple of systems (old +laptops, servers) which require it. Thanks herb langhans -- sprachtraining langhans herbert langhans, warschau http://www.langhans.com.pl herbert dot raimund at gmx dot net +0048 603 341 441 ___ 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 install from floppy
Illoai, Thanks a lot! Your solution works - system is up and running now :-) However, in such a case I really cannot understand why nobody can change just one parameter and put the file in a proper place in ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/ . It can simplify life for many people. Thanks again for your help. Take care, Piotr On 4 March 2010 05:51, ill...@gmail.com ill...@gmail.com wrote: On 3 March 2010 07:33, Piotr Lukawski plukaw...@googlemail.com wrote: Dears, I need to install Freebsd 8.0 using floppy and then ftp, but there are no floppy images in ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/ ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/ mentioned in http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html I tried so install Freebsd 7 using availiable floppy (successful) and update it to 8.0 (after 3 days finally error and now now whole /usr directory so I am stacked). Could you please produce install floppy images for Freebsd 8.0? Please please please. I have no power to do the install of 7, upgrade and fail again :-( Thanks in adavance. Piotr Have you tried installing 8.0-RELEASE from your 7.x floppies? I have heard rumour that it is possible by just changing the release name under View/Set Various Installation Options. -- -- ___ 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 install from floppy
On 5 March 2010 13:51, Piotr Lukawski plukaw...@googlemail.com wrote: On 4 March 2010 05:51, ill...@gmail.com ill...@gmail.com wrote: On 3 March 2010 07:33, Piotr Lukawski plukaw...@googlemail.com wrote: Dears, I need to install Freebsd 8.0 using floppy and then ftp, but there are no floppy images . . . Could you please produce install floppy images for Freebsd 8.0? Please please please. I have no power to do the install of 7, upgrade and fail again :-( Have you tried installing 8.0-RELEASE from your 7.x floppies? I have heard rumour that it is possible by just changing the release name under View/Set Various Installation Options. Illoai, Thanks a lot! Your solution works - system is up and running now :-) However, in such a case I really cannot understand why nobody can change just one parameter and put the file in a proper place in ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/. It can simplify life for many people. I'm glad it worked for you. :) I'm not aware of why the floppy images are no longer being generated, however, just repackaging the 7.x floppies is probably not the best idea: you can select a couple of options under 7.x that will likely break an 8.x install (I'm under the impression that Dangerously Dedicated disks do this). -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
freebsd install from floppy
Dears, I need to install Freebsd 8.0 using floppy and then ftp, but there are no floppy images in ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/mentioned in http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html I tried so install Freebsd 7 using availiable floppy (successful) and update it to 8.0 (after 3 days finally error and now now whole /usr directory so I am stacked). Could you please produce install floppy images for Freebsd 8.0? Please please please. I have no power to do the install of 7, upgrade and fail again :-( Thanks in adavance. Piotr ___ 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 install from floppy
On 3 March 2010 07:33, Piotr Lukawski plukaw...@googlemail.com wrote: Dears, I need to install Freebsd 8.0 using floppy and then ftp, but there are no floppy images in ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/8.0-RELEASE/floppies/mentioned in http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html I tried so install Freebsd 7 using availiable floppy (successful) and update it to 8.0 (after 3 days finally error and now now whole /usr directory so I am stacked). Could you please produce install floppy images for Freebsd 8.0? Please please please. I have no power to do the install of 7, upgrade and fail again :-( Thanks in adavance. Piotr Have you tried installing 8.0-RELEASE from your 7.x floppies? I have heard rumour that it is possible by just changing the release name under View/Set Various Installation Options. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
No floppy-images for FreeBSD 8.0 installation anymore?
Hi Daemons, I use to install FreeBSD with the floppies, then choosing the ftp-install. It was quite a while ago I had done so -- but now I see the x.flp images are gone. Or maybe I just havent found them on the ftp-site?? I cannot boot this computer from the SCSI-CD drives. Is there any chance to get 8.0 for floppies? Thank you herb langhans ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
No floppy-images for FreeBSD 8.0 installation anymore?
herbert langhans writes: I cannot boot this computer from the SCSI-CD drives. Is there any chance to get 8.0 for floppies? I do not believe there are (by default) floppies for 8.0; whether this is new for this release of not I cannot say. Is the machine modern enough it could boot from a USB-connected CDROM? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No floppy-images for FreeBSD 8.0 installation anymore?
Yes, just checked it. There is a 'boot from usb-cdrom' option in the setup. I guess I have to sacrifice a usb-stick for the installation. Will it work this way? This is not yet updated in the the handbook -- but the 8.0-RELEASE-amd64-memstick.img seems to be a file I have to dump on the usb-stick. Is this the boot-file I need for the ftp-install? Cheers herbs On Tue, Feb 09, 2010 at 12:12:38PM -0500, Robert Huff wrote: herbert langhans writes: I cannot boot this computer from the SCSI-CD drives. Is there any chance to get 8.0 for floppies? I do not believe there are (by default) floppies for 8.0; whether this is new for this release of not I cannot say. Is the machine modern enough it could boot from a USB-connected CDROM? Robert Huff ___ 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 -- sprachtraining langhans herbert langhans, warschau http://www.langhans.com.pl herbert dot raimund at gmx dot net +0048 603 341 441 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No floppy-images for FreeBSD 8.0 installation anymore?
herbert langhans writes:
I cannot boot this computer from the SCSI-CD drives. Is there any
chance to get 8.0 for floppies?
I do not believe there are (by default) floppies for 8.0;
whether this is new for this release of not I cannot say.
Is the machine modern enough it could boot from a USB-connected
CDROM?
Yes,
just checked it. There is a 'boot from usb-cdrom' option in the
setup. I guess I have to sacrifice a usb-stick for the installation.
Will it work this way?
This is not yet updated in the the handbook -- but the
8.0-RELEASE-amd64-memstick.img seems to be a file I have to dump on
the usb-stick. Is this the boot-file I need for the ftp-install?
The memstick.img is very large because it contains fixit. I download the
smaller disc1.iso and then use the following script to write it to a usb
stick drive. There is no need to do a FTP-install because the disc1.iso
has everything needed to install from.
The thing you have to keep in mind is that some bios older that 2008 do
not have option to boot from USB sticks or only can boot from some
vendors USB sticks not all of them.
#!/bin/sh
#Purpose = Use to transfer the FreeBSD install cd1 to
# a bootable 1GB USB flash drive so it can be used to install from.
# First fetch the FreeBSD 8.0-RELEASE-i386-disc1.iso to your
# hard drive /usr. Then execute this script from the command line
#
# fbsd2usb /usr/8.0-RELEASE-i386-disc1.iso /usr/8.0-disc1.img
#
# Change system bios to boot from USB-dd and away you go.
# NOTE: This script has to be run from root and your 1GB USB flash drive
# has to be plugged in before running this script.
# On the command line enterfbsd2usb iso-path img-path
# You can set some variables here. Edit them to fit your needs.
# Set serial variable to 0 if you don't want serial console at all,
# 1 if you want comconsole and 2 if you want comconsole and vidconsole
serial=0
set -u
if [ $# -lt 2 ]; then
echo Usage: $0 source-iso-path output-img-path
exit 1
fi
isoimage=$1; shift
imgoutfile=$1; shift
# Temp directory to be used later
#export tmpdir=$(mktemp -d -t fbsdmount)
export tmpdir=$(mktemp -d /usr/fbsdmount)
export isodev=$(mdconfig -a -t vnode -f ${isoimage})
ISOSIZE=$(du -k ${isoimage} | awk '{print $1}')
SECTS=$((($ISOSIZE + ($ISOSIZE/5))*4))
#SECTS=$((($ISOSIZE + ($ISOSIZE/5))*2))
echo
echo ### Initializing image File started ###
echo ### This will take about 1 minute ###
date
dd if=/dev/zero of=${imgoutfile} count=${SECTS}
echo ### Initializing image File completed ###
date
echo
ls -l ${imgoutfile}
export imgdev=$(mdconfig -a -t vnode -f ${imgoutfile})
bsdlabel -w -B ${imgdev}
newfs -O1 /dev/${imgdev}a
mkdir -p ${tmpdir}/iso ${tmpdir}/img
mount -t cd9660 /dev/${isodev} ${tmpdir}/iso
mount /dev/${imgdev}a ${tmpdir}/img
echo
echo ### Started Copying files to the image now ###
echo ### This will take about 6 minutes ###
date
( cd ${tmpdir}/iso find . -print -depth | cpio -dump ${tmpdir}/img )
echo ### Completed Copying files to the image ###
date
if [ ${serial} -eq 2 ]; then
echo -D ${tmpdir}/img/boot.config
echo 'console=comconsole, vidconsole'
${tmpdir}/img/boot/loader.conf
elif [ ${serial} -eq 1 ]; then
echo -h ${tmpdir}/img/boot.config
echo 'console=comconsole' ${tmpdir}/img/boot/loader.conf
fi
echo
echo ### Started writing image to flash drive now ###
echo ### This will take about 16 minutes ###
date
dd if=${imgoutfile} of=/dev/da0 bs=1m
echo ### Completed writing image to flash drive at ###
date
cleanup() {
umount ${tmpdir}/iso
mdconfig -d -u ${isodev}
umount ${tmpdir}/img
mdconfig -d -u ${imgdev}
rm -rf ${tmpdir}
}
cleanup
ls -lh ${imgoutfile}
echo ### Script finished ###
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Mount floppy image
I'm trying to mount a floppy image following the instructions on: http://www.bsdguides.org/guides/freebsd/beginners/mdconfig_mount_images To mount a floppy image, create a virtual device, /dev/md0, for the floppy image. # mdconfig -a -t vnode -f /tmp/boot.flp -u 0 I had to touch /tmp/boot.flp to make it work Next: Now mount the virtual device. # mount /dev/mnt0 /mnt _ I believe there's a typo here should be /dev/md0 I get: mount /dev/md0 /mnt mount: /dev/md0 : Input/output error I have no idea what to do now! Any suggestions? Thanks Leslie ___ 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: Mount floppy image
2010-01-31 09:27, Leslie Jensen skrev: I'm trying to mount a floppy image following the instructions on: http://www.bsdguides.org/guides/freebsd/beginners/mdconfig_mount_images To mount a floppy image, create a virtual device, /dev/md0, for the floppy image. # mdconfig -a -t vnode -f /tmp/boot.flp -u 0 I had to touch /tmp/boot.flp to make it work Next: Now mount the virtual device. # mount /dev/mnt0 /mnt _ I believe there's a typo here should be /dev/md0 I get: mount /dev/md0 /mnt mount: /dev/md0 : Input/output error I have no idea what to do now! Any suggestions? Thanks Of course the imagefile had to be in /tmp/ and it had to be mount_msdosfs /dev/mnt0 /mnt Sorry for the noise Leslie ___ 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: Mount floppy image
On Sun, Jan 31, 2010 at 09:27:48AM +0100, Leslie Jensen wrote: I'm trying to mount a floppy image following the instructions on: http://www.bsdguides.org/guides/freebsd/beginners/mdconfig_mount_images To mount a floppy image, create a virtual device, /dev/md0, for the floppy image. # mdconfig -a -t vnode -f /tmp/boot.flp -u 0 I had to touch /tmp/boot.flp to make it work That is strange. Is /tmp/boot.flp an existing image? If so, what size is it? Note that is you use touch on a non-existing file, it will create a file 0 bytes long! If you try to mount that, you'll get an error, because there is no data to be read. Now mount the virtual device. # mount /dev/mnt0 /mnt I believe there's a typo here should be /dev/md0 Yes. I get: mount /dev/md0 /mnt mount: /dev/md0 : Input/output error I have no idea what to do now! If you want to _create_ a floppy image, you can use: dd if=/dev/zero bs=1k count=1440 of=boot.flp Then use mdconfig to make an md device out of it. Of course you'll have to create an msdos filesystem on it; newfs_msdos /dev/md0 After that you can mount it and fill it with whatever you like. -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp1eGhk47ozj.pgp Description: PGP signature
Re: 8.0 and floppy support
Fbsd1 fb...@a1poweruser.com writes: When booting release 8.0 i no longer get the fd0 floppy device prob message. This pc has run freebsd 6.4 7.0 7.2 which all supported the floppy drive. Has floppy drive support been dropped in 8.0? No; it's still in the GENERIC kernel, and it still works for me. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.0 and floppy support
When booting release 8.0 i no longer get the fd0 floppy device prob message. This pc has run freebsd 6.4 7.0 7.2 which all supported the floppy drive. Has floppy drive support been dropped in 8.0? I know the floppy drive works because i can boot win98 floppy disk ok. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Failure to connect USB Floppy drive
When I plug in my USB floppy drive I get these messages: ugen1.2: NEC at usbus1 umass0: NEC NEC USB UF000x, class 0/0, rev 1.10/1.50, addr 2 on usbus1 umass0: UFI over CBI with CCI; quirks = 0x umass0:4:0:-1: Attached to scbus4 (da0:umass-sim0:0:0:0): got CAM status 0x4 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry I remember using the same drive in 7.0 without problems. Yuri ___ 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: Failure to connect USB Floppy drive
On Wed, Oct 28, 2009 at 2:08 PM, Yuri y...@rawbw.com wrote: When I plug in my USB floppy drive I get these messages: ugen1.2: NEC at usbus1 umass0: NEC NEC USB UF000x, class 0/0, rev 1.10/1.50, addr 2 on usbus1 umass0: UFI over CBI with CCI; quirks = 0x umass0:4:0:-1: Attached to scbus4 (da0:umass-sim0:0:0:0): got CAM status 0x4 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry I remember using the same drive in 7.0 without problems. Yuri Did you remove devel/libusb -- Adam Vande More ___ 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: Failure to connect USB Floppy drive
Adam Vande More wrote: Did you remove devel/libusb It's installed: libusb-0.1.12_4 I enabled debugging and now get an extended dmesg log: ugen1.2: NEC at usbus1 umass0: NEC NEC USB UF000x, class 0/0, rev 1.10/1.50, addr 2 on usbus1 umass0: UFI over CBI with CCI; quirks = 0x umass0:umass_cam_action: 4:-1:-1:XPT_PATH_INQ:. umass0:4:0:-1: Attached to scbus4 umass0:umass_cam_rescan: scbus4: scanning for 4:0:-1 umass0:umass_cam_action: 4:-1:-1:XPT_PATH_INQ:. umass0:umass_cam_action: 4:0:0:XPT_PATH_INQ:. umass0:umass_cam_action: 4:0:0:XPT_PATH_INQ:. umass0:umass_cam_action: 4:0:0:XPT_GET_TRAN_SETTINGS:. umass0:umass_cam_action: 4:0:0:XPT_SET_TRAN_SETTINGS:. umass0:umass_cam_action: 4:0:0:XPT_PATH_INQ:. umass0:umass_cam_action: 4:0:0:XPT_PATH_INQ:. umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/36b data/18b sense umass0:umass_attach: Attach finishedumass0:umass_cbi_dump_cmd: cmd = 12b (0x12002400...), data = 36b, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_cbi_data_read_callback: max_bulk=131072, data_rem=36 umass0:umass_t_cbi_data_read_callback: max_bulk=131072, data_rem=0 umass0:umass_transfer_start: transfer index = 8 umass0:umass_t_cbi_status_callback: UFI CCI, ASC = 0x00, ASCQ = 0x00 umass0:umass_cam_action: 4:0:0:XPT_PATH_INQ:. umass0:umass_cam_action: 4:0:0:XPT_PATH_INQ:. umass0:umass_cam_action: 4:0:0:XPT_GET_TRAN_SETTINGS:. umass0:umass_cam_action: 4:0:0:XPT_SET_TRAN_SETTINGS:. umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/255b data/18b sense umass0:umass_cbi_dump_cmd: cmd = 12b (0x1201ff00...), data = 255b, dir = in umass0:umass_transfer_start: transfer index = 4 umass0:umass_t_cbi_data_read_callback: max_bulk=131072, data_rem=255 umass0:umass_t_cbi_data_read_callback: max_bulk=131072, data_rem=0 umass0:umass_transfer_start: transfer index = 8 umass0:umass_t_cbi_status_callback: UFI CCI, ASC = 0x00, ASCQ = 0x00 umass0:umass_cam_action: 4:0:0:XPT_GET_TRAN_SETTINGS:. umass0:umass_cam_action: 4:0:0:XPT_PATH_INQ:. umass0:umass_cam_action: 4:0:0:XPT_GET_TRAN_SETTINGS:. umass0:umass_cam_action: 4:0:0:XPT_SET_TRAN_SETTINGS:. umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x00, flags: 0xc0, 6b cmd/0b data/32b sense umass0:umass_cbi_dump_cmd: cmd = 12b (0x...), data = 0b, dir = no data phase umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x00, flags: 0xc0, 6b cmd/0b data/32b sense umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x00, flags: 0xc0, 6b cmd/0b data/32b sense umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x00, flags: 0xc0, 6b cmd/0b data/32b sense umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x00, flags: 0xc0, 6b cmd/0b data/32b sense umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x00, flags: 0xc0, 6b cmd/0b data/32b sense umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x00, flags: 0xc0, 6b cmd/0b data/32b sense umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x00, flags: 0xc0, 6b cmd/0b data/32b sense umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x00, flags: 0xc0, 6b cmd/0b data/32b sense umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x00, flags: 0xc0, 6b cmd/0b data/32b sense umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x00, flags: 0xc0, 6b cmd/0b data/32b sense umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_PATH_INQ:. umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x25, flags: 0x40, 10b cmd/8b data/32b sense umassX:umass_cam_rescan_callback: xpt0: Rescan succeeded umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action: 4:0:0:XPT_SCSI_IO: cmd: 0x25, flags: 0x40, 10b cmd/8b data/32b sense umass0:umass_t_cbi_reset1_callback: CBI reset! umass0:umass_tr_error: transfer error, USB_ERR_STALLED - reset umass0:umass_cam_action:
Re: Failure to connect USB Floppy drive
What does this mean? I remember using the same drive in 7.0 without problems. Yuri -- Adam Vande More ___ 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: Failure to connect USB Floppy drive
Adam Vande More wrote: What does this mean? I remember using the same drive in 7.0 without problems. It used to work in FreeBSD-70 long time ago. Now in FReeBSD-8.0-RC1 it doesn't. Yuri ___ 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: Failure to connect USB Floppy drive
Yuri y...@rawbw.com writes: Adam Vande More wrote: Did you remove devel/libusb It's installed: libusb-0.1.12_4 That's your problem, then. You need to remove it and rebuild the ports that depended on it. This was mentioned in /usr/ports/UPDATING and /usr/src/UPDATING. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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: Failure to connect USB Floppy drive
Lowell Gilbert wrote: That's your problem, then. You need to remove it and rebuild the ports that depended on it. This was mentioned in /usr/ports/UPDATING and /usr/src/UPDATING. I removed this port but still have this problem. Yuri ___ 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
wine: app won't install from floppy
What is the correct way of installing something into wine from floppy? The obvious approach: $ wine 'a:\setup.exe' did not work with a (fairly old version of) Visio: the option dialogs seemed to work properly, but very shortly after starting the actual install I got an error box: VISIO Setup ! Tried to create an invalid path using 'A:\' and 'clipart.vs_' It somehow locked out CtrlAltF1 so I could not switch to a text screen, but AltTab did bring up FVWM's window list (thus making it possible to transcribe the error message into an xterm that was not related to the wine session). After clicking OK I got an info box: Visio Setup i Setup failed. and it quit when I clicked OK there. Comparing the contents of .wine before/after the attempt, it seems the only change involves the font entries in the registry: $ diff -r wineBak .wine diff -r wineBak/system.reg .wine/system.reg 9082c9082 [Software\\Microsoft\\Windows NT\\CurrentVersion\\Fonts] 1208923638 --- [Software\\Microsoft\\Windows NT\\CurrentVersion\\Fonts] 1209616619 diff -r wineBak/user.reg .wine/user.reg 453c453 [Software\\Wine\\Fonts] 1208923638 --- [Software\\Wine\\Fonts] 1209616619 456c456 [Software\\Wine\\Fonts\\External Fonts] 1208923638 --- [Software\\Wine\\Fonts\\External Fonts] 1209616619 and of course I have no clue whether this makes any difference to anything. $ uname -a FreeBSD fbsd70.uucp 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 $ wine --version wine-0.9.48 a: is symlinked to /fd in .wine/dosdevices and /dev/fd0 is mounted on /fd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems Installing FreeBSD 6.2 - No floppy devices found!
On Tuesday 20 November 2007 07:32:36 pm Cameron Stuart wrote: Hardware: Maxtron AMD opteron with 3ware 4 port PCI express SATA II raid 5 Problem Description: The 3ware driver must be loaded into the kernel using KLD, but the floppy device cannot be found However, the drive exists, and is configured correctly in the BIOS (IE, the system can boot from the floppy) Attempted Solutions: 1) Tried booting using APCI disabled 2) Tried set hint.fdc.0.flags=1 and the boot shell before continuing into the sysinstall 3) Tried enabling disabling the floppy device in the BIOS Any suggestions or solutions you may have would be greatly appreciated Cheers, Cam Which 3ware card do you have? I made 6.2 iso with working 96xx drivers on them so you can do a regular old install off the cd. I can give you a download link if you'd like, just need to know if you want amd64 or i386. -- Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB signature.asc Description: This is a digitally signed message part.
Problems Installing FreeBSD 6.2 - No floppy devices found!
Hardware: Maxtron AMD opteron with 3ware 4 port PCI express SATA II raid 5 Problem Description: The 3ware driver must be loaded into the kernel using KLD, but the floppy device cannot be found However, the drive exists, and is configured correctly in the BIOS (IE, the system can boot from the floppy) Attempted Solutions: 1) Tried booting using APCI disabled 2) Tried set hint.fdc.0.flags=1 and the boot shell before continuing into the sysinstall 3) Tried enabling disabling the floppy device in the BIOS Any suggestions or solutions you may have would be greatly appreciated Cheers, Cam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 Hangs Probing Floppy During Boot
Tim Daneliuk wrote: During the boot probe, FreeBSD 6.2 (Release or -STABLE) hangs for several minutes while probing the floppy. Eventually, it does get through it, but it takes a lng time. Disabling the floppy in the machine BIOS makes the problem go away because FBSD sees no floppy to probe, but that's not an optimal soltion. Have you tried adding hint.fd.0.disabled=1 and hint.fdc.0.disabled=1 to your loader.conf (or device.hints)? I don't know it it will work, it's just something you could try. signature.asc Description: OpenPGP digital signature
Re: 6.2 Hangs Probing Floppy During Boot
Ivan Voras wrote: Tim Daneliuk wrote: During the boot probe, FreeBSD 6.2 (Release or -STABLE) hangs for several minutes while probing the floppy. Eventually, it does get through it, but it takes a lng time. Disabling the floppy in the machine BIOS makes the problem go away because FBSD sees no floppy to probe, but that's not an optimal soltion. Have you tried adding hint.fd.0.disabled=1 and hint.fdc.0.disabled=1 to your loader.conf (or device.hints)? I don't know it it will work, it's just something you could try. I have not. If I do this, will it actually disable the floppy/controller? The issue for me is that I want to be able to actually use the floppy when I need it, I just don't want to have wait multiple minutes while the kernel figures out there is not floppy in the drive at boot time... -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
6.2 Hangs Probing Floppy During Boot
I recently noted this problem and thought it was related to a new MOBO I'd just installed. I've now seen the exact same problem with an old MOBO when I loaded FBSD 6.2. IOW, the following appears to be a 6.2 artifact: During the boot probe, FreeBSD 6.2 (Release or -STABLE) hangs for several minutes while probing the floppy. Eventually, it does get through it, but it takes a lng time. Disabling the floppy in the machine BIOS makes the problem go away because FBSD sees no floppy to probe, but that's not an optimal soltion. I DAGS and saw that others have seen this same problem but could not find a solution anywhere ... TIA, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sysinstall: No Floppy Devices Found
--- Dan Mahoney, System Admin [EMAIL PROTECTED] wrote: On Tue, 16 Jan 2007, Kevin Kobb wrote: I have found that when I do an install with an install.cfg file on a floppy, I must insert the floppy right after the system begins to boot from CD. If I don't when I tell sysinstall to read the floppy I get an error. On a related note, sysinstall often errors out while trying to read from the CD-ROM (with FreeBSD disk in it). When read errors occur, sysinstal behaves erratically. You never know what will be displayed or how it will handle the situation (sometimes it looks like it aborted, but when you press Enter, it goes ahead with the install). BTW, this is in FreeBSD 6.2. As a work around, if I go into the options and select rescan for hardware devices (not sure if that is the exact wording) after inserting the floppy disk, it will work OK as well. Might be worth a try. No luck. I've rescanned time after time, and get nothing. No sloppy devices show up in dmesg, cannot use mount_msdosfs to access the floppy, etc. This is truly, truly frustrating, as I am trying to follow THESE instructions: http://3ware.com/KB/article.aspx?id=14850 I've even tried installing to an external (non-raid) drive in an attempt to use that drive as a really big floppy. The boot loader doesn't know how to see the BSD partition on it, and apparently can only see raw bios drives. Another possible approach was to try and boot from the single drive and then use sysinstall to install onto the RAID array, but I've had issues with that before. As an aside, the module HAS to be loaded before the boot process, so I can't use kldload to load the module from a fixit floppy or something like that. My workaround at the moment is that I am downloading a snapshot ISO of -STABLE It might be nice if the loading modules from floppy procedure (while rarely required) was better documented. -Dan -- It's three o'clock in the morning. It's too late for 'oops'. After Locate Updates, don't even go there. -Paul Baecker January 3, 2k Indeed, sometime after 3AM Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sysinstall: No Floppy Devices Found
On Tue, 16 Jan 2007, Kevin Kobb wrote: I have found that when I do an install with an install.cfg file on a floppy, I must insert the floppy right after the system begins to boot from CD. If I don't when I tell sysinstall to read the floppy I get an error. As a work around, if I go into the options and select rescan for hardware devices (not sure if that is the exact wording) after inserting the floppy disk, it will work OK as well. Might be worth a try. No luck. I've rescanned time after time, and get nothing. No sloppy devices show up in dmesg, cannot use mount_msdosfs to access the floppy, etc. This is truly, truly frustrating, as I am trying to follow THESE instructions: http://3ware.com/KB/article.aspx?id=14850 I've even tried installing to an external (non-raid) drive in an attempt to use that drive as a really big floppy. The boot loader doesn't know how to see the BSD partition on it, and apparently can only see raw bios drives. Another possible approach was to try and boot from the single drive and then use sysinstall to install onto the RAID array, but I've had issues with that before. As an aside, the module HAS to be loaded before the boot process, so I can't use kldload to load the module from a fixit floppy or something like that. My workaround at the moment is that I am downloading a snapshot ISO of -STABLE It might be nice if the loading modules from floppy procedure (while rarely required) was better documented. -Dan -- It's three o'clock in the morning. It's too late for 'oops'. After Locate Updates, don't even go there. -Paul Baecker January 3, 2k Indeed, sometime after 3AM Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Floppy IO Errors
On Friday 31 August 2007 04:01:25 Dan Mahoney, System Admin wrote: I am trying to load a kernel module from a floppy disk (ms dos formatted). Is there anything special I have to do to format these disks, or make them readable? I can boot from an MS DOS startup disk (as generated by XP) but BSD returns an IO error when trying to read any floppy. I've tried multiple drives, cables, and disks. I don't see the relevance of the boot stage here, but if you wanna load a kernel module from a floppy: # mount_msdosfs /dev/fdc0 /mnt # sysctl kern.module_path=/boot/kernel;/boot/modules;/mnt # kldload mymodulename /dev/fdc0 being your floppy drive device. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Floppy IO Errors
All, I am trying to load a kernel module from a floppy disk (ms dos formatted). Is there anything special I have to do to format these disks, or make them readable? I can boot from an MS DOS startup disk (as generated by XP) but BSD returns an IO error when trying to read any floppy. I've tried multiple drives, cables, and disks. It's on a tyan dual opteron system. Help much appreciated -- next plan is to create a scratch SATA volume to play host to the raid card, but I would like to fix this somehow. -Dan -- I love you forever eternally. -Connaian Expression Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
teac USB FLOPPY problem
detects fine
umass0: detached
umass0: TEAC TEAC FD-05PUB, rev 2.00/0.00, addr 2
da0 at umass-sim0 bus 0 target 0 lun 0
da0: TEAC FD-05PUB 3000 Removable Direct Access SCSI-0 device
da0: 1.000MB/s transfers
da0: 1MB (2880 512 byte sectors: 64H 32S/T 1C)
i downloaded ufdformat from http://people.freebsd.org/~bms/dump/tools/ufdformat/
the tool compiles without errors on FreeBSD 6.2/i386
bit it doesn't work
it stalls at first cylinder and i'm getting in dmesg:
umass0: CBI reset failed, IOERROR
umass0: CBI bulk-in stall clear failed, STALLED
umass0: CBI bulk-out stall clear failed, STALLED
CTRL-C and kill doesn't work.
unplugging works.
from formatted diskettes i can read data (like dd if=/dev/da0
of=/dev/null bs=18k) but i can't write.
any attempt to write says device busy.
my drive is listed in scsi_da.c quirks like this
* TEAC USB floppy mechanisms
*/
{T_DIRECT, SIP_MEDIA_REMOVABLE, TEAC , FD-05*, *},
/*quirks*/ DA_Q_NO_SYNC_CACHE
more quirks? any clue?
thank you
Wojtek
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: questions about floppy disk
On Sun, 24 Jun 2007, Olivier Regnier wrote: Hi everyone, I have two questions about floppy disk with FreeBSD. How add a UFS filesystem to use the diskette for transfering files ? I think with this command but i'm not sure because, i can't check for the moment. # newfs /dev/fd0 To mount a floppy disk with ufs filesystem, i must use this command ? # mount /dev/fd0 /mnt/floppy Thank you for your help Bye bye, Olivier Regnier try mtools, from the ports. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
questions about floppy disk
Hi everyone, I have two questions about floppy disk with FreeBSD. How add a UFS filesystem to use the diskette for transfering files ? I think with this command but i'm not sure because, i can't check for the moment. # newfs /dev/fd0 To mount a floppy disk with ufs filesystem, i must use this command ? # mount /dev/fd0 /mnt/floppy Thank you for your help Bye bye, Olivier Regnier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: questions about floppy disk
At 07:21 PM 6/24/2007 +0200, Olivier Regnier wrote: I have two questions about floppy disk with FreeBSD. How add a UFS filesystem to use the diskette for transfering files ? I think with this command but i'm not sure because, i can't check for the moment. # newfs /dev/fd0 To mount a floppy disk with ufs filesystem, i must use this command ? # mount /dev/fd0 /mnt/floppy Thank you for your help Bye bye, Olivier Regnier http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/floppies.html -JD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
using dd to dump an image file to a floppy
Everyone, I'm trying to make boot and kern floppies, using dd, as follows: Cdrom is mounted, floppy is mounted (and I have test written to it) I have the 6.2 disk 1 in the cdrom drive (the floppies directory contains the disk images I'd like to write) I'm in the /cdrom directory When I try to disk image the boot.flp file, here's what happens: # dd if=floppies/boot.flp of=/dev/fd0 dd: /dev/fd0: Operation not permitted I keep getting the operation not permitted message. As I said before, I CAN write to the fd0 (floppy drive), and I am logged in as root. Anyone know what I'm doing wrong? Thanks, John So here's to the role of time, patience, and reflection in our lives. If we believe it is better to build than to destroy, better to live and let live, better to be than to be seen, then we might have a chance, slowly, to find a satisfying way through life, this flicker of consciousness between two great silences. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: using dd to dump an image file to a floppy
John wrote: Everyone, I'm trying to make boot and kern floppies, using dd, as follows: Cdrom is mounted, floppy is mounted (and I have test written to it) # dd if=floppies/boot.flp of=/dev/fd0 dd: /dev/fd0: Operation not permitted dd works on raw devices, and can't operate on a raw device if a filesystem is mounted. umount fd0 and try again Kevin Kinsey -- Satellite Safety Tip #14: If you see a bright streak in the sky coming at you, duck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: using dd to dump an image file to a floppy
On Mon, 16 Apr 2007 14:24:14 -0400 John [EMAIL PROTECTED] wrote: Everyone, I'm trying to make boot and kern floppies, using dd, as follows: Cdrom is mounted, floppy is mounted (and I have test written to it) I have the 6.2 disk 1 in the cdrom drive (the floppies directory contains the disk images I'd like to write) I'm in the /cdrom directory When I try to disk image the boot.flp file, here's what happens: # dd if=floppies/boot.flp of=/dev/fd0 dd: /dev/fd0: Operation not permitted I keep getting the operation not permitted message. As I said before, I CAN write to the fd0 (floppy drive), and I am logged in as root. Anyone know what I'm doing wrong? Maybe you just unmount your floppy before doing dd if=floppies/boot.flp of=/dev/fd0. It's blocked. Thanks, John So here's to the role of time, patience, and reflection in our lives. If we believe it is better to build than to destroy, better to live and let live, better to be than to be seen, then we might have a chance, slowly, to find a satisfying way through life, this flicker of consciousness between two great silences. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Floppy drive problem
Hello, Installed FreeBSD 6.0 last year, been using as cross development for VME. But discovered can not mount floppy drive, hardware seems ok, per below. However, mount command fails. Any ideas for me? Thanks Tom Sun Ultra 1 UPA/SBus (UltraSPARC 200MHz), Keyboard Present OpenBoot 3.11, 512 MB memory installed, Serial #8388337. Tesed wirh No Floppy in drive: ok test floppy Testing floppy disk system. A formatted disk should be in the drive. No diskette, or incorrect format. floppy selftest failed. Return code = -1 ok Tesed wirh Floppy in drive: ok test floppy Testing floppy disk system. A formatted disk should be in the drive. Test succeeded. ok ok eject ok Booting: FreeBSD/sparc64 bootstrap loader, Revision 1.0 ([EMAIL PROTECTED], Wed Nov 2 09:45:36 UTC 2005) bootpath=/[EMAIL PROTECTED],0/SUNW,[EMAIL PROTECTED],880/[EMAIL PROTECTED],0:a After boot: # mount /dev/fd/0 /mnt mount: /dev/fd/0: Block device required # _ Interest Rates near 39yr lows! $430,000 Mortgage for $1,399/mo - Calculate new payment http://www.lowermybills.com/lre/index.jsp?sourceid=lmb-9632-18466moid=7581 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Floppy drive problem
On Fri, Mar 30, 2007 at 02:02:10PM +, Tee Nor wrote: Booting: FreeBSD/sparc64 bootstrap loader, Revision 1.0 ([EMAIL PROTECTED], Wed Nov 2 09:45:36 UTC 2005) bootpath=/[EMAIL PROTECTED],0/SUNW,[EMAIL PROTECTED],880/[EMAIL PROTECTED],0:a After boot: # mount /dev/fd/0 /mnt mount: /dev/fd/0: Block device required You should not use /dev/fd/0! It is a file descriptor, not a floppy device. The floppy driver fdc(4) is for the PC architecture, not for sparc64. Both fdc(4) and atapifd(4) are commented out in the sparc64 GENERIC kernel. According to the 6.2 installation instructions for sparc64, a floppy disk based install is not supported on sparc64. Maybe the floppy is connected to the SCSI bus? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpO7cr886pZW.pgp Description: PGP signature
Re: Operation not permitted when mounting floppy or cdrom
Thanks everyone. On 2/19/07, Oliver Fromme [EMAIL PROTECTED] wrote: lysergius2001 [EMAIL PROTECTED] wrote: FreeBSD 6.2. Recently installed will not permit user mount of floppy disk, cdrom, or usb. Works fine as root. Checked devfs.conf, devfs.rules, fstab, /dev. Nothing seems to make a difference. For ordinary users to be able to mount file systems, three conditions have to be met: -1- sysctl vfs.usermount=1 -2- The user must have read+write access to the device to be mounted. Usually you will solve that via group permissions, e.g. create a group for people who are allowed to mount a certain device, then put those people into that group (via /etc/group), and change the permission modes of the device so that the group can read+write it. -3- The user must own the mount point. Note that read+ write access is not sufficient here, and group rights don't matter -- the user must be the owner of the mount point. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd C is quirky, flawed, and an enormous success. -- Dennis M. Ritchie. -- Lysergius says, Stay light, but trust gravity ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Operation not permitted when mounting floppy or cdrom
lysergius2001 [EMAIL PROTECTED] wrote: FreeBSD 6.2. Recently installed will not permit user mount of floppy disk, cdrom, or usb. Works fine as root. Checked devfs.conf, devfs.rules, fstab, /dev. Nothing seems to make a difference. For ordinary users to be able to mount file systems, three conditions have to be met: -1- sysctl vfs.usermount=1 -2- The user must have read+write access to the device to be mounted. Usually you will solve that via group permissions, e.g. create a group for people who are allowed to mount a certain device, then put those people into that group (via /etc/group), and change the permission modes of the device so that the group can read+write it. -3- The user must own the mount point. Note that read+ write access is not sufficient here, and group rights don't matter -- the user must be the owner of the mount point. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd C is quirky, flawed, and an enormous success. -- Dennis M. Ritchie. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Operation not permitted when mounting floppy or cdrom
FreeBSD 6.2. Recently installed will not permit user mount of floppy disk, cdrom, or usb. Works fine as root. Checked devfs.conf, devfs.rules, fstab, /dev. Nothing seems to make a difference. Any ideas welcomed... Thanks -- Lysergius says, Stay light, but trust gravity ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Operation not permitted when mounting floppy or cdrom
lysergius2001 wrote: FreeBSD 6.2. Recently installed will not permit user mount of floppy disk, cdrom, or usb. Works fine as root. Checked devfs.conf, devfs.rules, fstab, /dev. Nothing seems to make a difference. Any ideas welcomed... Thanks You don't have access to the /dev nodes. Make sure that your user has the ability to mount. Make sure that this sysctl is also set to 1: vfs.usermount: 1 If that doesn't work, then we'll have to get more info about the devices you're trying to mount (ls -l), what groups you're in, etc. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Operation not permitted when mounting floppy or cdrom
На 17.2.2007 21:11 lysergius2001 пише: FreeBSD 6.2. Recently installed will not permit user mount of floppy disk, cdrom, or usb. Works fine as root. Checked devfs.conf, devfs.rules, fstab, /dev. Nothing seems to make a difference. Any ideas welcomed... Thanks Try setting the vfs.usermount sysctl to 1 -- This correspondence is strictly confidential. Any screening, filtering and/or production for the purpose of public or otherwise disclosure is forbidden without written permission by the author signed above. If you are not the intended recipient, please immediately notify the sender and permanently delete any copies PGP KeyID: 0x3118168B Keyserver: pgp.mit.edu Key fingerprint BB50 2983 0714 36DC D02E 158A E03D 56DA 3118 168B pgpSBbroyeJzM.pgp Description: PGP signature
Re: 6.2 hangs probing floppy
Before eliminating fdc from the kernel I add another piece of info. If immediatedly after booting I put a floppy into the drive, the booting process goes on without problems. Any other. softer solution to tis problem. Vittorio Alle 17:51, martedì 30 gennaio 2007, Roland Smith ha scritto: On Tue, Jan 30, 2007 at 03:14:49PM +0100, Vittorio wrote: I updated my pentium 3 PC Compaq Desktop 450 from freebsd 5.3 (which was working like a charme indeed!) to the new 6.2 installing from a CD. It happens that the boot 1) runs smoothly as usual till after the probing of the CDs, 2) then the boot hangs for about 3 minutes probing the floppy (I see the floppy led turned on for the same time), 3) eventually again smoothly till the end of the booting process. I noticed that the /dev/fd0 device is not found and there's no way to mount it. Build a kernel without device fdc. Or maybe disable the floppy in the bios. Roland ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
6.2 hangs probing floppy
I updated my pentium 3 PC Compaq Desktop 450 from freebsd 5.3 (which was working like a charme indeed!) to the new 6.2 installing from a CD. It happens that the boot 1) runs smoothly as usual till after the probing of the CDs, 2) then the boot hangs for about 3 minutes probing the floppy (I see the floppy led turned on for the same time), 3) eventually again smoothly till the end of the booting process. I noticed that the /dev/fd0 device is not found and there's no way to mount it. What shall I do? Vittorio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2 hangs probing floppy
On Tue, Jan 30, 2007 at 03:14:49PM +0100, Vittorio wrote: I updated my pentium 3 PC Compaq Desktop 450 from freebsd 5.3 (which was working like a charme indeed!) to the new 6.2 installing from a CD. It happens that the boot 1) runs smoothly as usual till after the probing of the CDs, 2) then the boot hangs for about 3 minutes probing the floppy (I see the floppy led turned on for the same time), 3) eventually again smoothly till the end of the booting process. I noticed that the /dev/fd0 device is not found and there's no way to mount it. Build a kernel without device fdc. Or maybe disable the floppy in the bios. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpRY1GMk17wT.pgp Description: PGP signature
Re: Sysinstall: No Floppy Devices Found
Dan Mahoney, System Admin wrote: On Tue, 16 Jan 2007, Kevin Kobb wrote: I have found that when I do an install with an install.cfg file on a floppy, I must insert the floppy right after the system begins to boot from CD. If I don't when I tell sysinstall to read the floppy I get an error. I've found the floppy works okay when I escape to the bootloader, so I can load my KLD at that time. As a work around, if I go into the options and select rescan for hardware devices (not sure if that is the exact wording) after inserting the floppy disk, it will work OK as well. Might be worth a try. I'll be sure to try that, thanks. Any idea why it's not found initially, tho? I mean, the CONTROLLER is found, so... Is this the type of thing I should send-pr over? -Dan -- Be happy. Try not to hurt each other. Hope you fall in love. --Mallory, Family Ties Finale (on the meaning of life) Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I am not sure why this happens myself. I have also noticed that when I try to transfer a few files from floppy (during install my install.cfg mounts the floppy and copies a few custom scripts) the transfer is very slow, even by floppy disk speed standards. I haven't worried too much about it because I so seldom use floppies any more, and plan on getting a better install gameplan (PXE ?) if I install more than a few systems. Might be worth checking or filing a PR. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sysinstall: No Floppy Devices Found
Dan Mahoney, System Admin wrote: Hey all, I'm getting the message when I try to load a KLD in Sysinstall, even though I KNOW my floppy drive works. In fact, I can load the KLD from the loader prompt just fine. Is there a difference/advantage to one way of doing this over the other? -Dan Mahoney -- Hitler, Satan, those Hanson kids, anything. Just not the curious anteater. -Peter Scolari, as Wayne Szalinki in Honey, I Shrunk The Kids--The Series Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I have found that when I do an install with an install.cfg file on a floppy, I must insert the floppy right after the system begins to boot from CD. If I don't when I tell sysinstall to read the floppy I get an error. As a work around, if I go into the options and select rescan for hardware devices (not sure if that is the exact wording) after inserting the floppy disk, it will work OK as well. Might be worth a try. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sysinstall: No Floppy Devices Found
On Tue, 16 Jan 2007, Kevin Kobb wrote: I have found that when I do an install with an install.cfg file on a floppy, I must insert the floppy right after the system begins to boot from CD. If I don't when I tell sysinstall to read the floppy I get an error. I've found the floppy works okay when I escape to the bootloader, so I can load my KLD at that time. As a work around, if I go into the options and select rescan for hardware devices (not sure if that is the exact wording) after inserting the floppy disk, it will work OK as well. Might be worth a try. I'll be sure to try that, thanks. Any idea why it's not found initially, tho? I mean, the CONTROLLER is found, so... Is this the type of thing I should send-pr over? -Dan -- Be happy. Try not to hurt each other. Hope you fall in love. --Mallory, Family Ties Finale (on the meaning of life) Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Sysinstall: No Floppy Devices Found
Hey all, I'm getting the message when I try to load a KLD in Sysinstall, even though I KNOW my floppy drive works. In fact, I can load the KLD from the loader prompt just fine. Is there a difference/advantage to one way of doing this over the other? -Dan Mahoney -- Hitler, Satan, those Hanson kids, anything. Just not the curious anteater. -Peter Scolari, as Wayne Szalinki in Honey, I Shrunk The Kids--The Series Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problème avec le floppy disk.
Bonjour, Nous avons un problème au moment de l'installation d'un de nos logiciel: Lorsque que nous insérons une disquette et lançons notre commande d'installation, le message suivant apparait: /dev/fd0: Cannot read :Input/Output error At Beginning of tape - Quitting now Error is not recoverable: Exiting now Néanmoins, le lecteur de disquette fonctionne car nous utilisons plusieurs autres disquettes avant la disquette d'installation. Nous avons vérifié le BIOS et tout parait bien configuré... Pouvez vous nous aidez à résoudre notre problème? Cordialement ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problème avec le floppy disk.
Tribal, Grégory wrote: Bonjour, Nous avons un problème au moment de l'installation d'un de nos logiciel: Lorsque que nous insérons une disquette et lançons notre commande d'installation, le message suivant apparait: /dev/fd0: Cannot read :Input/Output error At Beginning of tape - Quitting now Error is not recoverable: Exiting now Néanmoins, le lecteur de disquette fonctionne car nous utilisons plusieurs autres disquettes avant la disquette d'installation. Nous avons vérifié le BIOS et tout parait bien configuré... Est-ce la disquette fonctionne? Est-ce que le filesystem de la disquette est de type msdosfs? Est-ce que vous pouvez lire la disquette sur une autre machine? Si vous pouvez répondre en anglais, vous aurez plus d'aide, cette liste est majoritairement anglophone. Je ne connais pas de liste francophone existe pour freebsd. Merci, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problème avec le floppy disk.
David Landgren wrote: Tribal, Grégory wrote: Bonjour, Nous avons un problème au moment de l'installation d'un de nos logiciel: Lorsque que nous insérons une disquette et lançons notre commande d'installation, le message suivant apparait: /dev/fd0: Cannot read :Input/Output error At Beginning of tape - Quitting now Error is not recoverable: Exiting now Néanmoins, le lecteur de disquette fonctionne car nous utilisons plusieurs autres disquettes avant la disquette d'installation. Nous avons vérifié le BIOS et tout parait bien configuré... Est-ce la disquette fonctionne? Est-ce que le filesystem de la disquette est de type msdosfs? Est-ce que vous pouvez lire la disquette sur une autre machine? Si vous pouvez répondre en anglais, vous aurez plus d'aide, cette liste est majoritairement anglophone. Je ne connais pas de liste francophone existe pour freebsd. http://www.freebsd.org/fr/community/mailinglists.html Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: fixit floppy contents?
Andy Dills wrote: Is there a standard way of installing complete filesystem images onto existing machines via the network, for example using dump, restore, nfs, and boot floppies? I want to upgrade our mail server cluster from 4-STABLE to 6-STABLE, and there is so much that goes into the mail server setup... postfix/amavisd-new/clamav/SA/Razor2/DCC/FuzzyOcr all chrooted, that's a lot of port installing and lib copying I don't feel like doing. I've got an image of the 6-STABLE box I'm happy with and I want to be able to serve it via NFS, then go through the cluster booting on (hopefully) the fixit floppy, format the disks and restore the image over nfs, edit some confs, and boot it and away it goes in a fraction of the time it would take to go from scratch with each. I'm not sure what tools the fixit floppy has. Anybody done anything like this before? Thanks, Andy I would look at FreeSBIE or some other LiveCD. It should not be to difficult to boot from a CD, do the needed disk and network setup and then simply pull the images from a server somewhere. Or just do a dump on the finished server, and pipe it to a local restore over ssh. -- R ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
fixit floppy contents?
Is there a standard way of installing complete filesystem images onto existing machines via the network, for example using dump, restore, nfs, and boot floppies? I want to upgrade our mail server cluster from 4-STABLE to 6-STABLE, and there is so much that goes into the mail server setup... postfix/amavisd-new/clamav/SA/Razor2/DCC/FuzzyOcr all chrooted, that's a lot of port installing and lib copying I don't feel like doing. I've got an image of the 6-STABLE box I'm happy with and I want to be able to serve it via NFS, then go through the cluster booting on (hopefully) the fixit floppy, format the disks and restore the image over nfs, edit some confs, and boot it and away it goes in a fraction of the time it would take to go from scratch with each. I'm not sure what tools the fixit floppy has. Anybody done anything like this before? Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fixit floppy contents?
On Thu, Dec 28, 2006 at 02:57:21PM -0500, Andy Dills wrote: Is there a standard way of installing complete filesystem images onto existing machines via the network, for example using dump, restore, nfs, and boot floppies? I want to upgrade our mail server cluster from 4-STABLE to 6-STABLE, and there is so much that goes into the mail server setup... postfix/amavisd-new/clamav/SA/Razor2/DCC/FuzzyOcr all chrooted, that's a lot of port installing and lib copying I don't feel like doing. I've got an image of the 6-STABLE box I'm happy with and I want to be able to serve it via NFS, then go through the cluster booting on (hopefully) the fixit floppy, format the disks and restore the image over nfs, edit some confs, and boot it and away it goes in a fraction of the time it would take to go from scratch with each. I'm not sure what tools the fixit floppy has. Anybody done anything like this before? The fixit floppy is basically a running system, minus extras like X stuff and the ports, that can be booted from the floppy - or preferrably from the CD. The first install CD also is a fixit, just choose the menu item to boot to a running system - I forget the label text. It is just basic FreeBSD Unix including necessary tools to deal with files. There are a number of ways of moving filesystems from one machine to another, including over the net. I am inclined to use dump/restore because it handles all situations of files and links and permissions, etc properly and doesn't get locked in to the sector-by-sector trap. But, you must create the filesystems yourself with either sysinstall or fdisk/bsdlabel/newfs. If you have room, the nicest thing is to create the file systems and then copy the dump file to the machine and restore it from there rather than over the net. But it will work over the net. Actually, it is possible to build your own install CD that just charges ahead and builds and installs things the way you want it. You may need more than one CD if you put a lot on - or make one to do the system build and then restore dump files on for the rest. jerry Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
umass external usb floppy devices
Greetings to all this morning, After several days of trying, reading, tweaking, and cursing.. I read up on supported umass usb devices supported by FreeBSD 6.1. The only umass usb external floppy drive I see in that list is a Panasonic external floppy. I have a TEAC FD-05PUB USB device. I can mount this device using mount_msdosfs /dev/da0 /mnt no problem. I can cd to this device, and ls and read the contents thereof. However, whenever I try to write to this device, I get device busy, among other messages which I cannot reproduce at the moment, because this is a dual boot machine and I'm on the other side of the HDD now. Does anyone know if there is a tweak, or a hack to get around this write problem with TEAC umass usb floppy drives? Thanks in advance. -- Rev. Z. Wade Hampton [EMAIL PROTECTED] Dedicated to those Rangers who laid down their lives; so that lesser men could be free to cry peace, when there was none. Author unknown ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Floppy drive problem
I rarely use them, but I have a floppy I needed to format and copy to. The problem is anything I try with the drive results in this error: Processing fdformat: ioctl(FD_FORM): Device not configured It shows up fine in dmesg, and I've used it before. fdc0: Enhanced floppy controller at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 These are brand new disks. Does anyone have a suggestion? BTW, I'm running the latest -CURRENT Thanks, Beech -- --- Beech Rintoul - Sys. Administrator - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Alaska Paradise \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com --- pgpvAC5Yv5cEa.pgp Description: PGP signature
Re: freebsd 6.1 floppy installation problem - boot loader finds only 16MB, but I have 256 MB - and it hangs
Hi. At Sat, 23 Sep 2006 21:49:20 +0200, Vo?ten?k Vladim?r wrote: I have an old HP NETSERVER PRO 2xpentium pro, 256 MB ram, and I tried to install the actual FREEBSD 6.1 there. I made 3 floppies: boot, kernel1 and kernel2. When it starts booting from the boot floppy, the loader show I only have 16 MB of RAM (instead 256MB I have there). Then it asks for kernel1 and 2 disk, and boot disk again. It gives me also the entry FREEBSD display with countdown - to choose boot type - default, no acpi, secure etc. I tried it all, but it alwaysl hangs after about 5 second after any choice. So I must just reboot. I think it is just because the lack of RAM, because, I think it requirets at least 24 MB of RAM. I have found something about this on the web, that it is necessary options MAXMEM=n to use all the RAM, because old BIOSes shows just first 16 MB or so, but I am just doing the installation. So how can I modify the kernel on the floppies to use such option during the installation from floppies? Or should I install from other media???Please can you help me with this??How can I make the installation boot floppy see all the RAM I have? Thank you very much for your reply. Greetings Vladimír Voštenák Choose 6. Escape to loader prompt from the boot menu and enter the two lines to the loader(8) prompt: set hw.physmem=256M boot See loader(8) for details. It's the same thing that you specify MAXMEM=256M to your kernel configulation file. --- Watanabe Kazuhiro ([EMAIL PROTECTED]) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd 6.1 floppy installation problem - boot loader finds only 16MB, but I have 256 MB - and it hangs
--- Vo¹tenák Vladimír [EMAIL PROTECTED] wrote: Hi I have an old HP NETSERVER PRO 2xpentium pro, 256 MB ram, and I tried to install the actual FREEBSD 6.1 there. I made 3 floppies: boot, kernel1 and kernel2. When it starts booting from the boot floppy, the loader show I only have 16 MB of RAM (instead 256MB I have there). Then it asks for kernel1 and 2 disk, and boot disk again. It gives me also the entry FREEBSD display with countdown - to choose boot type - default, no acpi, secure etc. I tried it all, but it alwaysl hangs after about 5 second after any choice. So I must just reboot. I think it is just because the lack of RAM, because, I think it requirets at least 24 MB of RAM. I have found something about this on the web, that it is necessary options MAXMEM=n to use all the RAM, because old BIOSes shows just first 16 MB or so, but I am just doing the installation. So how can I modify the kernel on the floppies to use such option during the installation from floppies? Or should I install from other media???Please can you help me with this??How can I make the installation boot floppy see all the RAM I have? Thank you very much for your reply. Greetings Vladimír Vo¹tenák make sure you don't have OS/2 compatability mode in your BIOS turned on. That will limit a system to 16 megs of RAM. I haven't played with an HP Netserver but I have several Kayaks that run things fine with about the same aged bios. -brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
freebsd 6.1 floppy installation problem - boot loader finds only 16MB, but I have 256 MB - and it hangs
Hi I have an old HP NETSERVER PRO 2xpentium pro, 256 MB ram, and I tried to install the actual FREEBSD 6.1 there. I made 3 floppies: boot, kernel1 and kernel2. When it starts booting from the boot floppy, the loader show I only have 16 MB of RAM (instead 256MB I have there). Then it asks for kernel1 and 2 disk, and boot disk again. It gives me also the entry FREEBSD display with countdown - to choose boot type - default, no acpi, secure etc. I tried it all, but it alwaysl hangs after about 5 second after any choice. So I must just reboot. I think it is just because the lack of RAM, because, I think it requirets at least 24 MB of RAM. I have found something about this on the web, that it is necessary options MAXMEM=n to use all the RAM, because old BIOSes shows just first 16 MB or so, but I am just doing the installation. So how can I modify the kernel on the floppies to use such option during the installation from floppies? Or should I install from other media???Please can you help me with this??How can I make the installation boot floppy see all the RAM I have? Thank you very much for your reply. Greetings Vladimír Voštenák ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Booting FreeBSD from floppy or CD
Hi All, Is it possible to boot FreeBSD from a floppy disk or a CD. I dont want the other users to know the OS is on the computer. Thanks Stan - Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting FreeBSD from floppy or CD
On Tue, 19 Sep 2006 01:52:07 -0700 (PDT) Stanley Wright [EMAIL PROTECTED] wrote: Is it possible to boot FreeBSD from a floppy disk or a CD. I dont want the other users to know the OS is on the computer. there are a few FreeBSD live-cds : http://www.freesbie.org http://livecd.sourceforge.net -- grtjs, albi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting FreeBSD from floppy or CD
On Tuesday 19 September 2006 09:52, Stanley Wright wrote: Hi All, Is it possible to boot FreeBSD from a floppy disk or a CD. I dont want the other users to know the OS is on the computer. I would suggest running the Gag bootmanager from a floppy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting FreeBSD from floppy or CD
Stanley Wright [EMAIL PROTECTED] writes: Is it possible to boot FreeBSD from a floppy disk or a CD. Sure. You just configure the loader(8) to find its kernel and root filesystem on the appropriate disk. If that's too tricky for you, there are lots of other boot loaders. Surely one of them will be to your taste. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting FreeBSD from floppy or CD
On Tue, Sep 19, 2006 at 01:52:07AM -0700, Stanley Wright wrote: Hi All, Is it possible to boot FreeBSD from a floppy disk or a CD. I dont want the other users to know the OS is on the computer. Wow, stealth FreeBSD. I haven't done it, but I think you can make a live CD and boot and run from that. But what about disk space to use - you will want to leave some stuff there somewhere to work on. Just getting it booted is not very exciting or fulfulling. Of course, if the other system on the machine is MS, and you squeeze it down to make room for some FreeBSD work space, it won't show up in MS. So, maybe no-one will notice the space shrinkage. You could go ahead and make it FreeBSD bootable too, but then they would see the FreeBSD boot select menu. You could put everything there, but replace the MBR with the MS one and then use the CD to start the boot and then select the FreeBSD slice from its menu and then just run from the disk. Then the CD is only needed for its MBR. I think that would work. Anyway, check the FreeBSD handbook on making a live CD and maybe someone else will also dip in their oar. So, what's so scarey about someone else knowing FreeBSD is on the machine? jerry Thanks Stan - freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting FreeBSD from floppy or CD
On Tue, 2006-09-19 at 10:49 -0400, Jerry McAllister wrote: On Tue, Sep 19, 2006 at 01:52:07AM -0700, Stanley Wright wrote: Hi All, Is it possible to boot FreeBSD from a floppy disk or a CD. I dont want the other users to know the OS is on the computer. Wow, stealth FreeBSD. I haven't done it, but I think you can make a live CD and boot and run from that. But what about disk space to use - you will want to leave some stuff there somewhere to work on. Just getting it booted is not very exciting or fulfulling. Of course, if the other system on the machine is MS, and you squeeze it down to make room for some FreeBSD work space, it won't show up in MS. So, maybe no-one will notice the space shrinkage. You could go ahead and make it FreeBSD bootable too, but then they would see the FreeBSD boot select menu. You could put everything there, but replace the MBR with the MS one and then use the CD to start the boot and then select the FreeBSD slice from its menu and then just run from the disk. Then the CD is only needed for its MBR. I think that would work. Anyway, check the FreeBSD handbook on making a live CD and maybe someone else will also dip in their oar. So, what's so scarey about someone else knowing FreeBSD is on the machine? jerry Thanks Stan - freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] A live CD such as Freesbie and a USB memory stick for personal storage should give you all you need. You can format the USB memory with the FreeBSD UFS filesystem, or leave is as a DOS FAT for compatibility with other operating systems. You won't need to change a single byte on the hard disk, and no one will know once you go away. If you are thwarting company or school policy, watch out! It might be much cheaper in the long run to buy another machine of your own. A used computer can be had for very little, and an older one will run FreeBSD just fine. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting FreeBSD from floppy or CD
- Original Message - From: Mike Jeays [EMAIL PROTECTED] To: Jerry McAllister [EMAIL PROTECTED] Subject: Re: Booting FreeBSD from floppy or CD Date: Tue, 19 Sep 2006 16:49:27 -0400 On Tue, 2006-09-19 at 10:49 -0400, Jerry McAllister wrote: On Tue, Sep 19, 2006 at 01:52:07AM -0700, Stanley Wright wrote: Hi All, Is it possible to boot FreeBSD from a floppy disk or a CD. I dont want the other users to know the OS is on the computer. Wow, stealth FreeBSD. I haven't done it, but I think you can make a live CD and boot and run from that. But what about disk space to use - you will want to leave some stuff there somewhere to work on. Just getting it booted is not very exciting or fulfulling. Of course, if the other system on the machine is MS, and you squeeze it down to make room for some FreeBSD work space, it won't show up in MS. So, maybe no-one will notice the space shrinkage. You could go ahead and make it FreeBSD bootable too, but then they would see the FreeBSD boot select menu. You could put everything there, but replace the MBR with the MS one and then use the CD to start the boot and then select the FreeBSD slice from its menu and then just run from the disk. Then the CD is only needed for its MBR. I think that would work. Anyway, check the FreeBSD handbook on making a live CD and maybe someone else will also dip in their oar. So, what's so scarey about someone else knowing FreeBSD is on the machine? jerry Thanks Stan - freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] A live CD such as Freesbie and a USB memory stick for personal storage should give you all you need. You can format the USB memory with the FreeBSD UFS filesystem, or leave is as a DOS FAT for compatibility with other operating systems. You won't need to change a single byte on the hard disk, and no one will know once you go away. If you are thwarting company or school policy, watch out! It might be much cheaper in the long run to buy another machine of your own. A used computer can be had for very little, and an older one will run FreeBSD just fine. yerps.. I've tried Freesbie and also NetBSD live cd.. it rocks!.. or maybe u can try normal installation without bootloader writing to /mbr.. maybe u can use GRUB on floppy or any other bootloader like SBM (SmartBootmanager) on floppy and point it to your FreeBSD slice.. gud luck! p/s: pls correct me if I'm wrong TQ -- ___ Play 100s of games for FREE! http://games.mail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Getting GELI Keys from Floppy
On Thursday 07 September 2006 00:00, Frank Steinborn wrote: Hello, i want to encrypt my HDD's with GELI (not the root-fs, though). I want to do the encryption without password, just with a key. The key should be stored in a floppy disk, and the read should be read automatically on boot, from the floppy. Are you sure you want to trust a floppy disk for your keys?? It's not the most safe medium these days... There is a problem here, because GELI initializes _before_ mounting the disks from /etc/fstab (for obvious reasons, of course). So GELI is not able to get the keys from the floppy and fails. So, any hints how I could get the floppy mounted _before_ GELI tries to initialize? Why don't you use the plain device(/dev/fd0) instead of using a file on a filesystem on the floppy? I think there are examples in the manual page. Anyway, I find this a very very bad idea. If the floppy break in some way you're gonna be in big trouble... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Getting GELI Keys from Floppy
Nikos Vassiliadis wrote: Are you sure you want to trust a floppy disk for your keys?? It's not the most safe medium these days... I'll backup the keys on CD. It's just that I don't want to waste a CD-ROM drive in this server. There is a problem here, because GELI initializes _before_ mounting the disks from /etc/fstab (for obvious reasons, of course). So GELI is not able to get the keys from the floppy and fails. So, any hints how I could get the floppy mounted _before_ GELI tries to initialize? Why don't you use the plain device(/dev/fd0) instead of using a file on a filesystem on the floppy? I think there are examples in the manual page. I could use /dev/fd0 directly but then I had to use the same key for all 6 HDD's in the server. I got a solution by hacking /etc/rc.d/geli - I'm just mounting the floppy there before it tries to read the key. Thanks for all the people giving suggestions! Frank ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Getting GELI Keys from Floppy
On Thu, 7 Sep 2006, Frank Steinborn wrote: I could use /dev/fd0 directly but then I had to use the same key for all 6 HDD's in the server. I got a solution by hacking /etc/rc.d/geli - I'm just mounting the floppy there before it tries to read the key. You could read different parts of the floppy for different keys. Speaking of which, do the keys have any identifiable strings in them? If not, you could fill the floppy with random garbage and 'hide' the key. I'm assuming since you don't want a password you don't want the boot to require interaction so it's not that useful, but if nothing else it would help if someone got access to the floppy (remotely or by physical access). -- Matt Piechota ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Getting GELI Keys from Floppy
Hello, i want to encrypt my HDD's with GELI (not the root-fs, though). I want to do the encryption without password, just with a key. The key should be stored in a floppy disk, and the read should be read automatically on boot, from the floppy. There is a problem here, because GELI initializes _before_ mounting the disks from /etc/fstab (for obvious reasons, of course). So GELI is not able to get the keys from the floppy and fails. So, any hints how I could get the floppy mounted _before_ GELI tries to initialize? Thanks in advance, Frank ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Is it possible to make a big floppy image to boot the freebsd installer?
Hi, I am want to make a floppy image for booting freebsd installer to install by network. So I can use 3COM DynamicAccess boot services to make a pxeboot menu to boot this image. By using DynamicAccess, I can make a pxeboot menu for many boot environment, such as WinPE, Dos, etc. Is it possible to make a floppy image with full FreeBSD installer environment? From 6.1-RELEASE ISO, I found there are 3 images, boot.flp, kernelX.flp, it can't be used for me. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it possible to make a big floppy image to boot the freebsd
Hi, I am want to make a floppy image for booting freebsd installer to install by network. So I can use 3COM DynamicAccess boot services to make a pxeboot menu to boot this image. By using DynamicAccess, I can make a pxeboot menu for many boot environment, such as WinPE, Dos, etc. Is it possible to make a floppy image with full FreeBSD installer environment? From 6.1-RELEASE ISO, I found there are 3 images, boot.flp, kernelX.flp, it can't be used for me. Well, that is essentially the way the CD installer is done. I made one of our variation of FreeBSD a few years back when it was only two floppies - had just gone up from 1 to 2. It would take me a while to remember what I had to do, but pretty much everything I did was right out of documentation with maybe a little research on some other online publication sites (OnLamp, etc). So, study a little and good luck, jerry Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bad floppy disks
At Mon, 8 May 2006 it looks like Kevin Kinsey composed: Marty Landman wrote: This is giving me problems for some reason. I've put the floppy images on a Debian box in my office and dd'd onto a floppy. The boot.flp worked but then with the kern1.flp - which I dd'd onto the same floppy as boot.flp had gone on, get this after a while: zf_read: fill error readin failed elf32_loadimage: read failed Unable to load a kernel! Yeah, hard to know. In our tests, failure rate for floppy diskettes, straight from a local discount retailer, is in the nominal 60% range. You could keep trying... ? Just last night I was just trying to get three good floppies from a brand new package of 10 to install on a Fujitsu Lifebook with only a floppy and could not believe the failure rate. Finally got 6.0 installed via NFS after the floppy experience. Which poses another issue for another email about having two ISO's available for an NFS install mounted on another system. They also seemed to be made of flimsier plastic for when I used to fold them in half in disgust it used to take more effort than it does now! -- Bill Schoolcraft | http://wiliweld.com If your life was full of nothing but sunshine, you would just be a desert. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bad floppy disks
On Monday 08 May 2006 23:49, Bill Schoolcraft wrote: Just last night I was just trying to get three good floppies from a brand new package of 10 to install on a Fujitsu Lifebook with only a floppy and could not believe the failure rate. I wonder if it might have more to do with the fact that these days the drives themselves just sit there seizing-up and gathering dust for months on end. A few months ago I bought a new floppy-drive just to flash a bios, the old drive had become really unreliable even though it had scarcely been used. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
