Re: ftpd weirdness; CWD/RETR/... handles {} specially?
Eugene M. Kim [EMAIL PROTECTED] wrote: It depends on the case; in my situation, I'm mirroring quite a large collection of files whose names are just wild, i.e. all sorts of special characters embedded, some of them being shell metacharacters. Note that shell globbing is only performed on LIST. I just tried -- CWD and RETR don't expand them. If mirror has a problem mirroring such files with meta- characters, then mirror has a bug. It works fine using omi (ports/ftp/omi). Regards Oliver PS: Please DO NOT continue to ignore my Reply-To headers. Send to the list, not to myself. Thanks. -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ftpd weirdness; CWD/RETR/... handles {} specially?
On Sun, Jul 08, 2001 at 05:33:23PM +0200, Oliver Fromme wrote: Eugene M. Kim [EMAIL PROTECTED] wrote: It depends on the case; in my situation, I'm mirroring quite a large collection of files whose names are just wild, i.e. all sorts of special characters embedded, some of them being shell metacharacters. Note that shell globbing is only performed on LIST. I just tried -- CWD and RETR don't expand them. They do. Please see the transcript, taken on a recent 4-stable machine, at the end of this message. If mirror has a problem mirroring such files with meta- characters, then mirror has a bug. It works fine using omi (ports/ftp/omi). Mirror is what I first suspected too, so I examined it; it is fine. PS: Please DO NOT continue to ignore my Reply-To headers. Send to the list, not to myself. Thanks. Okay. Sorry. Eugene --- cut here --- the-7 00:48:46 hanirc $ 50 ftp -d 127.0.0.1 Connected to 127.0.0.1. 220 the-7.net FTP server (Version 6.00LS) ready. Name (127.0.0.1:ab): test --- USER test 331 Password required for test. Password: --- PASS 230 User test logged in. --- SYST 215 UNIX Type: L8 Version: BSD-199506 Remote system type is UNIX. Using binary mode to transfer files. ftp cd /roo? --- CWD /roo? 250 CWD command successful. ftp pwd --- PWD 257 /root is current directory. ftp dir ? --- PORT 127,0,0,1,193,69 200 PORT command successful. --- LIST ? 150 Opening ASCII mode data connection for '/bin/ls'. -rwxr-xr-x 1 ab user 497 Dec 20 2000 p 226 Transfer complete. ftp get ? local: ? remote: ? --- TYPE I 200 Type set to I. --- SIZE ? 213 497 --- PORT 127,0,0,1,193,70 200 PORT command successful. --- RETR ? 150 Opening BINARY mode data connection for 'p' (497 bytes). 100% |**| 497 00:00 ETA 226 Transfer complete. 497 bytes received in 0.00 seconds (1.66 MB/s) --- MDTM ? 213 20001219211442 ftp --- cut here --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Jail issues with -STABLE
Hi, On Sun, Jul 08, 2001 at 05:24:30PM +0200, Oliver Fromme wrote: Try »ssh -v ...« to get verbose output. Then you can see where exactly it hangs. I guess it tries to make a reverse DNS lookup. Do you have DNS configured correctly inside the jail? # ssh -v -p 2022 [EMAIL PROTECTED] SSH Version OpenSSH_2.3.0 [EMAIL PROTECTED] 20010321, protocol versions 1.5/2.0. Compiled with SSL (0x0090601f). debug: Reading configuration data /etc/ssh/ssh_config debug: ssh_connect: getuid 0 geteuid 0 anon 0 debug: Connecting to (null) [10.0.0.137] port 2022. (then it hangs here...) When I try and ssh to localhost I get a line like: # ... debug: Connecting to localhost [127.0.0.1] port 22. debug: Allocated local port 1016. debug: Connection established. So it does appear that it is not resolving the hostname. I have the ip address 10.0.0.137 mapped to the name, 'atlas' in /etc/hosts, evidently this is not enough. Inside the jail the hostname is also 'atlas' and resolves to 10.0.0.137 as well. Is there something else I need to do? Regards Oliver Thanks! Dominic Marks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Headsup: Tcp ISN generation changes from 4.2 to 4.3
However, your patches do not apply cleanly to a 4.3-RELEASE system... are these meant for 4.3-STABLE only? Use this on 4.3-RELEASE only: That's great! Thanks for taking the time to make a 4.3-RELEASE patch... it's much appreciated. Hopefully, this will happen to be the cause of my strange problems... - Dave Rivers - -- [EMAIL PROTECTED]Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ftpd weirdness; CWD/RETR/... handles {} specially?
Eugene M. Kim [EMAIL PROTECTED] wrote: On Sun, Jul 08, 2001 at 05:33:23PM +0200, Oliver Fromme wrote: Note that shell globbing is only performed on LIST. I just tried -- CWD and RETR don't expand them. [...] ftp cd /roo? --- CWD /roo? 250 CWD command successful. ftp pwd --- PWD 257 /root is current directory. I get this: ftp cd /roo? --- CWD /roo? 550 /roo?: No such file or directory. (There is, of course, a directory /root.) This is the ftpd(8) from 4.3-Release. If the behaviour changed in 4-stable after 4.3-Release, then that's a serious incopatibility indeed. It should be backouted immediately. In particular, globbing upon RETR is _definitely_ not the job of the server. That's what the clients' mget command is for (which sends an NLST, then performs globbing on the client side, and then uses RETR to get the actual files). Globbing upon CWD could be subject to discussion, but at least it should be an option that defaults to off. Regards Oliver -- Oliver Fromme, secnetix GmbH Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. All that we see or seem is just a dream within a dream (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: XFS (was: ReiserFS (was: JFS (was: The FreeBSD core team needs your help)))a
On Sun, Jul 08, 2001 at 10:02:27AM -0400, Matthew Emmerton wrote: So why don't we get a FreeBSD port of XFS done real soon now, see what kind of kernel mods we have to make, and talk nice to the SGI folks? If they're running into brick walls at every turn on the Linux path, why don't we make the FreeBSD path look like the yellow brick road? It may be a great way to get some SGI resources headed the way of FreeBSD. Great idea! Why don't you go do it? I would, but since I currently work for IBM, it's not going to happen. (Under the terms of my current IP agreement with IBM, if I port XFS to FreeBSD, IBM will own the FreeBSD XFS port -- something I doubt SGI would be happy about. Believe me, I hate my IP agreement and want to change it, but I don't have the $$ for lawyers right now.) -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: ftpd weirdness; CWD/RETR/... handles {} specially?
On Sun, Jul 08, 2001 at 06:50:05PM +0200, Oliver Fromme wrote: Eugene M. Kim [EMAIL PROTECTED] wrote: On Sun, Jul 08, 2001 at 05:33:23PM +0200, Oliver Fromme wrote: Note that shell globbing is only performed on LIST. I just tried -- CWD and RETR don't expand them. [...] ftp cd /roo? --- CWD /roo? 250 CWD command successful. ftp pwd --- PWD 257 /root is current directory. I get this: ftp cd /roo? --- CWD /roo? 550 /roo?: No such file or directory. (There is, of course, a directory /root.) This is the ftpd(8) from 4.3-Release. If the behaviour changed in 4-stable after 4.3-Release, then that's a serious incopatibility indeed. It should be backouted immediately. It is strange. There's nothing related to the problem committed to 4-stable after 4.3-release (according to the cvsweb on www.freebsd.org). In particular, globbing upon RETR is _definitely_ not the job of the server. That's what the clients' mget command is for (which sends an NLST, then performs globbing on the client side, and then uses RETR to get the actual files). Globbing upon CWD could be subject to discussion, but at least it should be an option that defaults to off. At this moment, the globbing feature does almost nothing that the globbing itself was intended for; it just returns the `550 ambiguous' error when more than one entry match the glob pattern, e.g. CWD /*. After all, a single RETR/STOR/CWD command is designed to be used on a single file or directory. IMO the globbing can be thought as nothing other than a convenient shorthand (i.e. we can do /usr/src/sbin/merge*), and if it is the only reason I'd say we move the globbing feature entirely to the client side. And actually the globbing is done at the yacc level so *all* on-the-wire pathnames are subject to globbing (see the pathstring-to-pathname production in ftpcmd.y), which is just gross. Eugene To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: JFS
Dag-Erling Smorgrav wrote: Dave Uhring [EMAIL PROTECTED] writes: I just took a look at www.sistina.com and a web site which has its font set to Arial is suspect, IMHO. If they have to use Microsoft products to produce a web site.. Is that the best you could come up with? I mean, you could criticize the ingenuity of their designs, or the quality of their code, or their ability to deliver on their promises - or would that require too much effort? It's so much easier to just dismiss them out of hand because they use a font you don't like on their web page, isn't it? Generally, this is what most people do. I'm not defending Dave, or supporting DES. But many people judge a company by such first appearances. I know people who will dismiss a company as amatuer by the quality of their product packaging. I know my opinion of Wind River has been negatively impacted by the numerous spelling errors I found on their web site the first time I visited. Web pages that only display in M$ browsers also make me feel uncomfortable with a company. and _assuming_ that everyone will have a font just because it comes with Windows falls into that category. On the flip side, the Sistina page displays well even though I don't have that font, so _I_ wasn't put off by it. Other aspects of the page design made me decide not to read further into it, however. (primarily the diffucult-to-read blue on black text on the nav column) -Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: JFS
On Sat, Jul 07, 2001 at 08:35:35PM -0500, Dave Uhring wrote: You seem to have missed the critical point of that paper. When the system goes completely haywire and either crashes or locks up so hard that a manual reset is required, UFS/softupdates requires a substantial amount of time to run fsck. Background fsck is now working in -current, which means that when your system boots you don't have to fsck the disk immediately. It seems to work just fine for me so far. If you have a very large filesystem, you then have to wait until fsck completes. I believe that giving the right options to newfs can significantly reduce fsck times too. There's notes on it in the new tuning man page. I use logging on Solaris and XFS on Linux and have tried reiserfs on Linux. All are superior to UFS/softupdates when the going gets tough. Disk access times may or may not be comparable with UFS/softupdates, but the integrity of my filesystems is more important than raw speed. AFAIK Softupdates shouldn't be any less carefull with your data than journaling, providing the application calls fsync. One advantage might be that data is written to the disk twice, which means if one bit of the disk goes bad you might be able to find it elsewhere. (Mind you, I guess RAID is the right way to do that sort of thing.) I dunno which is harder to impliment right - journaling or softupdates. This may actually be the issue which determines the safety of your data. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
bogus undefined symbol from ld-elf.so.1 in kde2 programs
I cvsuped to 4.3-STABLE a few days ago, and am in the process of making the kde2 port(s). Quite a few of the programs fail as follows: $ kword /usr/libexec/ld-elf.so.1: /usr/local/lib/libksycoca.so.4: Undefined symbol comment__C18KDEDesktopMimeTypeRC7QStringb $ nm /usr/local/lib/libksycoca.so.4 | grep \ comment__C18KDEDesktopMimeTypeRC7QStringb 00030580 T comment__C18KDEDesktopMimeTypeRC7QStringb $ Has anyone else seen behaviour like this? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: XFS (was: ReiserFS (was: JFS (was: The FreeBSD core team needsyour help)))a
On Sun, 8 Jul 2001, Matthew Emmerton wrote: So why don't we get a FreeBSD port of XFS done real soon now, see what kind of kernel mods we have to make, and talk nice to the SGI folks? If they're running into brick walls at every turn on the Linux path, why don't we make the FreeBSD path look like the yellow brick road? It may be a great way to get some SGI resources headed the way of FreeBSD. I asked about this before... SGI isn't keen on Sun, Microsoft, IBM et al leeching its intellectual property, so while the developers like the idea, the lawyers are dead against it. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: JFS
On Sun, 8 Jul 2001, Bill Moran wrote: I know my opinion of Wind River has been negatively impacted by the numerous spelling errors I found on their web site the first time I visited. That's different though -- one person rubbishes the product because the presentation uses a Politically Incorrect typeface, whereas you (quite rightly) assume that if they can't be bothered to run a spelling checker over their Web page, their quality control is somewhat suspect... -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: XFS (was: ReiserFS (was: JFS (was: The FreeBSD core team needsyour help)))a
Juha Saarinen wrote: On Sun, 8 Jul 2001, Matthew Emmerton wrote: So why don't we get a FreeBSD port of XFS done real soon now, see what kind of kernel mods we have to make, and talk nice to the SGI folks? If they're running into brick walls at every turn on the Linux path, why don't we make the FreeBSD path look like the yellow brick road? It may be a great way to get some SGI resources headed the way of FreeBSD. I asked about this before... SGI isn't keen on Sun, Microsoft, IBM et al leeching its intellectual property, so while the developers like the idea, the lawyers are dead against it. Is it possible to have such filesystem compiled as a module to sidestep licensing issues? -- C-YA Jon http://www.witchspace.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: JFS
Juha Saarinen wrote: On Sun, 8 Jul 2001, Bill Moran wrote: I know my opinion of Wind River has been negatively impacted by the numerous spelling errors I found on their web site the first time I visited. That's different though -- one person rubbishes the product because the presentation uses a Politically Incorrect typeface, whereas you (quite rightly) assume that if they can't be bothered to run a spelling checker over their Web page, their quality control is somewhat suspect... True, as I pointed out later in my previous post: On the flip side, the Sistina page displays well even though I don't have that font, so _I_ wasn't put off by it. -Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
