Re: Text editor
Hi your answers help me a lot, I just want to know exactly what you said!! how many options I have around text editors. Finally,I will use vi, perhaps like you said is the harder option but if a lot of UNIX people use it and recommand that means something... Thank you very much for all the info ;) Salutes, Mike Mike Henker escribis: Hi yesterday I installed OpenBSD 3.7 seem to be all ok, my question is how I can edit the files of the operating system,what editor you recommand? (I m a newbie) If isn t in the default installation how can I install it? I saw the FAQ and the man but I can t find info about this doubt. Thanks Salutes, Mike
Re: Text editor
J.C. Roberts wrote: 3.) Learn ed -If vi is not installed, ed probably is. Some ancient systems don't have vi but the odds of coming across such a system are fairly slim. The only text editor in bsd.rd is ed, so chances are that one may have to use it on occasion (shudder). /Sigfred
Re: Text editor
On Sunday, 7 August 2005 at 9:34:18 +0200, Sigfred Heversen wrote: The only text editor in bsd.rd is ed, so chances are that one may have to use it on occasion (shudder). And if you are in support role, sometimes you have to tell someone on the phone how to edit system config files (in single user mode) with ed. Life is tough :-) Zoong
Re: Text editor
On Sun, Aug 07, 2005 at 06:21:55PM +1000, Zoong PHAM wrote: On Sunday, 7 August 2005 at 9:34:18 +0200, Sigfred Heversen wrote: The only text editor in bsd.rd is ed, so chances are that one may have to use it on occasion (shudder). And if you are in support role, sometimes you have to tell someone on the phone how to edit system config files (in single user mode) with ed. Life is tough :-) shudder? tough? it is 166kb of kick ass editor that will save your life someday. all hail and revel in the glory that is ed(1)! SEE ALSO A Tutorial Introduction to the UNIX Text Editor, /usr/share/doc/usd/09.edtut/. jmc
Re: Text editor
I'm surprised everyone keeps recommending using vi and vim, yet no one has given a pointer on how to learn it. Sure, an OReilly book may come in handly for this (such as the pocket version of vi tips), but the best way to learn is of course to read the man page. Aside from the man page, if you install vim (which i highly recommend), there is a little program/script/whatever called vimtutor that will get you familiar with vi/vim. I hop this helps a little bit. Good luck.. and welcome to UNIX (not those linux wannabees :P) On 8/7/05, Jason McIntyre [EMAIL PROTECTED] wrote: On Sun, Aug 07, 2005 at 06:21:55PM +1000, Zoong PHAM wrote: On Sunday, 7 August 2005 at 9:34:18 +0200, Sigfred Heversen wrote: The only text editor in bsd.rd is ed, so chances are that one may have to use it on occasion (shudder). And if you are in support role, sometimes you have to tell someone on the phone how to edit system config files (in single user mode) with ed. Life is tough :-) shudder? tough? it is 166kb of kick ass editor that will save your life someday. all hail and revel in the glory that is ed(1)! SEE ALSO A Tutorial Introduction to the UNIX Text Editor, /usr/share/doc/usd/09.edtut/. jmc
Re: Text editor
On Sun, 7 Aug 2005, imEnsion wrote: I'm surprised everyone keeps recommending using vi and vim, yet no one has given a pointer on how to learn it. Sure, an OReilly book may come in handly for this (such as the pocket version of vi tips), but the best way to learn is of course to read the man page. Which refers you to An Introduction to Display Editing with Vi, /usr/share/doc/usd/12.vi/. This document is the closest thing available to an introductionto the vi screen editor. -Otto
Re: wi0 troubles
Greg Thomas wrote : Better luck now. Things started working better when I got an off-list email suggesting to upgrade to 1.1.1/1.8.2. I tried 1.1.1/1.8.0, 1.1.1/1.8.2, and 1.1.1/1.8.4 and this was the result: Aug 6 18:47:43 grits /bsd: wi0 at pcmcia0 function 0 INTERSIL, HFA384x/IEEE, Version 01.02 port 0xa000/64 Aug 6 18:47:43 grits /bsd: wi0: PRISM2.5 ISL3873, Firmware 1.1.1 (primary), 1.8.0 (station), address 00:02:6f:08:0d:85 Aug 6 18:50:05 grits /bsd: wi0: init failed Aug 6 18:50:05 grits /bsd: wi0: failed to allocate 1594 bytes on NIC Aug 6 18:50:05 grits /bsd: wi0: tx buffer allocation failed Aug 6 18:50:05 grits /bsd: wi0: failed to allocate 1594 bytes on NIC Aug 6 18:50:05 grits /bsd: wi0: mgmt. buffer allocation failed Aug 6 18:50:05 grits /bsd: wi0: wi_start: xmit failed Hi, I've got the same trouble with a prism2 under 3.7 (stable) / sparc64 (U10) : pciide1: channel 1 configured to native-PCI mode wi0 at pci2 dev 4 function 0 US Robotics WL11000P rev 0x02: ivec 1c wi0: U.S. Robotics, IEEE 802.11b PC-CARD, Version 01.02 wi0: PRISM2 HWB3163 rev.A, Firmware 0.3.0 (primary), 1.4.9 (station), address 00:90:d1:08:19:8e wi0: init failed wi0: failed to allocate 1594 bytes on NIC wi0: tx buffer allocation failed wi0: failed to allocate 1594 bytes on NIC wi0: mgmt. buffer allocation failed it was the same OpenBSD 3.5 stable ... but not with the 3.4. The prism2 was running fine under OpenBSD 3.4 stable. -- batou aka Jean-marc from France
Re: Text editor
Otto Moerbeek wrote: On Sun, 7 Aug 2005, imEnsion wrote: I'm surprised everyone keeps recommending using vi and vim, yet no one has given a pointer on how to learn it. Sure, an OReilly book may come An Introduction to Display Editing with Vi, /usr/share/doc/usd/12.vi/. This document is the closest thing available to an introductionto the vi screen editor. To learn the basics of vi, vim comes in handy. After installing vim, one can use vimtutor to learn-by-doing all the useful basics in roughly 30 minutes - and those work in our base nvi as well. It is well-written and very effective at teaching vi. Afterwards one is skilled enough to appreciate the complete documentation and do any configuration work and/or nvi-based programming on OpenBSD without (further) packages installed. Moritz
Install Woes (3.7/sparc) - Spontaneous crashes
I'm attempting to install OBSD 3.7 sparc on a Sparcstation 20. I've been through installs numerous times on 20's, 2's, and an IPC using previous OBSD versions. Currently, I only have one install method -- floppy. I could conceivably set up a netboot install or wrangle a CDR drive if need be. The problem is this: every time I attempt to install, I get part-way or all the way through the package download process, and the installer bombs, dumps hex to the screen, and drops back into OFW. I don't have serial console, either: I'm using a monitor and keyboard, so it's tough to say what, if any, error messages may be present. The more packages I attempt to install, the more likely it is to crash in the middle of download. If I reduce the packages to bsd and base37.tgz, I can often get as far as building nodes before the crash. This system seemed to happily run Solaris 7, booting all the way into CDE and running seeral apps at once without bombing, so I'm hesitant to start yanking RAM, but if that's the only thing suspect, I'll do it. So, my questions are: any ideas what could be causing this? The farthest I've gotten is a bootable system with no network, so the possibility of a partial-install with manual addition of the other packages seems questionable. Any suggestions for what I might do to get through a complete install? Thanks, JMF
Re: Text editor
You guys are all sissies. Real men use cat(1).
Re: Text editor
If you install the port vim, it comes with vimtutor. You just type: $ /usr/local/bin/vimtutor And the tutor is pretty good. It helped me out. Brian Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs
Re: Text editor
You can use mg on OpenBSD. All you have to learn to get started is that ctrl-x ctrl-c saves the file and exits. # Han
Re: cpuburn: operation not permitted
On Fri, Aug 05, 2005 at 06:02:42PM -0500, Marco Peereboom wrote: On Fri, Aug 05, 2005 at 04:24:41PM -0500, Matt Garman wrote: Has anyone stress-tested their CPU under OpenBSD? In particular, I'd like to run the cpuburn program: http://pages.sbcglobal.net/redelm/ However, when I try to run any of the executables (even as root), it says Operation not permitted. What is you goal? I'd like to load the CPU as much as possible, while at the same time monitoring temperatures, so that I can make sure my computer doesn't overheat. (I just built a fanless Via Epia (CL600) Mini-ITX system, and stuffed it in a small case; even unloaded it gets somewhat warm to the touch, so I want to make sure it can handle a full load.) Thanks! Matt -- Matt Garman email at: http://raw-sewage.net/index.php?file=email
hlt-instruction
How do I enable the hlt-thing in obsd 3.7? I installed on a k6-3 with via vt82c598 and vt82c596 chipset. It used to show in dmesg: checking hlt ok or something like that. But it does not now. Anders Anders Henningsson [EMAIL PROTECTED]
Re: Text editor
Richard P. Koett wrote: X-Mailer: Microsoft Office Outlook, Build 11.0.6353 You guys are all sissies. Real men use cat(1). What kind of men use Outlook? Well, at least you can still do: C:\ copy con stuff.bat @echo off del /s * nul ^Z C:\ stuff
Re: Text editor
On 8/6/05, Gerardo Santana Gsmez Garrido [EMAIL PROTECTED] wrote: On 8/6/05, Mike Henker [EMAIL PROTECTED] wrote: Hi yesterday I installed OpenBSD 3.7 seem to be all ok, my question is how I can edit the files of the operating system,what editor you recommand? (I m a newbie) If isn t in the default installation how can I install it? I saw the FAQ and the man but I can t find info about this doubt. Thanks Salutes, Mike vi is my editor of choice. But if you don't have a UNIX background you might want to try joe. We need to be very carefull with the tools we learn as a student and the ones as we teach as a professor. That's because the tools we use shape the way we think and solve problems and will dictate aour thinking habit to the selenity. Unlearning is not a possible experience. So, we you have no experience with computer, start with unix, if you have no experience editing in unix env, start with vi, it's the only safe choice, it there, every where, in each unix flavor and is very mature. My 4 cents. -- Gerardo Santana Gsmez Garrido http://www.openbsd.org.mx/santana/ Entre los individuos, como entre las naciones, el respeto al derecho ajeno es la paz -Don Benito Juarez
Re: Install Woes (3.7/sparc) - Spontaneous crashes
On Sun, 7 Aug 2005 11:28:55 -0400, Jim Fron [EMAIL PROTECTED] wrote: I'm attempting to install OBSD 3.7 sparc on a Sparcstation 20. I've been through installs numerous times on 20's, 2's, and an IPC using previous OBSD versions. Currently, I only have one install method -- floppy. I could conceivably set up a netboot install or wrangle a CDR drive if need be. The problem is this: every time I attempt to install, I get part-way or all the way through the package download process, and the installer bombs, dumps hex to the screen, and drops back into OFW. I don't have serial console, either: I'm using a monitor and keyboard, so it's tough to say what, if any, error messages may be present. The more packages I attempt to install, the more likely it is to crash in the middle of download. If I reduce the packages to bsd and base37.tgz, I can often get as far as building nodes before the crash. This system seemed to happily run Solaris 7, booting all the way into CDE and running seeral apps at once without bombing, so I'm hesitant to start yanking RAM, but if that's the only thing suspect, I'll do it. So, my questions are: any ideas what could be causing this? The farthest I've gotten is a bootable system with no network, so the possibility of a partial-install with manual addition of the other packages seems questionable. Any suggestions for what I might do to get through a complete install? Thanks, JMF Floppy drives and diskettes are notorious for failing in very strange and unusual ways. Check out the mild but insightful message from Art on tech@ if you want to know the general consensus on floppies. From: Artur Grabowski art@ Message-ID: [EMAIL PROTECTED] In your situation, setting up serial is worthwhile if for no other reason than posting debug info to the list. If you've got spare openbsd/unix machine with a free serial port and a null modem cable, you're good to go. Note, that's a *null*modem* cable, not a straight wired serial cable. On the spare machine use tip(8) Make sure you've got the needed entry in remote(5). unix9600|9600 Baud dial-out to another UNIX system:\ :el=^U^C^R^O^D^S^Q:ie=%$:oe=^D:tc=dial1200:\ :br=#9600:dv=/dev/tty00: Run tip % sudo tip unix9600 On your spare machine, you could also serve ftp for the install *.tgz files as well as dhcp and netboot images. On the problematic SS20, disconnect the keyboard and monitor since on some (most/all/?) sun systems if you boot with a keyboard attached, the system will use it. If the keyboard is not attached, it will default to serial console. Then power up the SS20. With any luck, you've just have a bad floppy diskette and the netboot/serial/ftp install will work just fine. If not, you've got the needed debug info to figure out the problem. JCR
Re: Install Woes (3.7/sparc) - Spontaneous crashes
On Aug 7, 2005, at 2:46 PM, J.C. Roberts wrote: Floppy drives and diskettes are notorious for failing in very strange and unusual ways. Check out the mild but insightful message from Art on tech@ if you want to know the general consensus on floppies. That's good to know. Unfortunately, most of my machines (mac) don't have serial ports. My other sparc box is the reason I'm trying to configure this one: it stopped responding to the serial port and keyboard, it displays only a blank white screen on the monitor, and the ethernet port that didn't have all inbound services pf-blocked died on me, so I can't ssh into it. It's my NAT/firewall, and, though I have no way of getting into or out of the box, it's still running, and I don't want to risk powering it down until I have a replacement configured. :-/ So, going with the idea that floppies are just unreliable, I seem to have three options: 1. Use the floppy to boot, exit the installer, and install and configure manually (it doesn't seem to crash when I ftp tarballs in, but crashes regularly when I use the installer to do it). Has anyone written a walk-through for doing this? 2. Figure out how to configure OSX (client) as a netboot server. 3. Buy an OBSD CD, unplug the SCSI CDR drive from the running firewall and hope it doesn't crash. I'm eyeing option #1 right now.
Re: Text editor
http://www.gnu.org/fun/jokes/ed.msg.html Ed, man! !man ed On Sun, 7 Aug 2005, Richard P. Koett wrote: Date: Sun, 7 Aug 2005 09:01:40 -0700 From: Richard P. Koett [EMAIL PROTECTED] To: misc@openbsd.org Subject: Re: Text editor You guys are all sissies. Real men use cat(1).
Re: Text editor
On Sun, 7 Aug 2005 19:34:44 + (GMT), Paul Pruett [EMAIL PROTECTED] wrote: http://www.gnu.org/fun/jokes/ed.msg.html Ed, man! !man ed From the paged linked above: Let's look at a typical novice's session with the mighty ed: golem$ ed ? help ? ? ? quit ? exit ? bye ? hello? ? eat flaming death ? ^C ? ^C ? ^D ? An now I have to wonder if I've been hacked by someone who wants to record all my console sessions... ;-) JCR -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Install Woes (3.7/sparc) - Spontaneous crashes
On Sun, 7 Aug 2005 15:18:40 -0400, Jim Fron [EMAIL PROTECTED] wrote: On Aug 7, 2005, at 2:46 PM, J.C. Roberts wrote: Floppy drives and diskettes are notorious for failing in very strange and unusual ways. Check out the mild but insightful message from Art on tech@ if you want to know the general consensus on floppies. That's good to know. Unfortunately, most of my machines (mac) don't have serial ports. At times I wonder if Apple not supporting serial is smart or dumb but I never seem to come to a conclusion... A USB to serial device may do the trick but personally, I've never tried it. My other sparc box is the reason I'm trying to configure this one: it stopped responding to the serial port and keyboard, it displays only a blank white screen on the monitor, and the ethernet port that didn't have all inbound services pf-blocked died on me, so I can't ssh into it. It's my NAT/firewall, and, though I have no way of getting into or out of the box, it's still running, and I don't want to risk powering it down until I have a replacement configured. :-/ So, going with the idea that floppies are just unreliable, I seem to have three options: 1. Use the floppy to boot, exit the installer, and install and configure manually (it doesn't seem to crash when I ftp tarballs in, but crashes regularly when I use the installer to do it). Has anyone written a walk-through for doing this? 2. Figure out how to configure OSX (client) as a netboot server. 3. Buy an OBSD CD, unplug the SCSI CDR drive from the running firewall and hope it doesn't crash. I'm eyeing option #1 right now. Hopefully you've tried redownloading and reimaging on a new floppy diskette. The diskette could be the problem but if the created floppy is passing the test in the OBSD Install FAQ, the only possibility left for floppy being the cause is a bad diskette drive in the SS20 (or the drive just has dirty heads). I don't have the bandwidth to mess around with multiple/repeated FTP installs from the internet. It takes too long, so I usually transfer the files once and then host the FTP locally. It makes installs a lot easier. Option #2 with a local FTP server might work but getting a serial console on the beast should be your goal. If you've got flaky hardware in the SS20, you don't want to use it as a replacement for your (currently failing) firewall. Serial is probably the best way to figure out what the heck is going wrong. Using your MacOS box with tip and a USB-serial converter might just work. JCR -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
Re: Install Woes (3.7/sparc) - Spontaneous crashes
Jim Fron wrote: I'm attempting to install OBSD 3.7 sparc on a Sparcstation 20. I've been through installs numerous times on 20's, 2's, and an IPC using previous OBSD versions. Currently, I only have one install method -- floppy. I could conceivably set up a netboot install or wrangle a CDR drive if need be. The problem is this: every time I attempt to install, I get part-way or all the way through the package download process, and the installer bombs, dumps hex to the screen, and drops back into OFW. I don't have serial console, either: I'm using a monitor and keyboard, so it's tough to say what, if any, error messages may be present. The more packages I attempt to install, the more likely it is to crash in the middle of download. If I reduce the packages to bsd and base37.tgz, I can often get as far as building nodes before the crash. This system seemed to happily run Solaris 7, booting all the way into CDE and running seeral apps at once without bombing, so I'm hesitant to start yanking RAM, but if that's the only thing suspect, I'll do it. Sounds like one of two things: either 1) No one has ever installed OpenBSD 3.7 on a SS20, and you have discovered that it really doesn't work. 2) Your computer is broke. While it may be argued that I am a no one, it isn't due to the fact that I have installed OpenBSD 3.7 on an SS20. Two SS20, in fact, testing both CDROM and floppy based installs. It isn't #1. Your computer is broke. Get troubleshooting. Your description sounds just like a memory problem, the more your install, the more memory the system uses. MAKEDEV uses a LOT of RAM. If another OS fails on the same hardware, you can be pretty sure it is bad hardware. If another OS is still working, it is at best a suggestion that it might NOT be hardware. As the system is fully booting the kernel, I don't think it is a floppy problem. Nick.
Test
Test
Re: Install Woes (3.7/sparc) - Spontaneous crashes
On Aug 7, 2005, at 4:23 PM, J.C. Roberts wrote:' At times I wonder if Apple not supporting serial is smart or dumb but I never seem to come to a conclusion... OT: I think it's dumb. But that's from the standpoint of someone who does more with computers than 95% of the population. I also thought it was dumb to dump standard SCSI, and dumb to drop OFW/PPC for, presumably, a PC BIOS that may or may not support nice features like mouse-driven FW, netboot, target disk mode, and their plethora of long-standing startup key combinations. But big companies don't make computers for people like me, they make them for people who live at the mall. A USB to serial device may do the trick but personally, I've never tried it. I have a half-broken one, but I'll have to get out the soldering iron and hack up some old cables to make a functional din-db25 null-modem cable if I have to. Hopefully you've tried redownloading and reimaging on a new floppy diskette. The 'sum is correct. It could be the floppy, or the fd. I've had bad floppy problems before. Walking through the install script manually, it seems to be crashing at MAKEDEV. When using the install script, it would sometimes crash at (probably) MAKEDEV, and sometimes during ftp. I think I probably will need that serial console. Perhaps I have a bad SCSI drive. I don't have the bandwidth to mess around with multiple/repeated FTP installs from the internet. It takes too long, so I usually transfer the files once and then host the FTP locally. It makes installs a lot easier. I've been doing that. Well, I did that, found that it crashed sooner in the process when I did, and then tried FTP to an external site. If increased speed is causing me problems, I'm thinking I may have a bad disk or main board. Fsck. If you've got flaky hardware in the SS20, you don't want to use it as a replacement for your (currently failing) firewall. Probably. Well, one crap keyspan USB/serial device and one, possibly now two crap SS20's has taught me a lesson: for the money, it may be better to go out and but a cheap sh*t Wal-Mart PC instead of buying good hardware off eBay.
Re: cpuburn: operation not permitted
On Sun, Aug 07, 2005 at 12:49:02PM -0500, Matt Garman wrote: I'd like to load the CPU as much as possible, while at the same time monitoring temperatures, so that I can make sure my computer doesn't overheat. Try running blogbench - http://blogbench.pureftpd.org/ - it brings hardware to its knees and it can help to discover overheating.
Re: Text editor
On 2005-08-07 09:01:40 -0700, Richard P. Koett wrote: Real men use cat(1). And real women use magnets. :-) Best Martin -- http://www.tm.oneiros.de
Sparc QFE repeatable crashes [was: Install Woes (3.7/sparc) - Spontaneous crashes]
On Aug 7, 2005, at 4:42 PM, Nick Holland wrote: Your description sounds just like a memory problem, the more your install, the more memory the system uses. MAKEDEV uses a LOT of RAM. Well, I started by pulling out all the core, and swapping them in 2 at a time (2 @16Mb each). At first I was having issues with all combinations, and started to get worried. Then I stumbled on it: there was one sure thing I could do that would always crash the system: `ifconfig -a` I pulled out the qfe SBUS card, and it's stable as can be, with all core tested in pairs of 2, and with all 128Mb installed. I've added [EMAIL PROTECTED], as this may be platform-specific. Strange thing is, the card works. I used it under Solaris to transfer the 3.7 boot floppy image in. I used it with the boot floppy to grab all the files via FTP. The installation process would sometimes crash during FTP using the installer, but never if I escaped to shell and ran FTP manually. Also, the install process would fail at MAKEDEV, which I presume only uses the network if making network devices. Boot into the installed system, and I could ping the local IP. Sometimes I would get no route to host pinging another node on the subnet, and sometimes it would crash. `ifconfig =a` would always crash. I searched, and there are open qfe bugs for sparc64 (3928/sparc64, 3960/sparc64), but this is sun4m/SS20 sparc. There's (4218/kernel), but that just says not working. None of these reflect the severity (immediate drop into the debugger) I experienced. I also found this: http://archive.openbsd.nu/?ml=openbsd-sparca=2005-02t=659794 I've been trying for the last few days to build a router w/ a Sparc20 to get into our lab from our desks. The hardware on hand happens to be a Sparc20 w/ 1 le interface and a Quad card that are hme interfaces. From inside the box, I can ping the interface, but can't seem to ping anything outside of that. There are also a few entries in the dmesg that seem to indicate something more than my inability to pull my head out (thought I'm pretty sure that's the problem). ... If you comment out ukphy from your kernel and recompile it should start working. I have no problem with doing this, but I'd like a second opinion if possible. Is this the correct fix? Is this known, under the other bug reports? Thanks, JMF
Re: login group for users should be?
On Friday 05 August 2005 04:06 pm, Shawn K. Quinn wrote: On Fri, 2005-08-05 at 13:21 +0200, Tim wrote: When creating a user I am wondering what is recommended when assigning a login group to the user. There are to alternatives, giving the user unique login group (same as his name) or giving the user a general login group such as users. What do you recommend? I, personally, always use a unique login group, and add the group users as a secondary group. But, like a lot of other things, it really depends on what you need, and what your users need. That's what I typically do as well, primary group same as username. Then if the account is for a human it gets 'users' added as a secondary group. It matters in a few places, like sshd_config where I put something like this: AllowGroups users
any luck with CBL for spamd pf Table ?
Tried to use CBL for spamd.conf, it was a bust. may have been sysadmin err0r/misunderstanding..:). Anyone else successfully using CBL for /usr/libexec/spamd-setup ? It appears that the CBL black list has about 1,744,279 entries The CBL list is a big part of the Spamhaus XBL list, and gets a lot that others may miss. And using dns instead of pf to reject is not preferred... But how many addresses can be put into pf Table without overload? (depends on arch and resources... but in short.. rule of thumb.. how many lines should be stay under when putting Tables for spamd?) with over million IPs in CBL, trying /usr/libexec/spamd-setup -d just sets there cooking and doesn't finish retrieval notes: == /usr/local/bin/rsync rsync://rsync.cbl.abuseat.org/cbl/list.txt \ /tmp/cbl-list.txt.rsync sed -e '/^[0-9]/!d' /tmp/cbl-list.txt.rsync /tmp/cbl-list.txt wc -l /tmp/cbl-list.txt === mv list to appropriate folder, edit /etc/spamd.conf, run spamd-setup and it just does not do well... so many lines... or some of the lines have something that hangs spamd-setup???
