Re: cups prints only on reboots -- solved (firewall present)
Firewall prevented new reserved addresses (10.55.1.* and 192.168.*.*), although it still allowed former standard IP addresses on printers. Rather than roll with my own iptables firewall script; on this new computer, I had used the firewall firestarter. I had forgotten that I even installed a firewall, which I had installed to maximize security and minimize my footprint on our network (ducking and covering). So that our administrators wouldn't pry my Linux computer from my cold dead fingers, I had added a firewall. I was hoping to pre-empt any complaints about my use of Linux. My firewall was more against our organization, since our organization has its own firewall against the internet universe, so I had de facto two firewalls in series. Network IP changes that tripped me up came with numerous other computing changes as our administrators moved away from Novell to Microsoft, firming even more a Microsoft-centric base. The needed correction was done to firestarter's firewall configuration GUI by unclicking Block traffic from reserved addresses on public interfaces so I could use our printers that had IP addresses 10.55.1.* I might have more quickly seen this problem, since as my computer booted up, accumulated/unprinted print jobs would suddenly print. This happened because my booting computer must have started cupsys print services before the firewall fully ran. On Tue, May 08, 2007 at 03:35:16PM -0700, Andrew Sackville-West wrote: On Tue, May 08, 2007 at 04:27:47PM -0400, Jameson C. Burt wrote: When I print a file (test file has only 4 characters), CUPS does not print. However, whenever I reboot, CUPS will print all jobs, clearing the CUPS job queue. I can repeat this by creating new print jobs. [...] Printing worked fine before our Microsoft administrators decided to - ^ well, *there's* yer problem sheesh... change all printers from standard internet IP's (199.129.207.*) to reserved addresses (10.55.1.*). I changed my computers IP address and the printers' IP addresses. Indeed, I eventually removed all printing packages and reinstalled them. It's possible our administrators also added filters, but I get the following nmap results PORT STATE SERVICE 21/tcp open ftp 23/tcp open telnet 80/tcp open http 280/tcp open http-mgmt 443/tcp open https 515/tcp open printer 631/tcp open ipp 9100/tcp open jetdirect So the ports appear to be open, and besides, Debian is printing when it reboots. I run Debian version 4.0 with the following two packages installed cupsys 1.2.7-4 cupsys-driver-gutenprint 5.0.0-3 and no *foomatic* packages. Any ideas, so I needn't reboot to print? well. first. have you tried restarting cups as an alternative to rebooting? /etc/init.d/cupsys restart this would tell us whether to look at cups or at some other part of the system.
cups prints only on reboots
When I print a file (test file has only 4 characters), CUPS does not print. However, whenever I reboot, CUPS will print all jobs, clearing the CUPS job queue. I can repeat this by creating new print jobs. Before the reboot solution, about every 5 minutes, CUPS gives errors like the following in /var/log/cups/error_log, [Job 13] Unable to connect to printer; will retry in 30 seconds...: Connection timed out [Job 18] Unable to connect to IPP host: Connection timed out I configured the first printer (Job 13 above), an HP 4050, with lpd/lpr as lpd://10.55.1.63/ and I configured the second printer (Job 18 above), an HP 4200, with ipp as ipp://10.55.1.69/ although many other settings also worked similarly. I selected approprate print drivers thru the web interface http://localhost:631. For example, for the HP 4050, I selected the driver (PPD) which said HP Laserjet 4050 - CUPS+Gutenprint v5.0.0 (en) Printing worked fine before our Microsoft administrators decided to change all printers from standard internet IP's (199.129.207.*) to reserved addresses (10.55.1.*). I changed my computers IP address and the printers' IP addresses. Indeed, I eventually removed all printing packages and reinstalled them. It's possible our administrators also added filters, but I get the following nmap results PORT STATE SERVICE 21/tcp open ftp 23/tcp open telnet 80/tcp open http 280/tcp open http-mgmt 443/tcp open https 515/tcp open printer 631/tcp open ipp 9100/tcp open jetdirect So the ports appear to be open, and besides, Debian is printing when it reboots. I run Debian version 4.0 with the following two packages installed cupsys 1.2.7-4 cupsys-driver-gutenprint 5.0.0-3 and no *foomatic* packages. Any ideas, so I needn't reboot to print? -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) LTSP.org: magic mysterious and awe-inspiring even though we know they are real and not supernatural -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: No xterm (or equivalents) immediately accessible in default etch
On Sun, Oct 22, 2006 at 01:26:40AM -0400, Carl Fink wrote: On Sun, Oct 22, 2006 at 01:12:48AM -0400, Jameson C. Burt wrote: We in Linux heavily use the command-line. So, I was dismayed when my new Debian etch version displayed a Gnome interface WITHOUT ANY XTERM (or GNOME-TERMINAL or KONSOLE) and not even any immediate panel options for these terminals. Why did you install GNOME? I ignored tasksel and installed icewm/xdm instead, and xterm was right there. THE XTERM (or its equivalent) SHOULD BE IN MY FACE THE VERY FIRST TIME I LOGIN, requiring at most a single obvious mouse click. Why are you screaming? The correct thing to do, I believe, is to file a wishlist bug against debian-installer. I install a new Debian Linux a few times a year, as I have since about 1995, when I was at Purdue University where Ian hung out. Before exim, I remember spending 120 hours over a few weeks correcting and understanding the details of smail. Since then, I have gotten lazy, and am no longer willing to spend even 2 hours on a narrow configuration detail like gnome-terminal (or xterm). I tailor my Debian installations enough (20 hours so far on my latest Debian installation). I have finally tired spending time wholesale reconfiguring to my own whims, and I accept many defaults I formerly would not have accepted. Recently, after my year-old Debian Linux crashed on two disk drives in two weeks, I faced forensic work on my disk drives; I relented to not reconfiguring with icewm, kde, or fvwm as I have many times, each time feeling I missed the more thorough considerations that Debian volunteers put into Debian's default installation (eg, the handling of USB, CD, and DVD mounts possibly outside /etc/fstab). When tailoring a configuration, one never knows how much time will get used in unforseen problems. In analogy, I recall a car I purchased 30 years ago from an Australian professor who, each time he started that car, he first opened the hood, then moved a clothes pin on the voltage regulator. I bought a new voltage regulator as I bought that car, and I accept Debian's default Gnome installation as I install Debian Linux. For the first week of my current Debian installation, I attended other issues with my Debian installation (eg, no password authentication, only public key authentication in ssh, thereby forbidding ssh access except to several computers between which I must move keys with each new Debian installation). A couple times in that first week of my latest Debian installation, I briefly tried getting a gnome-terminal readily available either thru Gnome's panel or thru an acceptably quick menu. Instead, for that first week, to get gnome-terminal running, I kept going thru deeper menus as if I were using Microsoft. In fvwm, I would have just added all my startups like xterm (with about 10 options) into ~/.xsession . In my current Debian installation, I DIDN'T MIND SO MUCH THAT I DIDN'T IMMEDIATELY SEE A GNOME-TERMINAL OR A TERMINAL ICON, BUT WHEN THE PANEL OPTIONS OFFERED NO GNOME-TERMINAL AND GNOME MENUS OFFERED NO TERMINAL AT MENU'S FIRST LEVEL, I FELT SOMETHING WAS AMISS [I'm not shouting, just emphasing the meat of this message]. But you folks have affirmed that this was by design, so I'll quit being shrill. I'll also accept your solution to start gnome-terminal from a command-line using alt-F2 Luckily, when done once, Gnome usually saves even that effort, since Gnome remembers the previous gnome-terminal application between boots. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com LTSP.org: magic mysterious and awe-inspiring even though we know they are real and not supernatural -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Compiling a kernel
(which has more thought even than these email-lists); eg, Compiling a New Kernel at http://www.debian.org/releases/stable/i386/ch08s05.html.en which corresponds to www.debian.org -- installation manual -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) LTSP.org: magic mysterious and awe-inspiring even though we know they are real and not supernatural -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
No xterm (or equivalents) immediately accessible in default etch
We in Linux heavily use the command-line. So, I was dismayed when my new Debian etch version displayed a Gnome interface WITHOUT ANY XTERM (or GNOME-TERMINAL or KONSOLE) and not even any immediate panel options for these terminals. Gnome's Add to Panel includes a trashcan and a file-manager just like Microsoft, but not one of Unix's foundations -- a text terminal. I eventually kludged a gnome-terminal icon onto the Gnome panel. Or I can Applications - Accessories -- Terminal but this should not be the primary approach to command-line entries. Yes, once I have a gnome-terminal running, future logins re-deploy it, and that's actually an improvement to making inclusions in ~/.xsession (although Gnome drops some applications from later logins as Sun did 10 years ago). THE XTERM (or its equivalent) SHOULD BE IN MY FACE THE VERY FIRST TIME I LOGIN, requiring at most a single obvious mouse click. --- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) LTSP.org: magic mysterious and awe-inspiring even though we know they are real and not supernatural -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
mount /dev/sde1 is old vfat whole disk unless -t ext2
I took a 4 year old 80GB disk drive, formerly running Microsoft Windows, then repartitioned it with fdisk. But I get the following odd behavior mount /dev/sde1 /mnt #Mounts as 80GB vfat mount -t ext2 /dev/sde1 /mnt #Mounts as 1GB ext2 Of course, -t ext2 will guarantee no other partition type gets used, but a mount without options I would not expect to do either of a. Mount the whole disk drive, all 80GB rather than 1GB. b. Mount a different filesystem (vfat) type than I set with fdisk (83). I suppose that any of the commands shred, wide, sterilize, or dd if=/dev/zero of=/dev/sde bs=1000 count=8000 would prepare a disk drive so that later no ext2 partition would mount as a Microsoft vfat partition. However, one is behooved to use fewer such dangerous commands. Since 1994, I have used the following standard sequence to prepare a Linux disk drive, whether that drive was old or new, fdisk (or cfdisk) to create partitions mkfs (or mke2fs) to put filesystems on those partitions /etc/fstab changes if I want system mounts e2label if I want to mount with a label DID I MISS SOMETHING? Like this oddity today, on another disk drive 6 years ago, I was similarly perplexed by a first partition that misbehaved. Configuration: This internal Seagate ST380020A 80GB disk drive I attached to a CableMax USB2.0 to IDE SATA Cable so this bare (screwed on metal plate to protect electronics) ATA drive is externally connected by USB cable and a power connection. I run Debian 3.0 (not yet upgraded to 3.1). I don't expect this configuration causes these oddities, since I use this configuration often, although I don't often convert Microsoft disk drives to Linux ext2. The rest of this email supports the above statement. Here is the output for my 80GB disk drive using fdisk -l /dev/sde # Disk /dev/sde: 255 heads, 63 sectors, 9729 cylinders Units = cylinders of 16065 * 512 bytes # Device Boot Start EndBlocks Id System /dev/sde11 141 1132551 83 Linux #1.1GB /dev/sde2 142 422 2257132+ 83 Linux #2.2GB When I run mount /dev/sde1 /mnt I get the following response from mount, /dev/sde1 on /mnt type vfat (rw) which is not ext2! Indeed, I can see former Microsoft Windows files with ls -F /mnt, My Documents/ Program Files/ autoexec.bat* command.com* config.sys* I get the following from df, /dev/sde1 78131104 78131104 0 100% /mnt so the full 80GB disk drive has been mounted, not just /dev/sde1. When I run mount -t ext2 /dev/sde1 /mnt I get the following response from mount, /dev/sde1 on /mnt type ext2 (rw) as expected from my settings with fdisk. The files now include Linux (No Microsoft files) files/directories from /boot, as seen by the following ls -F /mnt, grub/ lost+found/ boot.b bzImage-2.4.27-sound System.map-2.4.27-sound boot-bmp.b boot-compat.b boot-menu.b boot-text.b chain.b os2_d.b map I get the following from df, /dev/sde1 1114724 14532 1043568 2% /mnt as expected for my 1.1GB partition. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) LTSP.org: magic mysterious and awe-inspiring even though we know they are real and not supernatural -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Memory limit testing: whether user really can use 2100MB memory
As a user, without administrative privileges,
I want to determine if I really can consume
a certain amount of memory.
Even though ulimit -a returned
max memory size unlimited,
I have an application that seemed limited to 2.1GB,
so I wanted to EMPIRICALLY TEST the memory limit.
I welcome other approaches for checking memory limits.
The following script does check this 2100MB,
with the command line argument $1 as 2200.
/usr/bin/bc +++
scale=102
for (x=1; x=$1; x++) {z[x]=1/3}
+++
if [ $? -eq 0 ] ; then
echo SUCCESSFUL: Consumed \$1\ megabytes memory (possibly as swap space).
else
echo FAILED: Could not consume \$1\ megabytes memory.
fi
You can watch as the memory use increases with something like
while : ; do /bin/ps -A -o %cpu,%mem,vsize,rss,cmd |
egrep 'RSS|bc'; sleep 1; done
With the bc calculator set with a scale of 1,020,000,
each variable set to 1/3 uses 1MB.
So to consume 2200MB, we need to create 2200 variables.
This worked for bc -v GNU version of 1.06 on Linux,
but would not work with the limited IBM AIX installed bc
which won't even allow scale=100 (so we installed the GNU version).
--
Jameson C. Burt, NJ9L Fairfax, Virginia, USA
[EMAIL PROTECTED] http://www.coost.com
(202) 690-0380 (work)
LTSP.org: magic mysterious and awe-inspiring even though
we know they are real and not supernatural
signature.asc
Description: Digital signature
Re: Network/DSL uptime log? solution is icpld
Internet Connection Performance Log Daemon icpld is a nice solution. I found no Debian package that logs when internet connections cease working, although this may be included as a minor aspect of some Debian package having broader purposes. I found this package at http://freshmeat.net/projects/icpld/ Now I can tell when and for how long my ADSL service fails, so I can better infer internet drop causes (me or Verizon). Here is an icpld response for one of 8 drops in my ADSL connection last night, elicited with icpld -log -m or from /var/log/icpld.log, IPv4: Connection down: Wed Jun 9 22:30:03 2004 IPv4: connection up: Wed Jun 9 22:41:09 2004 Down for: 00:11:06 IPv4 Total: 00:26:30 IPv4 connection dropped 6 times. This particular drop was down for 11 minutes, while my connection has been down 6 times for a total of 26 minutes since this daemon started yesterday. This icpld requires me to choose 2 IP addresses on the network I want to check -- I chose 2 IP addresses of my IP service provider, Verizon. The default was to attempt an ICMP connection every 8 seconds, which I changed to 127 seconds in the configuration file /usr/local/etc/icpld.conf I added my own /etc/init.d/icpld to run icpld as a daemon with each boot, essentially DAEMON=/usr/local/bin/icpld if [ -z $(/bin/pidof icpld) ]; then #if icpld not running. # icpld -quit would not remove file missing a running icpld process; # so if process is not running (as when system crashes), # then I remove any icpld.pid. /bin/rm -f ~/.icpld/icpld.pid #created by icpld on each startup. echo -n Starting Internet Connection Performance Logging Daemon: icpld /sbin/start-stop-daemon --start --quiet --exec $DAEMON /dev/null fi In the configuration file, I set nobeep=false cmd4dn=play /usr/share/games/frozen-bubble/snd/stick.wav cmd4up=play /usr/share/games/frozen-bubble/snd/rebound.wav so I hear a decreasing tone or an increasing tone when my ADSL connection goes down or up, respectively. This helps the mind-meld between my computer and myself. On Thu, Jun 03, 2004 at 04:26:32PM -0400, Jameson C. Burt wrote: I look for a command/daemon that will keep a history of my DSL-connection downtime. My Verizon ADSL connection has been down about 60% of the time for 3 weeks, so I want to log the actual downtimes. For example, in a file like /var/log/eth1-downtime I would like to see lines like June 2 10:14am to 7:33pm June 2 8:45pm to 10:04pm June 3 2:31am to 7:14am -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) signature.asc Description: Digital signature
Re: 3ware escalade 8006 SATA RAID recommendations; dual boot windows
I merely add more questions and an observation, and embelish on these further below. a. Doesn't command queing (NCQ) bring SATA much closer to SCSI performance? b. Aren't 3Ware adapter cards and most SATA disk drives Frankenstein drives with bolted-on translater cards that necessarily disallow any command queing? c. Does moving physical disk drives from one SATA RAID controller to another manufacturer's SATA RAID controller fail? d. Does Linux software RAID work almost as well as hardware RAID; perhaps with fewer difficulties, as when moving a set of drives to a different manufacturer's RAID adapter card? The article http://www.tomshardware.com/storage/20040123/index.html says An NCQ-compatible device, i.e. one that conforms to serial ATA II specifications, can accept up to 32 commands and process them in an optimized sequence. The forerunner in this respect is Seagate and its Barracuda 7200.7, which already supports NCQ. Both the following SATA drives handle command queing, Western Digital Raptor 74GB (not the 36GB version), Seagate Barracuda 7200.7, 120GB but none of the large inexpensive drives from Western Digital or Maxtor handles NCQ. Indeed, they are FRANKENSTEIN drives -- ATA drives with a board bolted on to convert SATA commands to the ATA disk drive's commands, disallowing non-ATA commands like NCQ. I believe 3Ware also uses a FRANKENSTEIN approach for its adapter cards, so they can't use NCQ command queing. So usually, both the disk drive and the adapter card are Frankenstein hardware. I gather the Sil3114 chips and the newer Sil3124 handle NCQ command queing. You can see some more information at http://www.tomshardware.com/storage/20040426/backplane_storage-08.html http://www.tomshardware.com/business/20040320/cebit2004_1-10.html where the Promise SATAII 150 SX8 is an 8-channel PCI X slot with tagged and NCQ. I suspect that if you change SATA control card manufacturers; eg, from 3Ware to Asus, then your RAID drives cannot immediately be moved to the new SATA card. This is really a question. When I switched from a BusLogic to an Adaptec SCSI adapter card, I could no longer use a disk drive formerly attached to my BusLogic card (although I could have missed a trick). So, I have wondered about using Linux's software RAID rather than hardware RAID. That is, use a SATA controller card that treats drives as JBOD (just a bunch of drives) without using hardware RAID. I have seen disparate performance reviews, but some of those reviews showed software RAID performing as good as hardware RAID, although the CPU must get involved a little more. This is really another question. On Thu, Jun 10, 2004 at 12:51:12AM -0500, Nick Lidakis wrote: I have been meaning to upgrade my hard disk setup to a RAID array 0 to help increase system responsiveness and reduce system applications start up times. After some research using google, it seems that the 3ware escalade line of RAID SATA cards, specifically the 8006-2LP 2 port RAID card, fit the bill nicely. The cards are supported with an open source Linux driver, is the only true hardware RAID card supported in LINUX (as per the kernel documentation), and is reasonably inexpensive ($139 @ newegg). I have a few questions that I coudn't find an answer to using either google or searching through the Debian archives: Is anybody using this card on a desktop system, and are they happy with the performance in a RAID 0 array? Would I still be able to use LILO or GRUB to dual boot windows off of a IDE drive connected to the motherbaords IDE interface? Is there a big performance increase using a SCSI RAID 0 array as opposed to SATA RAID? If yes, which would be a recommended (hardware RAID) SCSI card to use with Debian? -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) signature.asc Description: Digital signature
Network/DSL uptime log?
I look for a command/daemon that will keep a history of my DSL-connection downtime. My Verizon ADSL connection has been down about 60% of the time for 3 weeks, so I want to log the actual downtimes. For example, in a file like /var/log/eth1-downtime I would like to see lines like June 2 10:14am to 7:33pm June 2 8:45pm to 10:04pm June 3 2:31am to 7:14am -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) signature.asc Description: Digital signature
Re: xterm double-click to select words like cups-bsd, /var/log
On Sat, Mar 20, 2004 at 02:53:30PM -0500, Gregory Seidman wrote:
Some of us prefer this behavior, but it is configurable. You need to get
the following X resource to be noticed by xterm:
XTerm*charClass: 0-32:1,33-126:2,127-160:3,161-255:2
There are many ways of going about it, but the simplest is to put it in
you ~/.Xdefaults (or maybe it's ~/.Xresources; I forget which is
standard these days) and run xrdb -load ~/.Xdefaults somewhere in your
.xinitrc (or whatever else you use for starting X). Another option is to
put it on xterm's commandline:
xterm -xrm XTerm*charClass: 0-32:1,33-126:2,127-160:3,161-255:2
If you want to understand what's going on, read the CHARACTER CLASSES
section of the xterm man page.
--Greg
I thank Rebecca Dridan and Gregory Seidman for both telling
how to extend the character set highlighted when double-clicking
the mouse.
Summarizing, to extend the character set,
I could use any of the following after xterm,
-xrm XTerm*charClass: 33:48, ...
-xrm *charClass: 33:48, ...
-cc 33:48, ...
I use
-cc 33:48,37:48,45-47:48,64:48,92:48,126:48
Here, -cc signals that double-clicking the mouse
adds to the regular character class
(see man -S 7 ascii or enter ascii
if you installed the package ascii)
those characters with decimal values
! (33)
% (37)
- (45)
. (46)
/ (47)
@ (64)
\ (92)
~ (126)
The above -cc adds each character to the character class 48
[an arbitrary default category for mouse double-clicking in xterm],
which includes other characters like a-z, A-Z, and 0-9.
See man xterm 78 percent down under CHARACTER CLASSES
for xterm's default character class numbers like 48;
although my man xterm brings up man uxterm;
so you can man -a xterm, q, then return,
to see what should be man xterm.
I also use the xterm option
-cn
so newlines are not included in a mouse double-click.
I extended my xterm based function (like an alias) xtm
in ~/.bashrc to include -cc,
function xtm() {
xterm -sb -sl 3000 -j -si -sk -cn -fg yellow -bg black -cr red \
-ms cyan -geom 100x40 -fn 7x14 \
-cc 33:48,37:48,45-47:48,64:48,92:48,126:48 \
-xrm xterm.vt100.pointerColor:blue \
-xrm xterm.vt100.pointerColorBackground:yellow \
-xrm xterm.vt100.pointerShape:gumby
}
Notice that I like a mouse pointer of gumby,
so gumby's right finger points directly to a character when I
double-click, unlike most other mouse pointers.
Also notice that this xterm has gold characters on a black background,
like many of the standard monitors 30 years ago.
An retired fortran expert from an age without new fangled colors
mentioned that now one can never decide what infinite color scheme is best.
Thank you Debian users for making my Linux mouse more useful.
--Jim
signature.asc
Description: Digital signature
xterm double-click to select words like cups-bsd, /var/log
I frequently double-click with the left mouse button from a previous xterm displayed result like ii cupsys ii cupsys-bsd Here, double-clicking cupsys highlights the whole word, but double-clicking cupsys-bsd highlights only cupsys, since double-clicking sees a word boundary at characters like - / space As a result, I must left-click and drag my mouse over the word cupsys-bsd which is several times slower (perhaps 2 seconds). HOW CAN I GET DOUBLE-CLICKED WORDS TO HIGHLIGHT EVERYTHING BETWEEN SPACES; eg, all of cupsys-bsd or all of /var/log/messages? After either double-clicking or a more awkward highlighting, I click the middle mouse button to drop (ie, copy) my words cupsys and cupsys-bsd, forming a command-line like dpkg -L cupsys cupsys-bsd |xargs zgrep -i lpadmin This is a quick way to form command-lines that would be quicker if double-clicked words were delimited not by any - or /, but by spaces only. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) LTSP.org: magic mysterious and awe-inspiring even though we know they are real and not supernatural signature.asc Description: Digital signature
flash memory drives cannot initially mount rw -- SOLVED ODDLY
I mount using mount LABEL=LEXAR-256MB-2 /mnt for my labeled (e2label /dev/sdb1 LEXAR-256MB-2) ext3 thumbsized Lexar JumpDrive Trio which has inside the SanDisk Ultra II SD (Secure Digital) 256MB flash memory switched to unlock, attached to USB. While this mounts /dev/sdb1 as ext3 READ-ONLY, I get the response mount: block device /dev/sdb1 is write-protected, mounting read-only I get the same message if I initially try to force read-write, mount -o rw LABEL=LEXAR-256MB-2 /mnt After a couple hours trying to rectify this, I found (the only Google response) this answer by Rick Moen at http://www.linuxjournal.com/article.php?sid=6867 **To correct this, I must enter mount -o rw,remount /mnt So, to mount my flash drive read-write, I must always mount in two steps, mount LABEL=LEXAR-256MB-2 /mnt mount -o rw,remount /mnt Curiously, when I first got this flash drive, I could mount it as read-write with the single line mount LABEL=LEXAR-256MB-2 /mnt as above. However, after writing several files to this flash drive and unmounting this flash drive, I could no longer mount it as above. This severely confused my efforts. So, perhaps the flash drive secures itself after it has some files. Rick Moen had surmised that his flash drive also needed -o rw,remount because the flash drive knew it could only write about 10,000 times before it wore out (don't forget to use the mount option noatime so Linux does not keep writing to flash memory with the latest access time). Another oddity: I did the above on a sid distribution. When I move this flash memory drive to a woody distribution, mount LABEL=LEXAR-256MB-2 /mnt would mount the flash drive as a fat filesystem, so ls -a returned no files. I must specify the filesystem type to woody using mount -t ext3 LABEL=LEXAR-256MB-2 /mnt I suppose this just represents that my woody uses the older version 2.11n-7 rather than the sid version 2.12-6 of mount. Since flash drives are praised as the replacement for diskettes (eg, by Dell), in the Linux world, millions of desktop users are bound to be perplexed and to never get their flash drives working. Considering that these mount oddities hinder flash memory drives from wearing out, I don't mind mind them NOW THAT I KNOW UNNATURAL LINUX TRICKS. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) LTSP.org: magic mysterious and awe-inspiring even though we know they are real and not supernatural signature.asc Description: Digital signature
mount immutable, unchangeably except by reboot?
I would like to mount some filesystems or directories immutable, so that their files can't be altered or added to, except by rebooting. I currently use chattr +i filenames to make individual files immutable. Then I alter the kernel with lcap CAP_LINUX_IMMUTABLE so this immutability can't be changed without a reboot. As a result, those files cannot be altered without reboot, which is awkward for upgrades, but acceptably awkward to greatly limit attacks. Unfortunately, the use of chattr requires me to change tens of thousands of files, which takes time. It also alters the files atime, so an aide check for file changes doesn't straight forwardly work (although I could remount with -o noatime). A better approach would make all of a directory's or mount's files read-only unless the computer is rebooted. Unfortunately, mount -o ro can be changed with mount -o rw without reboot. A few hard drives are manufactured that can be physically changed to read-only, but this becomes awkward, especially for later file changes, but is also difficult to even purchase such a drive. Another possible approach chattr +i some-directory prevents removing or adding files from that directory, but does not prevent changing the files in that directory! And I know of no trick like chmod +t some-directory to prevent all users (including root) from changing that file except by reboot. Does anyone know how I might mount a filesystem or directory immutably, except by reboot. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) LTSP.org: magic mysterious and awe-inspiring even though we know they are real and not supernatural -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dselect/apt-get failed -- 6 year Debian installation corrupted
I have upgraded this computer's installation since 1997, about 6 years, transferring the installed disk drives across 3 successively newer computers. Two years ago, after upgrading several computers from potato to woody, I found upgrading from potato to woody produced enough problems that I never upgraded this one computer from potato to woody. Finally attempting to upgrade this computer from potato to woody, I previously mentioned that dslelect wanted to remove most packages, including essential packages. Referring to Release Notes for woody and others' archived mail, I considered the recommended apt-get install dpkg apt debconf but this also failed, complaining about the need for several old packages, yet apt-get should install all the packages it needs. I considered a full apt-get dist-upgrade which I should have done and did do on other computers 2 years ago, upgrading from potato to woody. As I recall, on those upgrades I did 2 years ago from potato to woody, problems arose as several installation scripts failed, but I was able to make repairs. I also considered forcing apt-get install dpkg apt debconf, but that would have made the following number of package changes 55 packages upgraded, 31 newly installed, 179 to remove and 998 not upgraded which is fewer than a full apt-get dist-upgrade, 1126 packages upgraded, 213 newly installed, 57 to remove and 40 not upgraded. Inexplicably, the above minimal apt-get wanted to remove 179 packages, while the full upgrade would only remove 57 packages. Having to force an installation tool like apt-get, I imagined the installation would present numerous problems as new forced packages would prevent later packages from installing properly (eg, if perl is forced, all later packages might fail to install). So I chose to force a minimal number of packages through dpkg, hopefully limiting the number of problems, dpkg -i --force-depends \ libc6_2.2.5-11.5_i386.deb \ libstdc++2.10-glibc2.2_1%3a2.95.4-11woody1_i386.deb \ perl-base_5.6.1-8.3_i386.deb \ perl-5.005-base_6.3_all.deb \ libncurses5_5.2.20020112a-7_i386.deb \ dpkg_1.9.21_i386.deb \ sysvinit_2.84-2woody1_i386.deb \ file-rc_0.6.3_all.deb \ apt_0.5.4_i386.deb \ debconf_1.0.32_all.deb \ perl-modules_5.6.1-8.3_all.deb \ binutils_2.12.90.0.1-4_i386.deb \ libperl5.6_5.6.1-8.3_i386.deb This failed as other packages depending on earlier versions of these packages (eg, perl-5.005) prevented even this forced installation. Further forcing with dpkg only revealed more problems. In the end, I suspect none of dselect, apt-get, and dpkg would let me upgrade this Debian installation. If I was to do this over, again facing a failing dselect, I would try working through the problems created by a forced apt-get dist-upgrade. I can always get a new Debian installation working in reasonable time. Since my first Debian installation in 1996 [though I first installed Linux on Slackware in 1994 and RedHat in 1995], about a third of my Debian upgrades have taken excessive time and presented several problems. AFTER 5 YEARS OF DEBIAN UPGRADES ON ANY COMPUTER, I NOW FEEL I BOTH SAVE TIME AND FRUSTRATION BY OVERLAYING THE OPERATING SYSTEM WITH A NEW DEBIAN OPERATING SYSTEM, SKIPPING ANY DEBIAN UPGRADES AFTER 5 YEARS. Luckily, in Linux, a users' most important information is easily retained from /home and /usr/local. While I have a tape backup, I forsee this computer's upgrade from potato to woody consuming time without success. I send this email, expect no possibility of reboot, and will overwrite this computer with a new sarge Debian installation. On Tue, Nov 25, 2003 at 08:46:16PM -0500, Jameson C. Burt wrote: I am upgrading from potato to woody (in anticipation of sarge), having just upgraded my potato packages with the Debian potato archives, and with the potato security archives. I run dselect with the apt access method, I update the list of packages, and now I am in dselect's 2. [S]elect I make no changes/selections, merely pressing enter. Dselect recommends removing or purging 1258 packages of 1459 installed packages, including numerous required packages like base-files base-passwd bash bsdutils debianutils dpkg fileutils libc6 Entering dselect's 2. [S]elect Request which packages you want on your system and immediately pressing enter, or later after entering U (set all to sUggested state), I see the following first three lines for conflict resolution, lines which BAFFLE ME, **- Req base base-files Debian base system miscellaneous files **- Req base base-passwd Debian Base System Password/Group Files **- Req base bash The GNU Bourne Again SHell or, in verbose mode I see [excluding Description], Installed Old mark Marked for Priority Section Package - -- --- installed install remove
Re: dvd burning using sid
Consider growisofs in the package dvd+rw-tools I haven't used growisofs, but it looks most promising. Read their lengthy /usr/share/doc/dvd+rw-tools/dvd-rw.html which is better viewed at http://fy.chalmers.se/~appro/linux/DVD+RW Remember that you will need to treat your IDE DVD as scsi device /dev/scd0 through kernel settings like ide-scsi. I also wonder what DVD+RW truly random access media can do; eg, making a UFS or ext2 on the DVD, then somehow write to it. And one looks forward to DVD+MRW (Mt.Rainier/Easywrite, MRW, support), which no manufacturer yet has. Still, since DVDs can be written to but 1000 times, one may still prefer an approach like growisofs. On Wed, Nov 26, 2003 at 09:33:42PM -0500, Kevin Coyner wrote: What's the recommended package(s) for burning DVD's in a Sid setup? I've done the apt-cache search stuff, and come up with cdrecord. But cdrecord from the debian mirrors does not support DVD writing out of the box. /usr/share/doc/cdrecord/README.DVD.Debian says to either: 1. get cdrecord-ProDVD by J. Schilling or 2. apply the dvdrecord-patch by: apt-get source cdrtools cd cdrtools-version fakeroot debian/rules dvd=yes cdrecord So I've opted for the second choice. It all went fine, but during the compiling process it errors out with multiple instances of: /usr/include/asm/sigcontext.h:79: error: parse error before '*' token /usr/include/asm/sigcontext.h:82: error: parse error before '}' token I've looked at this header file but don't have a clue as to what, if anything, should be changed. Any pointers, or suggestions for a DVD burning package, would be appreciated. Thanks Kevin -- Kevin Coyner mailto: [EMAIL PROTECTED] GnuPG key: 1024D/8CE11941 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) LTSP.org: magic mysterious and awe-inspiring even though we know they are real and not supernatural signature.asc Description: Digital signature
ssh error Authentication response too long: 1433299822
SOLVED: I show below both the ssh problem that arose and its solution. I upgraded ssh to version 3.4p1-0.0potato1 from within Debian's potato distribution to get the final potato versions and security updates (before I upgrade to woody, and then to sarge, neither of which enters into this problem). When I tried slogin to another computer without booting, I got the response, Authentication response too long: 1433299822 Adding debugging, slogin -v, I see, debug1: authentications that can continue: publickey debug1: next auth method to try is publickey Authentication response too long: 1433299822 I then stopped and started the ssh process, /etc/init.d/ssh stop /etc/init.d/ssh start This indeed killed the process sshd. However, slogin still produced the error Authentication response too long: 1433299822 and still couldn't slogin. I noticed that the following user process still ran from my xdm login, /usr/bin/ssh-agent /home/burtji/.xsession corresponding to the ssh-agent 15003 /usr/bin/enlightenment and I noticed that my previous ssh-add had created /tmp/ssh-igu15003/agent.15003= Killing the ssh-agent process started under enlightenment, 150032 15003 /usr/bin/ssh-agent /home/burtji/.xsession, I could again use slogin, although I needed to enter the passphrase. Indeed, all along I could slogin from the virtual terminal F2. In conclusion, upgrading ssh left a vestige ssh-agent that no longer co-operated with sshd. I could only get slogin working properly by restarting my user X-windows session. So, with xdm still running, I had to log out, log back into a new X-windows session (less harsh than a reboot), and run ssh-add. This was a benign problem that would have disappeared on reboot. Google turned up only 1 link for the following search, slogin Authentication response too long: 1433299822 and that link didn't solve my problem. Since this took me 2 hours to solve, I have enter the problem and solution here. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) LTSP.org: magic mysterious and awe-inspiring even though we know they are real and not supernatural signature.asc Description: Digital signature
dselect recommends removing 1258 packages, base-files, libc6
I am upgrading from potato to woody (in anticipation of sarge), having just upgraded my potato packages with the Debian potato archives, and with the potato security archives. I run dselect with the apt access method, I update the list of packages, and now I am in dselect's 2. [S]elect I make no changes/selections, merely pressing enter. Dselect recommends removing or purging 1258 packages of 1459 installed packages, including numerous required packages like base-files base-passwd bash bsdutils debianutils dpkg fileutils libc6 Entering dselect's 2. [S]elect Request which packages you want on your system and immediately pressing enter, or later after entering U (set all to sUggested state), I see the following first three lines for conflict resolution, lines which BAFFLE ME, **- Req base base-files Debian base system miscellaneous files **- Req base base-passwd Debian Base System Password/Group Files **- Req base bash The GNU Bourne Again SHell or, in verbose mode I see [excluding Description], Installed Old mark Marked for Priority Section Package - -- --- installed install remove Required basebase-files installed install remove Required basebase-passwd installed install remove Required basebash Clicking R (Revert to state before this list), I see the expected, *** Req base base-files Debian base system miscellaneous files *** Req base base-passwd Debian Base System Password/Group Files *** Req base bash The GNU Bourne Again SHell Following are the first few lines when I first enter dselect's 2. [S]elect, as expected, q All packages q qqq Updated packages (newer version is available) qqq q Updated Required packages q qqq Updated Required packages in section base qqq *** Req base base-files 2.2.0 3.0.2 *** Req base base-passwd 3.1.10 3.4.1 *** Req base bash 2.03-6 2.05a-11 Following are corresponding lines from dpkg -l, as expected, ii base-files 2.2.0 Debian base system miscellaneous files ii base-passwd 3.1.10 Debian Base System Password/Group Files ii bash 2.03-6 The GNU Bourne Again SHell The Release Notes for Woody, http://www.debian.org/releases/stable/i386/release-notes/ch-upgrading.en.html said The recommended method of upgrading is to use the apt method with dselect Can anyone clarify why dselect recommends obliterating required packages? Two years ago, I upgraded other computers from potato to woody using instead apt-get. Then, with apt-get dist-upgrade, I remember spending a couple days fumbling through upgrade problems, so I presume the Release Notes correctly recommend using dselect. My current potato distribution has the following package versions, libc6 2.1.3-25 bash 2.03-6 perl-5.005 5.005.03-7.2 perl-base 5.004.05-1.1 debconf0.2.80.17 dpkg 1.6.15 libncurses55.0-6.0potato2 libstdc++2.10 2.95.2-13.1 I have used Debian Linux since 1995, so I'm fairly well versed as a user in dselect, dpkg, and apt-get, but I am in Potato Hole with these dselect recommendations. Should no one respond, I will return to using apt-get. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) LTSP.org: magic mysterious and awe-inspiring even though we know they are real and not supernatural signature.asc Description: Digital signature
Re: Initrd diskless boot
The power supply is external, the size of a large eraser, in the middle of a cord like || house-connection--|power-supply|diskless-workstation || where -- represents a foot (30cm) of cord. The power-supply says on it, 5Volts 2Amps output While the power-supply gets slightly warm, the outstretched handsized Jammin 125 workstation from http://workstations.com does not get warm. I only wished it supported more than 1024x768 at 16-bit since I attach a 21 monitor. With Dell occasionally selling their 20 2000FP LCD monitor for $850, I consider wanting 1600x1200 DVI (digital) output, but the Jammin 125 is small so does NOT allow any add/change PCI/AGP cards. They mention 15 watts on their webpage [URL probably wrapped thru email], http://www.disklessworkstations.com/cgi-bin/cat/info/jam125.html?Bpdb2RQX;;99 On Sun, Jan 26, 2003 at 03:30:32AM +0100, Carel Fellinger wrote: On Fri, Jan 24, 2003 at 09:55:06PM -0500, Jameson C. Burt wrote: I re-emphasize the www.ltsp.org approach. ... I bought a diskless workstation 3 weeks ago from a link on ltsp.org, a workstation the size of your outstretched hand yet having audio, USB, parallel, serial, and ethernet ports -- all with a 15 watt power supply and no fans. I never could really find the info whether that 15Watt power supply is part of the bricks or not and whether it needs any fan itself. Could you enlighten me? -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) msg26504/pgp0.pgp Description: PGP signature
DEVFS, howto test creation of devices in /dev?
For Device File System, Debian devfsd package, how might I test that devfsd properly creates files in /dev? As a particular example, I work with the Debian camserv package, so I added to devfsd's configuration file, /etc/devfs/devfsd.conf the line, REGISTER ^v4l/video0$ CFUNCTION GLOBAL symlink v4l/video0 video0 When starting camserv, I get the not so specific error message, (V4L) video_open: No such file or directory Unfortunately, this message does not specify the problematic file, but I get neither the device /dev/v4l/video0 nor /dev/video0. So, with several possible sources for this error (camserv, devfsd, devfsd.conf), I would like to test that devfsd properly creates devices in /dev. For example, I would like some testing-tool that my command line *** some-testing-tool /dev/video0 would induce devfsd to consider devfsd.conf, then create the following device and link, /dev/v4l/video0 /dev/video0 -- v4l/video0 Such a testing-tool would hopefully induce devfsd to create any specified device, whether concerning video, audio, or mass-storage. *** Does anyone know of such a devfsd testing-tool? PS: I would address this question to a devfs email-list, but the author's email-list site, http://oss.sgi.com/projects/devfs/archive no longer exists, and I find no replacement. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) msg26076/pgp0.pgp Description: PGP signature
Re: Initrd diskless boot
I re-emphasize the www.ltsp.org approach. In the mid-1990's, I worked with diskless Suns and also tried making several Debian Linux computers diskless. After several weeks identifying files I wanted to keep, sometimes different for each computer, I abandoned that too-time-consuming approach to diskless computers. The Linux Terminal Server Project (ltsp) approach greatly simplifies running computers diskless. You still must configure your DHCP server (configure one file), run the package tftpd or atftpd on your server, configure NFS with permissions to server your diskless computers (one file on your server), configure xdm/gdm/kdm to serve your diskless computers (2 files on your server), and install the operating system files for your diskless computers (in /opt with LTSP's packages). The last part was greatly simplified by LTSP. With LTSP, your disless Linux GUI terminals let you login to your main computer, and only by changing the runlevel can you even see your tranparently running diskless computer (its processes, its mounts, ...). LTSP's default installation has your diskless computers working like X-servers, but without software on a local disk. While you can extend this with LTSP to run software locally, you increase configuration complexities; eg, you must then run Network Information Service (NIS) for usernames/passwords and you must tailor several files for each computer. Without extra configuration, your local computer can rather easily get sound off your main computer into your diskless workstation (if it has a sound card), by running a daemon without needing full NIS user configuration. And you can attach a webcam to your workstation, though I have worked for 2 days trying to get someone else's webcam tar files working in Debian. I bought a diskless workstation 3 weeks ago from a link on ltsp.org, a workstation the size of your outstretched hand yet having audio, USB, parallel, serial, and ethernet ports -- all with a 15 watt power supply and no fans. Magic. This LTSP approach gives wonder, since so many technical details work so smoothly, and those diskless workstations work seemingly oddly. On Thu, Jan 16, 2003 at 08:42:42PM +0100, Tobias Kraus wrote: Check www.ltsp.org Linux Terminal Server Project. This might help you. Tobias Am Donnerstag, 16. Januar 2003 17:17 schrieb Rodrigo F. Baroni: m needing to set a diskless pc, and I have been studing the initrd procedure. The idea is to have the read-only directories mounted on nfs, and others one read-write in ram-disks. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) msg26083/pgp0.pgp Description: PGP signature
Re: ls120 (Howto make it a Bootable/Rescue Disk)
new, and have looked all over, but can't find a way to make an LS-120 bootable. I have found a way to reformat it and all the partitions on it work. It's like having a 120mb hd. (but slower) What I want to do is get a copy of my current kernel (or a new one after I customize it and set it up) and put it on the ls-120 and use the ls-120 as a backup system disk (ie: rescue disks). Any ideas? I've already tried all the things I could find for making boot floppies, rescue disks.. etc.. I just don't know where to go from here. -- Michelle Alexia Jade Storm -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) msg10252/pgp0.pgp Description: PGP signature
find -mtime: 1,782 /etc files over 250 years old!?
Find produces 1,782 /etc files last modified over 250 years ago, /usr/bin/find /etc -mtime +10 -printf '%Tc %p\n' |wc If you remove |wc, you will see that none of these files was modified before 1998. I notice this same -mtime bug with GNU find on Debian Linux (woody distribution), on Debian Linux (potato distribution), and on AIX, but NOT with IBM's own (non-GNU) find on AIX version 4.3. So, this appears to be the upstream author's problem that has existed for at least 3 years. Seeking more understanding, one can run the bash script at the end of this email. Using that, here is the the number of Files-found in /etc with a name having the string host that were last modified over Days ago [Files-found should never increase with increasing -mtime days]. Days Files-found 1 30 10 30 100 30 1000 6 1 0 10 24 --OVER 250 YEARS OLD 100 0 1000 0 1 0 I include the upstream email address [EMAIL PROTECTED] in the To: address so that they might fix this problem/bug [I was too lazy to look at the source code]. ~~~Script used:~~ printf ' Days Files-found\n' for DAYS in $(cat +++ 1 10 100 1000 1 10 100 1000 1 +++ ) do printf '%10s' $DAYS /usr/bin/find /etc -name '*host*' -mtime +$DAYS |wc -l done -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Apt's sources.list has line-length limit 299
apt-get update hangs with no response when I add a line anywhere in /etc/apt/sources.list that is greater than 299 characters. Specifically, I added the following 308-character commented line to aid my choice of Debian sites [the line-continuation characters were not originally present and this had at most one contiguous space], # fping -c 3 ftp.egr.msu.edu carroll.aset.psu.edu \ mirror.cs.wisc.edu mirror.csit.fsu.edu umn.dl.sourceforge.net \ unc.dl.sourceforge.net telia.dl.sourceforge.net debian.teleglobe.net \ mirrors.xmission.com ftp-linux.cc.gatech.edu debian.uchicago.edu \ debian.fifi.org ftp.silug.org debian.tod.net After removing the last debian.tod.net, this line had but 292 characters, so apt-get update would no longer hang. I run Debian woody 3.0, with all packages upgraded as of 9/26/2002, including apt version 0.5.4 . Oh, I see this remains an outstanding apt bug-report filed May 13, 2002, #146846 -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printer Recommendation Requested
The Lexmark Optra Color 45 inkjet has postscript and you can even get a network card included, but it costs about $1100. This is one of the very few postscript inkjet printers. All inkjet manufacturers make exorbitant profits off their ensuing ink sales, legally designing their cartridges to attempt maintaining a monopoly, though court cases have weakened this somewhat. Hewlett Packard makes more profit from here than anywhere else in the company. So, how do you avoid exorbitant ink costs? Answer: you add-on a third-party's CONTINUOUS INKING SYSTEM (CIS) for about $250 [paid for in 1 year], after seeing the Slashdot article [piece together the following 2 line Slashdot link, which has no spaces], http://slashdot.org/comments.pl?sid=33357threshold=0 commentsort=0tid=98mode=threadpid=3602781#3603183 That response lists some sellers of CIS, but I will one day try the CIS seller ranked high by Google, http://www.tssphoto.com/sp/dg/cis which is the same site as InkJetArt. With such a system, you can choose to use inks almost identical to your manufacturer's for about 1/4 the cost. Or you can choose to use archival inks, or other inks: flexibility in hardware like the flexibility we like in Linux software. That tssphoto.com site above tells with which printers the CIS system works, all Epson printers! Evidently, Epson makes printers that are more easily altered, although their latest line includes electronics on their cartridges, increasing the expense of a CIS system. You can see their ink comparisons at, http://www.tssphoto.com/sp/dg/archival_inks.html One of these months, I will buy either a. Epson Stylus Photo 1280 $450 b. Epson Stylus Photo 1200 $180? over ebay Epson no longer makes this model, but it is one of the last without electronics in the print cartridges. As a result, the third-party CIS system costs less, and the Epson 1200 costs less new and now used. At the above website, http://www.tssphoto.com/sp/dg/cis/ look at the displayed printer. On the right you will see six 4-ounce/125ml bottles of ink. You can see installation instructions with lots of pictures, http://www.tssphoto.com/sp/dg/cis/instructions/CIS-nonchipped.html Looking at these pictures, you can see the high Geek Factor. Did you look at Linux suggested printers at, http://www.linuxprinting.org/suggested.html On Tue, Jun 18, 2002 at 03:03:12PM -0600, Mike Fontenot wrote: I've got a Lexmark Optra Ep that just died, and I need to replace it. I've read the linuxprinting.org web page, and that has helped some, but I don't see many of their recommendations in the mail-order catalogs that I've got. My wife has been bugging me to get a color printer anyway, so I guess I'll need to go with an inkjet. But I've thought the cost/page of the Lexmark is already bad, so I'll probably be horrified with the operating costs of an inkjet. I've been using CUPS with the Optra Ep, and it's been working pretty well. I've liked having the built-in postscript. Is postscript not a factor on the inkjet printers? (I don't think postscript is mentioned in the inkjet section of the linuxprinting.org webpage). I've also searched for past recommendations. The webpage seems to push Epson C80 the most. I've seen some complaints of reliability for other Epson models, but nothing specifically for the C80. Any recent experience with these (or other) printers (and info about where to buy them)? I'm running potato, and using the parallel connector for printing. Mike Fontenot [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lexmark Printing
and default installations, rather than the exptertise of Debian's hundreds of developers. For example, the most installed mail-reader is mailx, but hardly anyone deliberately uses this mail-reader. So, this popularity site largely wastes one's time. When each Debian user spends HUNDREDS of hours trying software, then trying its alternative, then trying another alternative, then reading email-lists about what others say about the alternatives, ..., then we have slowed the usage of Debian. Users need not decide between over 13 email-readers, when they could be told that experts prefer Mutt, although either Evolution or Kmail will likely dominate the dummed-down business world. On Mon, Jun 17, 2002 at 12:36:06PM +0200, Tinus Kotzé wrote: Thanx alot for the post The reason why the HP is BW could be one of 2 1. There is a lot of printers based on the 4076, including the ExecJet IIc which i have 2. It could be that that specific driver only supports BW. My printer does have a cartridge changer for BW and color. Everything worked fine, but when I try to connect to my local host I don't get anything. I checked in /etc/services and the port is open.I also checked in the inetd conf's and the port was also open there. Should lpd still be running? If found the following line in the beginning which I think might cause it to exit since I don't get any messages after running /etc/init.d/lpd (with _start_ or nothing). test -x $DAEMON -a -f /usr/sbin/pac ||exit Any advise? Thanx in advance Tinus On Mon, 2002-06-17 at 02:27, Jameson C. Burt wrote: You might try CUPS (which I believe RedHat now uses as the default print server, replacing the lpr package). You can find CUPS (Common Unix Printing System) in woody. I installed *cupsys cupsys-bsd cupsys-client cupsys-driver-gimpprint cupsys-pstoraster kdelibs3-cups *foomatic-bin *foomatic-db *cupsomatic-ppd The last package includes 918 *.ppd files, including /usr/share/cups/model/IBM/Execjet_4072-bj200.ppd While this isn't your 4076, perhaps its close enough. You configure CUPS via a local webpage, http://localhost:631 Installation of cups removed my print server package lprng, but then I only expect one printserver to dominate printing on one computer. I see your 4076 mentioned in the Unix printer compatability database, http://www.linuxprinting.org/printer_list.cgi There, select Lexmark, then select 4076. This spawns a webpage that says this Lexmark 4076 printer Works with drivers for the HP DeskJet 500 But this also says the Lexmark 4076 is a BW Inkjet 300x300 while you say it is a Colorprinter (hmmm). I also see your printer mentioned on Lexmark's site, http://drivers.lexmark.com/drivers.nsf/SelectPrinter?OpenForm0 and their website you probably visited, http://drivers.lexmark.com/drivers.nsf/SelectPrinter?OpenForm4076 If you download one of their drivers (eg, one for Windows 95, 76WN313E.EXE), then run that *.exe file on the appropriate computer, you likely get a *.ppd file that you can use in CUPS. But this is a too involved a solution, though I have seen Linux documentation mention this very solution: to run a *.exe file then get the needed *.ppd file. Of course, as said above, the cupsomatic-ppd supplied 4072 *.ppd might work well under CUPS. On Sun, Jun 16, 2002 at 12:41:41PM +0200, Tinus Kotzé wrote: Can anyone help me with the Lexmark ExecJet IIc 4076 Colorprinter. I have searched the net and could not find a solution for my problem getting this printer to work. At lexmark's page everything goes well until I have to state a operating system where the choices are only Redhat, SuSe... but not Debian and no source to compile the drivers with for Debian. I have found that it supposedly works in BW ok with the HP DeskJet 500. Thankyou in advance Tinuns -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian: abandon ship?
On Mon, Jun 17, 2002 at 11:44:53AM +0200, Jan Johansson wrote: so contractual, however inresponsive, support from a lame-ass linux distro means more to you than actually securing the system? Nope. Read my last paragraph. A system provider which can not also offer a _legally binding_ support contract is simply not allowed on any production / mission critical servers within our organisation. So it doesnt really matter that i prefer Debian and Slack over RedHat, i still wouldnt be allowed to deploy a deb-system. Analogy to life insurance: I know people fully comforatable dying because they have life insurance. By analogy, some managers are fully happy killing a company with high costs, because they have insured themselves through some expensive contracts. Within a year, 1994-1995, I went through Slackware, RedHat, and Debian, when I realized that most of my understanding, most of my power, most of my solutions were coming from the debian-user email-list. Perusing Debian's archives for solutions produces knowledgeable personel. A co-worker of mine arranged an expensive contract with IBM for AIX solutions. He calls IBM to even add a username. Where I work (a government agency), managers have stated that they want a contract, so that should problems become insurmountable, the managers can lay blame with the contractor. Rather than laying a foundation in personnel, they lay a foundation for external blame. This is the culmination of support contracts: effete personel. We should all have taken moral classes as every Japanese must, with its 5 fundamentals, all intertwined, 3 of which I remember, Do the hard thing Endure hardships Persevere in striving In 1993, I remember our paying Sun an exorbitant price, which included letting me see email solutions. Debian's email solutions are far more extensive than Sun's, so I sometimes successfully searched Debian's archives for solutions to what were really Sun problems. I have seen nothing as good as Debian's email lists. No for-profit company can induce users to contribute even 5 percent of what Debian users/developers contribute to their email lists. These email-lists have encyclopedic information, not thin Boolean information of a contract, yes, I bought a contract. HOW MUCH MUST YOU PAY TO GET ARCHIVED SOLUTIONS AT THE LEVEL OF DEBIAN'S? Request such archives as part of your support. You cannot buy the level of information found in Debian's archives! Why seek lesser support? From tradition? Only about once a year do I ask a question on the Debian email-list, because its vast email-list archives and bug-archives retain solutions to my other sought problems. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lexmark Printing
You might try CUPS (which I believe RedHat now uses as the default print server, replacing the lpr package). You can find CUPS (Common Unix Printing System) in woody. I installed *cupsys cupsys-bsd cupsys-client cupsys-driver-gimpprint cupsys-pstoraster kdelibs3-cups *foomatic-bin *foomatic-db *cupsomatic-ppd The last package includes 918 *.ppd files, including /usr/share/cups/model/IBM/Execjet_4072-bj200.ppd While this isn't your 4076, perhaps its close enough. You configure CUPS via a local webpage, http://localhost:631 Installation of cups removed my print server package lprng, but then I only expect one printserver to dominate printing on one computer. I see your 4076 mentioned in the Unix printer compatability database, http://www.linuxprinting.org/printer_list.cgi There, select Lexmark, then select 4076. This spawns a webpage that says this Lexmark 4076 printer Works with drivers for the HP DeskJet 500 But this also says the Lexmark 4076 is a BW Inkjet 300x300 while you say it is a Colorprinter (hmmm). I also see your printer mentioned on Lexmark's site, http://drivers.lexmark.com/drivers.nsf/SelectPrinter?OpenForm0 and their website you probably visited, http://drivers.lexmark.com/drivers.nsf/SelectPrinter?OpenForm4076 If you download one of their drivers (eg, one for Windows 95, 76WN313E.EXE), then run that *.exe file on the appropriate computer, you likely get a *.ppd file that you can use in CUPS. But this is a too involved a solution, though I have seen Linux documentation mention this very solution: to run a *.exe file then get the needed *.ppd file. Of course, as said above, the cupsomatic-ppd supplied 4072 *.ppd might work well under CUPS. On Sun, Jun 16, 2002 at 12:41:41PM +0200, Tinus Kotzé wrote: Can anyone help me with the Lexmark ExecJet IIc 4076 Colorprinter. I have searched the net and could not find a solution for my problem getting this printer to work. At lexmark's page everything goes well until I have to state a operating system where the choices are only Redhat, SuSe... but not Debian and no source to compile the drivers with for Debian. I have found that it supposedly works in BW ok with the HP DeskJet 500. Thankyou in advance Tinuns -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
syslog-ng gets no kernel messages --- SOLVED
I installed the package syslog-ng, replacing the package sysklogd.
After this, my kernel logs (including my iptables logs) no longer
went to /var/log/{kern,debug,messages}, or any other file in /var/log.
Syslog-ng would log the usual daemon messages.
After spending 5 hours alterning the new /etc/syslog-ng/syslog-ng.conf,
I saw that my Debian Linux needed only a reboot [aka Windows].
Actually, I didn't reboot, I ran
/etc/rc2.d/S10syslog-ng stop
/etc/rc2.d/S11klogd stop
/etc/rc2.d/S10syslog-ng start
/etc/rc2.d/S11klogd start
Normally, one would restart these in /etc/init.d,
which I had been futily doing, but the start order
seemed necessary from /etc/rc2.d .
The two packages syslog-ng [or sysklogd] and klogd,
as the documentation says, work closely with each other.
The package klogd sends kernel logs
(including my wanted iptables firewall logs) to the syslog daemon.
As long as I have the pulpit, I'll comment on syslog-ng a little more,
and elucidate some documentation.
In several ways, syslog-ng eases my logging.
a. My firewall messages cluttered my /var/log files
almost to uselessness.
Since my firewall rules logged with options like,
-j LOG --log-level info --log-prefix FIREWALL
then every syslog message included the string FIREWALL.
Knowing this, I added three lines to /etc/syslog-ng/syslog-ng.conf,
including
filter f_firewall { match(FIREWALL); };
With the following additional lines,
destination firewall{ file(/var/log/firewall.log \
owner(root) group(adm) perm(0640)); };
log { source(src); filter(f_firewall); destination(firewall); \
flags(final); };
all my iptables FIREWALL logging went to the file
/var/log/firewall.log.
Notice the flags(final), which prevents looking at
further log rules for an incoming matched message
[after looking at the syslog-ng documentation cross-eyed,
one finally sees how to write this option].
My iptables firewall logs now go to ONLY one file---wonderful.
b. Before, syslog messages were repeated across
several files in /etc/log/.
While this helps the administrator see logs several ways,
including time-sequenced messages in /var/log/syslog,
many of my log files became unuseable,
having over 1 million lines after 1 week's logging.
Using many flags(final) as above,
I need see no duplicate log messages.
Additional comment:
One default configuration line had,
source src { unix-dgram(/dev/log); internal(); };
The syslog-ng documentation
in /usr/share/doc/syslog-ng/sgml/syslog-ng.ps.gz
said linux uses SOCK_STREAM while BSD operating systems use SOCK_DGRAM,
which lead me to wrongly attempt changing this line to unix-stream,
as several other people on-the-web also attempted.
Additionally, the syslog-ng documentation didn't tell if the above
source entry represented,
unix-dgram AND internal
unix-dgram OR internal
It represents the latter,
logs coming from either unix-dgram OR internal.
This internal() was necessary to get kernel logs processed
by syslog-ng.
This syslog-ng package is Linux-candy.
--
Jameson C. Burt, NJ9L Fairfax, Virginia, USA
[EMAIL PROTECTED] http://www.coost.com
(202) 690-0380 (work)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: slogin telnet 60-minute timeout---SOLVED
I was logging in from my office Debian computer through an office firewall, through my home Debian computer's firewall into my home Debian computer. Then a timeout occured at 60 minutes. When a friend slogin from his Debian home computer to my Debian home computer, no timeout occured. THE TIMEOUT PROBLEM RESIDED IN MY OFFICE'S CISCO ROUTERS OR ITS FIREWALL The solution to this timeout can be found within comments of the following perl script, http://www.humbug.org.au/ssh-https-tunnel Specifically, he says, Many proxies will timeout connections very quickly when there is no activity. If your ssh client supports it, ADD THE FOLLOWING TO THE ~/.ssh/config file. #Debian-email: or to /etc/ssh/ssh_config? ProtocolKeepAlives 5 Another popular method is to X-Forward something like xclock -update 5 to keep the connection active. After some reading, I see that this ProtocolKeepAlives is set for the ssh client, not for the sshd daemon. It sends ssh IGNORE (SSH_MSG_IGNORE) packets. Tangential: I must upgrade my office computer from potato to woody to get a newer ssh using ProtocolKeepAlives. ---Jim Burt On Fri, May 24, 2002 at 04:31:18PM -0400, Jameson C. Burt wrote: Ever since upgrading to woody 8 months ago, both my slogin and telnet sessions lock after idling 60 minutes. These sessions still work after 50 minutes idling, but lock after 1 hour 10 minutes idling. After 2 hours, the remote host ends both the original ssh [telnet] and spawned bash processes. Both the remote and local computers run Debian Linux, and the remote Debian computer seems to cause the locking. I would like my slogin working as before my upgrade to woody, without idle timeouts every 60 minutes. I welcome any suggestions. Following are some of my many attempts and 35 hours of effort to solve this problem. These attempts almost [but nothing is absolute] rule out timeouts arising from any of, slogin and the spawned ssh daemon [or telnet] bash shell iptables and its conntrack 1. SLOGIN and TELNET After my slogin [telnet] connection locks (at 1 hour) and before it disappears (2 hours), both ssh [in.telnetd] and its spawned bash shell remain running processes on the remote Debian computer. And slogin [telnet] remains a running process on the local Debian computer. From this, I conclude that ssh [telnet] has not timed-out, and ssh [telnet] has not caused my local xterm to lock. Additionally, this timeout problem occurs with both slogin and telnet, adding support that the problem does not lie in either. 2. BASH If on the target computer I set TMOUT=5, 5 seconds later I get the message, timed out waiting for input: auto-logout Because this message differs from the message I get with a slogin or telnet timeout after 120 minutes (60 minutes while locked), Read from remote host bbmo.com: Connection timed out then I conclude that my problem does not come from the bash shell TMOUT variable. 3. IPTABLES/NETFILTER The ultimate test with iptables would flush the firewall and check for any timeout. Unfortunately, the logs on my remote computer show numerous nefarious connections attempts, so I won't bring down iptables without disconnecting my DSL cable. However, I have observed the following. Iptable's/netfilter's connection tracking (conntrack) for -m state base rules appears to work correctly, since the third column of, /proc/net/ip_conntrack counts down by seconds from 5 days (hardcoded into the netfilter file .../net/ipv4/netfilter/linux-2.5.17.tar.bz2), 432,000 #seconds After the 428,400 second countdown mark (1 hour or 3600 seconds), I still see netfilte's conntrack working; indeed, after some time, I saw a count as low as (just before 2 hours or 7200 seconds when this remote computer removed the connection), 424,842 #seconds Soon after this, the remote computer removed both the ssh and bash processes, at which time this conntrack count was reset to 5 hours, 432,000 then a few minutes later, this conntrack line was removed. At that time, neither computer had any ghosts of slogin [telnet] session, except in log files. Here are two example conntrack lines I observed, the first for ssh (sport=22), and the second for telnet (sport=223). Remember, the third column represents the number of seconds until netfilter times-out. tcp 6 431811 ESTABLISHED \ src=199.129.208.230 dst=66.92.166.19 sport=724 dport=22 \ src=66.92.166.19 dst=199.129.208.230 sport=22 dport=724 \ [ASSURED] use=1 # tcp 6 425116 ESTABLISHED \ src=199.129.208.230 dst=66.92.166.19 sport=2468 dport=23 \ src=66.92.166.19 dst=199.129.208.230 sport=23 dport=2468 \ [ASSURED] use=1
slogin telnet 60-minute timeout at remote computer. Why?
Ever since upgrading to woody 8 months ago, both my slogin and telnet sessions lock after idling 60 minutes. These sessions still work after 50 minutes idling, but lock after 1 hour 10 minutes idling. After 2 hours, the remote host ends both the original ssh [telnet] and spawned bash processes. Both the remote and local computers run Debian Linux, and the remote Debian computer seems to cause the locking. I would like my slogin working as before my upgrade to woody, without idle timeouts every 60 minutes. I welcome any suggestions. Following are some of my many attempts and 35 hours of effort to solve this problem. These attempts almost [but nothing is absolute] rule out timeouts arising from any of, slogin and the spawned ssh daemon [or telnet] bash shell iptables and its conntrack 1. SLOGIN and TELNET After my slogin [telnet] connection locks (at 1 hour) and before it disappears (2 hours), both ssh [in.telnetd] and its spawned bash shell remain running processes on the remote Debian computer. And slogin [telnet] remains a running process on the local Debian computer. From this, I conclude that ssh [telnet] has not timed-out, and ssh [telnet] has not caused my local xterm to lock. Additionally, this timeout problem occurs with both slogin and telnet, adding support that the problem does not lie in either. 2. BASH If on the target computer I set TMOUT=5, 5 seconds later I get the message, timed out waiting for input: auto-logout Because this message differs from the message I get with a slogin or telnet timeout after 120 minutes (60 minutes while locked), Read from remote host bbmo.com: Connection timed out then I conclude that my problem does not come from the bash shell TMOUT variable. 3. IPTABLES/NETFILTER The ultimate test with iptables would flush the firewall and check for any timeout. Unfortunately, the logs on my remote computer show numerous nefarious connections attempts, so I won't bring down iptables without disconnecting my DSL cable. However, I have observed the following. Iptable's/netfilter's connection tracking (conntrack) for -m state base rules appears to work correctly, since the third column of, /proc/net/ip_conntrack counts down by seconds from 5 days (hardcoded into the netfilter file .../net/ipv4/netfilter/linux-2.5.17.tar.bz2), 432,000 #seconds After the 428,400 second countdown mark (1 hour or 3600 seconds), I still see netfilte's conntrack working; indeed, after some time, I saw a count as low as (just before 2 hours or 7200 seconds when this remote computer removed the connection), 424,842 #seconds Soon after this, the remote computer removed both the ssh and bash processes, at which time this conntrack count was reset to 5 hours, 432,000 then a few minutes later, this conntrack line was removed. At that time, neither computer had any ghosts of slogin [telnet] session, except in log files. Here are two example conntrack lines I observed, the first for ssh (sport=22), and the second for telnet (sport=223). Remember, the third column represents the number of seconds until netfilter times-out. tcp 6 431811 ESTABLISHED \ src=199.129.208.230 dst=66.92.166.19 sport=724 dport=22 \ src=66.92.166.19 dst=199.129.208.230 sport=22 dport=724 \ [ASSURED] use=1 # tcp 6 425116 ESTABLISHED \ src=199.129.208.230 dst=66.92.166.19 sport=2468 dport=23 \ src=66.92.166.19 dst=199.129.208.230 sport=23 dport=2468 \ [ASSURED] use=1 WORKAROUND: a process that displays on the local screen from the remote screen can keep the connection open. For example, the following process sends a message from the remote computer to the local computer every 10 minutes, keeping the connection open past even 2 hours. while : ; do date; sleep 600; done Both my remote computer and my local computer run Debian Linux. The remote computer to which I slogin runs Debian's woody. The local computer still runs Debian's potato. The local potato computer can slogin to an AIX computer and remain logged in for weeks. I would like to do that same eternal slogin to my remote Debian woody computer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ssh hangs after about 15 minutes for each connection
Both I and a friend have noticed that our slogin connections hang (timeout?) after not using our connections for about 15 minutes. I noticed this hanging after I upgraded from potato to woody about 10 months ago, and my friend noticed this hanging after he upgraded from potato to woody about 3 months ago. For example, from my office-computer, slogin -X my-home-computer after which I seem to remain connected as long as I interract with the connection for about a 15 minute period. But if I do not interract for about 15 minutes, then I will no longer get any keyboard interraction however many minutes/days pass, including no response from ctl-C, ctl-D, ctrl-Z. I can only get my local xterm back, and I do that with ~. However, my remote computer [home computer in my case] continues to run the corresponding ssh process. After using ~. on my local computer [office computer in my case], I merely accumulate these ssh processes on my remote computer [home computer in my case], a process clutter that I eventually kill after a week. I have even tried changing on my remote [home] computer /etc/ssh/ssh_conf and /etc/ssh/ssh_conf with KeepAlive no but my slogin still hangs after about 15 minutes of non-use. I notice no aberrant log entries with the pattern ssh. Something seems to have changed between the potato and the woody versions of ssh. I welcome any suggestions. Here is some of my current Debian woody configuration (up-to-date via apt-get) as of April 9. ssh3.0.2p1-8.3 debconf1.0.31 libc6 2.2.5-4 libpam-modules 0.72-35 libpam-runtime 0.72-35 libpam0g 0.72-35 libssl0.9.60.9.6c-2 libwrap0 7.6-9 Wietse Venema's TCP wrappers library zlib1g 1.1.4-1 compression library - runtime -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) You can only find truth with logic if you have already found truth without it. -- G.K. Chesterton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Linux in Business---accounting packages
Sometimes users mostly prefer software other than that their employer provides. This is especially true among the technical elite who might prefer LaTeX on Unix, while their managers give them Microsoft Word. If the employees mostly graduated in the last 5 years, they may well prefer some accounting package other than what their employer provides. Concerning accounting packages, while I don't know their quality, I have recently seen articles on software coming from the U.S. state of Ohio, Noguska's Nola which is web based and GPLed, so they make their profit on support and customization. Such an outfit VERY MUCH WANTS TO PROVIDE SUPPORT. Here is a link, http://www.linuxworld.com/site-stories/2002/0225.xterminal13.html The author of the above LinuxWorld article preferred Noguska's Nola to another accounting software, SQL-Ledger, http://www.sql-ledger.com On Mon, Apr 08, 2002 at 02:59:51PM +0100, Phill Gillespie wrote: Can anyone suggest good (commercial) software or at least point me in the right direction? I guess the other big factor is European focus? Two stateside products are Appgen Proven but I would much prefer a UK/EU based approach. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) You can only find truth with logic if you have already found truth without it. -- G.K. Chesterton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
LS-120 grub boot with 1.44MB but not 120MB floppy: Geom Error
CONFIG_BLK_DEV_IDEDMA_PCI=y CONFIG_BLK_DEV_ADMA=y CONFIG_IDEDMA_PCI_AUTO=y CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDEDMA_AUTO=y CONFIG_BLK_DEV_IDE_MODES=y 3. I run Debian Linux woody. 4. I have only two regular hard drives, both scsi, /dev/sda /dev/sdb 5. Motherboard Asus P3B-F, Bios version 1007 Beta 1 [Bios versions 1004 and 1006 produced the same results] 6. grub version 0.90-9 ~~~COMMENTS:~~ 1. Comments. I prefer the LS-120 because it has a locking switch, missing from all other non-standard floppy drives like the Zip drives. This provides security for tripwire/aide checksum checking, and possibly booting strictly from a read-only/locked 120MB LS-120 floppy. The LS-240 drives have come out for USB, using 240MB floppies, and standard floppies (25 cents US) formattable to 32MB (WOW), if Linux supports this. IDE and soon SCSI versions are offered for $170 by http://www.winstation.com/Superdisk.htm with model numbers W0281 Int IDE 1x standard height beige. W0071 Int SCSI 1x standard height beige, 7.3FW W0271 Ext SCSI 1x standard height beige, 7.3FW -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) You can only find truth with logic if you have already found truth without it. -- G.K. Chesterton
Email line-length defaults to about 76; how to increase?
My email lines get split after about 76 characters. How could I change this to something longer, or should email lines be split at 76 characters? This limit causes problems whenever I email Linux syslog lines, which are seldom less than even 90 characters in length. I haven't been able to determine if this line-length limit is set by exim, procmail, or perhaps my mail user agent (balsa). -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work)
Re: Kernel 2.4.6 won't boot---kernel ethernet developers have changed
On Wed, 04 Jul 2001 19:38:50 Wayne Topa wrote: Subject: Re: Kernel 2.4.6 won't boot Date: Thu, Jul 05, 2001 at 12:58:37AM +0200 In reply to:Viktor Rosenfeld Quoting Viktor Rosenfeld([EMAIL PROTECTED]): Bostjan Muller wrote: Hi! I have just found out that kernel 2.4.6 won't boot on my pentium 200 MMX machine. The same has allready happened with kernel 2.4.6-pre8, but I thought it will be fixed later when stable release comes out. The same kernel boots just ok on my toshiba p75 laptop. Has anyone had any experience like that? The boot stops after this line: FDC 0 is a post-1991 82077 Also, as suggested in another mail, after the floppy stuff comes the network stuff. If this is still the same with 2.4.6 (it should be, but I wouldn't know, I have floppy support compiled as a module), than something is broken there. HTH, Viktor PS: I just compiled 2.4.6 on my machine, let's see, if it's boots. Just did reboot and here is what my dmesg shows Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 ne2k-pci.c:v1.02 10/19/2000 D. Becker/P. Gortmaker http://www.scyld.com/network/ne2k-pci.html PCI: Found IRQ 11 for device 00:0b.0 eth0: RealTek RTL-8029 found at 0x6500, IRQ 11, 00:40:05:3D:34:51. PPP generic driver version 2.4.1 SCSI subsystem driver Revision: 1.00 PCI: Found IRQ 9 for device 00:0f.0 Boots fine except my OSS doesn't sork and they don't have thr 2.4.6 version aavilable, yet. So I agree, the network is where you need to look. Donald Becker, ethernet expert, apparently still works in the arena of the older (legacy) kernel 2.2.* . Jeff Garzik, who now does much of the ethernet kernel work, has made many changes. Jeff is very active, making many changes and quickly coding to users' concerns. But this activity has stopped some of our networking. Jeff wants Donald Becker to look at some patches, but Donald Becker is busy elsewhere. You can see one of Jeff Garzik's comments on this at http://www.tux.org/hypermail/linux-tulip/2001-Jun/0042.html That mail archive thread reveals much about current ethernet kernel problems. Going from kernel 2.4.2 to 2.4.5, my 4-port tulip based Compex FL400TX ethernet card no longer works: it works on eth0 but not on eth1, effectively reducing my 4-port ethernet card to a 1-port ethernet card. My problem upgrading to kernel 2.4.5 might be in Jeff Garznik's words from /usr/src/linux-2.4.5/drivers/net/tulip/ChangeLog, 2001-05-12 Jeff Garzik [EMAIL PROTECTED] * tulip_core.c, tulip.h: Remove Conexant PCI id, no chip docs are available to fix problems with support. I have read about problems running other multi-port ethernet cards with the new tulip driver; eg, the Znyx cards. I hope these multi-port tulip based cards get kernel support again, because many of us run firewalls so to conserve PCI slots we use multi-port ethernet cards.
Re: Kernel 2.4.6 won't boot---kernel ethernet developers have changed
On Wed, 04 Jul 2001 19:38:50 Wayne Topa wrote: Subject: Re: Kernel 2.4.6 won't boot Date: Thu, Jul 05, 2001 at 12:58:37AM +0200 In reply to:Viktor Rosenfeld Quoting Viktor Rosenfeld([EMAIL PROTECTED]): Bostjan Muller wrote: Hi! I have just found out that kernel 2.4.6 won't boot on my pentium 200 MMX machine. The same has allready happened with kernel 2.4.6-pre8, but I thought it will be fixed later when stable release comes out. The same kernel boots just ok on my toshiba p75 laptop. Has anyone had any experience like that? The boot stops after this line: FDC 0 is a post-1991 82077 Also, as suggested in another mail, after the floppy stuff comes the network stuff. If this is still the same with 2.4.6 (it should be, but I wouldn't know, I have floppy support compiled as a module), than something is broken there. HTH, Viktor PS: I just compiled 2.4.6 on my machine, let's see, if it's boots. Just did reboot and here is what my dmesg shows Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 ne2k-pci.c:v1.02 10/19/2000 D. Becker/P. Gortmaker http://www.scyld.com/network/ne2k-pci.html PCI: Found IRQ 11 for device 00:0b.0 eth0: RealTek RTL-8029 found at 0x6500, IRQ 11, 00:40:05:3D:34:51. PPP generic driver version 2.4.1 SCSI subsystem driver Revision: 1.00 PCI: Found IRQ 9 for device 00:0f.0 Boots fine except my OSS doesn't sork and they don't have thr 2.4.6 version aavilable, yet. So I agree, the network is where you need to look. Donald Becker, ethernet expert, apparently still works in the arena of the older (legacy) kernel 2.2.* . Jeff Garzik, who now does much of the ethernet kernel work, has made many changes. Jeff is very active, making many changes and quickly coding to users' concerns. But this activity has stopped some of our networking. Jeff wants Donald Becker to look at some patches, but Donald Becker is busy elsewhere. You can see one of Jeff Garzik's comments on this at http://www.tux.org/hypermail/linux-tulip/2001-Jun/0042.html That mail archive thread reveals much about current ethernet kernel problems. Going from kernel 2.4.2 to 2.4.5, my 4-port tulip based Compex FL400TX ethernet card no longer works: it works on eth0 but not on eth1, effectively reducing my 4-port ethernet card to a 1-port ethernet card. My problem upgrading to kernel 2.4.5 might be in Jeff Garznik's words from /usr/src/linux-2.4.5/drivers/net/tulip/ChangeLog, 2001-05-12 Jeff Garzik [EMAIL PROTECTED] * tulip_core.c, tulip.h: Remove Conexant PCI id, no chip docs are available to fix problems with support. I have read about problems running other multi-port ethernet cards with the new tulip driver; eg, the Znyx cards. I hope these multi-port tulip based cards get kernel support again, because many of us run firewalls so to conserve PCI slots we use multi-port ethernet cards. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work)
imap package ignores MH style email folders (potato)
With mh style (directory) folders in ~/Mail, I used the imap mail user-agents imp, postilion, and mutt, giving (if needed) the folders directory Mail/, but all user-agents responded essentially, 0 Messages then if I look for folders, I see all the following as folders (that is, every file is treated as a folder, which is mbox folder style) context inbox/.xmhcache inbox/1 #an actual singular email message Here is a listing of all files in ~/Mail, files originally created for/using the mh mail-user agent exmh, ./: .folders context ./drafts:#empty directory ./inbox: .xmhcache 1 Perhaps I need another file in this ~/Mail directory for imap to recognize mh folders. My ~/.mh_profile file mentioned in a University of Washington imap tar file's FAQ contains the lines, Path: Mail draft-folder: drafts unseen-sequence: unseen That UW FAQ also mentioned referring to mh mailboxes thru #mhinbox and #mh/, though my feeble attempts interpreting/trying these possibilities failed. Do I need to use any of these oddities? Imap mail user-agents would, however, correctly recognize all mail when I created the following file with four email messages, ~/mbox I run imap package version 4.7c-1. Imap's binary imapd contains the string mhdriver, hinting mh support. And the imap package file /usr/share/doc/imap/bugs.txt.gz contains the line, Supported local file formats: mbx, mh, mmdf, mtx, mx, news, phile, tenex, unix So, again, the imap package supposedly supports mh style folders. But the imap package only mentions mh folders in the above bugs.txt.gz file and in the tmail manual page, so the imap package's brief mention of mh gives no hints on manually configuring/forcing imap for mh style folders. Do you have any idea how I can use MH style folders with the imap potato package? -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work)
imap package ignores MH style email folders (potato)
With mh style (directory) folders in ~/Mail, I tried several imap mail user-agents, imp, postilion, and mutt, requesting (if needed) the folders directory Mail/, but all these imap-aware user-agents responded essentially, 0 Messages then if I look for folders, I see all the following as folders (that is, every file is treated as a folder, which is mbox folder style) context inbox/.xmhcache inbox/1 #an actual singular email message Here is a listing of all files in ~/Mail, files originally created for/using the mh mail-user agent exmh, ./: .folders context ./drafts:#empty directory ./inbox: .xmhcache 1 Perhaps I need another file in this ~/Mail directory for imap to recognize mh folders. My ~/.mh_profile file mentioned in a University of Washington imap tar file's FAQ contains the lines, Path: Mail draft-folder: drafts unseen-sequence: unseen That UW FAQ also mentioned referring to mh mailboxes thru #mhinbox and #mh/, though my feeble attempts interpreting/trying these possibilities failed. Do I need to use any of these oddities? Imap mail user-agents would, however, correctly recognize all mail when I created the following file with four email messages, ~/mbox I run imap package version 4.7c-1. Imap's binary imapd contains the string mhdriver, hinting mh support. And the imap package file /usr/share/doc/imap/bugs.txt.gz contains the line, Supported local file formats: mbx, mh, mmdf, mtx, mx, news, phile, tenex, unix So, again, the imap package supposedly supports mh style folders. But the imap package only mentions mh folders in the above bugs.txt.gz file and in the tmail manual page, so the imap package's brief mention of mh gives no hints on manually configuring/forcing imap for mh style folders. Do you have any idea how I can use MH style folders with the imap potato package? - -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work)
php4 will not handle *.php3 files? (potato)
Shouldn't the Debian package php4_4.0.3pl1-0potato1.deb handle *.php3 files? Through netscape http://localhost/test-jameson.php, I can see php4 working, where test-jameson.php is ?php phpinfo() ? This common test properly displays a few pages of PHP configuration information. However, testing thru any of netscape/opera/mozilla on the file http://localhost/test4-jameson.php3, I only get a popup window, titled Save As... (type application/x-httpd-php3) to download the test4-jameson.php3 file. I get this same download-response whether test4-jameson.php3 contains the single line !-- ?php phpinfo() ? -- or the single line (recommended test line in Horde Administrator's FAQ) ?php php_info() ? Here are all lines in /etc/apache/* that contain php, where all entries have been put there by Debian package installations, 1. httpd.conf: LoadModule php4_module /usr/lib/apache/1.3/libphp4.so 2. srm.conf: DirectoryIndex index.html index.php index.php3 3. mime.types: application/x-httpd-php phtml pht php application/x-httpd-php3php3 application/x-httpd-php3-source phps application/x-httpd-php3-preprocessed php3p I have installed the following php and apache modules, Package Version --- --- php4 4.0.3pl1-0potato1 php4-cgi 4.0.3pl1-0potato1 php4-gd 4.0.3pl1-0potato1 php4-imap 4.0.3pl1-0potato1 php4-ldap 4.0.3pl1-0potato1 php4-pgsql4.0.3pl1-0potato1 phplib7.3dev-3.1 apache1.3.9-13.1 apache-common 1.3.9-13.1 libapache-mod-ssl 2.4.10-1.3.9-1 I presume that the php4 Debian package should handle php3 files. I deduce this because I am installing imp, whose description (dpkg -s imp) includes Depends: php3 | php4 (= 4.0.3pl1) But the imp package is accessed thru the php3 web page, /usr/share/horde/imp/index.php3 So, while the imp package allows using the package php4 rather than the package php3, web access must be able to interpret *.php3 files---but does not. What have I done wrong? -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) You can only find truth with logic if you have already found truth without it. -- G.K. Chesterton
php4 will not handle *.php3 files? (potato)
Shouldn't the Debian package php4_4.0.3pl1-0potato1.deb handle *.php3 files? Through netscape http://localhost/test-jameson.php, I can see php4 working, where test-jameson.php is ?php phpinfo() ? This common test properly displays a few pages of PHP configuration information. However, testing thru any of netscape/opera/mozilla on the file http://localhost/test4-jameson.php3, I only get a popup window, titled Save As... (type application/x-httpd-php3) to download the test4-jameson.php3 file. I get this same download-response whether test4-jameson.php3 contains the single line !-- ?php phpinfo() ? -- or the single line (recommended test line in Horde Administrator's FAQ) ?php php_info() ? Here are all lines in /etc/apache/* that contain php, where all entries have been put there by Debian package installations, 1. httpd.conf: LoadModule php4_module /usr/lib/apache/1.3/libphp4.so 2. srm.conf: DirectoryIndex index.html index.php index.php3 3. mime.types: application/x-httpd-php phtml pht php application/x-httpd-php3php3 application/x-httpd-php3-source phps application/x-httpd-php3-preprocessed php3p I have installed the following php and apache modules, Package Version --- --- php4 4.0.3pl1-0potato1 php4-cgi 4.0.3pl1-0potato1 php4-gd 4.0.3pl1-0potato1 php4-imap 4.0.3pl1-0potato1 php4-ldap 4.0.3pl1-0potato1 php4-pgsql4.0.3pl1-0potato1 phplib7.3dev-3.1 apache1.3.9-13.1 apache-common 1.3.9-13.1 libapache-mod-ssl 2.4.10-1.3.9-1 I presume that the php4 Debian package should handle php3 files. I deduce this because I am installing imp, whose description (dpkg -s imp) includes Depends: php3 | php4 (= 4.0.3pl1) But the imp package is accessed thru the php3 web page, /usr/share/horde/imp/index.php3 So, while the imp package allows using the package php4 rather than the package php3, web access must be able to interpret *.php3 files---but does not. What have I done wrong? -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) You can only find truth with logic if you have already found truth without it. -- G.K. Chesterton
kernel 2.4, modutils requires libc6 2.1.97
All suggestions for using kernel 2.4 mention upgrading to modutils in either woody or sid, for modutils version 2.3.22 or 2.3.23. However, these have the dependency Depends: libc6 (= 2.1.97) Since I largely keep a potato distribution, I use libc6 version libc6_2.1.3-13 so an upgrade would require upgrading to a woody libc6 version. This flashes a WARNING to me, since libc is very foundational; indeed, a few Debian distributions back, most distribution upgrades failed because of libc changes. Does an upgrade of libc6 from version 2.1.3 to 2.1.97 largely work? But more, I no longer see libc6 version 2.1.97, so I must go all the way to libc6 version libc6_2.2-5 in woody. Oh my, I have heard people having problems with libc6 version 2.2: are there problems upgrading to libc6_2.2? Perhaps my best solution would compile modutils version myself. Besides, I now notice that the kernel source linux-2.4.0.tar.bz2 document .../Documentation/Changes has upped the modutils version requirement from 2.3.15 (in linux-2.4.0-test8) to modutils version 2.4.0 (in linux-2.4.0) which appears nowhere, not even in the .../pool/* directories. -- Jameson C. Burt, NJ9L Fairfax, Virginia, USA [EMAIL PROTECTED] http://www.coost.com (202) 690-0380 (work) You can only find truth with logic if you have already found truth without it. -- G.K. Chesterton
