Re: OpenBSD MetaStore: Distributed hosting?
Please take this off our lists. I am sure noone cares. Why block access to your website in an attempt to block spam? Spam harvesters? If so it's pointless, these lists are archived all over the net, your address is already out there. No, I just block netblocks because I don't care about any traffic from those countries, whose rich spectrum of bogosity is not entirely spam (though spam is a major part of it). Again, I've received enough bogus shit from these countries to not care anymore. Scorched Earth. It is _my network_, I am entitled to do this. Yet I have already said this, and grow tired of repeating myself. I have also already said that I do not intend to be the permanent sole host of this project, that it is subject to going away at any time if I cannot find another host for it, and that this is only one possible candidate solution to the problem of How to collect information about which OpenBSD hardware is supported, and how to make its purchase easier. You are entirely welcome to make _your_ _own_ solution to this problem and stick it out there if you would like. You may even use mine as a base, I will forward to you the work I have done so far and a dump of the database. I would recommend that distributed hosting be explored, however - this seems to solve _everybody's_ problem, keeping the inherent information-cleanliness of centralized control while obtaining the reliability and local convenience of a distributed network. It also causes people to not have any reason to be concerned with my network policies, and causes me to not have to worry about any innocents' being denied use of a resource they may find valuable. Perhaps I misunderstood you, was this an offer to host a copy? It's ironic that much of the hardware you're promoting is likely made in the same shitholes that should be nuked from orbit. Sounds like you need an enema. Great, they can make all the hardware they want. I still don't want to receive their network traffic. The hardware is good, sort of. The network traffic isn't. Clear? Again: Was this an offer to host a copy of the MetaStore? -- (c) 2005 Unscathed Haze via Central Plexus [EMAIL PROTECTED] I am Chaos. I am alive, and I tell you that you are Free. -Eris Big Brother is watching you. Learn to become Invisible. | Your message must be this wide to ride the Internet. |
Re: congrats on OpenBSD SAN... one little question
On 10/21/05, Bob Beck [EMAIL PROTECTED] wrote: i can certainly see how this would be annoying from a scalability standpoint, but how often are you changing user storage limits? it would, however, be most convenient to just have one huge-ass partition :). Annoying from a scalability standpoint? gimme a break. one huge filesystem is annoying from a scalablility standpoint. For what little it's worth, I'm with Bob on this. If whatever you're running *must* be on one big partition, scalability will be a pain. Once you fill the partition, you've got to expand it somehow (never a simple thing, even with PartitionMagic or whatever). If, on the other hand, your system can deal with many small partitions, making the available storage space bigger is merely a matter of adding a new partition somewhere and linking it in the right place. Even in cases where you do need more space on a partition, it's much easier to move the data to a larger partition if larger means 100 GB instead of 1 TB. -Josh Tolley
Re: OpenBSD MetaStore: Distributed hosting?
On Fri, 21 Oct 2005 21:43:11 -0800, Szechuan Death [EMAIL PROTECTED] wrote: Jason Dixon wrote: snip self-serving vitriol Good luck with that MetaStore thing. I'm sure it's going to be a huge success. Thank you, although the goal is not that it be a success for me, but rather that it will provide useful information to OpenBSD users and assistance to the OpenBSD development team in negotiating with vendors. ..this is coming from a person with an alias like yours, a visceral and vile content and the fact that no one bloody cares! Honestly mate, how the bloody hell do you get so much time? -Bruno
Re: filtering trunked Interfaces with PF
On 10/22/05, Siju George [EMAIL PROTECTED] wrote: Hi all, When I build a trunk like # ifconfig rl0 up # ifconfig rl1 up # ifconfig trunk0 create trunkport rl0 trunkport rl1 # ifconfig trunk0 192.168.1.200 netmask 255.255.255.0 up Sorry the above line should read # ifconfig trunk0 172.16.1.1 netmask 255.240.0.0 up Sorry again for being careless :-( in upcomming 3.8 release. Will I be able to use pf rules like pass in on trunk0 proto tcp from 172.16.0.0/12 to any keep state. to filter traffic through rl0 and rl1 or will I have to put rl0 rl1 on the same interface group and write the pf rule for the interface group? Thankyou so much :-) Kind Regards Siju
filtering trunked Interfaces with PF
Hi all, When I build a trunk like # ifconfig rl0 up # ifconfig rl1 up # ifconfig trunk0 create trunkport rl0 trunkport rl1 # ifconfig trunk0 192.168.1.200 netmask 255.255.255.0 up in upcomming 3.8 release. Will I be able to use pf rules like pass in on trunk0 proto tcp from 172.16.0.0/12 to any keep state. to filter traffic through rl0 and rl1 or will I have to put rl0 rl1 on the same interface group and write the pf rule for the interface group? Thankyou so much :-) Kind Regards Siju
Re: tar(1) problem with long file names.
Hello! On Fri, Oct 21, 2005 at 02:07:16PM -0500, eric wrote: It seems that tar(1) is only able to archive filenames of 100 characters or less. However, ufs can handle (I've been testing using touch(1)) filenames up to 255 characters. I tried to modify the following in src/bin/pax/tar.h It's an issue of the (us)tar data format. Especially, raising it to 255 doesn't help either, as the field encodes *path* names, and *path* names can be up to 1023 or so bytes. [...] Has anyone bumped into this and made a more reliable fix? Use a more apt data format in your use case. Ehm correcting myself: According to pax(1), 100 is the limit for pathnames in the old tar format, while the limit for ustar is 250. For *pathnames*!. Perhaps you can use cpio (or pax with -x cpio). [...] - Eric Kind regards, Hannah.
Re: memtest86
My apologies for posting to the wrong list, i'll try running from CD thanks On Saturday 22 October 2005 06:33 am, you wrote: On Friday 21 October 2005 18:07, Gareth Nelson wrote: Hi Any ideas on if this can be loaded by the OpenBSD bootloader or if it's possible to run a memory test in a booted system? (redirected to misc@ where it belongs) Sure, its possible, but why would you want to? Get the CD version of memtest and let it run on its own. If you suspect a system of bad ram let it run at least 24 hours. --STeve Andre'
DISKLESS tutorial that need feedback
http://bkw.lindesign.se/tmp/diskless.pdf Please read my step-by-step tutorial and give me feedback. I really hope it will be useful to the OpenBSD community, for those who want to setup a diskless environment. There are still some shaping left but the basics should be ready by now. /bkw -- ## BKW - Bachman Kharazmi bahkha AT gmail DOT com uin: #24089491 SWEDEN ##
Q: why is OpenBSD's openssl build without -pthread ???
Hi, Can anyone tell me why OpenBSD's openssl not build with -pthread ? I'm evaluating 'pound' SSL reverse proxy ( http://www.apsis.ch/ pound/ ), which seems to require threaded SSL libs. The OpenBSD supplied openssl seems to have threads disabled, but if I retrieve make a local copy with the -pthread complier option, it seems to build run fine. I'm sure there's a good reason for it not being enabled by default - I'm just interested to know what is it... thanks /Pete
Re: tar(1) problem with long file names.
Hannah Schroeter [EMAIL PROTECTED] wrote: Use a more apt data format in your use case. Ehm correcting myself: According to pax(1), 100 is the limit for pathnames in the old tar format, while the limit for ustar is 250. For *pathnames*!. Perhaps you can use cpio (or pax with -x cpio). Actually, it's the SVR4 cpio format (sv4cpio or the variant sv4crc) you want. 1024-char file/path names, 32-bit inode and device numbers, and even reasonably portable. -- Christian naddy Weisgerber [EMAIL PROTECTED]
Re: tar(1) problem with long file names.
Jay Fenlason [EMAIL PROTECTED] wrote: GNU tar uses a variety of ugly hacks to get around the 100 (original tar) or 255 (ustar) character limit in file and path names. Unfortunatly, only gnu tar can correctly extract such archives. Well, there are at least two independent implementations that can extract this format (star and FreeBSD's new libarchive-based tar), but yes, it is in questionable taste. -- Christian naddy Weisgerber [EMAIL PROTECTED]
Re: DISKLESS tutorial that need feedback
Bachman Kharazmi wrote: http://bkw.lindesign.se/tmp/diskless.pdf Please read my step-by-step tutorial and give me feedback. I would have pulled it up and read it right away, but it's in pdf format. Yes, I can read them, but it's enough of a pain to make it not worth it for me unless I *know* I want to read it. If you're really interested in sharing information on the internet, you might want to author at a higher level and produce pdf + html + text. If I'd read some html and wanted a nice hardcopy I'd definitely go for a pdf if available. -- Darrin Chandler [EMAIL PROTECTED] http://www.stilyagin.com/
DISKLESS tutorial that need feedback
On 10/22/05, Darrin Chandler [EMAIL PROTECTED] wrote: Bachman Kharazmi wrote: http://bkw.lindesign.se/tmp/diskless.pdf Please read my step-by-step tutorial and give me feedback. I would have pulled it up and read it right away, but it's in pdf format. Yes, I can read them, but it's enough of a pain to make it not worth it for me unless I *know* I want to read it. If you're really interested in sharing information on the internet, you might want to author at a higher level and produce pdf + html + text. If I'd read some html and wanted a nice hardcopy I'd definitely go for a pdf if available. Do not feel foced reading my doc. PDF is a portable document format widely used and accepted on the inet. Of course it would be good publishing it using latex that can convert to various formats. but this aint any essay and I don't have time/care about getting it in latex atm. If you now can read pdfs why are you complaining about that it isn't worth reading it? And I've emailed faq@ requesting a link to it from the main FAQ at openbsd.org. /bkw -- Darrin Chandler [EMAIL PROTECTED] http://www.stilyagin.com/ -- ## BKW - Bachman Kharazmi bahkha AT gmail DOT com uin: #24089491 SWEDEN ##
Re: DISKLESS tutorial that need feedback
Bachman Kharazmi wrote: On 10/22/05, Darrin Chandler [EMAIL PROTECTED] wrote: Bachman Kharazmi wrote: http://bkw.lindesign.se/tmp/diskless.pdf Please read my step-by-step tutorial and give me feedback. I would have pulled it up and read it right away, but it's in pdf format. Yes, I can read them, but it's enough of a pain to make it not worth it for me unless I *know* I want to read it. If you're really interested in sharing information on the internet, you might want to author at a higher level and produce pdf + html + text. If I'd read some html and wanted a nice hardcopy I'd definitely go for a pdf if available. Do not feel foced reading my doc. PDF is a portable document format widely used and accepted on the inet. Of course it would be good publishing it using latex that can convert to various formats. but this aint any essay and I don't have time/care about getting it in latex atm. If you now can read pdfs why are you complaining about that it isn't worth reading it? And I've emailed faq@ requesting a link to it from the main FAQ at openbsd.org. /bkw -- Darrin Chandler [EMAIL PROTECTED] http://www.stilyagin.com/ You need to keep in mind - there are those on this list that are not happy unless they are bitching about someone / something / anything. With that in mind - Bypass these dults and keep contributing. We're happy you are. -- Best regards, Chris Hindsight is an exact science.
Re: DISKLESS tutorial that need feedback
Bachman Kharazmi wrote: Do not feel foced reading my doc. PDF is a portable document format widely used and accepted on the inet. Of course it would be good publishing it using latex that can convert to various formats. but this aint any essay and I don't have time/care about getting it in latex atm. If you now can read pdfs why are you complaining about that it isn't worth reading it? And I've emailed faq@ requesting a link to it from the main FAQ at openbsd.org. /bkw I do not feel forced. But as I said, I would have read it immediately had it been in a more accessable format. Reading a PDF file forces me to use programs with cumbersome interfaces. I may end up reading your document. It does sound interesting and worthwhile. But if I do I'll be cursing PDF the whole time. Many people think PDF is nifty and cool and don't mind it a bit, but others don't like the additional hassle required. But I've never seen anyone complain about finding HTML when they follow a link. I'm not saying what you're doing is bad or wrong, but that it makes it less accessible. I'm sure that's not your goal, since you've taken the time and effort to put this together and share it. -- Darrin Chandler [EMAIL PROTECTED] http://www.stilyagin.com/
Re: tar(1) problem with long file names.
Hello! On Sat, Oct 22, 2005 at 01:43:03PM +, Christian Weisgerber wrote: Hannah Schroeter [EMAIL PROTECTED] wrote: Use a more apt data format in your use case. Ehm correcting myself: According to pax(1), 100 is the limit for pathnames in the old tar format, while the limit for ustar is 250. For *pathnames*!. Perhaps you can use cpio (or pax with -x cpio). Actually, it's the SVR4 cpio format (sv4cpio or the variant sv4crc) you want. 1024-char file/path names, 32-bit inode and device numbers, and even reasonably portable. If the plain cpio format itself isn't up to the task, perhaps the pax manual page should document its limitations. I went by the manual page and saw no mention of restrictions there for cpio, either. Still good to know about that recommendation, I might have some use for it too. Kind regards, Hannah.
Re: tar(1) problem with long file names.
Hello! On Sat, Oct 22, 2005 at 01:46:10PM +, Christian Weisgerber wrote: Jay Fenlason [EMAIL PROTECTED] wrote: GNU tar uses a variety of ugly hacks to get around the 100 (original tar) or 255 (ustar) character limit in file and path names. Unfortunatly, only gnu tar can correctly extract such archives. Well, there are at least two independent implementations that can extract this format (star and FreeBSD's new libarchive-based tar), but yes, it is in questionable taste. That libarchive thing would be interesting, perhaps as port. And support for that pax interchange format would look like an interesting addition to our pax, wouldn't it? Looks like it's a standard format, extends the ustar format and removes its limitations. Kind regards, Hannah.
OpenBSD-binary-upgrade
Hi, Since it's a few days before release I'll advertise about my upgrade-script again: It aims to make an as simple as possible upgrade. Especially the updating of /etc is made a lot simpler. From the README: MERGESLAVE: You shouldn't notice too much about mergeslave, but here is a little something about how it works: You have to have the etcXX.tgz that matches your current release. Mergeslave moves it to a backupfile name and downloads the new etcXX.tgz. After that it uppacks both files into sepperate dirs, removes files from those dirs you never want to be examined and some data-files. And then a diff is created between those dirs. After that a testrun is done to see if that patch cleanly applies to your live filesystem. The patch is applied and you are warned to merge all rejected patches, if they were created. Don't worry about loosing important data. A backup file of all replaced files is also created. Most people I have spoken are really satisfied with the way it handles the whole update. You can get it over here: http://www.xs4all.nl/~hanb/software/OpenBSD-binary-upgrade/ # Han
Security of multiple applications in chroot-ed apache
This is what I do: chrooted Apache, PHP, MySQL. User directories are in /var/www/users; softlinked to HOME/public_html. Problem: Running some php-mysql applications somewhere in /var/www/. These do work, but they need some config files containing mysql usernames and passwords for the databases. And these need at least xx4 permissions; xx0 will not permit those files to be read by apache / mysql / php. But once these have permissions of 'r' for world, the other local users can go and read those just as well; across their access to /var/www/users. Now I am looking for a pointer how to prevent that. I went through the archives and searched Google, but have no good idea on search terms in this case. TIA, Uwe
Re: Security of multiple applications in chroot-ed apache
On 10/22/05 19:57, Uwe Dippel wrote: This is what I do: chrooted Apache, PHP, MySQL. User directories are in /var/www/users; softlinked to HOME/public_html. Problem: Running some php-mysql applications somewhere in /var/www/. These do work, but they need some config files containing mysql usernames and passwords for the databases. And these need at least xx4 permissions; xx0 will not permit those files to be read by apache / mysql / php. Forgive me if I am overlooking sth obvious, but why don't you use group permissions? But once these have permissions of 'r' for world, the other local users can go and read those just as well; across their access to /var/www/users. Now I am looking for a pointer how to prevent that. I went through the archives and searched Google, but have no good idea on search terms in this case. TIA, Uwe -- Don't fix it if it ain't broke.
Re: DISKLESS tutorial that need feedback
On Sat, Oct 22, 2005 at 09:05:25PM +0200, [EMAIL PROTECTED] wrote: But I see no difference to simple ASCII-Textfiles anymore (wich are another std. imho). So just use ASCII.
Re: DISKLESS tutorial that need feedback
On 2005/10/22 21:05:25, [EMAIL PROTECTED] wrote: But I see no difference to simple ASCII-Textfiles anymore Ahh, do you know of a nice simple console-mode pdf viewer then?
Re: tar(1) problem with long file names.
On 22 October 2005, Hannah Schroeter [EMAIL PROTECTED] wrote: Hello! On Sat, Oct 22, 2005 at 01:43:03PM +, Christian Weisgerber wrote: Hannah Schroeter [EMAIL PROTECTED] wrote: Use a more apt data format in your use case. Ehm correcting myself: According to pax(1), 100 is the limit for pathnames in the old tar format, while the limit for ustar is 250. For *pathnames*!. Perhaps you can use cpio (or pax with -x cpio). Actually, it's the SVR4 cpio format (sv4cpio or the variant sv4crc) you want. 1024-char file/path names, 32-bit inode and device numbers, and even reasonably portable. If the plain cpio format itself isn't up to the task, perhaps the pax manual page should document its limitations. I went by the manual page and saw no mention of restrictions there for cpio, either. Still good to know about that recommendation, I might have some use for it too. See also the classical articles by Elizabeth Zwicky: http://berdmann.dyndns.org/doc/dump/zwicky/testdump.doc.html http://www.usenix.org/events/lisa03/tech/full_papers/zwicky/zwicky_html/ Regards, Liviu Daia -- Dr. Liviu Daia e-mail: [EMAIL PROTECTED] Institute of Mathematics web page: http://www.imar.ro/~daia of the Romanian Academy PGP key: http://www.imar.ro/~daia/daia.asc
Re: OpenBSD MetaStore: Distributed hosting?
A brief recap of the Which SATA controller to purchase thread, OpenBSD Hardware Sales thread, and all the MetaStore threads: -user asks misc@ which hardware to purchase for OBSD 3.Y. The user wants to know how to match supported chipsets with actual products. -the list says, Gee, wouldn't it be swell if we had a system for tracking which hardware worked on a given OBSD release. Theo tells the list his time is too precious to waste building such a system (and I agree). He repeatedly says, You can do this. -SZECHUAN ACTUALLY DOES IT!! ( I think this the mythical Step 3: on /. ) -OBSD users nitpick the creator (and NOT the work) rather than help improve the resource. Despite repeated attempts to give his work to the community, Szechuan is persecuted for being a network admin fascist (which he is- the same goes for all of you who straight drop packets from Linux boxes). This whole situation is very sad. Without wasting the devs effort for a single line of code, a goose which is 80% of the way to laying golden eggs will get scrapped because few of you have even a shred of tact or grace. This MetaStore could be a very nice stream of revenue for the project (not to mention the untold satisfaction it will give when we can just post it's URL in response to stupid questions about hardware) if only everyone could put their egos aside and just use the resource and help. I am NOT saying the devs should waste any time working on this. I'm saying members of the community who have web dev experience (a few of you already stepped up in previous threads), should help polish off the store. The project should host it when it begins collecting revenue from referrals. Why can't we ALL win??
Re: OpenBSD MetaStore: Distributed hosting?
2005/10/22, Jurvis LaSalle [EMAIL PROTECTED]: snip I totally agree!
Re: DISKLESS tutorial that need feedback
Please STOP the discussion about document formats in this thread. You're taking my time complaing on the document format (pdf). In my first post I wrote that I want feedback on the document and nothing else. If your computer can't run any pdf reader that's your problem. So please stop asking if I can make any HTML or other formats. |ber und aus /bkw On 10/22/05, Bachman Kharazmi [EMAIL PROTECTED] wrote: http://bkw.lindesign.se/tmp/diskless.pdf Please read my step-by-step tutorial and give me feedback. I really hope it will be useful to the OpenBSD community, for those who want to setup a diskless environment. There are still some shaping left but the basics should be ready by now. /bkw -- ## BKW - Bachman Kharazmi bahkha AT gmail DOT com uin: #24089491 SWEDEN ##
Re: DISKLESS tutorial that need feedback
1 - Perhaps it is better to produce the document in a standard format in order to get feedback from the greatest number of people (not a flame, just a suggestion). I recommend you convert it to plain ASCII when you get the chance, should be a fairly simple copy and paste job and then add section numbers etc 2 - About the document content itself: I had a brief read over it, what I found missing was using seperate filesystems for each client. Ideally, you'd have a seperate subdirectory on your diskless server for the root of each client, and possibly do a hardlink to /bin etc to avoid redundancy. I would recommend the following structure: /usr/local/diskless/clienta /usr/local/diskless/clientb etc etc /usr/local/diskless/clienta/bin -- /bin /usr/local/diskless/clienta/usr/bin - /usr/bin you get the idea On Saturday 22 October 2005 10:44 pm, Bachman Kharazmi wrote: Please STOP the discussion about document formats in this thread. You're taking my time complaing on the document format (pdf). In my first post I wrote that I want feedback on the document and nothing else. If your computer can't run any pdf reader that's your problem. So please stop asking if I can make any HTML or other formats. |ber und aus /bkw On 10/22/05, Bachman Kharazmi [EMAIL PROTECTED] wrote: http://bkw.lindesign.se/tmp/diskless.pdf Please read my step-by-step tutorial and give me feedback. I really hope it will be useful to the OpenBSD community, for those who want to setup a diskless environment. There are still some shaping left but the basics should be ready by now. /bkw -- ## BKW - Bachman Kharazmi bahkha AT gmail DOT com uin: #24089491 SWEDEN ##
3.8 japanese
Hi all , i am a japanese , and i run openbsd3.8 (snapshot) on pentium4 1.5G .
i have no stress using kde on this machine and i can use japanese in jvim .
but i hava some defects .
1) i cannot use canna , so i use Wnn ( namely jserver) .
2) i can write japanese only in jvim ( i run jvim on kterm on konsole ) ,
so i copy japanese words in jvim to konqueror.
3) i hope openbsd will use uim anthy which is commonly used in LINUX
japanese input method (this is not kanji-server type).
i also make /etc/X11/xorg.conf with Xorg-configure(on
/usr/X11R6/bin) .
but my keyboard is made in japan , so some corrections are needed .
in /etc/X11/xorg.conf
-
Section InputDevice
Identifier Keyboard0
Driver kbd
Option XkbModel jp106
Option XkbLayout jp
EndSection
Section InputDevice
Identifier Mouse0
Driver mouse
Option Protocol wsmouse
Option Device /dev/wsmouse
Option ZAxisMapping 4 5
EndSection
Section Screen
Identifier Screen0
Device Card0
MonitorMonitor0
DefaultDepth 16
SubSection Display
Viewport 0 0
Depth 1
EndSubSection
SubSection Display
Viewport 0 0
Depth 4
EndSubSection
SubSection Display
Viewport 0 0
Depth 8
EndSubSection
SubSection Display
Viewport 0 0
Depth 15
EndSubSection
SubSection Display
Viewport 0 0
Modes 1024x768 640x480
Depth 16
EndSubSection
SubSection Display
Viewport 0 0
Depth 24
EndSubSection
EndSection
---
i install mainly kde packages with pkg_add -v
ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/i386/kdebase-3.4.3.tgz
and so on .
i write down some important files .
1) /etc/hosts
::1 localhost.nakajin.dyndns.org localhost
127.0.0.1 localhost.nakajin.dyndns.org localhost
127.0.0.1 localhost.nakajin.dyndns.org jserver
::1 p4.nakajin.dyndns.org p4
192.168.72.66 p4.nakajin.dyndns.org p4
2)/home/tuyosi/.bashrc --- i use bash .
export LANG=ja_JP.eucJP
export XMODIFIERS=@im=kinput2
# /etc/skel/.bashrc:
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/skel/.bashrc,v 1.8
2003/02/28 15:45:35 azarah Exp $
# This file is sourced by all *interactive* bash shells on startup. This
# file *should generate no output* or it will break the scp and rcp commands.
# colors for ls, etc.
eval `dircolors -b /etc/DIR_COLORS`
alias d=ls --color
alias ls=ls --color=auto
alias ll=ls --color -l
# Change the window title of X terminals
case $TERM in
xterm*|rxvt|Eterm|eterm)
PROMPT_COMMAND='echo -ne \033]0;[EMAIL
PROTECTED]:${PWD/$HOME/~}\007'
;;
screen)
PROMPT_COMMAND='echo -ne [EMAIL
PROTECTED]:${PWD/$HOME/~}\033\\'
;;
esac
##uncomment the following to activate bash-completion:
#[ -f /etc/profile.d/bash-completion ] source /etc/profile.d/bash-completion
3) /home/tuyosi/.xinitrc
#!/bin/bash
export LANG=ja_JP.eucJP
export XMODIFIERS=@im=kinput2
kinput2 -wnn
startkde
4)pkg_info
OpenEXR-1.2.2p1 high dynamic range image format
Wnn-data-4.2common files to all languages of Wnn
arts-1.4.3 K Desktop Environment, aRTs
aspell-0.50.5p1 spell checker designed to eventually replace Ispell
bash-3.0.16p1 GNU Bourne Again Shell
bzip2-1.0.3 block-sorting file compressor, unencumbered
cdparanoia-3.a9.8 CDDA reading utility with extra data verification features
cyrus-sasl-2.1.20p4 RFC SASL (Simple Authentication and Security Layer)
esound-0.2.34 sound library for Enlightenment
expat-1.95.6XML 1.0 parser written in C
flac-1.1.2 free lossless audio codec
gettext-0.10.40p3 GNU gettext
glib-1.2.10p0 useful routines for C programming
glib2-2.6.4 general-purpose utility library
gnupg-1.4.1p0 GNU privacy guard - a free PGP replacement
gpgme-1.0.2p0 GnuPG Made Easy
gstreamer-0.8.10GStreamer streaming media framework runtime
gtk+-1.2.10p3 General Toolkit for X11 GUI
ja-Wnn-4.2p1Japanese input method
ja-Wnndict-4.2p0dictionaries for Japanese Wnn
ja-jvim-2.0rp0-wnn Japanized Vim, wnn input method
ja-kinput2-3.0-wnn X input method for Japanese, wnn support
ja-kterm-6.2.0p2Japanese-capable xterm
ja-less-3.32p2.48 less + zcat + ISO-2022 - a pager similar to more and pg
ja-onew-wnn4-2.2.10 library for Japanese Input Method Wnn4
jasper-1.701.0 reference implementation of JPEG-2000
jpeg-6bp2 IJG's JPEG compression utilities
kde-i18n-ja-3.4.3 ja translations for KDE
kdeaddons-3.4.3 K Desktop Environment,
Re: DISKLESS tutorial that need feedback
Bachman Kharazmi wrote: Please STOP the discussion about document formats in this thread. You're taking my time complaing on the document format (pdf). In my first post I wrote that I want feedback on the document and nothing else. If your computer can't run any pdf reader that's your problem. So please stop asking if I can make any HTML or other formats. |ber und aus /bkw On 10/22/05, Bachman Kharazmi [EMAIL PROTECTED] wrote: http://bkw.lindesign.se/tmp/diskless.pdf Please read my step-by-step tutorial and give me feedback. I really hope it will be useful to the OpenBSD community, for those who want to setup a diskless environment. There are still some shaping left but the basics should be ready by now. /bkw -- ## BKW - Bachman Kharazmi bahkha AT gmail DOT com uin: #24089491 SWEDEN ## I have read your tutorial, and I think it's well written, concise, and should be quite useful. It's always nice to see easy to read step-by-step instructions like this. I have some boxes with net boot capability and I might give it a try. If I do, and I run into any problems with your instructions I'll send you a note. Regards, Darrin Chandler -- Darrin Chandler [EMAIL PROTECTED] http://www.stilyagin.com/
Re: DISKLESS tutorial that need feedback
On Sat, Oct 22, 2005 at 10:13:06PM +0100, Stuart Henderson wrote: On 2005/10/22 21:05:25, [EMAIL PROTECTED] wrote: But I see no difference to simple ASCII-Textfiles anymore Ahh, do you know of a nice simple console-mode pdf viewer then? try pdftotext, it's in the xpdf package. Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Re: DISKLESS tutorial that need feedback
On 10/23/05, Gareth Nelson [EMAIL PROTECTED] wrote: 1 - Perhaps it is better to produce the document in a standard format in order to get feedback from the greatest number of people (not a flame, just a suggestion). I recommend you convert it to plain ASCII when you get the chance, should be a fairly simple copy and paste job and then add section numbers etc ... 2 - About the document content itself: I had a brief read over it, what I found missing was using seperate filesystems for each client. Ideally, you'd have a seperate subdirectory on your diskless server for the root of each client, and possibly do a hardlink to /bin etc to avoid redundancy. I would recommend the following structure: /usr/local/diskless/clienta /usr/local/diskless/clientb etc etc /usr/local/diskless/clienta/bin -- /bin /usr/local/diskless/clienta/usr/bin - /usr/bin you get the idea yes I do. The whole root for every client vill be approx 50Mb so there's no need to mount /bin also. But sure, it's possible. You know where stuff will be placed if I install _any_ pkg on the server... /bkw
pxeboot halting...
Hello list, help for the following problem would be greatly
appreciated, it's so frustrating.
Trying to pxeboot 3.7 on an EPIA machine with what Linux is reporting
to be a Centaur VIA Samuel 2 stepping 03 processor. The server is a
mac with os 10.4, here is the /etc/dhcpd.conf:
allow booting;
allow bootp;
ddns-update-style none;
shared-network LOCAL-NET {
subnet 192.168.1.0 netmask 255.255.255.0 {
option routers 192.168.1.88;
option root-path /tftpboot;
filename pxeboot;
range 192.168.1.32 192.168.1.52;
default-lease-time 86400;
max-lease-time 9;
}
}
The directory /tftpboot has the files pxeboot and bsd.rd and tftpd
has been verified to transfer files correctly. The EPIA machine is
pushed the pxeboot file and the usual prompt appears, so I type
bsd.rd and the spinning pipe character stays vertical and doesn'r move.
after a wait of around 1 minute the number 4302596 appears, about a
30 second wait then the following text appears:
read text: Unknown error: code 60
failed(60). will try /bsd.old
Perhaps I should copy the file bsd.old into the tftpboot directory
but I cannot find such a file.
Can anyone help me, I have attempted googling but not found much,
Any solution and I promise to submit my dmesg! - what an incentive :(
thanks in advance
poncenby
Re: pxeboot halting...
On 10/23/05, poncenby smythe [EMAIL PROTECTED] wrote: option root-path /tftpboot; IIRC, this isn't what pxeboot(8) advises you to do. Why are you entering a root path to be found at what seems to be a TFTP location? Specifying a root disc location would seem to be more appropriate for a setup described such as in diskless(8). If you're trying to obtain the bsd.rd kernel through TFTP - e.g. to install a new system over the network - you're probably better off creating an approprate boot.conf(5) file on the TFTP server location. Something to the likes of creating /tftpboot/etc/boot.conf with settings similar to boot tftp:/bsd.rd. At least, that's the way it works for me. Unless of course, I'm entirely wrong on guessing your intended functionality, which I could not find in your original message. Cheers, Rogier -- If you don't know where you're going, any road will get you there.
Re: 3.8 japanese
On Sun, Oct 23, 2005 at 07:20:23AM +0900, OS rider wrote: Hi all , i am a japanese , and i run openbsd3.8 (snapshot) on pentium4 1.5G . i have no stress using kde on this machine and i can use japanese in jvim . but i hava some defects . 1) i cannot use canna , so i use Wnn ( namely jserver) . 2) i can write japanese only in jvim ( i run jvim on kterm on konsole ) , so i copy japanese words in jvim to konqueror. 3) i hope openbsd will use uim anthy which is commonly used in LINUX japanese input method (this is not kanji-server type). Happy to have you aboard. o tanoshimi ni! international support has seen some progress in OpenBSD 3.8. We're hopefully going to have utf8, jis, euc, and sjis support in the near future. I've been using wnn + jvim in the past as well, I haven't figured out what's missing with respect to modern X input methods yet... kinput2 doesn't appear to work. If you want `uim anthy' supported on OpenBSD in the future, let's start by giving us a www address for it... I don't know all japanese software, unfortunately.
Re: DISKLESS tutorial that need feedback
Gareth Nelson wrote: 2 - About the document content itself: I had a brief read over it, what I found missing was using seperate filesystems for each client. Ideally, you'd have a seperate subdirectory on your diskless server for the root of each client, and possibly do a hardlink to /bin etc to avoid redundancy. Well, except that hard links are filesystem specific, you can't cross filesystem boundaries with one. Also, depending on design, you probably actually want a single RO filesystem to serve as / for all diskless clients, and have smaller per-client RW volumes (like /etc) or per-user RW volumes (so each machine is identical and everyone can use each machine). -- Matthew Weigel hacker [EMAIL PROTECTED]
Re: DISKLESS tutorial that need feedback
To be honest, i've never used hardlinks/symlinks with NFS, so I wasn't aware this was a problem (I have used mount_nullfs on FreeBSD, and was thinking about this at the time I posted). The idea of having a seperate RW filesystem for each client as opposed to having several with the full root probably solves this in a much more elegant way. Export /usr, /bin etc as RO and /home, /etc and others as RW. On Sunday 23 October 2005 12:27 am, Matthew Weigel wrote: Gareth Nelson wrote: 2 - About the document content itself: I had a brief read over it, what I found missing was using seperate filesystems for each client. Ideally, you'd have a seperate subdirectory on your diskless server for the root of each client, and possibly do a hardlink to /bin etc to avoid redundancy. Well, except that hard links are filesystem specific, you can't cross filesystem boundaries with one. Also, depending on design, you probably actually want a single RO filesystem to serve as / for all diskless clients, and have smaller per-client RW volumes (like /etc) or per-user RW volumes (so each machine is identical and everyone can use each machine).
Re: 3.8 japanese
Hi , Marc Espie . your message is very kind and you give us japanese a lot of encouragement . it is a pity that i myself cannot read program , so i cannot any contribution to japanese input method programming . i merely write down some infometion next . - uim is here , and this is a english www page . http://uim.freedesktop.org/wiki/UimDownload anthy is here , and it is sorrry that this page is written by japanese . Anthy is a system for Japanese input method. It converts Hiragana text to Kana Kanji mixed text http://sourceforge.jp/projects/anthy/files/ -- HomePage : nakajin.dyndns.org Mail: [EMAIL PROTECTED] Each for All All for One
Re: Security of multiple applications in chroot-ed apache
On Sat, 22 Oct 2005 20:48:40 +0200, Philip S. Schulz wrote: Forgive me if I am overlooking sth obvious, but why don't you use group permissions? The current ownership of /var/www/users/foo/ is foo:daemon I was following some older post here on 'how to handle UserDirs in chrooted Apache'. I didn't dare to chgrp www /var/www/users/foo. But come to think of it, it might be the thing to do. Still, zope, mysql and clamav are in group daemon. Therefore: add www to group daemon ? Come to think of it, it might be the only thing to do. On the other hand, do I want to make the unprivileged user www member of daemon ? I welcome your comments on security implications ! Thanks for the plenty off-line mails, I hope this post answers some as well. I want to roll out wordpress (http://wordpress.org) to 150 users. Wordpress requires individual installs (don't argue with me, argue with the chaps of wordpress). So I put these into /var/www/users/foo/blog. In these dirs, everyone needs a config file containing the mysql details. This file itself is blank from remote; therefore safe. But locally, it is accessible. Of course, I tried to chmod it to 640 (by default it is 644), but then the blog renders to blank pages only, and that's not what a blog is for. A similar thing might apply to phpMyAdmin. And then we might want to write some advice into the post-install message(s). So far I followed these by the point but have yet to came across a hint on this, and on security in case of UserDirs. Uwe
Re: OpenOffice.org 2.0 works on OpenBSD
On Thu, 20 Oct 2005 19:47:43 -0400, Roy Morris wrote: Confirmed! Works on 3.7-stable. There were a few items which you may or may not want to include in your blog, If your interested let me know I'll send them to you. Go ahead, share them with us, please, as well. Some are looking forward to get OpenOffice to work and if you found a few items worth noting to that behalf, help us. Uwe
Re: iptables vs pf
Roger Neth Jr [EMAIL PROTECTED] writes: and it was okay on response. Then I redid my pf.conf with the tutorial by Jeff Hansteen posted a couple of days ago. It's Peter, not Jeff, but I'm very happy to hear you found the tutorial useful. Wow! what a difference. My DEC firewall is faster than snot loading up web pages. PF is fast, with very low overhead, in my experience, and the most user(admin) friendly firewall I've ever encounter. I'm a bit surprised you got a noticeable speedup by following the rather basic advice in the tutorial. Then again, just keeping it all simple may help in that respect. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/ First, we kill all the spammers The Usenet Bard, Twice-forwarded tales
