From owner-freebsd-small Sun Apr 30 6:27:51 2000 Delivered-To: freebsd-small@freebsd.org Received: from hydrant.intranova.net (msb-ts-slip10.UMDNJ.EDU [130.219.28.70]) by hub.freebsd.org (Postfix) with SMTP id 7AD2337BC8B for ; Sun, 30 Apr 2000 06:27:47 -0700 (PDT) (envelope-from oogali@intranova.net) Received: (qmail 60269 invoked from network); 29 Apr 2000 15:41:07 -0000 Received: from localhost.abuselabs.com (HELO localhost) (missnglnk@127.0.0.1) by localhost.abuselabs.com with SMTP; 29 Apr 2000 15:41:06 -0000 Date: Sat, 29 Apr 2000 11:41:06 -0400 (EDT) From: Omachonu Ogali To: Mike Wade Cc: freebsd-small@FreeBSD.ORG Subject: Re: Journaling Flash File System (JFFS) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wouldn't mounting the flash device as read-only achieve the same effect? (No, I don't know much about flash devices, if that was your next question). On Sat, 29 Apr 2000, Mike Wade wrote: > It seems there is a journal flash file system available for Linux > now. Information can be obtained from: > > http://www.developer.axis.com/software/jffs/ > > "JFFS is the Journaling Flash File System developed by Axis Communications > in Sweden, aimed at providing a crash/powerdown-safe filesystem for > disk-less embedded devices. It is released under the GPL, and the current > version works for the Linux 2.0 kernel series and memory-mapped > industry-standard flash-memories (aka NOR-flashes)." > > I certainly wouldn't mind seeing something like this for PicoBSD... > > --- > Mike Wade (mwade@cdc.net) > Director of Systems Administration > CDC Internet, Inc. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message > -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Apr 30 11:19:50 2000 Delivered-To: freebsd-small@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id C812337BC6F for ; Sun, 30 Apr 2000 11:19:44 -0700 (PDT) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id LAA15957; Sun, 30 Apr 2000 11:19:36 -0700 (PDT) Date: Sun, 30 Apr 2000 11:19:36 -0700 From: Brooks Davis To: Omachonu Ogali Cc: Mike Wade , freebsd-small@FreeBSD.ORG Subject: Re: Journaling Flash File System (JFFS) Message-ID: <20000430111936.A15334@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from oogali@intranova.net on Sat, Apr 29, 2000 at 11:41:06AM -0400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Apr 29, 2000 at 11:41:06AM -0400, Omachonu Ogali wrote: > Wouldn't mounting the flash device as read-only achieve the same effect? > (No, I don't know much about flash devices, if that was your next > question). Not if you want the ability to write to it... -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon May 1 18: 4:33 2000 Delivered-To: freebsd-small@freebsd.org Received: from gull.prod.itd.earthlink.net (gull.prod.itd.earthlink.net [207.217.121.85]) by hub.freebsd.org (Postfix) with ESMTP id E487E37B982; Mon, 1 May 2000 18:04:18 -0700 (PDT) (envelope-from eakeyson@earthlink.net) Received: from dell (ip232.stamford19.ct.pub-ip.psi.net [38.32.134.232]) by gull.prod.itd.earthlink.net (8.9.3/8.9.3) with SMTP id SAA13266; Mon, 1 May 2000 18:04:13 -0700 (PDT) From: "Edward W. Akeyson" To: Cc: Subject: 3.4-STABLE on IOPENER, no console output Date: Mon, 1 May 2000 21:04:12 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all: I am trying to get FreeBSD running on an Iopener, and am getting some strange behavior. I am running 3.4-STBLE, but during boot the screen and keyboard stop responding. It gets to "Booting [kernel]..." and then stops responding. However, it boots fine (I can hear the hard drive spin) and I can telnet and FTP into it from the server to which it is attached by PLIP. I have included the dmesg output and my kernel config file below. It is as if it is sending output to the serial console, and I do not want this. I haven't hooked up anything to the serial line, as this requires some interface circuitry first, so I don't know if this is the case really. I have tried "boot -h" at the boot: prompt trying to toggle it back to console output. Interestingly, in dmesg it says vga and sc0 not found although I know they are there and seen elsewhere in 4.0-STABLE on the same hardware(dmesg output for 4.0-stable can be seen here: http://www.kenseglerdesigns.com/cgi-bin/UltraBoard/UltraBoard.pl?Action=Show Post&Board=technical&Post=115&Idle=0&Sort=0&Order=Descend&Page=0&Session= ). I downloaded a Linux image to the Sandisk and it works the console fine. I will go to 4.0 if necessary, but I just want to know if this is a hardware problem (did I get a bum unit?) or a version problem. Could it be something else? Anyone know how I can solve this problem so that I can get on with my life!!! Script started on Mon May 1 20:54:02 2000 twinhead# uname -a FreeBSD twinhead.podunk.net 3.4-STABLE FreeBSD 3.4-STABLE #2: Mon May 1 18:49:32 GMT 2000 root@twinhead.podunk.net:/usr/src/sys/compile/IOPENER i386 twinhead# dmesg Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-STABLE #2: Mon May 1 18:49:32 GMT 2000 root@twinhead.podunk.net:/usr/src/sys/compile/IOPENER Timecounter "i8254" frequency 1193182 Hz CPU: IDT WinChip C6 (200.46-MHz 586-class CPU) Origin = "CentaurHauls" Id = 0x541 Stepping = 1 Features=0x8000b5 real memory = 31457280 (30720K bytes) avail memory = 28164096 (27504K bytes) Preloaded elf kernel "kernel" at 0xc028e000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x00 on pci0.1.0 chip2: rev 0x1b on pci0.7.0 ide_pci0: rev 0x06 on pci0.7.1 chip3: rev 0x20 on pci0.7.4 Probing for devices on PCI bus 1: vga0: rev 0x5c int a irq 15 on pci1.0.0 Probing for PnP devices: CSN 1 Vendor ID: YMH0020 [0x2000a865] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] Probing for devices on the ISA bus: sc0 not found atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2145MB (4394880 sectors), 4360 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 15MB (31360 sectors), 490 cyls, 2 heads, 32 S/T, 512 B/S wdc1 not found at 0x170 ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 vga0 not found npx0 on motherboard npx0: INT 16 interface changing root device to wd0s1a twinhead# cat /sys/i386/conf/IOPENER # # IOPENER- ide disks, etc # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.143.2.12 1999/05/14 15:12:26 jkh Exp $ machine "i386" #cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident GENERIC maxusers 32 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0 # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 controller pnp0 controller eisa0 controller pci0 #controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 #disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM #device acd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. #controller ncr0 #controller ahb0 #controller ahc0 #controller isp0 # This controller offers a number of configuration options, too many to # document here - see the LINT file in this directory and look up the # dpt0 entry there for much fuller documentation on this. #controller dpt0 #controller adv0 at isa? port ? cam irq ? #controller adw0 #controller bt0 at isa? port ? cam irq ? #controller aha0 at isa? port ? cam irq ? #controller scbus0 #device da0 #device sa0 #device pass0 #device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 #device mcd0 at isa? port 0x300 bio irq 10 #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 #device sio2 at isa? disable port "IO_COM3" tty irq 5 #device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 net irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? #controller vpo0 at ppbus? # # The following Ethernet NICs are all PCI devices. # #device ax0 # ASIX AX88140A #device de0 # DEC/Intel DC21x4x (``Tulip'') #device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) #device mx0 # Macronix 98713/98715/98725 (``PMAC'') #device pn0 # Lite-On 82c168/82c169 (``PNIC'') #device rl0 # RealTek 8129/8139 #device tl0 # Texas Instruments ThunderLAN #device tx0 # SMC 9432TX (83c170 ``EPIC'') #device vr0 # VIA Rhine, Rhine II #device vx0 # 3Com 3c590, 3c595 (``Vortex'') #device wb0 # Winbond W89C840F #device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 #device ep0 at isa? port 0x300 net irq 10 #device ex0 at isa? port? net irq? #device fe0 at isa? port 0x300 net irq ? #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 net irq 10 drq 0 #device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device cs0 at isa? port 0x300 net irq ? pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. #pseudo-device bpfilter 4 #Berkeley packet filter twinhead# exit Script done on Mon May 1 20:54:51 2000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon May 1 19: 3:37 2000 Delivered-To: freebsd-small@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id 130E037B999; Mon, 1 May 2000 19:03:28 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA04914; Mon, 1 May 2000 19:11:48 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005020211.TAA04914@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Edward W. Akeyson" Cc: freebsd-small@freebsd.org, freebsd-questions@freebsd.org Subject: Re: 3.4-STABLE on IOPENER, no console output In-reply-to: Your message of "Mon, 01 May 2000 21:04:12 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 May 2000 19:11:47 -0700 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am trying to get FreeBSD running on an Iopener, and am getting some > strange behavior. I am running 3.4-STBLE, but during boot the screen and > keyboard stop responding. ... > Interestingly, in dmesg it says vga and sc0 not found although I > know they are there and seen elsewhere in 4.0-STABLE on the same > hardware One would be inclined to draw the fairly obvious conclusion then that sometime between 3.4 and 4.0 something was fixed that allows us to see the iOpener's video. I'd recommend using 4.0 just on principle, anyway. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon May 1 19:12:14 2000 Delivered-To: freebsd-small@freebsd.org Received: from sofia.csl.sri.com (sofia.csl.sri.com [130.107.19.127]) by hub.freebsd.org (Postfix) with ESMTP id 98FB437B638 for ; Mon, 1 May 2000 19:12:09 -0700 (PDT) (envelope-from molter@sofia.csl.sri.com) Received: (from molter@localhost) by sofia.csl.sri.com (8.9.3/8.9.3) id TAA72545; Mon, 1 May 2000 19:13:05 -0700 (PDT) (envelope-from molter) From: Marco Molteni Date: Mon, 1 May 2000 19:13:05 -0700 To: "Edward W. Akeyson" Cc: freebsd-small@FreeBSD.ORG Subject: Re: 3.4-STABLE on IOPENER, no console output Message-ID: <20000501191305.A72524@sofia.csl.sri.com> Mail-Followup-To: "Edward W. Akeyson" , freebsd-small@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from eakeyson@earthlink.net on Mon, May 01, 2000 at 09:04:12PM -0400 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 01 May 2000, Edward W. Akeyson wrote: > I am trying to get FreeBSD running on an Iopener, and am getting some > strange behavior. I am running 3.4-STBLE, but during boot the screen and > keyboard stop responding. It gets to "Booting [kernel]..." and then stops > responding. However, it boots fine (I can hear the hard drive spin) and I > can telnet and FTP into it from the server to which it is attached by PLIP. > I have included the dmesg output and my kernel config file below. > > It is as if it is sending output to the serial console, and I do not want > this. I haven't hooked up anything to the serial line, as this requires some > interface circuitry first, so I don't know if this is the case really. [..] I have seen something similar on FreeBSD installed via the serial port. Check /boot/loader.conf for a line like console="vidconsole" # Set the current console if you have it set to something like "serial" (sorry, I don't remember the exact name), this will mean that the console will be the serial port. You can comment the line out and it should work. Marco -- Marco Molteni "rough consensus and running code" SRI International, System Design Laboratory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon May 1 19:15:36 2000 Delivered-To: freebsd-small@freebsd.org Received: from mass.cdrom.com (adsl-63-202-176-114.dsl.snfc21.pacbell.net [63.202.176.114]) by hub.freebsd.org (Postfix) with ESMTP id 155D037BA0C for ; Mon, 1 May 2000 19:15:34 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA04985; Mon, 1 May 2000 19:23:46 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005020223.TAA04985@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Marco Molteni Cc: "Edward W. Akeyson" , freebsd-small@FreeBSD.ORG Subject: Re: 3.4-STABLE on IOPENER, no console output In-reply-to: Your message of "Mon, 01 May 2000 19:13:05 PDT." <20000501191305.A72524@sofia.csl.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 May 2000 19:23:46 -0700 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 01 May 2000, Edward W. Akeyson wrote: > > > I am trying to get FreeBSD running on an Iopener, and am getting some > > strange behavior. I am running 3.4-STBLE, but during boot the screen and > > keyboard stop responding. It gets to "Booting [kernel]..." and then stops > > responding. However, it boots fine (I can hear the hard drive spin) and I > > can telnet and FTP into it from the server to which it is attached by PLIP. > > I have included the dmesg output and my kernel config file below. > > > > It is as if it is sending output to the serial console, and I do not want > > this. I haven't hooked up anything to the serial line, as this requires some > > interface circuitry first, so I don't know if this is the case really. > > [..] > > I have seen something similar on FreeBSD installed via the serial port. > Check /boot/loader.conf for a line like > > console="vidconsole" # Set the current console > > if you have it set to something like "serial" (sorry, I don't remember > the exact name), this will mean that the console will be the serial > port. You can comment the line out and it should work. That would be "comconsole", but it takes effect earlier than this. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu May 4 10:35:11 2000 Delivered-To: freebsd-small@freebsd.org Received: from lastmile.lastmile.ru (lastmile.lastmile.ru [194.135.17.195]) by hub.freebsd.org (Postfix) with ESMTP id C039037C13C for ; Thu, 4 May 2000 10:34:49 -0700 (PDT) (envelope-from yaa@lastmile.ru) Received: from yaa (artkino.artkino.ru [194.135.17.197]) by lastmile.lastmile.ru (8.9.1/8.8.7) with SMTP id VAA13953 for ; Thu, 4 May 2000 21:44:38 GMT (envelope-from yaa@lastmile.ru) Message-ID: <001401bfb5ef$0566d620$0200a8c0@yaa> From: "Andrew Yugai" To: Subject: DiskOnChip multipartition problems Date: Thu, 4 May 2000 21:34:07 +0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01BFB610.7A33A480" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01BFB610.7A33A480 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable I need to divide my Flash into two parts. I've created partitions by means of fdisk (sysinstall), but formatting seem to be a problem. Attempts of formatting (disklabel and newfs) as shown in = /usr/src/sys/contrib/dev/fla/prep.fla.sh gave no results, since this file is used for formatting the whole Flash disk. Please, help me with formatting! Andrew. ------=_NextPart_000_0007_01BFB610.7A33A480 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
I need to divide my Flash into = two parts.=20 I've created partitions by
means of fdisk (sysinstall), but = formatting=20 seem to be a problem.
Attempts of formatting (disklabel = and newfs)=20 as shown in /usr/src/sys/contrib/dev/fla/prep.fla.sh = gave=20 no results, since
this file is used for formatting = the whole=20 Flash disk. Please, help me
with formatting!
 
Andrew.
------=_NextPart_000_0007_01BFB610.7A33A480-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message