Linux-Setup Digest #502, Volume #20 Thu, 25 Jan 01 16:13:10 EST
Contents:
Re: Kernel 2.4 installation problem (Frederic Faure)
Re: RH7 fail to bring up eth0; but pump work...?! ([EMAIL PROTECTED])
Re: Trying to install dual boot WinNT + Linux ("Eric en Jolanda")
Re: X Config ("Eric en Jolanda")
Re: Peer not authorized ("Peter T. Breuer")
Re: Somebody create a How-To on upgrading to Kernel 2.4, please !
([EMAIL PROTECTED])
Re: Somebody create a How-To on upgrading to Kernel 2.4, please ! ("Phar Awei")
Re: Trying to install dual boot WinNT + Linux ("Eric en Jolanda")
Re: SMC 1211 Network Card - Problems with Kernel 2.4 ("S. Umar")
Broken RPM upgrade with Cooker ("Ross Burton")
Re: Trying to install dual boot WinNT + Linux ("Tyberghein Jorrit")
Re: Trying to install dual boot WinNT + Linux ("Tyberghein Jorrit")
Getting Win2000 On GRUB Menu (rob)
"Dos" Extended ASCII in Linux??? ([EMAIL PROTECTED])
"Dos" Extended ASCII in Linux??? ([EMAIL PROTECTED])
Re: Somebody create a How-To on upgrading to Kernel 2.4, please ! (Colin Watson)
Re: remote printing problem ([EMAIL PROTECTED])
Can you use "DOS" Extended ASCII in Linux? ([EMAIL PROTECTED])
2.2.18 kernel fails to load ([EMAIL PROTECTED])
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Frederic Faure)
Subject: Re: Kernel 2.4 installation problem
Date: Thu, 25 Jan 2001 19:08:12 GMT
On Wed, 24 Jan 2001 10:57:12 +0100, Dirk Emmermacher
<[EMAIL PROTECTED]> wrote:
>I've got the same problem with Suse 7.0. Is it possible to use the
>redhat patches with Suse??? I don't found this files at the Suse
>server...
>Jeff Moore wrote:
>> Upgrade to gcc2.96-69 and glibc2.2-9 as per redhat upgrades and try again.
>> > Hi, I tried to install Kernel 2.4 on my machine. I compiled it with gcc
>> > 2.95.2. The compilation was all right. But when I put the bzImage into
>> > /boot and changed lilo entries, then started booting, the screen shows:
>> >
>> > Uncompressing Kernel...
>> > Ok, booting the kernel.
>> >
>> > Then stopped there.
>
>Do you have installed the files? Works this solution?
>
>I want to be glad to get an answer from you.
Don't bother just yet. I installed a fresh RH 7, and it would get
stuck as indicated below. D'loaded both gcc, cpp, glibc source RPMs,
compiled and installed them. Recompiled 2.4. Same problem.
In another thread, someone says to check the CPU setting when
configuring the kernel (make menuconfig or make xconfig.) Indeed, the
default is set to P III instead of 386.
FF.
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: RH7 fail to bring up eth0; but pump work...?!
Date: Thu, 25 Jan 2001 18:56:52 GMT
In article <[EMAIL PROTECTED]>,
Ernest Siu <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I just installed RH7.0 and I have a RealTek8XXX for my eth0. When it
> boots up it always show:
>
> Bringing up interface eth0. Determining the IP Information.
> Operation Failed.
>
> I can't even get anything from "dmesg | grep eth". But using the
> graphical network configurator, I can see eth0 there but it is
> "inactive". The strange thing is when I got in as root, I do "pump -i
> etho0 -h crxxxxx-x", it will get IP and connected to Internet no
> problem.
>
> So what's the deal when it boots up? Now I put the pump command under
> boot-up script so it will run, but it takes RH so much time trying to
> resolve whatever the "Bringing up interface eth0...."-problem is. At
> the very least I'd like to stop RH to perform that task. If possible
it
> will be the best if I can fix this fail thing and not use my pump
> command in the script.
>
> Thanks for any comment/suggestion!!
>
> Ernest
> [EMAIL PROTECTED]
>
>
This looks to me like your card is trying to get an ip address but
can't, is it set up for DHCP? couple things to check run as root
linuxconf and check to see that either you have the correct ip address
assigned or that it is set up for DHCP and check for correct domain name
and work forward from there. hope that helps
--
Tim Coble
Support provided by Linuxgruven, Inc.
www.linuxgruven.com
314-727-0918
Sent via Deja.com
http://www.deja.com/
------------------------------
From: "Eric en Jolanda" <[EMAIL PROTECTED]>
Subject: Re: Trying to install dual boot WinNT + Linux
Date: Thu, 25 Jan 2001 20:01:31 +0100
Probably the installer created a messy table.
`fdisk -l /dev/hda`
and post the result here.
I'll try to tell you how to correct it.
Eric
------------------------------
From: "Eric en Jolanda" <[EMAIL PROTECTED]>
Subject: Re: X Config
Date: Thu, 25 Jan 2001 20:12:12 +0100
> I am running Red Hat Linux 7.0 with VA Linux Enhancements...
> I cannot start x in non-superuser mode.
> Below is the error message I receive upon attempting to do so ("startx")
> =====================================
> Fatal server error:
> xf86OpenConsole: Server must be running with root permissions
> You should be running Xwrapper to start the server or xdm
> We strongly advise against making the SUID root!
>
> When reporting the problem related to a server crash, please send the
> full server output, not just the last messages
>
> X connection to :0.0 broken (explicit kill or server shutdown).
> ==========================================
> What appears to be the problem?
>
It appears to be that the X server isn't started as root.
As the message says.
Fix it.
startx/Xwrapper/xdm/X : one of these has something erroneous.
I can't tell from here.
> I am using the "Xconfigurator" utility.
>
How do you manage without the X server?
Eric
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Subject: Re: Peer not authorized
Date: Thu, 25 Jan 2001 19:46:02 GMT
Ed Champion <[EMAIL PROTECTED]> wrote:
> When I connect to my ISP I get terminated and I get the following
> message in my ppp-log file that says Peer is not authorized to use
> remote address 208.237.4.7.
> My local network address is 192.168.0.1.
> Can someone help me with this problem.
remove the option from your ppp configuration that is requiring the
other computer (the "peer") to authenticate itself. It should be
obvious.
I'm just guessing, mind you, since you didn't reproduce the error
message, but paraphrased it!
Peter
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Somebody create a How-To on upgrading to Kernel 2.4, please !
Crossposted-To: comp.os.linux.misc
Date: Thu, 25 Jan 2001 19:48:23 GMT
In comp.os.linux.misc Arctic Storm <[EMAIL PROTECTED]> wrote:
: seem to have greater insight and better understanding of the spirit of
: Linux. Let me explain to you. The intension of Linux is to provide a
: reliable/dependable product for productivity and utility, for *everyone*; to
: help and serve the general public.
It is also intended for people to adhere to the mantra that "God Helps Those
Who Help Themselves". It is, always has been, and will continue to be
expected that people try their darndest to help themselves out before coming
and seeking help. And, since it shouldn't be rocket science to upgrade
your kernel, perhaps the belief on the part of that poster was that you
didn't exactly do your darndest.
So no, it isn't for "everyone", it is for "everyone who wants to put effort
forth".
--
Jeff Gentry [EMAIL PROTECTED] [EMAIL PROTECTED]
SEX DRUGS UNIX
------------------------------
From: "Phar Awei" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: Somebody create a How-To on upgrading to Kernel 2.4, please !
Date: Thu, 25 Jan 2001 20:09:46 GMT
For REDHAT from REDHAT
3. The Upgrade
We should now be ready to actually upgrade the kernel RPMs and related
packages. You will need to be logged in as root to execute all of these
commands.
3.1 Non Kernel Packages
First, I will upgrade the non-kernel packages. On a Red Hat Linux 5.2
system, you would type something similar to
rpm -Uvh mkinitrd*rpm SysVinit*rpm initscripts*rpm
3.2 Kernel Source Packages
Note: Unless you do development work, you do not need to install or upgrade
these packages.
Next, you should upgrade the kernel-headers and kernel-source packages.
These packages take up a lot of room, and unless you are a deep kernel
hacker, you probably do not need multiple copies of the source around.
# rpm -Uvh kernel-headers-2.0.36-1.i386.rpm kernel-source-2.0.36-1.i386.rpm
kernel-headers
##################################################
kernel-source
##################################################
If you receive errors when upgrading the kernel-headers file, it is due to
the fact it couldn't find a directory to remove but everything else should
work ok.
3.3 Kernel and Modules
The final task to do with RPM is to install the new kernels. We do an
install instead of an upgrade as an added safety step. By not removing the
old kernel and modules, you should be able to boot back into the old version
if you need to. Again, on my example machine,
# rpm -ivh kernel-2.0.36-1.i386.rpm kernel-ibcs-2.0.36-1.i386.rpm
kernel-pcmcia-cs-2.0.36-1.i386.rpm
kernel
##################################################
kernel-ibcs
##################################################
kernel-pcmcia-cs
##################################################
You may find out that there are conflicts between the old and new
kernel-pcmcia packages. To get around this error you can either force the
install, or upgrade the package (Note: You can't use the old kernel with
PCMCIA if you upgrade the package.)
# rpm -ivh --force kernel-pcmcia-cs-2.0.36-1.i386.rpm
kernel-pcmcia-cs
##################################################
3.4 Initial RAM disk
The final steps of the upgrade are to make the initial RAM disk for your
machine, and to manipulate LILO to boot the new kernel. These steps will
require you to edit the /etc/lilo.conf file.
The purpose of the initial RAM disk is to allow a modular kernel to have
access to modules that it might need to boot from before the kernel has
access to the device where the modules normally reside. Thus, you end up
with a chicken and egg problem, where you need a driver to talk to the
hardware where the driver resides on. This problem normally occurs on
systems with SCSI controllers.
To make this RAM disk, you will first need to find out what the kernel in
/boot is called and then use the mkinitrd command.
To find out what the kernel we need to link against, we will list the /boot
directory, and look for what kernels are installed. The Red Hat kernel RPM
install should create a symbolic link from the file /boot/vmlinuz to the
kernel that it installed. Also see the section on lilo.conf above.
# ls -l /boot/vmlinuz*
lrwxrwxrwx 1 root root 16 Dec 2 18:31 /boot/vmlinuz ->
vmlinuz-2.0.36-1
-rw-r--r-- 1 root root 454325 Oct 13 22:41
/boot/vmlinuz-2.0.36-0.7
-rw-r--r-- 1 root root 454349 Nov 17 13:11
/boot/vmlinuz-2.0.36-1
In the above example, the kernel is /boot/vmlinuz-2.0.36-1 and we can feed
this data to the mkinitrd command.
# mkinitrd /boot/initrd-2.0.36.img 2.0.36-1
# ls -l /boot/initrd-2.0.36*
-rw-r--r-- 1 root root 210885 Nov 20 09:57
/boot/initrd-2.0.36-0.7.img
-rw-r--r-- 1 root root 212043 Dec 2 18:47
/boot/initrd-2.0.36.img
We have successfully created the initial RAM disk called
/boot/initrd-2.0.36.img, and can proceed to editing the LILO files.
3.5 Setting up LILO
The last step before rebooting your machine should be editing LILO to find
the new kernel images. This is fairly simple by adding an entry that follows
this template:
image=/boot/vmlinuz-<kernel version goes here>
label=linux-test
root=<your root (/) partition goes here
initrd=/boot/initrd-<kernel version goes here>
read-only
On my Red Hat Linux 5.2 machine, I made the following changes to the
/etc/lilo.conf file.
# cat /etc/lilo.conf
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
image=/boot/vmlinuz-2.0.36-1
label=linux
root=/dev/hda9
initrd=/boot/initrd-2.0.36.img
read-only
image=/boot/vmlinuz-2.0.36-0.7
label=linux.old
root=/dev/hda9
initrd=/boot/initrd-2.0.36-0.7.img
read-only
other=/dev/hda1
label=dos
table=/dev/hda
What this did was make the "default" boot kernel the new one I installed. I
also renamed the option for booting the old kernel to be linux.old. On my
system the root partition is /dev/hda9, but this will most likely different
on your machine.
Finally, you need to run the lilo command to write these changes to the boot
sector LILO is installed on.
# lilo -v
LILO version 20, Copyright 1992-1997 Werner Almesberger
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Boot image: /boot/vmlinuz-2.0.36-1
Mapping RAM disk /boot/initrd-2.0.36.img
Added linux *
Boot image: /boot/vmlinuz-2.0.36-0.7
Mapping RAM disk /boot/initrd-2.0.36-0.7.img
Added linux.old
Boot other: /dev/hda1, on /dev/hda, loader /boot/chain.b
Added dos
/boot/boot.0300 exists - no backup copy made.
Writing boot sector.
You should be ready to reboot your machine with shutdown -r now and the
system will come up with the new kernel. Remember to remove the rescue
floppy from the drive (which is what I forgot to do when writing this
article).
<[EMAIL PROTECTED]> wrote in message
news:bq%b6.2783$[EMAIL PROTECTED]...
> In comp.os.linux.misc Arctic Storm
<[EMAIL PROTECTED]> wrote:
> : seem to have greater insight and better understanding of the spirit of
> : Linux. Let me explain to you. The intension of Linux is to provide a
> : reliable/dependable product for productivity and utility, for
*everyone*; to
> : help and serve the general public.
>
> It is also intended for people to adhere to the mantra that "God Helps
Those
> Who Help Themselves". It is, always has been, and will continue to be
> expected that people try their darndest to help themselves out before
coming
> and seeking help. And, since it shouldn't be rocket science to upgrade
> your kernel, perhaps the belief on the part of that poster was that you
> didn't exactly do your darndest.
>
> So no, it isn't for "everyone", it is for "everyone who wants to put
effort
> forth".
>
> --
> Jeff Gentry [EMAIL PROTECTED] [EMAIL PROTECTED]
> SEX DRUGS UNIX
------------------------------
From: "Eric en Jolanda" <[EMAIL PROTECTED]>
Subject: Re: Trying to install dual boot WinNT + Linux
Date: Thu, 25 Jan 2001 21:11:11 +0100
> Hi Jorrit. Generally you should install a windows partition first and
> then use fdisk or another linux product to make the linux partions.
agreed
> Windows won't recognize anything that it does not create, but linux
> does.
windows only recognise windows partition ID's, but you make this with linux
fdisk just fine too.
> If you make the linux partitions last it will recognize dos and
> linux partitions.
And windows won't be able to mess with your linux install
> Then use lilo to select which os to boot.
I like that advise,
but the NT loader as main bootloader is fine too. And better documented.
> You should
> also NOT use a swap partition over 100M.
for WHAT reason?
mine is 128M and works like a charm.
> Check linuxnewbies.org for
> information on dual booting and setup of the partitions.
Very good advise
------------------------------
From: "S. Umar" <[EMAIL PROTECTED]>
Subject: Re: SMC 1211 Network Card - Problems with Kernel 2.4
Date: Thu, 25 Jan 2001 14:13:54 -0600
At this point this seems to be a problem for many people...the built in
pcmcia
support in 2.4. Despite choosing everything right it still fails to
configure
the card. My solution is to turn off pcmcia support in the kernel all
together,
get the pcmcia-3.1.23 source and compile and build and install all the
modules.
Two things to pay attention to is to make sure that the file
/etc/pcmcia/config
corresponds to the one that is NOT using kernel pcmcia (e.g. 3c575 has
the driver
3c575_cb in the pcmcia package but is built into 3c59x in the kernel),
and the
file /etc/sysconfig/pcmcia has PCMCIA on. This way everyhting is working
for me
and I'll wait until 2.4.x has solid support for pcmcia.
--
Prof. S. Umar
Dept. of Physics & Astronomy
Vanderbilt University
Nashville, TN 37235
Tel : (615) 322-2459
Fax : (615) 343-7263
[EMAIL PROTECTED]
http://compsci.cas.vanderbilt.edu/~umar/resu.htm
------------------------------
From: "Ross Burton" <[EMAIL PROTECTED]>
Subject: Broken RPM upgrade with Cooker
Date: Thu, 25 Jan 2001 20:21:18 GMT
Hi,
I was in the middle of upgrading my Mandrake 7.0 machine to the Mandrake
Cooker system when I upgraded rpm to version 4.0... and broke everything.
RPM doesn't know anything is installed and won't install anything... do
I need to install every package again so that RPM knows about it (from
glibc and ldconfig upwards) or can I get rpm to read the old RPM3 package
list?
Or do I re-install? :-(
Thanks for any help,
Ross Burton, sobbing quietly in the corner
------------------------------
From: "Tyberghein Jorrit" <[EMAIL PROTECTED]>
Subject: Re: Trying to install dual boot WinNT + Linux
Date: Thu, 25 Jan 2001 20:25:55 GMT
"> windows only recognise windows partition ID's, but you make this with
linux
> fdisk just fine too.
How? That's the problem that I have now. I have a FAT partition which I
created
using fdisk but now I want NT to recognize that partition as well. How can I
do that?
> for WHAT reason?
> mine is 128M and works like a charm.
Yes, this is no longer a problem.
Greetings,
------------------------------
From: "Tyberghein Jorrit" <[EMAIL PROTECTED]>
Subject: Re: Trying to install dual boot WinNT + Linux
Date: Thu, 25 Jan 2001 20:34:20 GMT
> > Check linuxnewbies.org for
> > information on dual booting and setup of the partitions.
>
> Very good advise
Ok, I just went to that site and I cannot find any information at
all about this issue. I even opened the Site Map and browed
it but I can't find it. Any more specific URL that I can visit?
Greetings and thanks,
------------------------------
From: rob <[EMAIL PROTECTED]>
Subject: Getting Win2000 On GRUB Menu
Date: Thu, 25 Jan 2001 20:44:59 GMT
Dear All:
Complete Linux newbie here. Due to circumstances beyond my control, I
am forced to use Win2000 for some tasks. So I would like to dual boot
Win2000 and Linux Mandrake 7.2. Starting fresh, I first installed
Win2000 on 2GB (the first partition, C:) of a 4GB drive on my laptop.
Then I installed LM7.2 on the second partition, also of 2GB. The LM
installer did all the default/recommended setup setting (e.g. Auto
Allocate /, /swap, and /home and install the Recommended apps., etc.).
However, when I boot up, and the GRUB comes up I do not see Win2000 as
an option (some might call this a "Good Thing" ;-)). How do I tell GRUB
to present Win2000 as an option?
Many thanks in advance, rob
Sent via Deja.com
http://www.deja.com/
------------------------------
From: [EMAIL PROTECTED]
Subject: "Dos" Extended ASCII in Linux???
Date: Thu, 25 Jan 2001 20:42:33 GMT
OK,
First off, I have read the man pages for ascii,
iso_8859_1 (section 7 on both). I've looked up
information on setlocale. And looked up
information on the setfont and consolechars
programs in Linux.
My background is, I am porting an old legacy
application from SCO/pSOS to Linux. It will only
be run in Linux. And it will only run in US
English. We do our language conversions
internally.
What I need is the 7-bit ASCII with the extended
ascii that is available in dos, etc. The main
thing I need is the borders and bars that are 179-
215 in the DOS extended ASCII. Right now when I
print chr(205) I get "GREEK CAPITAL LETTER NU".
I'd rather do this OS conversion with as little
changes to our proprietary code as possible.
Is there any way I can use the old extended ascii
in linux? If there is, do I need to do it with
setlocal or setfont. And what font do I need to
set it to.
Any help here would be great.
Thanks,
Adam Oldham
Sent via Deja.com
http://www.deja.com/
------------------------------
From: [EMAIL PROTECTED]
Subject: "Dos" Extended ASCII in Linux???
Date: Thu, 25 Jan 2001 20:42:36 GMT
OK,
First off, I have read the man pages for ascii,
iso_8859_1 (section 7 on both). I've looked up
information on setlocale. And looked up
information on the setfont and consolechars
programs in Linux.
My background is, I am porting an old legacy
application from SCO/pSOS to Linux. It will only
be run in Linux. And it will only run in US
English. We do our language conversions
internally.
What I need is the 7-bit ASCII with the extended
ascii that is available in dos, etc. The main
thing I need is the borders and bars that are 179-
215 in the DOS extended ASCII. Right now when I
print chr(205) I get "GREEK CAPITAL LETTER NU".
I'd rather do this OS conversion with as little
changes to our proprietary code as possible.
Is there any way I can use the old extended ascii
in linux? If there is, do I need to do it with
setlocal or setfont. And what font do I need to
set it to.
Any help here would be great.
Thanks,
Adam Oldham
Sent via Deja.com
http://www.deja.com/
------------------------------
From: [EMAIL PROTECTED] (Colin Watson)
Crossposted-To: comp.os.linux.misc
Subject: Re: Somebody create a How-To on upgrading to Kernel 2.4, please !
Date: 25 Jan 2001 20:58:00 GMT
Arctic Storm <[EMAIL PROTECTED]> wrote:
>John Hasler wrote:
>> Arctic Storm wrote:
>> > There are a few tips here and there on upgrading the kernel in general,
>> > but nothing specific for 2.4. I'm talking about the proverbial "Idiot's
>> > Guide to Linux Kernel 2.4 Upgrade."
>>
>> Why do idiots need to upgrade to 2.4 now?
>
>Ironically, although you may know slightly more about Linux than I do, I
>seem to have greater insight and better understanding of the spirit of
>Linux. Let me explain to you. The intension of Linux is to provide a
>reliable/dependable product for productivity and utility, for *everyone*; to
>help and serve the general public.
Anybody who's used, for example, John's ppp packages for Debian will see
just how much he's done to make a reliable product that the general
public can use: an awful lot. I doubt he needs lectures about it.
Think about John's point a little more. 2.4.0 may be, technically, a
"stable" kernel, but the general consensus among 2.2 users was
frequently that 2.2 didn't really become stable until 2.2.10 or so.
There are still plenty of bugs in 2.4.0 - it's only a couple of months
since it was eating filesystems on a fairly regular basis, after all.
People who can't figure out the simple instructions in
Documentation/Changes are unlikely to be able to track down and report
bugs in the kernel, and what Linux 2.4 really needs now is people who
can help to sort out the remaining bugs. The average user, honestly, is
better off sticking to 2.2.18 or the forthcoming 2.2.19 for now,
especially if their distribution's support for 2.4 is weak. If you want
a stable, working operating system, stable distributions are the way to
go; if you want an unstable operating system, well, nobody will make it
intentionally difficult for you to do so, but actively encouraging
everyone to do so actually ends up being counterproductive.
With regard to your lecture: sure, one of the purposes of Linux is to
provide everyone with a free, reliable, and powerful operating system.
Another is to provide a platform that's as comfortable as possible for
developers. Another is because it's interesting and fun. If you think
it's just about 'keeping the customers happy', then I think you're
glorifying the "spirit of Linux" somewhat; that's one of the nice
effects, certainly, but I don't think it's ever been the driving force.
All of these things are bidirectional, too. Rather than saying that
other people should provide everything, if you think there should be a
mini-HOWTO on upgrading, say, Red Hat 6.2 to be able to support kernel
2.4, then why not try it yourself and write down what you did? Sharing
of information goes both ways, and I'm sure people would thank you for
it.
>> Here is a complete set of easy-to-understand instructions:
>> Hire an expert to do it for you.
>
>I will represent the Linux community and tell you that *information* and
>*knowledge* regarding Linux is *free*, and will remain so with or without
>the upgrade. It's reasonable to pay & charge for time/service for setup of
>a computer system. However, not for the information & knowledge. Sharing
>of knowledeg is free and is encouraged in Linux.
Of course it's free (I'm guessing John was being at least a little
sarcastic, not wanting to put words into his mouth). In any case, notice
that the above says "do it for you", not "tell you how to do it".
Anyway, yes, sharing is good, but give and take is also encouraged. If
people always take, and sound aggrieved that no-one has written the
document they want on quite a large topic rather than asking for help on
something specific, then eventually people will indeed start suggesting
that you might have an easier time of it if you get an expert to give
you hands-on assistance - whether that involves money or not.
Anyway, enough talk about the spirit of Linux. I'm off down the pub to
sample some spirit of Ireland.
Cheers,
--
Colin Watson [[EMAIL PROTECTED]]
"There is perhaps in every thing of any consequence, secret history,
which it would be amusing to know, could we have it authentically
communicated." - James Boswell
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: remote printing problem
Date: Thu, 25 Jan 2001 20:54:52 GMT
In article <[EMAIL PROTECTED]>,
Anthony Hung <[EMAIL PROTECTED]> wrote:
> Hi all, I can't seem to get remote printing to work.
>
> I do the following, I setup the printcap file with remote access..
>
> ##PRINTTOOL3## REMOTE
> lp:\
> :sd=/var/spool/lpd/lp:\
> :mx#0:\
> :sh:\
> :rm=yosemite.home.com:\
> :rp=lp:\
> :lpd_bounce=true:
> .
>
> The spool directories all seem to be there......
>
> I setup the /etc/hosts.lpd file to allow the remote machine access but
> when i print I get the following message:
>
> Jan 24 22:36:46 lapdog (Worker - Remote)[1054]: lp: Remote_job: fstatb
> failed - Bad file descriptor
> Jan 24 22:36:46 lapdog (Worker - Remote)[1054]: lp: Remote_job:
close(4)
> failed - Bad file descriptor
> Jan 24 22:36:56 lapdog (Worker - Remote)[1055]: lp: Remote_job: fstatb
> failed - Bad file descriptor
> Jan 24 22:36:56 lapdog (Worker - Remote)[1055]: lp: Remote_job:
close(5)
> failed - Bad file descriptor
> Jan 24 22:37:16 lapdog (Worker - Remote)[1058]: lp: Remote_job: fstatb
> failed - Bad file descriptor
> Jan 24 22:37:16 lapdog (Worker - Remote)[1058]: lp: Remote_job:
close(5)
> failed - Bad file descriptor
> Jan 24
>
> I am using RH7, thanks in advance
>
> --
> Anthony
>
>
--
Hi Anthony, Try using the RH7 printtool by typeing printtool at the CLI
and then using the GUI to setup.
Support provided by Linuxgruven, Inc
www.linuxgruven.com
314-727-0918
Sent via Deja.com
http://www.deja.com/
------------------------------
From: [EMAIL PROTECTED]
Subject: Can you use "DOS" Extended ASCII in Linux?
Date: Thu, 25 Jan 2001 20:52:27 GMT
OK,
First off, I have read the man pages for ascii, iso_8859_1 (section 7
on both). I've looked up information on setlocale. And looked up
information on the setfont and consolechars programs in Linux.
My background is, I am porting an old legacy application from SCO/pSOS
to Linux. It will only be run in Linux. And it will only run in US
English. We do our language conversions internally.
What I need is the 7-bit ASCII with the extended ascii that is
available in dos, etc. The main thing I need is the borders and bars
that are 179-215 in the DOS extended ASCII. Right now when I print chr
(205) I get "GREEK CAPITAL LETTER NU". I'd rather do this OS
conversion with as little changes to our proprietary code as possible.
Is there any way I can use the old extended ascii in linux? If there
is, do I need to do it with setlocal or setfont. And what font do I
need to set it to.
Any help here would be great.
Thanks,
Adam Oldham
Sent via Deja.com
http://www.deja.com/
------------------------------
From: [EMAIL PROTECTED]
Subject: 2.2.18 kernel fails to load
Date: Thu, 25 Jan 2001 20:54:33 GMT
Hi All,
I just recompiled and installed the 2.2.18 kernel. Everything went
smoothly, but after I restart my system, I get the LILO: prompt as
expected and then request the new kernel. I get the characterstic
message on the display
Linux Loading.........
the dots only continue halfway across my display, then the machine
hangs.
Any ideas? I have RAM disk support enable.
Thanks in advance!
Sent via Deja.com
http://www.deja.com/
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.setup.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Setup Digest
******************************
