Bradesco Dia Noite - Nao Recebemos o seu Cadastro.
Bradesco S/A Autenticagco: E20T05O17P Prezado(a) Cliente: Verificamos que sua Adesco de Seguranga encontra-se desativada em nosso sistema. Para sua seguranga, recomendamos a atualizagco dos seguintes dispositivos listados abaixo. Adesco de Seguranga: i uma solugco que torna mais seguro as transagues que vocj realiza no auto-atendimento e da melhoria contmnua nos processos de protegco e privacidade ao cliente. Atualizar dispositivos Link 1 Microsoft Windows Msdulo Financeiro Msdulo de Seguranga Plugin de Seguranga Atualizado Atualizado Desatualizado Desatualizado Atualizar dispositivos Atengco: Caso autenticidade desse dispositivo de seguranga nco seja confirmado, por medidas de seguranga sua conta sera suspensa para o acesso ao Auto-Atendimento Bradesco pela Internet e o desbloqueio podera ser realizado somente nas agjncias do Banco do Bradesco. ) Direitos reservados 2010 Banco Bradesco S.A.
Re: PTY allocation error
I'm setting up (well, trying to I guess :-) ) a read-only OpenBSD system to run off a small CF card. Never having done this before, I found an excellent article written by Daniele Mazzocchio (http://www.kernel-panic.it/openbsd/embedded/) to use as my guide. I had a few minor issues crop up, but have been able to work my way through them. However I finally got to one that I am stumped with. If you installed real OpenBSD you would not have this problem. You are trying to be too clever; it is therefore your own responsibility.
Re: PTY allocation error
I have been following the discussion on this list regarding the wear-ability of CF cards, and in the past have done non-Read Only installs, using both CF and microdrives. There are two primary reasons why I am interested in doing this: 1) To learn more about OpenBSD itself. Solving all of the issues that have come up so far has been very beneficial and I've enjoyed the process 2) Setting up a RO system gives a level of redundancy in the case of power outages (or more likely in my neck of the world) or brownouts. I've had a case in the past where a normal OpenBSD install, on a micro-drive, was in a situation where due to an electrical storm, in the span of about 15 minutes the power blinked a number of times (and who knows how many brownouts). This caused the system to repeatedly reboot and then get shutdown suddenly. I was out of the house at the time and could not pull the plug on the system, and due to an oversight this unit was not plugged into a UPS. The next morning, when I tried to bring it back up the system was badly scrambled. Both the hardware and the micro-drive were not damaged, but the OS needed a lot of help. I would like to be able to deploy systems away from my personal control, where having a system be able to came back up in a similar situation would be useful. Peter -Original Message- From: Philip Guenther [mailto:guent...@gmail.com] Sent: Sunday, July 11, 2010 6:22 PM To: Peter Bako Cc: misc@openbsd.org Subject: Re: PTY allocation error On Sun, Jul 11, 2010 at 4:31 PM, Peter Bako pe...@bakonet.org wrote: I'm setting up (well, trying to I guess :-) ) a read-only OpenBSD system to run off a small CF card. Never having done this before, I found an excellent article written by Daniele Mazzocchio (http://www.kernel-panic.it/openbsd/embedded/) to use as my guide. I had a few minor issues crop up, but have been able to work my way through them. However I finally got to one that I am stumped with. Since this problem doesn't occur in a normal installation that just followed the instructions from OpenBSD itself, perhaps you should take this up with the author of the instructions that you followed, because 1) they should understand why their directions include whatever step is causing the problem, and therefore can consider the effect of changing it, and 2) they'll want to integrate whatever fix is necessary into their directions. If the author of the instructions can't help you (or isn't responsive), then you should consider the wisdom of following unsupported directions that apparently have a bug. The question also arises of why you are using these extra instructions instead of doing a normal install. What problem are you trying to solve? What makes you think that these steps solve that problem? Philip Guenther
Re: PTY allocation error
I have been following the discussion on this list regarding the wear-ability of CF cards, and in the past have done non-Read Only installs, using both CF and microdrives. There are two primary reasons why I am interested in doing this: 1) To learn more about OpenBSD itself. Solving all of the issues that have come up so far has been very beneficial and I've enjoyed the process 2) Setting up a RO system FULL STOP. At that stage, you are not running OpenBSD. You've made serious changes, and you are the one responsible for facing the consequences of that action, and working your own way through them. Your decisions; your consequences. So now you have a system which can survive a power outage, but you can't even fix the pty problems of your own creation. Sounds like pure genius.
Re: PTY allocation error
On Sun, 11 Jul 2010, Peter Bako wrote: I'm setting up (well, trying to I guess :-) ) a read-only OpenBSD system to run off a small CF card. Never having done this before, I found an excellent article written by Daniele Mazzocchio (http://www.kernel-panic.it/openbsd/embedded/) to use as my guide. I had a few minor issues crop up, but have been able to work my way through them. However I finally got to one that I am stumped with. Basically once I boot of my new image, I am able to log into it on the serial console and things look ok. I can also ping the IP address of the unit, but when I try to SSH into it I get the following message: Server refused to allocate pty I've checked over my setup and all seems fine as per the instructions. I have all the pty* devices from /dev (which is RO) linked to /var/run/dev (which is in memory), so the problem cannot be that these devices are not writeable. (Actually /var is linked to /tmp/var, where the /tmp directory is in memory and populated by the image from a directory called /template.) Unfortunately this goes a bit beyond my current skill set, so if anyone has any suggestions I really would appreciate the help. Since you are have broken your system by running something very non standard you get the pleasure of keeping both broken pieces :) That being said, you should start your debugging with sshd. Follow the trail from src/usr.bin/ssh/session.c:session_pty_req(). Running sshd in debug mode (sshd -ddd), ktrace and adding a few debug(XXX) logs in there can be enormously illuminating. -d
Re: PTY allocation error
Theo de Raadt dera...@cvs.openbsd.org wrote: I have been following the discussion on this list regarding the wear-ability of CF cards, and in the past have done non-Read Only installs, using both CF and microdrives. There are two primary reasons why I am interested in doing this: 1) To learn more about OpenBSD itself. Solving all of the issues that have come up so far has been very beneficial and I've enjoyed the process 2) Setting up a RO system FULL STOP. At that stage, you are not running OpenBSD. You've made serious changes, and you are the one responsible for facing the consequences of that action, and working your own way through them. Your decisions; your consequences. So now you have a system which can survive a power outage, but you can't even fix the pty problems of your own creation. Sounds like pure genius. This is not about Theo personally, it's about everyone in this thread. Peter did't pretend to get a custommer support, neither he said someone is obliged to answer his question. He simply wanted someone familiar with pty allocation to give him an advice. If you don't want or don't know how to help him, why just not ignore the message? -- Dmitrij D. Czarkoff
Re: OpenBSD : FFS : Large Directories : Small files
On Mon 12/07/10 11:09, Otto Moerbeek o...@drijf.net wrote: On Sun, Jul 11, 2010 at 10:22:41AM +0200, Mayuresh Kathe wrote: Hello, may I know of limitations on supporting large directories (over 5 million files) with small files (less than 10 KB) under FFS/FFS2? This is for a research project under AMD x86 with SATA Disk[s]. Directories are linear structures. There's caching, but it will be slow. Create subdirecties. As a rule of thumb, restrict yourself to a few ten-thousends of files per dir. Otto, I will re-structure my solution. As always, you've given the most clear and relevant response. Thanks a million :)
Re: need help --reboot of newly installed OpenBSD 4.7 on Toshiba Libretto 70 neds in integet divide fault trap
I confirm -- disabling softraid did not fix it. Actually, I went for option of installing OpenBSD after reading Freds' webpage on the topic ;-). /wbr Ariel Burbaickij On Sun, Jul 11, 2010 at 12:16 AM, Fred Crowson fred.crow...@gmail.com wrote: On 10 July 2010 06:58, Joel Sing js...@openbsd.org wrote: Hi Ariel/Fred, Could one of you please try a current kernel with softraid disabled (boot with 'bsd -c' and type 'disable softraid' and then 'quit' at the UKC prompt) and let me know if this resolves the issue? Thanks, Joel Hi Joel, Booting with softraid disabled does not solve the issue. Hopefully, I'll find time over the next few weeks to do more investigations thanks Fred Output of boot process follows: Connected OpenBSD/i386 BOOT 3.02 boot bsd -c booting hd0a:bsd: /-\|/8127708-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/- \|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\ |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\| /-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/ -\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/- \|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\ |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-+1088136\ [61+365104|/-\|/-\|/-\|/-\|/-\|/+350630-\|/-\|/-\|/-\|/-\|/-]=0x978d18 entry point at 0x200120 [ using 716212 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2010 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.7-current (GENERIC) #111: Sat Jul 10 00:33:14 MDT 2010 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel Pentium/MMX (GenuineIntel 586-class) 121 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX real mem = 16478208 (15MB) avail mem = 6356992 (6MB) User Kernel Config UKC disable softraid 9 softraid0 disabled UKC quit Continuing... mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 11/11/97 apm0 at bios0: Power Management spec V1.2 apm0: battery life expectancy 100% apm0: AC on, battery charge high, charging pcibios at bios0 function 0x1a not configured bios0: ROM list: 0xe4000/0xc000 cpu0 at mainbus0: (uniprocessor) cpu0: F00F bug workaround installed isa0 at mainbus0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo com0: console com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 vga0 at isa0 port 0x3b0/48 iomem 0xa/131072 wsdisplay0 at vga0 mux 1: console (80x25, vt100 emulation), using wskbd0 wsdisplay0: screen 1-5 added (80x25, vt100 emulation) wdc0 at isa0 port 0x1f0/8 irq 14 wd0 at wdc0 channel 0 drive 0: BI-MDDAL2-6102 wd0: 16-sector PIO, LBA, 1551MB, 3177216 sectors wd0(wdc0:0:0): using BIOS timings sb0 at isa0 port 0x220/24 irq 5 drq 1: dsp v3.01 midi0 at sb0: SB MIDI UART audio0 at sb0 opl0 at sb0: model OPL3 midi1 at opl0: SB Yamaha OPL3 wss0 at isa0 port 0x530/8 irq 10 drq 0: CS4231 or AD1845 (vers 4) audio1 at wss0 pcppi0 at isa0 port 0x61 midi2 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pcic0 at isa0 port 0x3e0/2 iomem 0xd/65536 pcic0 controller 0: Intel 82365SL rev 1 has sockets A and B pcmcia0 at pcic0 controller 0 socket 0 xe0 at pcmcia0 function 0 Xircom, CreditCard 10Base-T, PS-CE2-10 port 0x340/16, irq 9: address 00:80:c7:42:37:d9 pcmcia1 at pcic0 controller 0 socket 1 pcic0: irq 11, polling enabled biomask e145 netmask e345 ttymask fbdf vscsi0 at root scsibus0 at vscsi0: 256 targets root device softraid not configured kernel: integer divide fault trap, code=0 Stopped at cpu_switchto+0x76: popl%ebx ddb ps PID PPID PGRPUID S FLAGS WAIT COMMAND 8 0 0 0 20x100200pfpurge 7 0 0 0 20x100200pcic0,0,1 6 0 0 0 20x100200pcic0,0,0 5 0 0 0 20x100200apm0 4 0 0 0 20x100200syswq 3 0 0 0 20x100200idle0 2 0 0 0 20x100200kmthread *1 0 0 0 7 0swapper 0 -1 0 0 3 0x80200 wdccmdswapper ddb trace cpu_switchto(d0202fe5,0,d0b7af08,d03ecf17,d09a1458) at cpu_switchto+0x76 end(0,0,0,efffeecc,efffeecc) at 0xd0b7aed8 (null)(d0d1c004,d0997aa0,0,73637376,3069) at 0 ddb boot poweroff Attempting to power down... ~ [EOT]
Re: need help --reboot of newly installed OpenBSD 4.7 on Toshiba Libretto 70 neds in integet divide fault trap
Could you tell somehting more, why cpu_swithchto on popping ebx (or other registers for this matter close the spot in code) from stack would exist in such way as it does right now? Something manages to corrupt stack to this amount/something else? On Sat, Jul 10, 2010 at 5:51 PM, Theo de Raadt dera...@cvs.openbsd.org wrote: On Sat, Jul 10, 2010 at 12:48 AM, Theo de Raadt dera...@cvs.openbsd.org wrote: Can you please try a kernel with softraid disabled? Yes, I will try. Any additional requests/specific procedure how it should be tried? I believe I finally understand the bug, and it is a softraid bug.
Roulez en toute sérénité pour 35€/an
[IMAGE] [IMAGE]
Re: Other FS support in OpenBSD
2010/7/12, Paolo Aglialoro paol...@gmail.com: Unfortunately the question was meant for a dual boot P3-M 256MB laptop, so BTW: I can hardly think of a person I know who used XFS on laptop and didn't lose at least subset of his data there. My suggestion: run, before it's too late. Ext3fs works for me between Linux, OpenBSD and Windows (even though I miss fsck, for which I have to use linux sometimes). -- Martin Pelikan
Re: PTY allocation error
On Mon, Jul 12, 2010 at 1:31 AM, Peter Bako pe...@bakonet.org wrote: Basically once I boot of my new image, I am able to log into it on the serial console and things look ok. B I can also ping the IP address of the unit, but when I try to SSH into it I get the following message: B Server refused to allocate pty I've checked over my setup and all seems fine as per the instructions. B I have all the pty* devices from /dev (which is RO) linked to /var/run/dev (which is in memory), so the problem cannot be that these devices are not writeable. B (Actually /var is linked to /tmp/var, where the /tmp directory is in memory and populated by the image from a directory called /template.) Can you create new entries in /dev? See pty(4) for more info. But my advise would be: Just do a normal install to a 1GB+ CF card. Floor -- Floor Terra flo...@gmail.com www: http://brobding.mine.nu/
Re: Other FS support in OpenBSD
Hi Martin, I'm afraid we've had some different experiences... power outages plus ext3 sometimes gave me woes (all partition gone), while I've been using both JFS and XFS on my servers, PCs and laptops without a single glitch. After all, they are mature industrial standards. Some of these systems are many years old. Oh, btw, a rule I always follow is trying to avoid to keep heavy loaded disks for too much time in a machine, with disk swaps when I feel it's the right time. Especially in laptops, I always prefer the 5400rpm versus the 7200rpm which go faster but offer smaller mtbf btw, my main 8 yrs laptop features a disk I changed a couple of yrs ago with ntfs, jfs and xfs partitions. 2010/7/12 Martin PelikC!n martin.peli...@gmail.com 2010/7/12, Paolo Aglialoro paol...@gmail.com: Unfortunately the question was meant for a dual boot P3-M 256MB laptop, so BTW: I can hardly think of a person I know who used XFS on laptop and didn't lose at least subset of his data there. My suggestion: run, before it's too late. Ext3fs works for me between Linux, OpenBSD and Windows (even though I miss fsck, for which I have to use linux sometimes). -- Martin Pelikan
Re: PTY allocation error
Hiya. I wish I'd caught this before I started drinking. Nevermind. As others have said: * CF cards are cheap. Do yourself a favour and buy a card at least big enough to take the required sets with some leg room. http://www.openbsd.org/faq/faq4.html#FilesNeeded * Don't use a frankenstein installer. Especially if you are a noob. Especially if they don't explain the whys and not only the hows. Don't paint by the numbers. Personally when I bought my box I bought two 256MB CF cards. When I install the latest release I pull one out (that's my last stable install), insert the other one and install over the network - use PXE and have a desktop serving tftpboot. Result? Off the shelf, straight to the media in its intended environment, OpenBSD install. Have a problem? Put the old card back in. Success? Pop the old card in a drawer for next release. http://www.openbsd.org/faq/faq6.html#PXE Simple answer to your problem. CF cards don't wear. I have been doing this for a few years now. RW everything. Standard install over the network (PXE and tftpboot). Plenty of other people share this view. So you're still interested in RO? 1) To learn more about OpenBSD itself. Solving all of the issues that have come up so far has been very beneficial and I've enjoyed the process Doing a standard install and attempting to reduce write access on your own steam is a much better pursuit than looking for somebody elses how and not why guesstimation of making OpenBSD RO. Try reading man hier for a really good start. As an example, you could spend half a day (or longer if you're dopey like me) reading man syslog, man newsyslog, man cron. All my logs are in RAM (either using buffers or mfs mounted file systems). What did I achieve? Well I removed 25% of my disk thrashing (actual result may vary, see your doctor, etcetera) but much more importantly I read these man pages and absorbed the consequences (not inclusive) - cron, crontab, syslogd, syslog.conf, newsyslog.conf, daily, etcetera. I learnt about message levels (an important system wide concept) and a whole lot more. I know exactly where all my logs go and how to read them and how to bump up the level of logging when I need to. Not only have I satisfied my less disk writing aim I've also learnt a useful skill for any install environment. I had a few minor issues crop up, but have been able to work my way through them. I think it's better to learn common administration procedures than half understood methods that don't apply to other environments (a desktop say). My experience is that the paint by the numbers, obtuse pre-installation setups are poorly documented (specifically for the target audience - noobs). Well intentioned perhaps but off the mark. If you don't have the skillset to run a non generic kernel don't do it. If you can't understand some installation script don't use it. Etcetera. FWIW, I do have /dev in RAM but it's not using 'populate' or some other method. Want to know how? Read man fstab and man makedev and man rc. Learn a whole lot and build a frankenstein that you understand. What's the punch line? This is again out of sphere and not a situation that should crop up on misc@ ... I won't be writing to misc@ asking questions about my RAM mounted /dev. If I can't solve my own problem I'll either be trying to reproduce it on my desktop or changing my mount (because I like to play it safe this will probably mean re-installing release) or reading a whole lot more man pages. You're on your own. Best wishes.
Re: PTY allocation error
On 07/12/10 03:11, czark...@gmail.com wrote: ... This is not about Theo personally, it's about everyone in this thread. Peter did't pretend to get a custommer support, neither he said someone is obliged to answer his question. He simply wanted someone familiar with pty allocation to give him an advice. They did, don't do this. If you don't want or don't know how to help him, why just not ignore the message? Why do you think saying don't do this is not helping him? It is certainly more productive than helping him continue down his wrong path. Nick.
Re: PTY allocation error
Nick Holland wrote: On 07/12/10 03:11, czark...@gmail.com wrote: ... This is not about Theo personally, it's about everyone in this thread. Peter did't pretend to get a custommer support, neither he said someone is obliged to answer his question. He simply wanted someone familiar with pty allocation to give him an advice. They did, don't do this. If you don't want or don't know how to help him, why just not ignore the message? Why do you think saying don't do this is not helping him? It is certainly more productive than helping him continue down his wrong path. Nick. The most UNFRIENDLY thing anyone can do to me is to help me persist in some momentary delusion that cannot lead to anything worthwhile.
Re: PTY allocation error
On 07/12/10 02:05, Peter Bako wrote: ... 2) Setting up a RO system gives a level of redundancy in the case of power outages (or more likely in my neck of the world) or brownouts. I've had a case in the past where a normal OpenBSD install, on a micro-drive, was in a situation where due to an electrical storm, in the span of about 15 minutes the power blinked a number of times (and who knows how many brownouts). This caused the system to repeatedly reboot and then get shutdown suddenly. I was out of the house at the time and could not pull the plug on the system, and due to an oversight this unit was not plugged into a UPS. The next morning, when I tried to bring it back up the system was badly scrambled. Both the hardware and the micro-drive were not damaged, but the OS needed a lot of help. I would like to be able to deploy systems away from my personal control, where having a system be able to came back up in a similar situation would be useful. Usually, ffs responds quite well to power-down while mounted, primary exception to this is when you are writing to the disk (I power-down and reboot systems all the time using the power switch :). But, now that we understand the problem you are actually trying to solve, I would suggest attacking this problem from that perspective rather than from a Frankenstein solution. I'm guessing this is a firewall app, I can't think of too many other apps where you will try to cram everything onto a 64M RO flash drive. So, about the only thing normally writing to disk is logging. So...put your logging partition on its own file system. Minimize it as much as you can. MAYBE make it an MFS. RO what you can easily (i.e., /usr, /home, but think about how you will do upgrades!). Keep all your partitions as small as reasonably possible (smaller = faster fsck), and if you end up with a 4G flash device, expect to have _most_ of it unallocated. In short, start with the most basic install, and make the fewest and smallest customizations needed to fix the actual problems you see or reasonably anticipate. Also...as this is a Soekris device, a simple UPS can be made by simply putting a gel-cell battery and an appropriate charger, and a fairly small battery will give you hours of run time. I'm making this sound a bit simpler than it really is -- your charger has to both supply enough power to run the computer and trickle charge the battery, but not fry the battery by overcharging it...and you probably want some way to disconnect the computer from the battery to force a reboot when the battery voltage drops low enough that the computer crashes, but not low enough that the system resets (and yes, that was the voice of experience). The battery will help filter the power supply somewhat, and should help with surge handling. Nick.
Re: PTY allocation error
So now you have a system which can survive a power outage, but you can't even fix the pty problems of your own creation. Sounds like pure genius. This is not about Theo personally, it's about everyone in this thread. Peter did't pretend to get a custommer support, neither he said someone is obliged to answer his question. He simply wanted someone familiar with pty allocation to give him an advice. If you don't want or don't know how to help him, why just not ignore the message? No -- this is about people continuing to make ridiculous I can make massive changes to OpenBSD so that it isn't OpenBSD, and people who are there will spend their time to help me. Everyone who is running massively modified OpenBSD is doing themselves _AND US_ a diservice. We will not help them.
July 10 snapshot: scambled harddisk name in dmesg
Hello, list! I couldn't find this reported elsewhere so far: With the July 10 snapshot (still the latest one right now) the harddisk name gets scrambled in the dmesg on both a new and on an old machine. Otherwise the snapshot seems to work fine. Tas. New machine: # dmesg | diff -u snapshot_Jul05 - --- snapshot_Jul05 Tue Jul 6 00:09:06 2010 +++ - Mon Jul 12 19:21:56 2010 @@ -1,9 +1,9 @@ -OpenBSD 4.7-current (GENERIC.MP) #77: Mon Jul 5 12:18:28 MDT 2010 +OpenBSD 4.7-current (GENERIC.MP) #191: Sat Jul 10 15:00:55 MDT 2010 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Genuine Intel(R) CPU 1400 @ 1.83GHz (GenuineIntel 686-class) 1.84 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM real mem = 2114367488 (2016MB) -avail mem = 2070663168 (1974MB) +avail mem = 2069774336 (1973MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/29/05, SMBIOS rev. 2.4 @ 0xe73f0 (39 entries) bios0: vendor Apple Computer, Inc. version MM11.88Z.0055.B08.0610121326 date 10/12/06 @@ -78,7 +78,7 @@ pciide0: channel 1 disabled (no drives) pciide1 at pci0 dev 31 function 2 Intel 82801GBM SATA rev 0x02: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide1: using apic 1 int 19 (irq 11) for native-PCI interrupt -wd0 at pciide1 channel 0 drive 1: FUJITSU MHV2080BHPL +wd0 at pciide1 channel 0 drive 1: UFIJST UHM2V80B0PH L wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors wd0(pciide1:0:1): using PIO mode 4, Ultra-DMA mode 5 ichiic0 at pci0 dev 31 function 3 Intel 82801GB SMBus rev 0x02: apic 1 int 19 (irq 11) Old machine: # dmesg | diff -u snapshot_Jul05 - --- snapshot_Jul05 Tue Jul 6 00:08:08 2010 +++ - Mon Jul 12 19:24:31 2010 @@ -1,9 +1,9 @@ -OpenBSD 4.7-current (GENERIC) #89: Mon Jul 5 12:10:22 MDT 2010 +OpenBSD 4.7-current (GENERIC) #113: Sat Jul 10 14:50:49 MDT 2010 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: AMD-K6(tm) 3D processor (AuthenticAMD 586-class) 502 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX real mem = 536440832 (511MB) -avail mem = 518574080 (494MB) +avail mem = 517689344 (493MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 08/05/99, BIOS32 rev. 0 @ 0xfb390, SMBIOS rev. 2.1 @ 0xf0800 (29 entries) bios0: vendor Award Software International, Inc. version 4.51 PG date 08/05/99 @@ -25,7 +25,7 @@ pci1 at ppb0 bus 1 pcib0 at pci0 dev 7 function 0 VIA VT82C586 ISA rev 0x47 pciide0 at pci0 dev 7 function 1 VIA VT82C571 IDE rev 0x06: ATA33, channel 0 configured to compatibility, channel 1 configured to compatibility -wd0 at pciide0 channel 0 drive 0: Maxtor 6Y120L0 +wd0 at pciide0 channel 0 drive 0: aMtxro6 1Y020L wd0: 16-sector PIO, LBA, 117246MB, 240121728 sectors atapiscsi0 at pciide0 channel 0 drive 1 scsibus0 at atapiscsi0: 2 targets Full dmesg of new machine: OpenBSD 4.7-current (GENERIC.MP) #191: Sat Jul 10 15:00:55 MDT 2010 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Genuine Intel(R) CPU 1400 @ 1.83GHz (GenuineIntel 686-class) 1.84 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM real mem = 2114367488 (2016MB) avail mem = 2069774336 (1973MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/29/05, SMBIOS rev. 2.4 @ 0xe73f0 (39 entries) bios0: vendor Apple Computer, Inc. version MM11.88Z.0055.B08.0610121326 date 10/12/06 bios0: Apple Computer, Inc. Macmini1,1 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP HPET APIC MCFG ASF! SBST ECDT SSDT SSDT SSDT acpi0: wakeup devices PXS1(S4) PXS2(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB7(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 166MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Genuine Intel(R) CPU 1400 @ 1.83GHz (GenuineIntel 686-class) 1.84 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,VMX,EST,TM2,xTPR,PDCM ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (RP01) acpiprt2 at acpi0: bus 2 (RP02) acpiprt3 at acpi0: bus 3 (PCIB) acpiec0 at acpi0: Failed to register address space acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpibtn0 at acpi0: PWRB acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: VGA_ acpivout1 at acpivideo0: TV__ bios0: ROM list: 0xc/0xe600! cpu0: Enhanced SpeedStep 1834 MHz: speeds: 1833, 1667, 1500, 1333, 1000 MHz memory map conflict 0xe00f8000/0x1000 memory map conflict 0xfed1c000/0x4000 memory map conflict 0xfffb/0x3 pci0 at mainbus0 bus 0:
Re: PTY allocation error
Nick Holland n...@holland-consulting.net wrote: If you don't want or don't know how to help him, why just not ignore the message? Why do you think saying don't do this is not helping him? It is certainly more productive than helping him continue down his wrong path. I think don't do this is helping him in some way, but that's definitly not what he is asking for. -- Dmitrij D. Czarkoff
Re: PTY allocation error
Nick Holland n...@holland-consulting.net wrote: If you don't want or don't know how to help him, why just not ignore the message? Why do you think saying don't do this is not helping him? It is certainly more productive than helping him continue down his wrong path. I think don't do this is helping him in some way, but that's definitly not what he is asking for. He lives in an highrise apartment, and he is asking for a pony.
Re: PTY allocation error
On Mon, Jul 12, 2010 at 11:18 AM, Dmitrij D. Czarkoff czark...@gmail.com wrote: Nick Holland n...@holland-consulting.net wrote: If you don't want or don't know how to help him, why just not ignore the message? Why do you think saying don't do this is not helping him? It is certainly more productive than helping him continue down his wrong path. I think don't do this is helping him in some way, but that's definitly not what he is asking for. So you feel that he's asking to be left to wander down a path where fewer and fewer people can help him, all without warning, so that eventually no one will answer his questions because they can't do so? Interesting: I missed the spot in his note where he indicated that he didn't want that warning and understood that as the path he was heading down. While I've seen that as the default assumption on some other mailing lists, it certainly isn't the default assumption here. Philip Guenther
Re: PTY allocation error
On 07/11/2010 06:31 PM, Peter Bako wrote: I'm setting up (well, trying to I guess :-) ) a read-only OpenBSD system to run off a small CF card. Never having done this before, I found an excellent article written by Daniele Mazzocchio (http://www.kernel-panic.it/openbsd/embedded/) to use as my guide. I had a few minor issues crop up, but have been able to work my way through them. However I finally got to one that I am stumped with. Basically once I boot of my new image, I am able to log into it on the serial console and things look ok. I can also ping the IP address of the unit, but when I try to SSH into it I get the following message: Server refused to allocate pty I've checked over my setup and all seems fine as per the instructions. I have all the pty* devices from /dev (which is RO) linked to /var/run/dev (which is in memory), so the problem cannot be that these devices are not writeable. (Actually /var is linked to /tmp/var, where the /tmp directory is in memory and populated by the image from a directory called /template.) Unfortunately this goes a bit beyond my current skill set, so if anyone has any suggestions I really would appreciate the help. BTW, in case it matters. I'm using OpenBSD 4.6 as both the host on which I setup the image and OS on the CF card. The card in question is a 64M SanDisk CF and is being plugged into a Soekris Net4801 box. None of these should make a difference, but you never know... :-) Thanks, Peter You probably need your entire /dev directory in memory. It worked that way for me. But I'll tell you something from my own experience: I got this whole RO-flash, RW-on-MFS thing working on a Soekris net5501, but it was a big hassle -- a hassle that I would have to repeat on every upgrade. I started with the link you mentioned, plus several others, and still had to work through several more issues myself (I had read plenty of, shall we say, admonitions on this list about not doing what I was trying to do, so I decided I needed to fix everything myself :). Some of those issues didn't rear their ugly heads until several days after the initial install. After much suffering, and reading this list and the experiences of many folks getting reasonable life out of modern CF cards (at least comparable to hard disks), I decided that a standard OpenBSD install was the way to go. On my next snapshot install I did exactly that; it went much more smoothly. The only real reason to do the RO-flash setup is to make the device unpluggable with impunity, i.e., it will not have corrupt filesystems after a non-orderly shutdown (but you may of course still lose data on the MFS). For me, unless I was making and selling these things to the unwashed public, even that is not worth the hassle of the RO-flash setup. CF cards are cheaper than my time. If you want to do it for the learning experience alone, then OK, but be prepared to do it mostly, if not all, yourself. And once you do, or once you do an upgrade, I suspect you will want to go back to a standard install. My $2.98 US, FWIW. Corey
Re: PTY allocation error
And what is your opinion of people who run sshd on non-standard poorts? I recently had to smack one of my guys for that momentary brilliance. On 7/12/10, Corey clinge...@gmail.com wrote: On 07/11/2010 06:31 PM, Peter Bako wrote: I'm setting up (well, trying to I guess :-) ) a read-only OpenBSD system to run off a small CF card. Never having done this before, I found an excellent article written by Daniele Mazzocchio (http://www.kernel-panic.it/openbsd/embedded/) to use as my guide. I had a few minor issues crop up, but have been able to work my way through them. However I finally got to one that I am stumped with. Basically once I boot of my new image, I am able to log into it on the serial console and things look ok. I can also ping the IP address of the unit, but when I try to SSH into it I get the following message: Server refused to allocate pty I've checked over my setup and all seems fine as per the instructions. I have all the pty* devices from /dev (which is RO) linked to /var/run/dev (which is in memory), so the problem cannot be that these devices are not writeable. (Actually /var is linked to /tmp/var, where the /tmp directory is in memory and populated by the image from a directory called /template.) Unfortunately this goes a bit beyond my current skill set, so if anyone has any suggestions I really would appreciate the help. BTW, in case it matters. I'm using OpenBSD 4.6 as both the host on which I setup the image and OS on the CF card. The card in question is a 64M SanDisk CF and is being plugged into a Soekris Net4801 box. None of these should make a difference, but you never know... :-) Thanks, Peter You probably need your entire /dev directory in memory. It worked that way for me. But I'll tell you something from my own experience: I got this whole RO-flash, RW-on-MFS thing working on a Soekris net5501, but it was a big hassle -- a hassle that I would have to repeat on every upgrade. I started with the link you mentioned, plus several others, and still had to work through several more issues myself (I had read plenty of, shall we say, admonitions on this list about not doing what I was trying to do, so I decided I needed to fix everything myself :). Some of those issues didn't rear their ugly heads until several days after the initial install. After much suffering, and reading this list and the experiences of many folks getting reasonable life out of modern CF cards (at least comparable to hard disks), I decided that a standard OpenBSD install was the way to go. On my next snapshot install I did exactly that; it went much more smoothly. The only real reason to do the RO-flash setup is to make the device unpluggable with impunity, i.e., it will not have corrupt filesystems after a non-orderly shutdown (but you may of course still lose data on the MFS). For me, unless I was making and selling these things to the unwashed public, even that is not worth the hassle of the RO-flash setup. CF cards are cheaper than my time. If you want to do it for the learning experience alone, then OK, but be prepared to do it mostly, if not all, yourself. And once you do, or once you do an upgrade, I suspect you will want to go back to a standard install. My $2.98 US, FWIW. Corey -- Sent from my mobile device http://www.glumbert.com/media/shift http://www.youtube.com/watch?v=tGvHNNOLnCk This officer's men seem to follow him merely out of idle curiosity. -- Sandhurst officer cadet evaluation. Securing an environment of Windows platforms from abuse - external or internal - is akin to trying to install sprinklers in a fireworks factory where smoking on the job is permitted. -- Gene Spafford learn french: http://www.youtube.com/watch?v=30v_g83VHK4
Plan Peninsula BlackBerry Joven, Informate
Blackberry Gratis [IMAGE]
Re: PTY allocation error
On 07/12/10 14:10, bofh wrote: And what is your opinion of people who run sshd on non-standard poorts? I recently had to smack one of my guys for that momentary brilliance. OK, this is the second time I've seen someone say this. What is the difference? Is there some magical property with port 22? I run several websites with non port 80 addresses. They work just fine. When money was short, I just dropped the domain name.
Re: PTY allocation error
On 07/12/2010 03:38 PM, Chris Bennett wrote: On 07/12/10 14:10, bofh wrote: And what is your opinion of people who run sshd on non-standard poorts? I recently had to smack one of my guys for that momentary brilliance. OK, this is the second time I've seen someone say this. What is the difference? Is there some magical property with port 22? I run several websites with non port 80 addresses. They work just fine. When money was short, I just dropped the domain name. I ONLY run the sshd that are allowed to connect from the Internet in non-standard ports. Anyone that matters to know knows on witch port the sshd is running.
nous vous informer que nous ne pouvions pas traiter votre paiement recent de facture.
Banque Postal: retour ? l'accueil Bonjour, Cet email a ete envoye pour vous informer que nous ne pouvions pas traiter votre paiement recent de facture. Ceci pourrait etre du a l une ou l autre des raisons suivantes: 1. Un changement recent de vos informations personnelles. (par exemple : adresse de facturation, telephone) 2. Soumission de l information incorrecte pendant le processus de paiement de facture. 3. Une incapacite de verifier exactement votre option choisie de paiement due a une erreur interne dans nos processeurs. En raison de ceci, pour s assurer que votre service n est pas interrompu, nous vous invitons a confirmer et mettre a jour votre information de facturation aujourd hui: Cliquer Ici Pour Une Resolution.. Merci de votre confiance.
Re: PTY allocation error
On Mon, Jul 12, 2010 at 2:46 PM, Leonardo Carneiro - Veltrac lscarne...@veltrac.com.br wrote: I ONLY run the sshd that are allowed to connect from the Internet in non-standard ports. Anyone that matters to know knows on witch port the sshd is running. Well, them and anyone who knows how to half-assed run nmap or any other numerous service fingerprinting utilities.
Re: PTY allocation error
On 07/12/10 15:01, J Sisson wrote: On Mon, Jul 12, 2010 at 2:46 PM, Leonardo Carneiro - Veltrac lscarne...@veltrac.com.br wrote: I ONLY run the sshd that are allowed to connect from the Internet in non-standard ports. Anyone that matters to know knows on witch port the sshd is running. Well, them and anyone who knows how to half-assed run nmap or any other numerous service fingerprinting utilities. Yes, absolutely true. Any well thought out, skilled attack will quickly find these other ports. But I get many thousands of idiot bot attacks on my web server a month. Since I have a good script to slam them out right away with pfctl, I don't see much more than one or two log entries for each evil-doer. All attempts after that never get in. Since most attacks on port 22 are by equally idiotic bots, I think it is reasonable to move sshd and block port 22. Even with sshd moved, when I finally decided to block port 22, my bandwidth use dropped noticeably.
Re: PTY allocation error
On 07/12/2010 04:33 PM, Chris Bennett wrote: On 07/12/10 15:01, J Sisson wrote: On Mon, Jul 12, 2010 at 2:46 PM, Leonardo Carneiro - Veltrac lscarne...@veltrac.com.br wrote: I ONLY run the sshd that are allowed to connect from the Internet in non-standard ports. Anyone that matters to know knows on witch port the sshd is running. Well, them and anyone who knows how to half-assed run nmap or any other numerous service fingerprinting utilities. Yes, absolutely true. Any well thought out, skilled attack will quickly find these other ports. But I get many thousands of idiot bot attacks on my web server a month. Since I have a good script to slam them out right away with pfctl, I don't see much more than one or two log entries for each evil-doer. All attempts after that never get in. Since most attacks on port 22 are by equally idiotic bots, I think it is reasonable to move sshd and block port 22. Even with sshd moved, when I finally decided to block port 22, my bandwidth use dropped noticeably. You made the point: bandwidth!
Openbgpd Max Number of Neighbors per Instance
Does anyone have information about the maximum number of BGP neighbors a single instance of OpenBGPD could support assuming the following: 1. OpenBGPD would send only Default Route to each neighbor 2. Each neighbor would advertise only 1 subnet to OpenBGPD 3. OpenBGPD could run in passive mode for all of the connections 4. OpenBGPD running on new/current/modern fully supported hardware with no other services running. I am looking to scale this configuration to support between 500 - 10,000 peers and I need to know how much hardware I would need to purchase to support this. James D. Reid Spacenet Inc. Network Engineer Office: (703) 848 - 1266 Spacenet Inc. Notice and Disclaimer IMPORTANT: This e-mail along with any attachment(s) is intended for the above named addressee(s) only, and may contain information which is proprietary, confidential and/or privileged. If you are not the intended recipient or if you received this e-mail transmittal in error, please be advised that any review, copying, use, distribution or dissemination of this e-mail and any attachment(s) is strictly prohibited. Please immediately notify the sender by e-mail or to phone number 703-848-1000 and delete this e-mail and any attachments. Thank you.
HI,misc:由著名導師主講，針對0-12歲小朋友之家長的免費教育講座「家教從小開始，財富由此生！」
Having problems viewing this email? Please click here.For enquiry, please send email to reg...@arpeggios.com.hk eg!f3i1h.d;%d8 ge'e.9o h+ f f-$.ef d;;d=f %h)h+ i;i5h3 reg...@arpeggios.com.hk HI,misc ef f(d8 f3e f6e0fegd?!d;6o h+ f ih#ie. Important Notice: Base on the Unsolicited Electronic Messages Ordinance, if you DO NOT want to receive any promotional email messages from us in the future, please kindly reply this e-mail for DELETION. If you would like to continue to receive our promotional email massages, you do not need to reply us.
Re: Openbgpd Max Number of Neighbors per Instance
On Mon, Jul 12, 2010 at 03:07:23PM -0400, James Reid - McLean wrote: Does anyone have information about the maximum number of BGP neighbors a single instance of OpenBGPD could support assuming the following: 1. OpenBGPD would send only Default Route to each neighbor 2. Each neighbor would advertise only 1 subnet to OpenBGPD 3. OpenBGPD could run in passive mode for all of the connections 4. OpenBGPD running on new/current/modern fully supported hardware with no other services running. I am looking to scale this configuration to support between 500 - 10,000 peers and I need to know how much hardware I would need to purchase to support this. Nobody ever tested 10k peers but here are some tips. Get a box with 3-4GB of RAM. Do not run i386 (amd64 has less kvm restrictions and you will need a lot of kernel memory). Increase kern.maxclusters to 4-8 times the max number of sockets you expect and don't forget to increase kern.nfiles. Expect to hit a few other issues as well. I know of people doing tests with 500-1000 sessions that actually injected a few routes. But limiting bgpd to only announce a default route should reduce the load on the RDE massivly. good luck -- :wq Claudio
Re: PTY allocation error
On Mon, Jul 12, 2010 at 2:06 AM, Peter Bako pe...@bakonet.org wrote: 2) Setting up a RO system gives a level of redundancy in the case of power outages (or more likely in my neck of the world) or brownouts. I've had a case in the past where a normal OpenBSD install, on a micro-drive, was in a situation where due to an electrical storm, in the span of about 15 minutes the power blinked a number of times (and who knows how many brownouts). This caused the system to repeatedly reboot and then get shutdown suddenly. This is where telling people the real problem, instead of your solution, is important. Now I can give you the easy solution. You need to make three changes. 1. edit /etc/fstab and enable softdep on all filesystems 2. edit /etc/rc and change the mount line to mount -f 3. edit /etc/rc and delete the fsck line
Re: PTY allocation error
On 12 July 2010 20:46, Leonardo Carneiro - Veltrac lscarne...@veltrac.com.br wrote: I ONLY run the sshd that are allowed to connect from the Internet in non-standard ports. Anyone that matters to know knows on witch port the sshd is running. And any one who doesn't just runs nmap to find port 222 :~) Fred
Has anyone any idea what this is...
I've a base install, with only firefox on top, and with broadband ADSL with a vpn provider also,. The cursor starts jumping around text boxes in firefox, within a box, but also between boxes, typically from a password box to the login name box, so by the time I've typed the password in I realise the cursor has in fact jumped to the login name box, and I've have typed the password into the clear text login name text box by accident. Also the typing speed may slow right down, so that text typed will not appear for a second or so. I am someone btw who was a full blown criminal stalking and Internet harassment problem -- Windows is useless, even with a mobile broadband modem (hacked quite quickly nowadays). I assume my 'phone line has hardware hacking it somewhere down the line. Apart from that I am glad to say OpenBSD has held out quite well. An ftp install resulted in a bug whereby the letters in console mode were sometimes not displaying properly (corrupted), but otherwise with an install from CD only the above hack and only in firefox. Library Web http://libraryweb.info
request help with tip and serial port problem
Hello, A user needs to connect to external equipment using tip and a serial port. I created an /etc/remote file: snake:br=9600:dv=/dev/tty01:hf:nb:pa=none The group associated with /dev/tty01 was changed from dialer to one that includes the user: $ls -l /dev/tty01 crw-rw 1 uucp wheel 8, 1 Feb 7 09:38 /dev/tty01 Root can use tip and connect ok but if the user tries it: $tip snake /var/spool/lock/LCK...tty01: No such file or directory Can't open lock file. all ports busy I assume the user doesn't have permission to write to /var/spool/lock and having root give the user rw permission on the port is probably not the correct way to handle this. How can I fix this problem?
Re: request help with tip and serial port problem
On Mon, Jul 12, 2010 at 2:58 PM, fred f...@blakemfg.com wrote: Hello, A user needs to connect to external equipment using tip and a serial port. I created an /etc/remote file: snake:br=9600:dv=/dev/tty01:hf:nb:pa=none The group associated with /dev/tty01 was changed from dialer to one that includes the user: $ls -l /dev/tty01 crw-rw 1 uucp wheel 8, 1 Feb 7 09:38 /dev/tty01 so, the user is already in wheel group. Revert above change. Enable sudo (if not already done so) for users in group wheel. $ sudo -u uucp tip snake --patrick Root can use tip and connect ok but if the user tries it: $tip snake /var/spool/lock/LCK...tty01: No such file or directory Can't open lock file. all ports busy I assume the user doesn't have permission to write to /var/spool/lock and having root give the user rw permission on the port is probably not the correct way to handle this. How can I fix this problem?
Question about moving system to different hardware
Hello: I was very happy with myself after setting up a file server for my home with some old hardware (and some new old hardware). Everything works great. Now, I have come into possession of some better old hardware (an actual server - Compaq Evo W8000 - with SCSI disks! Wow, that's big for me). So, I wanted to move my fileserver over. I was reading the FAQ (14.10) about backing up, and I think this will work, but I have a couple of basic questions, if anyone has the time to answer. 1. Since I will be moving to new hardware, and from ide to scsi disks, I will need to modify /etc/fstab. Is there anything else I should be thinking about editing for the move to new hardware (the network card will be the same, since it's moving too). I can't think of anything other than fstab. 2. I note that in the example for backing up and restoring that raw devices are used. In my situation, I will be going from ide to a usb drive, and then from the usb drive to scsi disks. So, the ide drive I can't access raw, but I don't think this is an issue. Is it? And, if I don't read from the raw device with dump, it's still okay to write to the raw device with restore, right? I think these are pretty basic questions, and I think I would figure it out on my own when I do it. I guess I am looking for peace of mind that I am on the right track. Thanks Bye - ted
:: Renuévate :: Diseño Profesional de Sitios desde 139.000
- RENUC VATE !! - PLAN E-START : DISECO WEB PROFESIONAL DESDE $139.000 + IVA DiseC1o Sitios Web acorde con su necesidad Para ver galerC-a diseC1os: http://www.interactua.cl/e-marketer/link.php?M=6322013N=143L=119F=T Para mas informacion: http://www.interactua.cl/e-marketer/link.php?M=6322013N=143L=89F=T Haga sus CONSULTAS en: http://www.interactua.cl/e-marketer/link.php?M=6322013N=143L=31F=T o LLAMANDO a (562) 940 4155 - (562) 761 9556 respuestas a este email no son monitorizadas OTROS PLANES - PLAN E-POWER El mC!s completo SITIO WEB ADMINISTRABLE - * Ideal para Empresas que necesitan de un potente y moderno sitio administrable con grandes posibilidades de interaccion con sus clientes y con una capacidad de expansion casi ilimitada. * Permite disponer de una potente vitrina y canal de comunicacion, con la posibilidad de administrar en forma directa sus contenidos, catalogo de productos o servicios. Para ver galerC-a diseC1os: http://www.interactua.cl/e-marketer/link.php?M=6322013N=143L=120F=T Para mC!s informaciC3n: http://www.interactua.cl/e-marketer/link.php?M=6322013N=143L=88F=T - EXPANDA SIN LIMITES SU PLAN E-POWER Tenemos alternativas profesionales para que su empresa utilice todo el potencial que ofrece Internet - * E-POWER_SHOP. Completa y flexible tienda virtual con registro de usuarios, manejo de inventarios, pago en linea, etc. * E-POWER PROPIEDADES. Completa tienda virtual para la exhibicion de propiedades, departamentos y casas. * E-POWER MARKET. Administre un sistema de avisos en linea. Los usuarios podran registrarse, publicar sus avisos con fotos y comunicarse entre ellos. * E-POWER ACCESS. Acceso a contenidos especC-ficos para usuarios o grupos de usuarios tales como clientes o empleados. * E-POWER DOCUMENTS. Herramienta profesional de gestiC3n documental. Posibilidad de restringir el acceso a usuarios especC-ficos. Soporta cualquier tipo de archivos. * E-POWER BANNERS. Gane dinero con su sitio con un completo sistema de administracion de anuncios publicitarios. * E-POWER FORO. Un potente foro de conversacion en linea completamente integrado a su sitio. - TODOS LOS PLANES DE DISECO SITIOS WEB INCLUYEN : - * Alojamiento (Hosting) del Sitio de 120 MB de capacidad * Hasta 6 cuentas de Correo Electronico con el nombre de su empresa * Realizacion del DiseC1o Web optimizado para Buscadores (Google) * Inscripcion del Sitio en Buscadores * Formulario de Contacto para recibir consultas * Estadisticas de Visitas al sitio Web * Animaciones Flash para cautivar a sus visitantes Servicio de envio de CORREOS por E-Factory: http://www.interactua.cl/e-marketer/link.php?M=6322013N=143L=55F=T Realizamos DiseC1o Sitios Web acorde con su necesidad: - Sitios Animados, Administrables, Tiendas Virtuales, Catalogos Web Servicios Adicionales: - Mantencion Sitios, Mailing, Hosting Profesional Acatando la Ley NB: 19.496 y su modificacion 19.955 del 2006 artC-culo 28 B donde se regula el envio de correos electronicos, en caso de no ser de su interes lo invitamos a Ud. hacer clic en: http://www.interactua.cl/e-marketer/link.php?M=6322013N=143L=56F=T para cursar la baja de su correo electronico para los efectos de futuras publicaciones de este servicio.
Khuyến Mãi: thiết kế web miễn phí, cung cấp phàn mềm quản lý, phần mềm công nghiệp.
http://tinviettid.com/ KC-nh ga; i quC- khC!ch hC ng: TC-n Via;t TID Co., Ltd lC cC4ng ty hoa:!t Da;ng trong lD)nh va;1c thia:?t ka:? web site, pha:'n ma;m qua:#n lC=, pha:'n ma;m Dia;u khia;n cC4ng nghia;p vC chuyC*n cung ca:%p cC!c sa:#n pha:)m cC4ng nghia;p... Va;i Da;i ngE) nhCn viC*n giC u kinh nghia;m trong lD)nh va;1c Dia;n ta;-, tin ha; c, chC:ng tC4i xin ga; i Da:?n quC- doanh nghia;p cC!c gia:#i phC!p ka;9 thua:-t tiC*n tia:?n nha:%t: * Gia:#i phC!p thu phC- giao thC4ng * Gia:#i phC!p bC#i gia;/ xe ( hai bC!nh, C4 tC4 ) * Gia:#i phC!p Dia;u khia;n thia:?t ba; ta;+ xa thC4ng qua ma:!ng Internet, GPRS, CDMA, 3G... * Pha:'n ma;m qua:#n lC=, Dia;u khia;n cC4ng nghia;p theo yC*u ca:'u ca;'a quC- khC!ch hC ng. * Thia:?t ka:? website giC! ra:;, website cha:%t lF0a;#ng cao. * CC!c da; ch va;% qua:#n tra; website, da; ch va;% ga; i mail quC ng cC!o, dich va;% qua:#ng bC! trang web SEO... Da:7c bia;t cC4ng ty va;+a trang ba; ha; tha;ng Web hosting ( mC!y cha;' nuC4i web ) ta;c Da; cao, chC:ng tC4i sa:= mia;n phC- thia:?t ka:? web cho 99 khC!ch hC ng Da:'u Da:'u tiC*n sa;- da;%ng da; ch va;% Web hosting ca;'a chC:ng tC4i (C!p da;%ng ta;+ 30/07/2010 Da:?n 30/09/2010 ). CC3 tha; nC3i trong tha; i Da:!i internet bC9ng na; nhF0 hia;n nay, lF0a;#ng ngF0a; i truy ca:-p internet ngC y cC ng nhia;u ua;c tC-nh a; Via;t Nam, con sa; DC3 vC o khoa:#n 22 tria;u ngF0a; i, chF0a ka; sa; lF0a;#ng ngF0a; i truy ca:-p internet ba:1ng Dia;n thoa:!i ngC y cC ng tDng. Do DC3 trang web lC phF0F!ng tia;n Da; hC ng tria;u ngF0a; i bia:?t Da:?n ba:!n, bia:?t Da:?n sa:#n pha:)m ca;'a ba:!n. Na:?u ba:!n chF0a cC3 trang web cho riC*ng mC,nh hC#y nhanh chCn Da; cC3 ma;t trang web cha:%t lF0a;#ng hoC n toC n mia;n phC-. Xem chi tia:?t ta:!i DCy: http://tinviettid.com/index.php?/thiet-ke-web-tron-goi/goi-web-mien-phi.html http://tinviettid.com/index.php?/thiet-ke-web-tron-goi/goi-web-mien-phi.html Da:?n va;i chC:ng tC4i ba:!n sa:= tha;1c sa;1 yC*n tCm va;i phong cC!ch lC m via;c chuyC*n nghia;p, thC!i Da; pha;%c va;% Cn ca:'n, vC ma;t cha:? Da; ha:-u mC#i uy tC-n. ChC:ng tC4i thC nh tha:-t xin la;i na:?u email nC y lC m phia;n ba:!n, xin hC#y reply cho chC:ng tC4i na:?u ba:!n khC4ng mua;n nha:-n email. Thanks best regard! Ba:#o, Tra:'n (Mr) Mobile : 098.959.4048 Email: b...@tinviettid.com mailto:b...@tinviettid.com YM : ymsgr:sendim?tvbao2010 Skype : skype:tranvbao?call CTY TNHH Da:U TF/ PHCT TRIa;N CCNG NGHa; TC N VIa;T ( TC N VIa;T TID Co., Ltd) Address : 118/4/4A Tha;ng Nha:%t, Ward 11, GC2 Va:%p Dist, HCM City Telephone : (84).(8). 39 212 892 Fax: (84).(8). 39 212 893 Email : i...@tinviettid.com mailto:i...@tinviettid.com Webite : http://tinviettid.com http://tinviettid.com/
Re: Question about moving system to different hardware
On 07/12/10 19:00, Ted Wynnychenko wrote: Hello: I was very happy with myself after setting up a file server for my home with some old hardware (and some new old hardware). Everything works great. Now, I have come into possession of some better old hardware (an actual server - Compaq Evo W8000 - with SCSI disks! Wow, that's big for me). So, I wanted to move my fileserver over. I was reading the FAQ (14.10) about backing up, and I think this will work, but I have a couple of basic questions, if anyone has the time to answer. 1. Since I will be moving to new hardware, and from ide to scsi disks, I will need to modify /etc/fstab. Is there anything else I should be thinking about editing for the move to new hardware (the network card will be the same, since it's moving too). I can't think of anything other than fstab. Nope. General rule: fstab and hostname.*, and the later is taken care of in your case by moving the card (PROBABLY. I presume the new HW has the some kind of network interface, if your card is a different kind of interface, no problem. If the on-board is the same kind of chip (or similar family), you might have an issue, in that you might need to use device #1 instead of #0 (i.e., bge1 instead of bge0, or em1 instead of em0). It is..disturbing..how few OSs are this simple to migrate between different hardware. 2. I note that in the example for backing up and restoring that raw devices are used. In my situation, I will be going from ide to a usb drive, and then from the usb drive to scsi disks. So, the ide drive I can't access raw, but I don't think this is an issue. Is it? And, if I don't read from the raw device with dump, it's still okay to write to the raw device with restore, right? actually, if you are going to an interim device, you will be dumping to a file (on a file system on that device), so you will go raw device to file, then file to raw device. I think these are pretty basic questions, and I think I would figure it out on my own when I do it. I guess I am looking for peace of mind that I am on the right track. Mostly, yes. :) Nick.
Re: request help with tip and serial port problem
On 07/12/10 19:32, patrick keshishian wrote: On Mon, Jul 12, 2010 at 2:58 PM, fred f...@blakemfg.com wrote: Hello, A user needs to connect to external equipment using tip and a serial port. I created an /etc/remote file: snake:br=9600:dv=/dev/tty01:hf:nb:pa=none The group associated with /dev/tty01 was changed from dialer to one that includes the user: $ls -l /dev/tty01 crw-rw 1 uucp wheel 8, 1 Feb 7 09:38 /dev/tty01 so, the user is already in wheel group. Revert above change. Enable sudo (if not already done so) for users in group wheel. $ sudo -u uucp tip snake --patrick uh...if all else fails, do it as root? I think we'd prefer to avoid that, unless really a root-like activity. The dialer group is set up just for this purpose. The problem with changing the ownership (or group) of a device file is the next upgrade will overwrite your ownership change. Ask me how I know. Better idea, don't -- just use your imagination. I'm not sure why you didn't just add that user to group dialer, but it is quite straight forward: /home/nick $ grep nick /etc/group wheel:*:0:root,nick wsrc:*:9:nick dialer:*:117:nick nick:*:1000: and...I (as nick) have no trouble using my serial port without using sudo and without changing device file ownership. You will probably want to create a file /var/log/aculog which is writable by group dialer, as well... Squishes an error message, and provides some useful logging, too. Nick.
Re: Has anyone any idea what this is...
On Mon, Jul 12, 2010 at 5:47 PM, GSO gso...@yahoo.co.uk wrote: I've a base install, with only firefox on top, and with broadband ADSL with a vpn provider also,. The cursor starts jumping around text boxes in firefox, within a box, but also between boxes, typically from a password box to the login name box, so by the time I've typed the password in I realise the cursor has in fact jumped to the login name box, and I've have typed the password into the clear text login name text box by accident. weird (perhaps de weerd) Also the typing speed may slow right down, so that text typed will not appear for a second or so. weirder I am someone btw who was a full blown criminal stalking and Internet harassment problem h . . . weirdest (assuming I'm interpreting the English right) -- Windows is useless, even with a mobile broadband modem (hacked quite quickly nowadays). I assume my 'phone line has hardware hacking it somewhere down the line. nonsense Apart from that I am glad to say OpenBSD has held out quite well. nice An ftpinstall resulted in a bug whereby the letters in console mode were sometimes not displaying properly (corrupted), but otherwise with an install from CD only the above hack and only in firefox. more nonsense . . . nice! Library Web http://libraryweb.info I gave this post a few hours before responding, to see if anyone would bite. It is one of the more odd posts. To the OP, if you are serious, rethink your post ;-)
Re: request help with tip and serial port problem
On Mon, Jul 12, 2010 at 6:03 PM, Nick Holland n...@holland-consulting.net wrote: On 07/12/10 19:32, patrick keshishian wrote: On Mon, Jul 12, 2010 at 2:58 PM, fred f...@blakemfg.com wrote: Hello, A user needs to connect to external equipment using tip and a serial port. I created an /etc/remote file: snake:br=9600:dv=/dev/tty01:hf:nb:pa=none The group associated with /dev/tty01 was changed from dialer to one that includes the user: $ls -l /dev/tty01 crw-rw 1 uucp wheel 8, 1 Feb 7 09:38 /dev/tty01 so, the user is already in wheel group. Revert above change. Enable sudo (if not already done so) for users in group wheel. $ sudo -u uucp tip snake --patrick uh...if all else fails, do it as root? I think we'd prefer to avoid that, unless really a root-like activity. you saw root somewhere? --patrick The dialer group is set up just for this purpose. The problem with changing the ownership (or group) of a device file is the next upgrade will overwrite your ownership change. Ask me how I know. Better idea, don't -- just use your imagination. I'm not sure why you didn't just add that user to group dialer, but it is quite straight forward: /home/nick $ grep nick /etc/group wheel:*:0:root,nick wsrc:*:9:nick dialer:*:117:nick nick:*:1000: and...I (as nick) have no trouble using my serial port without using sudo and without changing device file ownership. You will probably want to create a file /var/log/aculog which is writable by group dialer, as well... Squishes an error message, and provides some useful logging, too. Nick.
Re: request help with tip and serial port problem
On 07/12/10 21:54, patrick keshishian wrote: On Mon, Jul 12, 2010 at 6:03 PM, Nick Holland n...@holland-consulting.net wrote: On 07/12/10 19:32, patrick keshishian wrote: ... $ sudo -u uucp tip snake --patrick uh...if all else fails, do it as root? I think we'd prefer to avoid that, unless really a root-like activity. you saw root somewhere? --patrick yeah I did, but that doesn't mean it was there. :) (i.e., oops! :) Still...sudo is not needed for this process, and just adding to the group dialer may be desirable over adding to wheel Nick.
Re: PTY allocation error
On Mon, Jul 12, 2010 at 4:41 PM, Leonardo Carneiro - Veltrac lscarne...@veltrac.com.br wrote: Well, them and anyone who knows how to half-assed run nmap or any other numerous service fingerprinting utilities. Even with sshd moved, when I finally decided to block port 22, my bandwidth use dropped noticeably. You made the point: bandwidth! umm... this is *INSIDE* the corporate network. If there's anyone portscanning my box, I want to know about it, especially since I have the power to go smack hands. And if there was someone capable of breaking ssh, that person would find it no matter what port it's on. He also did some other brilliant things such as set up a boot up password, bios password and other assorted security things. Guess what happened? He didn't tell me he did it, and he forgot the passwords. He got to spend half a day in the data center rebuilding crap. -- http://www.glumbert.com/media/shift http://www.youtube.com/watch?v=tGvHNNOLnCk This officer's men seem to follow him merely out of idle curiosity. -- Sandhurst officer cadet evaluation. Securing an environment of Windows platforms from abuse - external or internal - is akin to trying to install sprinklers in a fireworks factory where smoking on the job is permitted. -- Gene Spafford learn french: http://www.youtube.com/watch?v=30v_g83VHK4
睿正7月出口退税，贸易代理服务更新
10:11:18 g ?f-#7f f e ! d8d8d;#gh?e:e#of (f ci# ece ;ge(f0ce f fg- o oe:e#ig(ce +g(o d;#gh49d=h31%h57o d;#gd?!g(h/g;g.o f6d;f1o ed?!g(h/ 500/h/ o TTf6f1 200/g, oi6h! h49g(eh.!o h/fh/7hg3;o d?!g(h//TTd8e !og e0e' TEL: 0755-33345347FAX:0755-33345343 sm...@region-trading.com e:e#ig(ch48fd;#go f2eg TEL: 0755-33345348 FAX:0755-33345344 den...@region-trading.com f71e 3e8g ?f-#h?e:e#f ie,e8 Region(Shenzhen)ImpExp Co.,Ltd. e 0e of71e 3e8gg0e :f71e d8-h7/2010e7d8 i#e$'e9f%e e : e,e8g=g+owww.region-trading.com ed8 h?0ee.9e/9f(i fe0f0o ff(d8 i e f6e0g1;di.d;6o h/7e e$ e g %o fde0f(ghg3;f9ee (eh!(d8-e i$cef f f 0o f,h/7e h0c
Re: July 10 snapshot: scambled harddisk name in dmesg
the harddisk name gets scrambled The second July 12 snapshot fixes this. Thank you! :-) Tas.
Hello
- This mail is in HTML. Some elements may be ommited in plain text. - I have a good business proposal to share with you. Thanks and Regards.
