hj?lp!!

hj?lp!!

Post by Lamer′ » Mon, 25 Jan 1999 04:00:00



Jag har ett problem som jag inte har n?gon vuxen att prata med om.

?r det ?verhuvudtaget m?jligt att f? ig?ng X Window (XFree86),
med mitt sugande ATI Rage Pro Turbo AGP 4Mb,
som Siemens svetsat fast p? mitt moderkort?
RedHat 5.0 kanske ?r av intresse?
K?r jag SuperProbe f?r jag veta att det ?r ATI unknown chipset,
0 kbytes memory och n?nting typ:signatur data : 333f003c(please report)
K?r jag startX f?r jag d?remot veta att det ?r en ATI Mach 64 video adapter
detekted,IBM RGB 514 or similar RAMDAC och programmeble clock generator
detekted och att det ?r 4Mb videoram.
Men inte satan startar det.
Vad ?r fel, jag orkar inte vara vaken m?nga dygn till?

/Lamern

 
 
 

hj?lp!!

Post by Jonas Norlin » Tue, 26 Jan 1999 04:00:00


Quote:> Vad ?r fel, jag orkar inte vara vaken m?nga dygn till?

Det som ?r fel ?r att du skriver p? svenska. Det h?r ?r en
ENGELSKSRP?KIG nyhetsgrupp.
(Please excuse him)
//Jonas Norling

 
 
 

hj?lp!!

Post by cmol.. » Sat, 30 Jan 1999 04:00:00




Quote:>Jag har ett problem som jag inte har n?gon vuxen att prata med om.

>?r det ?verhuvudtaget m?jligt att f? ig?ng X Window (XFree86),
>med mitt sugande ATI Rage Pro Turbo AGP 4Mb,
>som Siemens svetsat fast p? mitt moderkort?
>RedHat 5.0 kanske ?r av intresse?
>K?r jag SuperProbe f?r jag veta att det ?r ATI unknown chipset,
>0 kbytes memory och n?nting typ:signatur data : 333f003c(please report)
>K?r jag startX f?r jag d?remot veta att det ?r en ATI Mach 64 video adapter
>detekted,IBM RGB 514 or similar RAMDAC och programmeble clock generator
>detekted och att det ?r 4Mb videoram.
>Men inte satan startar det.
>Vad ?r fel, jag orkar inte vara vaken m?nga dygn till?

Heisann ...

Du trenger en nyere versjon av XFree86 ... Versjon 3.3.3 er siste.
Men, hvis du har Redhat 5.0 vil jeg anbefale ? finne tak i en nyere
versjon av Redhat - 5.2 er siste.

Xfree kan d/l fra ftp.xfree86.org ...

mvh
Cato M. Olsen

 
 
 

1. lp(1) suid to lp-Secure files fail.

We run an environment where some of our files are 'secure', and don't
have world read access. Such files can't be printed with lp, but can be
printed with lpr. For complex reasons, we can't use lpr on these systems.

hermes:/users/johnk/bar> ll foo
-rw-rw----   1 johnk    ee         36454 Feb 17 16:51 foo
hermes:/n/hermes/johnk/bar> lp -dhp4_text foo
request id is hp4_text-2078 (1 file)

lp is suid lp, and thus can't read the file, which hangs out in the queue
forever.

hermes:/n/hermes/johnk/bar> which lp
/usr/bin/lp
hermes:/n/hermes/johnk/bar> ll /usr/bin/lp
-rwsr-xr-x   1 lp       sys        81968 Jul 31  1993 /usr/bin/lp*
hermes:/n/hermes/johnk/bar>

A workaround is to pipe all print jobs into lp, but this is a pain for
users to remember, and doesn't work well with other programs that expect
to be able to give file arguments to lp.

I suppose I could make lp suid root, but this opens the spectre of all
sorts of security problems (up to, and possibly including allowing
anyone to print any file on the system)

Any ideas on how to get lp working in such an environment?

                -John Kalucki

2. A7V promise IDE controler WITH UDMA MODE

3. #$%@! lp:Solaris remote lp failing

4. inetd functions very slow to authenticate

5. lp: unable to get major 6 - Initialization of lp failed

6. flytraps

7. lp-init: no lp devices found

8. Printer stopped working with eth1 installed

9. Modifying lp & lp sched

10. HPLJ4l lp init: no lp devices found

11. Starting lpd: Warning - lp: cannot stat lp device '/dev/lp0'

12. LP doesn't work after lp jumbo patch

13. jumbo lp patch breaks lp ???