Re: Why Are You Using FreeBSD?
On 5/31/2012 12:52 PM, Damien Fleuriot wrote: On 5/31/12 6:37 PM, Nikos Vassiliadis wrote: On 5/31/2012 5:41 PM, Damien Fleuriot wrote: Furthermore, when upgrading the CARP Master firewall, we need to plan with the Project Manager a failover to the CARP Backup firewall. Yes, I know about pfsync, yes, we use it, no, it doesn't *instantly* sync sessions for PF. A bit offtopic on this thread, but isn't pfsync designed to do just that? instantly? With instantly I really mean: Communicate every change to the stable table to the other firewall in order to let the stateful connections survive a firewall failover. Obviously, some packets will be lost, but TCP connections should survive, right? I am not arguing, I ask. Nikos Updates aren't instantaneous, they're sent in bundles. This means that when you failover, you lose the connections that have completed a SYN/SYNACK/ACK sequence on your main firewall but which aren't synched on your backup. These connections will continue with the peer sending regular non-syn packets, which your backup-now-master PF will drop. On topic, if anyone has an awesome idea around this, I'm all ears, this exact topic is causing us some level of discomfort at work, when we need to swap firewalls for updates. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" I don't see this option on FreeBSD 9, but on OpenBSD pfsync has a defer flag that would appear to address your issue. The options are as follows: defer Defer transmission of the first packet in a state until a peer has acknowledged that the associated state has been inserted. See pfsync(4) for more information. -defer Do not defer the first packet in a state. This is the default. From pfsync(4) The pfsync interface will attempt to collapse multiple state updates into a single packet where possible. The maximum number of times a single state can be updated before a pfsync packet will be sent out is con- trolled by the maxupd parameter to ifconfig (see ifconfig(8) and the ex- ample below for more details). The sending out of a pfsync packet will be delayed by a maximum of one second. Where more than one firewall might actively handle packets, e.g. with certain ospfd(8), bgpd(8) or carp(4) configurations, it is beneficial to defer transmission of the initial packet of a connection. The pfsync state insert message is sent immediately; the packet is queued until ei- ther this message is acknowledged by another system, or a timeout has ex- pired. This behaviour is enabled with the defer parameter to ifconfig(8). I'm sure this could be ported over. -Nick ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Rancid/Expect failing on FreeBSD/SMP systems
Lars Erik Gullerud wrote: So it only seems to be on newer FreeBSD with SMP. (If anyone have RANCID working okay on FreeBSD 6.x/7.x on SMP systems at all, please let me know...) This probably won't be of much help, I figured I'd chime in anyway since it may effect me in the future, but I just haven't had any trouble with rancid on 7.x yet. It's only been in operation for 11 days though. FreeBSD .x.com 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Fri Dec 28 21:48:39 EST 2007 CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3059.98-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Features2=0x4400 real memory = 4026376192 (3839 MB) avail memory = 3937681408 (3755 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 I'm currently monitoring 18 cisco routers using ssh login, probably not enough to trigger the problem. grep -c up router.db 18 pkg_info -r rancid-2.3.1_2 Information for rancid-2.3.1_2: Depends on: Dependency: kbproto-1.0.3 Dependency: inputproto-1.4.2.1 Dependency: tcl-8.4.16,1 Dependency: perl-5.8.8_1 Dependency: p5-Scalar-List-Utils-1.19,1 Dependency: pkg-config-0.22_1 Dependency: xtrans-1.0.4 Dependency: xproto-7.0.10_1 Dependency: libXdmcp-1.0.2 Dependency: libXau-1.0.3_2 Dependency: libX11-1.1.3,1 Dependency: tk-8.4.16,2 Dependency: expect-5.43.0_3 Dependency: p5-PathTools-3.2501 Dependency: p5-CGI.pm-3.31,1 Dependency: p5-LockFile-Simple-0.2.6 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RocketRAID 2224
Dave Kingsley wrote: I am attemping to use a RocketRAID 2224 8 channel card to set up a storage server. The server board is an Intel SE7230NH1-E with a P4-D 2.8GHz, 2GB RAM. When I set up a RAID5 with 7 750GB drives I get nothing but wierdness. Using sysinstall -> Configure -> Fdisk I can see the full size: DISK Geometry: 547149 cyls/255 heads/63 sectors = 8789948685 sectors (4291967MB) But Label sees: Disk: da0 Partition name: da0s1 Free: 200014030 blocks (97663MB) What am I doing wrong? All of the drivers seem to installed; at least they say they are. Is this just too big for FreeBSD? I hope not! Help! Zero out the first few tracks of da0 to clean off any cruft and use gpt to create the label (from memory, did this August 2005) gpt create /dev/da0 gpt add /dev/da0 newfs -youroptionshere /dev/da0p1 - df -h /3ware FilesystemSizeUsed Avail Capacity Mounted on /dev/da0p14.0T3.8T161G96%/3ware ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp redial unsuccessful
Ulrich Spoerlein wrote: cpghost wrote: On Wed, Oct 04, 2006 at 08:51:48PM +0200, Ulrich Spoerlein wrote: Hello all, with my ADSL provider (a reseller of the german Telekom), I'm unable to make ppp redial after the link has been lost. With Telekom, you usually get disconnected every 24h hours, but you can simply reconnect if our ppp would support it. Have you added this to /etc/rc.conf? ppp_mode="ddial" Yes of course, as you can see, ppp(8) is not exiting, but entering an redial endless loop ... Ulrich Spoerlein Not that it helps you much, but I do see working pppoe redial behavior with Yahoo/AT&T dsl at a client site in the US. I can unhook the dsl line and it will autoreconnect as soon as it's plugged in again. In the event of a provider outage it comes back up on its own. The current ppp session has been running for 59 days, longest session was 353 days, but the server had to be moved for remodeling. ppp.conf : --- default: ident user-ppp VERSION (built COMPILATIONDATE) set device PPPoE:dc0 set log Phase Chat LCP IPCP CCP tun command set dial set ifaddr 10.0.0.1/0 10.0.0.2/0 add default HISADDR# Add a (sticky) default route set login enable dns # request DNS info (for resolv.conf) papchap: set authname x set authkey --- ppp commandline: /usr/sbin/ppp -quiet -ddial -nat papchap uname -a: FreeBSD .lan 4.11-STABLE FreeBSD 4.11-STABLE #1: Tue Apr 26 13:45:16 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ i386 current trimmed px axu: USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 55 0.0 1.5 2840 896 ?? Ss5Aug06 32:10.11 /usr/sbin/ppp -quiet -ddial -nat papchap ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp redial unsuccessful
Ulrich Spoerlein wrote: cpghost wrote: On Wed, Oct 04, 2006 at 03:37:37PM -0400, Nick Gustas wrote: Not that it helps you much, but I do see working pppoe redial behavior with Yahoo/AT&T dsl at a client site in the US. I can unhook the dsl line and it will autoreconnect as soon as it's plugged in again. In the event of a provider outage it comes back up on its own. The current ppp session has been running for 59 days, longest session was 353 days, but the server had to be moved for remodeling. Same here. I've got some 6.1-STABLE boxes running since 70 days uninterrupted on german T-Com ADSL (PPPoE). ppp redials automatically without any problems there. I maintain three FreeBSD boxes from 4.11 to 6.1-RELEASE and 6-STABLE. They have been showing this for at least 1 or 2 years. So it is/was also present in the 5.x line. I usually work around this by having a cron job that restarts ppp every day at 04:00 or somewhere around that. So either I'm just unlucky or I'm doing something fundamentally wrong. Could someone paste me the snippet from ppp.log of a successful 24h disconnect + redial? Thanks. Ulrich Spoerlein If all of those boxes are with the same provider I have to wonder if it's something on their end preventing the redial. I don't have physical access to the client box to pull the cable and I've only seen a drop in the event of an outage. Every time it has dropped, manually or otherwise, it gets a new IP address, and she generally has the same IP for months. My ppp.log only goes back 9 days because I've apparently been logging my LCP keepalives, so I don't have any reconnects in it. Sep 26 10:02:10 xxx ppp[55]: tun0: LCP: deflink: RecvEchoRequest(19) state = Opened Sep 26 10:02:10 xxx ppp[55]: tun0: LCP: deflink: SendEchoReply(19) state = Opened ^^ 9 days of that. However, I forced a reconnect by doing a ifconfig dc0 down ; sleep 30 ; ifconfig dc0 up in a screen session here's the resulting ppp.log, note the "Connect time: 5195480 secs:" or 60.133 days. Oct 4 19:00:43 xxx ppp[55]: tun0: LCP: deflink: RecvEchoRequest(122) state = Opened Oct 4 19:00:43 xxx ppp[55]: tun0: LCP: deflink: SendEchoReply(122) state = Opened Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: write (fd 1, len 86): Network is down Oct 4 19:02:30 xxx ppp[55]: tun0: CCP: deflink: State change Stopped --> Closed Oct 4 19:02:30 xxx ppp[55]: tun0: CCP: deflink: State change Closed --> Initial Oct 4 19:02:30 xxx ppp[55]: tun0: LCP: deflink: LayerDown Oct 4 19:02:30 xxx ppp[55]: tun0: LCP: deflink: State change Opened --> Starting Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: open -> lcp Oct 4 19:02:30 xxx ppp[55]: tun0: IPCP: deflink: LayerDown: 64.149.135.98 Oct 4 19:02:30 xxx ppp[55]: tun0: IPCP: deflink: State change Opened --> Starting Oct 4 19:02:30 xxx ppp[55]: tun0: IPCP: deflink: LayerFinish. Oct 4 19:02:30 xxx ppp[55]: tun0: IPCP: Connect time: 5195480 secs: 1934412196 octets in, 540652575 octets out Oct 4 19:02:30 xxx ppp[55]: tun0: IPCP: 3723224 packets in, 2819374 packets out Oct 4 19:02:30 xxx ppp[55]: tun0: IPCP: total 476 bytes/sec, peak 178816 bytes/sec on Tue Oct 3 15:25:50 2006 Oct 4 19:02:30 xxx ppp[55]: tun0: IPCP: deflink: State change Starting --> Initial Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: bundle: Terminate Oct 4 19:02:30 xxx ppp[55]: tun0: LCP: deflink: LayerFinish Oct 4 19:02:30 xxx ppp[55]: tun0: LCP: deflink: State change Starting --> Initial Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: Disconnected! Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: lcp -> logout Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: Disconnected! Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: logout -> hangup Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: Connect time: 5195483 secs: 1927138891 octets in, 546464385 octets out Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: 3740513 packets in, 2836661 packets out Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: total 476 bytes/sec, peak 177877 bytes/sec on Tue Oct 3 15:25:49 2006 Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: hangup -> opening Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: bundle: Establish Oct 4 19:02:30 xxx ppp[55]: tun0: Phase: deflink: Enter pause (3) for redialing. Oct 4 19:02:30 xxx ppp[55]: tun0: Chat: deflink: Reconnect try 1 of 0 Oct 4 19:02:33 xxx ppp[55]: tun0: Chat: deflink: Redial timer expired. Oct 4 19:02:33 xxx ppp[55]: tun0: Phase: deflink: Connected! Oct 4 19:02:33 xxx ppp[55]: tun0: Phase: deflink: opening -> dial Oct 4 19:02:33 xxx ppp[55]: tun0: Phase: deflink: dial -> carrier Oct 4 19:02:35 xxx ppp[55]: tun0: Phase: Received NGM_PPPOE_ACNAME (hook "62031030047548-") Oct 4 19:02
Re: UPDATE: ATA mkIII first official patches - please test!
Dag-Erling Smørgrav wrote: Søren Schmidt <[EMAIL PROTECTED]> writes: New version that fixes known problems so far etc now available: ah, just commit it already. it works for me, so it must be good enough ;) DES heh :) Works for me, but one problem, slaves attached to a Seagate master, don't show up :/ Tried a verbose boot, but it hung. Controller is a 4 port highpoint rocketraid in jbod mode. Drives are cabled and jumpered correctly, also tried CS mode, no difference. This was on 5.3 stable, may try MK3 on 6.0 tonight, vanilla 6.0 is fine. MK3 patched 5.3 dmesg from yesterday FreeBSD 5.3-STABLE #20: Wed Feb 9 17:51:03 EST 2005 root@:/usr/src/sys/i386/compile/OPPRESSION Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) Processor (1200.05-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc048 real memory = 1073217536 (1023 MB) avail memory = 1044873216 (996 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 agp0: port 0x1050-0x1053 mem 0xea10-0xea100fff,0xec00-0xefff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0x376,0x170-0 x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 7.3 (no driver attached) em0: port 0x1000-0x103f mem 0xe800-0xe801,0xe802-0xe803 irq 16 at device 8.0 on pci0 em0: Ethernet address: 00:07:e9:00:ae:36 em0: Speed:N/A Duplex:N/A pcib2: at device 16.0 on pci0 pci2: on pcib2 atapci1: port 0x2000-0x20ff,0x2880-0x2883,0x2888-0x288f,0x2884-0x2887,0x2890-0x2897 irq 17 at device 5.0 on pci2 ata2: on atapci1 ata3: on atapci1 atapci2: port 0x2400-0x24ff,0x2898-0x289b,0x28a0-0x28a7,0x289c-0x289f,0x28a8-0x28af irq 17 at device 5.1 on pci2 ata4: on atapci2 ata5: on atapci2 pci2: at device 8.0 (no driver attached) cpu0 on motherboard cpu1 on motherboard pmtimer0 on isa0 orm0: at iomem 0xe-0xe3fff,0xcc000-0xc,0xcb000-0xcbfff,0xca800-0xcafff,0xc-0xca7ff on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (memory) fdc1: cannot allocate I/O port (6 ports) Timecounters tick every 10.000 msec ad0: 76319MB at ata0-master UDMA100 ad4: 381554MB at ata2-master UDMA100 ad6: 190782MB at ata3-master UDMA100 ad8: 176700MB at ata4-master UDMA100 ad9: 95396MB at ata4-slave UDMA100 ad10: 156334MB at ata5-master UDMA133 ad11: 381554MB at ata5-slave UDMA100 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad0s1a As you can see the hitachi and maxtor mastered slaves showed up I don't have a recent non mk3 5.3 dmesg handy, but here is a working plain 6.0 dmesg from the same machine FreeBSD 6.0-CURRENT #1: Thu Feb 10 10:37:33 EST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/OP6 MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) Processor (1200.05-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc048 real memory = 1073217536 (1023 MB) avail memory = 1041399808 (993 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard cpu1 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 agp0: port 0x1050-0x1053 mem 0xea10-0xea100fff,0xec00-0xefff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.3 (no driver attached) em0: port 0x1000-0x103f mem 0xe800-0xe801,0xe802-0xe803 irq 16 at device 8.0 on pci0 em0: Ethernet address: 00:07:e9:00:ae:36 em0: Speed:N/A Duplex:N/A pcib2: at device 16.0 on pci0 pci2: on pcib2 atapci1: port 0x2000-0x20ff,0x2880-0x2883,0x2888-0x288f,0x2884-0x2887,0x2890-0x2897 irq 17 at device 5.0 on pci2 ata2: channel #0 on atapci1 ata3: ch
Re: charset conversion support in amd(8)
I have an old amd.map from 1999 or so that we use for a freebsd cd
server here at work, it uses a mount "type" of program. I don't see
this format documented in the current amd man pages, but it still works
on 6-stable.
You should be able to change the mount commands to mount_cd9660 and add
the -C option.
amd.map:
cdrom0 type:=program;\
fs:=/realmounts/cdrom0;\
mount:="/sbin/mount mount /realmounts/cdrom0";\
unmount:="/sbin/umount umount /realmounts/cdrom0"
cdrom1 type:=program;\
fs:=/realmounts/cdrom1;\
mount:="/sbin/mount mount /realmounts/cdrom1";\
unmount:="/sbin/umount umount /realmounts/cdrom1"
cdrom2 type:=program;\
fs:=/realmounts/cdrom2;\
mount:="/sbin/mount mount /realmounts/cdrom2";\
unmount:="/sbin/umount umount /realmounts/cdrom2"
cdrom3 type:=program;\
fs:=/realmounts/cdrom3;\
mount:="/sbin/mount mount /realmounts/cdrom3";\
unmount:="/sbin/umount umount /realmounts/cdrom3"
cdrom4 type:=program;\
fs:=/realmounts/cdrom4;\
mount:="/sbin/mount mount /realmounts/cdrom4";\
unmount:="/sbin/umount umount /realmounts/cdrom4"
cdrom5 type:=program;\
fs:=/realmounts/cdrom5;\
mount:="/sbin/mount mount /realmounts/cdrom5";\
unmount:="/sbin/umount umount /realmounts/cdrom5"
cdrom6 type:=program;\
fs:=/realmounts/cdrom6;\
mount:="/sbin/mount mount /realmounts/cdrom6";\
unmount:="/sbin/umount umount /realmounts/cdrom6"
fstab:
/dev/cd0 /realmounts/cdrom0 cd9660
ro,noauto 0 0
/dev/cd1 /realmounts/cdrom1 cd9660
ro,noauto 0 0
/dev/cd2 /realmounts/cdrom2 cd9660
ro,noauto 0 0
/dev/cd3 /realmounts/cdrom3 cd9660
ro,noauto 0 0
/dev/cd4 /realmounts/cdrom4 cd9660
ro,noauto 0 0
/dev/cd5 /realmounts/cdrom5 cd9660
ro,noauto 0 0
/dev/cd6 /realmounts/cdrom6 cd9660
ro,noauto 0 0
amd command line:
/usr/sbin/amd -p -a /cdrom -w 5 -c 10 /cdrom /etc/amd.map /cdrom
/etc/amd.map
directories to create:
mkdir -p /realmounts/cdrom0
mkdir -p /realmounts/cdrom1
mkdir -p /realmounts/cdrom2
mkdir -p /realmounts/cdrom3
mkdir -p /realmounts/cdrom4
mkdir -p /realmounts/cdrom5
mkdir -p /realmounts/cdrom6
mkdir /cdrom
It certainly looks hacky compared to your config, but it's worked from
freebsd 3.1 through now so I never changed it.
Marat N.Afanasyev wrote:
Hello!
I found that automount daemon configured to use cdrom device doesn't
support -C option to convert filenames to local charset. Is there any
ways to make it work?
my amd.map is as follows:
# $FreeBSD: src/etc/amd.map,v 1.9 2002/05/15 22:24:29 obrien Exp $
#
/defaults type:=host;fs:=${autodir}/${rhost}/host;rhost:=${key}
* opts:=rw,grpid,resvport,vers=3,proto=udp,nosuid,nodev
cdrom fs:=${autodir}/cdrom;type:=cdfs;opts:=ro;dev:=/dev/cd2
adding Ckoi8-r to opts doesn't solve the problem. I suppose one should
add charset conversion ability to amd itself. Am I right?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: charset conversion support in amd(8)
Marat N.Afanasyev wrote:
Nick Gustas wrote:
Marat N.Afanasyev wrote:
Hello!
I found that automount daemon configured to use cdrom device doesn't
support -C option to convert filenames to local charset. Is there
any ways to make it work?
my amd.map is as follows:
# $FreeBSD: src/etc/amd.map,v 1.9 2002/05/15 22:24:29 obrien Exp $
#
/defaults type:=host;fs:=${autodir}/${rhost}/host;rhost:=${key}
* opts:=rw,grpid,resvport,vers=3,proto=udp,nosuid,nodev
cdrom fs:=${autodir}/cdrom;type:=cdfs;opts:=ro;dev:=/dev/cd2
adding Ckoi8-r to opts doesn't solve the problem. I suppose one
should add charset conversion ability to amd itself. Am I right?
I have an old amd.map from 1999 or so that we use for a freebsd cd
server here at work, it uses a mount "type" of program. I don't see
this format documented in the current amd man pages, but it still
works on 6-stable.
You should be able to change the mount commands to mount_cd9660 and
add the -C option.
amd.map:
cdrom0 type:=program;\
fs:=/realmounts/cdrom0;\
mount:="/sbin/mount mount /realmounts/cdrom0";\
unmount:="/sbin/umount umount /realmounts/cdrom0"
cdrom1 type:=program;\
fs:=/realmounts/cdrom1;\
mount:="/sbin/mount mount /realmounts/cdrom1";\
unmount:="/sbin/umount umount /realmounts/cdrom1"
cdrom2 type:=program;\
fs:=/realmounts/cdrom2;\
mount:="/sbin/mount mount /realmounts/cdrom2";\
unmount:="/sbin/umount umount /realmounts/cdrom2"
cdrom3 type:=program;\
fs:=/realmounts/cdrom3;\
mount:="/sbin/mount mount /realmounts/cdrom3";\
unmount:="/sbin/umount umount /realmounts/cdrom3"
cdrom4 type:=program;\
fs:=/realmounts/cdrom4;\
mount:="/sbin/mount mount /realmounts/cdrom4";\
unmount:="/sbin/umount umount /realmounts/cdrom4"
cdrom5 type:=program;\
fs:=/realmounts/cdrom5;\
mount:="/sbin/mount mount /realmounts/cdrom5";\
unmount:="/sbin/umount umount /realmounts/cdrom5"
cdrom6 type:=program;\
fs:=/realmounts/cdrom6;\
mount:="/sbin/mount mount /realmounts/cdrom6";\
unmount:="/sbin/umount umount /realmounts/cdrom6"
fstab:
/dev/cd0 /realmounts/cdrom0 cd9660
ro,noauto 0 0
/dev/cd1 /realmounts/cdrom1 cd9660
ro,noauto 0 0
/dev/cd2 /realmounts/cdrom2 cd9660
ro,noauto 0 0
/dev/cd3 /realmounts/cdrom3 cd9660
ro,noauto 0 0
/dev/cd4 /realmounts/cdrom4 cd9660
ro,noauto 0 0
/dev/cd5 /realmounts/cdrom5 cd9660
ro,noauto 0 0
/dev/cd6 /realmounts/cdrom6 cd9660
ro,noauto 0 0
amd command line:
/usr/sbin/amd -p -a /cdrom -w 5 -c 10 /cdrom /etc/amd.map /cdrom
/etc/amd.map
directories to create:
mkdir -p /realmounts/cdrom0
mkdir -p /realmounts/cdrom1
mkdir -p /realmounts/cdrom2
mkdir -p /realmounts/cdrom3
mkdir -p /realmounts/cdrom4
mkdir -p /realmounts/cdrom5
mkdir -p /realmounts/cdrom6
mkdir /cdrom
It certainly looks hacky compared to your config, but it's worked
from freebsd 3.1 through now so I never changed it.
thanks, I made my config similar to yours and it works ;)
Glad it works for you! I was rather surprised at the lack of info in the
man pages about this setup.. I even rechecked the FreeBSD 3.3
amd/amd.conf man pages just now and they didn't list this option either,
maybe I'm missing it. Not sure where I found the original config, must
have been online at some point.
I suppose this quote from the amd(8) man page applies:
"A weird imagination is most useful to gain full advantage of all the
features."
-Nick
(inadvertent top posting fixed)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
