There were a few other places where I noticed (long time ago, but I've
now written it all down) somewhat strange messages:
mkdir / gives:
mkdir: /: Is a directory
whereas mkdir /usr gives:
mkdir: /usr: File exists
Is this a bug in the kernel to return EISDIR in case of "/" or is
Alfred Perlstein wrote:
[ mkdir ]
> I'll commit the patch shortly.
Here's a better patch, it checks for multiple slashes, so mkdir
/tmp/aa///bb will give:
mkdir: /tmp/aa: No such file or directory
Also, renamed the function to dirname as it does the same as dirname(1).
Regards,
Wouter
Alfred Perlstein wrote:
> > 1. a pppd patch which sends the pppd messages to stderr.
>
> not sure about this one, I would open a PR about it.
I'm not sure either :) Maybe everyone else uses gui frontend which reads
pppd's syslog messages or starts pppd as root?
> Ok, I may be misreading this, b
L.S.
Here are two patches I've been using for a while on both 3.3R and 4.1R:
1. a pppd patch which sends the pppd messages to stderr.
This is useful for dialup connections under X (I use a script to startup
pppd, when the script is killed, so is pppd). Now the pppd startup
messages are sent to
L.S.
Update on previous mail a while back. I tried the latest sym driver from
the CVS tree (into fbsd 3.3) but little has changed (haven't checked
what happens with 640MB 2048 b/s disks yet):
> 4. Formatting ufs on fbsd:
> newfs hangs (unkillable).
This now works.
> 3. ufs disk formatted on ob
L.s.
small addendum:
- it's fbsd 3.3R on i386 as you may have guesssed from the mail headers.
- I use the new fbsd symbios/ncr scsi driver (the README says latest
revision is sym-0.12.0-19991127).
Also my mail address is [EMAIL PROTECTED], reply on the previous mail will
give spaces in the mail
L.S.
(the following is on fbsd 3.3 R)
I tried use 2048 bytes/sector MO media recently, but it doesn't work.
Disklabel complains about /boot/boot2 being to large or something.
It seems to have worked (more or less) up until 3.1 as I saw a few posts
in the SCSI list, e.g.
> From: "Kenneth D. Merr
Christian Weisgerber wrote:
>
> Ollivier Robert <[EMAIL PROTECTED]> wrote:
>
> > > > As there isnt a dutch keymap for syscons,
> > > ^
> > > That's an acute accent (the same diacritic as in ''), not an
> > > apostrophe.
> >
> > In 8859-1 yes but not in 8859-15 (aka Latin9)...
>
>
L.S.
As there isn´t a dutch keymap for syscons, I made one (iso8859-1) but
I´m having some problems. First, how do I enable/use dead keys? (which
look like they´re being defined in the standard map, a dump of the
defaults gives e.g. this line
dced 184 ( 'c' 231 ) ( 'C' 199 )
)
Secondly, t
L.S.
Here are patches for FreeBSD's ls (from version 3.3 release) and
OpenBSD's ls (version 2.6, didn't actually test this obsd patch as I'm
working on a FreeBSD machine at the moment).
What it does is add an option (yes another one) to sort alpha & numeric
separately, i.e. instead of something
Kenneth D. Merry wrote:
> In general, the stock NCR driver isn't being actively maintained, and your
> problem could be the result of a bug in the driver, or some problem with
> your MO drive. It's hard to say for sure. Gerard's driver is actively
> maintained, though, so if you still have prob
11 matches
Mail list logo