Re: LiveUSB OpenBSD and LiveCD-OpenBSD site updated
> Andres Perera > if you cant install through network because you only got one machine So you can't install OpenBSD but you CAN download the pre-made OpenBSD images? >and feel that guerrilla overwriting your mbr after installing the locks within >another os in > order to do a hdd boot is too risky, you're left with this I've used OpenBSD in a multiboot and it was working perfectly fine, no guerilla there. > the page you linked does not provide that It does not, since the page is for a specific purpose. If you take your time and go back to the root of FAQ you may find what you are looking for. But I guess is nicer for you to spread crazy thing on the list.
III Ateneo 2012 - QUE TIENEN LOS POLITICOS EN LA CABEZA
Escuela Sistimica Argentina Institucisn dedicada a la formacisn, asistencia e investigacisn psicolsgica. Hoy nos acercamos a Uds. para invitarlos a la realizacisn del III Ateneo 2012 ATENEO CLINICO QUE TIENEN LOS POLITICOS EN LA CABEZA La maxima dirma asm: Detras de todo cuadro polmtico, hay un cuadro psiquiatrico. ?Qui diagnsstico le corresponde a Elisa Carris? ?Es verdad que escucha A Dos Voces? ?Es curable el masoquismo polmtico de Scioli? ?Y la cleptomanma filial de Ricardo Alfonsmn? Reutemann se queds sin serotonina en la zltima vuelta. ?Eso se medica? Qui tienen los polmticos en la cabeza es un Manual de Psicopatologma, claro que sm, pero en clave de humor. En cada capmtulo, los y las grandes protagonistas de la actualidad son estudiados a fondo por Diego Sehinkman, periodista, psicslogo y humorista/guionista de radio y TV, autor de Terapia, columna de humor polmtico en el suplemento Enfoques del diario La Nacisn. Aqum se despliegan, con conocimiento de causa, los traumas, complejos y taras psicolsgicas de nuestros dirigentes. Para que nadie diga despuis que no sabma a quien votaba. Dma: Viernes 13 de abril de 2012, 19 horas Coordina: Diego Sehinkman (*) Presentador: Dr. Marcelo R. Ceberio (*) Diego Sehinkman es periodista, psicslogo y guionista. Todos los domingos escribe la columna Terapia en el Suplemento Enfoques y acaba de sacar el libro ?Qui tienen los polmticos en la cabeza? (Traumas, complejos y taras psicolsgicas de nuestros dirigentes) por Ediciones B- Vergara. ENTRADA LIBRE Y GRATUITA (Sin inscripcisn previa) Prsximos ateneos: Fecha Ateneo Coordinador Presentador 20/04: Ateneo clmnico El diagnsstico de lo posible en la terapia de pareja. Lic. Fernando Rubano Lic. Eliana Durand 27/04: Las patas de la mentira Lic. Miguel Rodriguez Arias Lic. Fernando Rubano 04/05: La vejez no pensada. Dr. Enrique Rozitchner Dr. Marcelo R. Ceberio 11/05: Ateneo clmnico La dinamica de la psicopatologma durante el tratamiento terapiutico. Lic. Silvia Mitjans Dr. Horacio Serebrinsky 01/06: El poder del ahora o el arte de vivir mejor (Refrescando a Eckhart Tolle). Lic. Juan Verni Lic. Graciela Piatti 24/08: Y si Hamer tendria razon? Psicobiologia, la nueva medicina. Lic. Juan Verni Lic. Claudio Fontana ESCUELA SISTIMICA ARGENTINA Fray J. S. M. Oro 1843 (C1414DBC) Cap. Fed. Tel/ Fax: 4774-2875/6112 - 4899-1053 i...@escuelasistemica.com.ar / www.escuelasistemica.com.ar
Re: Recent DELL hardware support
On 2012/04/05 22:02, Kostas Zorbadelos wrote: > Yes, clear. I think I will add R610 to the options. The only remaining > question is PERC H200 support. It is not mentioned in mfi(4), so should I > consider it unsupported? this is an H200: $ ssh mh3-pl7 dmesg|grep -e Dell -e mpii bios0: vendor Dell Inc. version "1.5.2" date 10/15/2010 bios0: Dell Inc. PowerEdge R310 mpii0 at pci2 dev 0 function 0 "Symbios Logic SAS2008" rev 0x03: msi scsibus0 at mpii0: 42 targets sd0 at scsibus0 targ 1 lun 0: SCSI4 0/direct fixed naa.600508e013201cfbcb2f1f04 mfi should be faster, but this works well enough.
Re: Recent DELL hardware support
On Thu, Apr 5, 2012 at 21:02, Kostas Zorbadelos wrote: > The only remaining question is PERC H200 support. mpii(4) should cover the Dell PERC H200.
Re: Recent DELL hardware support
Stuart Henderson writes: Thsnks for the replies. > I haven't come across any problems with bnx(4). Did you look at > 2U boxes at all? > I am interested mainly in 1U boxes. Reliability is the most crucial factor because the machines will be deployed in remote places, geographically distributed. I was thinking SSD disks to avoid mechanical parts but DELL prices for them are obsurd I think. > > So your choice is between hardware which should already work in > OpenBSD and hardware which (at least the nics) is known not to > work yet but might work sometime in the future. Nobody here can > make that decision for you :) > Yes, clear. I think I will add R610 to the options. The only remaining question is PERC H200 support. It is not mentioned in mfi(4), so should I consider it unsupported? In any case, if I happen to have access to needed hardware (e.g the company buys some 12G Dell servers) I can arrange for remote access to a dedicated machine for a period of time to interested developers. Thanks, Kostas -- Kostas Zorbadelos twitter:@kzorbadelos http://gr.linkedin.com/in/kzorba () www.asciiribbon.org - against HTML e-mail & proprietary attachments /\
Re: Manual IPsec setup with ipsec.conf
On 04/04/2012 08:23 PM, Girish Venkatachalam wrote: # ipsecctl -sa -v FLOWS: flow esp in from 10.1.23.0/24 to 192.168.1.0/24 peer 173.167.82.52 type require flow esp out from 192.168.1.0/24 to 10.1.23.0/24 peer 173.167.82.52 type require flow esp in from 173.167.82.52 to 59.99.242.167 peer 173.167.82.52 type require flow esp out from 59.99.242.167 to 173.167.82.52 peer 173.167.82.52 type require SAD: esp tunnel from 173.167.82.52 to 59.99.242.167 spi 0xbeefdead auth hmac-sha1 enc aes sa: spi 0xbeefdead auth hmac-sha1 enc aes state mature replay 0 flags 4 lifetime_cur: alloc 0 bytes 0 add 1333585275 first 0 address_src: 173.167.82.52 address_dst: 59.99.242.167 esp tunnel from 59.99.242.167 to 173.167.82.52 spi 0xdeadbeef auth hmac-sha1 enc aes sa: spi 0xdeadbeef auth hmac-sha1 enc aes state mature replay 0 flags 4 lifetime_cur: alloc 0 bytes 196 add 1333585275 first 1333585277 address_src: 59.99.242.167 address_dst: 173.167.82.52 lifetime_lastuse: alloc 0 bytes 0 add 0 first 1333585277 I cannot ping between 192.168.1.50 and 10.1.23.2 Possibly just a routing issue (since the tunnels seem to be established). See this thread: http://comments.gmane.org/gmane.os.openbsd.misc/192986 It's kind of counter intuitive to have to specify a separate route for a tunnel, since it is adding no real information for the system to use, but it looks like it's a peculiarity of the current implementation. - Aner
Re: fork failed: resource temporarily unavailable
On Thu, Apr 05, 2012 at 03:11:20PM +0200, David Coppa wrote: > On Thu, Apr 5, 2012 at 3:01 PM, Mattieu Baptiste wrote: > > Hi all, > > > > Since the switch to rthreads, and the new snapshot packages, I see a > > lot of these errors after some time using my desktop machine: > > fork failed: resource temporarily unavailable > > > > Then, I cannot start any process, and the machine starts to become > > unusable, till the next reboot. I'm using a lot firefox, thunderbird > > and XFCE. > > > > Do you see these errors? How could I track this? > > As a workaround, modify the staff class (which your user should be > part of) with these values: > > openfiles-cur=1024 > openfiles-max=2048 > maxproc-cur=512 > maxproc-max=1024 > > And increase maxproc to 1024 in your .xsession (ulimit -Sp 1024). > > Cheers, > David Hmm, didn't a diff go in that made the limits per-process again? -Otto
Re: fork failed: resource temporarily unavailable
On Thu, Apr 5, 2012 at 3:01 PM, Mattieu Baptiste wrote: > Hi all, > > Since the switch to rthreads, and the new snapshot packages, I see a > lot of these errors after some time using my desktop machine: > fork failed: resource temporarily unavailable > > Then, I cannot start any process, and the machine starts to become > unusable, till the next reboot. I'm using a lot firefox, thunderbird > and XFCE. > > Do you see these errors? How could I track this? As a workaround, modify the staff class (which your user should be part of) with these values: openfiles-cur=1024 openfiles-max=2048 maxproc-cur=512 maxproc-max=1024 And increase maxproc to 1024 in your .xsession (ulimit -Sp 1024). Cheers, David
fork failed: resource temporarily unavailable
Hi all, Since the switch to rthreads, and the new snapshot packages, I see a lot of these errors after some time using my desktop machine: fork failed: resource temporarily unavailable Then, I cannot start any process, and the machine starts to become unusable, till the next reboot. I'm using a lot firefox, thunderbird and XFCE. Do you see these errors? How could I track this? dmesg follows: OpenBSD 5.1-current (GENERIC.MP) #1: Wed Apr 4 11:50:54 CEST 2012 r...@grimbergen.boulogne.netasq.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 11 real mem = 2110779392 (2012MB) avail mem = 2032308224 (1938MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xf0450 (82 entries) bios0: vendor Dell Inc. version "A01" date 09/23/2008 bios0: Dell Inc. OptiPlex 960 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC BOOT ASF! MCFG HPET DMAR SSDT SSDT SSDT acpi0: wakeup devices VBTN(S4) PCI0(S5) PCI4(S5) PCI2(S5) PCI3(S5) PCI1(S5) PCI5(S5) PCI6(S5) MOU_(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz, 2992.90 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF cpu0: 6MB 64b/line 16-way L2 cache cpu0: apic clock running at 332MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz, 2992.48 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF cpu1: 6MB 64b/line 16-way L2 cache ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 4 (PCI4) acpiprt1 at acpi0: bus 2 (PCI2) acpiprt2 at acpi0: bus 3 (PCI3) acpiprt3 at acpi0: bus 1 (PCI1) acpiprt4 at acpi0: bus -1 (PCI5) acpiprt5 at acpi0: bus -1 (PCI6) acpiprt6 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: C1, PSS acpicpu1 at acpi0: C1, PSS acpibtn0 at acpi0: VBTN cpu0: Enhanced SpeedStep 2992 MHz: speeds: 3000, 2667, 2333, 2000 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Q45 Host" rev 0x03 ppb0 at pci0 dev 1 function 0 "Intel Q45 PCIE" rev 0x03: msi pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 "ATI Radeon HD 2400 XT" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) radeondrm0 at vga1: apic 8 int 16 drm0 at radeondrm0 "Intel Q45 HECI" rev 0x03 at pci0 dev 3 function 0 not configured pciide0 at pci0 dev 3 function 2 "Intel Q45 PT IDER" rev 0x03: DMA (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using apic 8 int 18 for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) "Intel Q45 KT" rev 0x03 at pci0 dev 3 function 3 not configured em0 at pci0 dev 25 function 0 "Intel ICH10 D BM LM" rev 0x02: msi, address 00:22:19:19:71:1e uhci0 at pci0 dev 26 function 0 "Intel 82801JD USB" rev 0x02: apic 8 int 16 uhci1 at pci0 dev 26 function 1 "Intel 82801JD USB" rev 0x02: apic 8 int 17 uhci2 at pci0 dev 26 function 2 "Intel 82801JD USB" rev 0x02: apic 8 int 22 ehci0 at pci0 dev 26 function 7 "Intel 82801JD USB" rev 0x02: apic 8 int 22 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 "Intel 82801JD HD Audio" rev 0x02: msi azalia0: codecs: Analog Devices AD1984A audio0 at azalia0 ppb1 at pci0 dev 28 function 0 "Intel 82801JD PCIE" rev 0x02: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 1 "Intel 82801JD PCIE" rev 0x02: msi pci3 at ppb2 bus 3 uhci3 at pci0 dev 29 function 0 "Intel 82801JD USB" rev 0x02: apic 8 int 23 uhci4 at pci0 dev 29 function 1 "Intel 82801JD USB" rev 0x02: apic 8 int 17 uhci5 at pci0 dev 29 function 2 "Intel 82801JD USB" rev 0x02: apic 8 int 18 ehci1 at pci0 dev 29 function 7 "Intel 82801JD USB" rev 0x02: apic 8 int 23 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb3 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xa2 pci4 at ppb3 bus 4 pcib0 at pci0 dev 31 function 0 "Intel 82801JDO LPC" rev 0x02 ahci0 at pci0 dev 31 function 2 "Intel 82801JD AHCI" rev 0x02: msi, AHCI 1.2 ahci0: PHY offline on port 2 ahci0: PHY offline on port 3 scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed naa.50014ee1ad13e28d sd0: 152587MB, 512 bytes/sector, 31250 sectors cd0 at scsibus0 targ 1 lun 0: ATAPI 5/cdrom
Re: Manual IPsec setup with ipsec.conf
- Original Message - > From: "Girish Venkatachalam" > To: "OpenBSD general usage list" > Sent: Wednesday, April 4, 2012 8:23:27 PM > Subject: Manual IPsec setup with ipsec.conf > > Dear all, > > Such a silly thing is not documented anywhere, no vpn(8) man page and > not on the Internet. > > I am forced to send this mail though it is embarrassing having worked > on the > internals of manual IPsec keying back in 2004. But well here goes. > > on peer A: > > remoteip="173.167.82.52" > remotenet="10.1.23.0/24" > > flow esp from 59.99.242.167 to $remoteip > flow esp from 192.168.1.0/24 to $remotenet peer $remoteip > esp from 59.99.242.167 to $remoteip spi 0xdeadbeef:0xbeefdead auth > hmac-sha1 \ >authkey >0xeda8f06463b2d0fed008ccc474216dba8c463a7c:0x91c763de940ce1745215c84b7 > 535269acaef516d >\ >enckey >0xb341aa065c3850edd6a61e150d6a5fd3:0xf7795f6bdd697a43a4d28dcf1b79062d > > on peer B: > > localnet="192.168.0.0/16" > remoteip="59.99.242.167" > > flow esp from 173.167.82.52 to 59.99.242.167 > flow esp from 10.1.23.0/24 to 192.168.1.0/24 peer $remoteip > esp from 173.167.82.52 to 59.99.242.167 spi 0xbeefdead:0xdeadbeef > auth > hmac-sha1 \ >authkey >0x91c763de940ce1745215c84b7535269acaef516d:0xeda8f06463b2d0fed008ccc47 > 4216dba8c463a7c >\ >enckey >0xf7795f6bdd697a43a4d28dcf1b79062d:0xb341aa065c3850edd6a61e150d6a5fd3 > > > It is a test. I don't care about the keys and IP addresses. > > pf(4) is disabled both sides and here is the output of > > #ipsecctl -sa on peer B > > # ipsecctl -sa -v > FLOWS: > flow esp in from 192.168.1.0/24 to 10.1.23.0/24 peer 59.99.242.167 > type > require > flow esp out from 10.1.23.0/24 to 192.168.1.0/24 peer 59.99.242.167 > type > require > flow esp in from 59.99.242.167 to 173.167.82.52 peer 59.99.242.167 > type > require > flow esp out from 173.167.82.52 to 59.99.242.167 peer 59.99.242.167 > type > require > > SAD: > esp tunnel from 173.167.82.52 to 59.99.242.167 spi 0xbeefdead auth > hmac-sha1 enc aes > sa: spi 0xbeefdead auth hmac-sha1 enc aes > state mature replay 0 flags 4 > lifetime_cur: alloc 0 bytes 0 add 1333585323 first 0 > address_src: 173.167.82.52 > address_dst: 59.99.242.167 > esp tunnel from 59.99.242.167 to 173.167.82.52 spi 0xdeadbeef auth > hmac-sha1 enc aes > sa: spi 0xdeadbeef auth hmac-sha1 enc aes > state mature replay 0 flags 4 > lifetime_cur: alloc 0 bytes 0 add 1333585323 first 0 > address_src: 59.99.242.167 > address_dst: 173.167.82.52 > > And peer A: > > # ipsecctl -sa -v > FLOWS: > flow esp in from 10.1.23.0/24 to 192.168.1.0/24 peer 173.167.82.52 > type > require > flow esp out from 192.168.1.0/24 to 10.1.23.0/24 peer 173.167.82.52 > type > require > flow esp in from 173.167.82.52 to 59.99.242.167 peer 173.167.82.52 > type > require > flow esp out from 59.99.242.167 to 173.167.82.52 peer 173.167.82.52 > type > require > > SAD: > esp tunnel from 173.167.82.52 to 59.99.242.167 spi 0xbeefdead auth > hmac-sha1 enc aes > sa: spi 0xbeefdead auth hmac-sha1 enc aes > state mature replay 0 flags 4 > lifetime_cur: alloc 0 bytes 0 add 1333585275 first 0 > address_src: 173.167.82.52 > address_dst: 59.99.242.167 > esp tunnel from 59.99.242.167 to 173.167.82.52 spi 0xdeadbeef auth > hmac-sha1 enc aes > sa: spi 0xdeadbeef auth hmac-sha1 enc aes > state mature replay 0 flags 4 > lifetime_cur: alloc 0 bytes 196 add 1333585275 first > 1333585277 > address_src: 59.99.242.167 > address_dst: 173.167.82.52 > lifetime_lastuse: alloc 0 bytes 0 add 0 first 1333585277 > > I cannot ping between 192.168.1.50 and 10.1.23.2 > > What is going on? > > -Girish > > -- > G3 Tech > Networking appliance company > web: http://g3tech.in mail: gir...@g3tech.in two very basic questions, both of which have bitten me at some point: 1) is ip forwarding enabled on both boxes? 2) do you have the appropriate routes setup on both sides?
Re: Thank you OpenBSD
Alan Cheng wrote: > simple & clean, is one of the reasons I like OB ~ > FUNNY ABBREVIATION ALERT ! Where I live OB is a brand of tampons, so you just made yourself sound like one of their slogans ! LOL
Re: Manual IPsec setup with ipsec.conf
On Thu, Apr 05, 2012 at 03:07:17PM +0530, Girish Venkatachalam wrote: > On Thu, Apr 5, 2012 at 11:37 AM, Jason McIntyre wrote: > > On Thu, Apr 05, 2012 at 05:53:27AM +0530, Girish Venkatachalam wrote: > >> Dear all, > >> > >> Such a silly thing is not documented anywhere, no vpn(8) man page and > >> not on the Internet. > >> > > > >Subject: Manual IPsec setup with ipsec.conf > > > > have you looked at the manual page for ipsec.conf? > > > > jmc > > > > Sorry I did not mean to antagonize. > > I did read the section. But an example would be a great addition. Interesting, hasn't been somewhere posted that asking person is guru and reviewd OpenBSD IPSEC's code? :) jirib
Re: Manual IPsec setup with ipsec.conf
On Thu, Apr 05, 2012 at 03:07:17PM +0530, Girish Venkatachalam wrote: > On Thu, Apr 5, 2012 at 11:37 AM, Jason McIntyre wrote: > > On Thu, Apr 05, 2012 at 05:53:27AM +0530, Girish Venkatachalam wrote: > >> Dear all, > >> > >> Such a silly thing is not documented anywhere, no vpn(8) man page and > >> not on the Internet. > >> > > > >Subject: Manual IPsec setup with ipsec.conf > > > > have you looked at the manual page for ipsec.conf? > > > > jmc > > > > Sorry I did not mean to antagonize. > > I did read the section. But an example would be a great addition. > well, there are examples of both setting up flows manually and setting up SAs manually. it maybe doesn;t cover what you are trying to do though. jmc
Re: Manual IPsec setup with ipsec.conf
On Thu, Apr 5, 2012 at 11:37 AM, Jason McIntyre wrote: > On Thu, Apr 05, 2012 at 05:53:27AM +0530, Girish Venkatachalam wrote: >> Dear all, >> >> Such a silly thing is not documented anywhere, no vpn(8) man page and >> not on the Internet. >> > >Subject: Manual IPsec setup with ipsec.conf > > have you looked at the manual page for ipsec.conf? > > jmc > Sorry I did not mean to antagonize. I did read the section. But an example would be a great addition. -Girish -- G3 Tech Networking appliance company web: http://g3tech.in mail: gir...@g3tech.in
Re: Question on LPD and OpenBSD printing
On Thu, Apr 5, 2012 at 3:39 AM, Jan Stary wrote: > On Apr 05 05:19:18, Girish Venkatachalam wrote: >> On Thu, Apr 5, 2012 at 4:46 AM, Jan Stary wrote: >> >> >> >> Nothing. >> > >> > Then something else is broken. >> > >> > Run lpd with -l to make sure that the print job >> > at least made it to lpd as a request. >> > >> >> If the queue clears that is what it means right? It does make it. >> >> I will also take a stab at the -l switch. > > What I mean is that with lpd -l, there will be an entry in the > log saying there was a rint job requested; which you say is > not there now, so we are not sure that pd even knows about your > printjob. > >> > You do actually have the foomatic* packages installed, right? >> > You did not just blindly copy the ':if=/usr/local/bin/foomatic-rip:' >> > line, right? >> > >> >> But of course yes. If you install hpijs it is installed as a dependency. >> >> -Girish >> >> -- >> G3 Tech >> Networking appliance company >> web: http://g3tech.in B mail: gir...@g3tech.in > It's also useful if you use: debug: 1 in your /etc/foomatic/filter.conf, next: $ lpr file.ps; and then check: # cat /tmp/foomatic*
hi~
hi misc we start to sell iphone,ipad,ps3.. the price is good, welcome to our site misc s i t e : ydlmn . com 16:35:51
Re: xfce4 freeze on Loongson netbook
With help from many on and off-list, I finally worked around the freeze issue, by doing the following: 1. went back to 5.0 release 2. in .xinitrc, use "dbus-lunch startxfce4" instead of just "startxfce4. Just in case anyone is still interested in this. Thanks again. - Alan
Re: Thank you OpenBSD
simple & clean, is one of the reasons I like OB ~ On Tue, Apr 3, 2012 at 12:32 AM, Eric S Pulley wrote: > I'd just like to take a moment to thank everyone involved in releases of > OpenBSD for having a nice clear and concise release schedule and version > system. It's fantastic. > > I use FreeBSD on my file-server to take advantage of ZFS and all their > convoluted versions/branches are just... a pain. > > So thank you all for keeping it simple, clean and efficient. > > -- > ESP
Re: Question on LPD and OpenBSD printing
On Apr 05 05:19:18, Girish Venkatachalam wrote: > On Thu, Apr 5, 2012 at 4:46 AM, Jan Stary wrote: > >> > >> Nothing. > > > > Then something else is broken. > > > > Run lpd with -l to make sure that the print job > > at least made it to lpd as a request. > > > > If the queue clears that is what it means right? It does make it. > > I will also take a stab at the -l switch. What I mean is that with lpd -l, there will be an entry in the log saying there was a rint job requested; which you say is not there now, so we are not sure that pd even knows about your printjob. > > You do actually have the foomatic* packages installed, right? > > You did not just blindly copy the ':if=/usr/local/bin/foomatic-rip:' > > line, right? > > > > But of course yes. If you install hpijs it is installed as a dependency. > > -Girish > > -- > G3 Tech > Networking appliance company > web: http://g3tech.in mail: gir...@g3tech.in
