blubee blubeeme wrote (2018/01/14):
> if you first run the mount_msdosfs command as root, it'll load the locale
> settings just fine.
> If you logout or reboot and try to call mount_msdosfs -L [locale] as a
> regular user;
> The command will fail.
If you have kiconvtool already installed and userm
Hello,
since 1.557 in cvs:main/CVSROOT/modules, there are three duplicate keys:
# egrep -w "(fib|libpanel|rain)" modules.1.557 | sort
fib ports/devel/fib
fib src/usr.bin/fib
libpanelports/x11/libpanel
libpanelsrc/lib/libpanel
rainports/securit
Garance A Drosihn wrote (2002/02/06):
> Anything else I should check? I realize there's about a million
> differences between the two branches, and there might also be
> something about my machine's setup which is a major culprit here.
> I'm just looking for a basic idea of what other people have
Bruce Evans wrote (2001/04/28):
> This is probably caused by write caching now being off by default
> in the ata driver, possibly amplified by not using soft updates.
> Without the new dir allocation, -current would be even slower :(.
Yes, thanks. I really forgot on this change.
My rough results
Right now, I have upgraded my -current machine from
February 13 to April 26.
I were pleased with change to dir allocation in FFS,
but here are my unpleasant test results (UDMA33, partition
is 3 GB where 1 GB is free, soft-updates are enabled):
Old system New system
Andrey A. Chernov wrote (2001/04/19):
> In any case it must be sysctl-controlled variable and not kernel
> option only. Rebuilding whole kernel to just change console language is
> superfluous! rc.syscon/rc.conf hooks must be added too.
I agree that there should be some rc.* variable.
It is not
Sheldon Hearn wrote (2001/02/01):
> What I remember of the discussions that surrounded this one, your
> summary is correct. The only thing is that nice isn't so much _broken_
> as it just isn't doing what you'd expect it to. :-)
Ok, scheduler in -current is not broken. But I'm afraid that in -st
Hi,
I'm afraid that we have still problems with task scheduler:
Until 1999/11/28, it was known that a process with nice 20 were
capable to steal many CPU cycles from processes without nice.
1999/11/28 came commit
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=15023+20131+/usr/local/www/db/text/19
I have found that in Single Unix Specification 2 in waitpid() function
there are allowed options not only WNOHANG and WUNTRACED as is in FreeBSD,
but furthermore option WCONTINUED (Unixware and Solaris both know about
this option and FreeBSD and possible Linux don't).
The next problem is in macr
Kazutaka YOKOTA wrote (1999/12/03):
> This strange behavior was reported several times in the past. It must
> be related to screen update logic in syscons. But, I don't think we
> have successfully fixed it at that time :-(
> It's time to analyze the problem again...
Yes. I know about this prob
els is back...
I hope I really don't need to reformat my disk. Or is it possible
there will be another problem?
Soren Schmidt wrote (1999/09/25):
> It seems Cejka Rudolf wrote:
Yes - it was really me :-)
> The ATA driver has no bad144 support, thats probably why you get
> the above
I'm trying to update my -current system compiled from July 12 (both
kernel and base system). But before all system updating I have tried to
compile and run new kernel from today (September 25) - and it won't
boot so I'm afraid to update all the system...
Booting ends with these lines:
wd0: bad
David O'Brien wrote (1999/08/23):
> - - Forwarded message from [EMAIL PROTECTED] -
> Solaris 7 machines cannot use NFSv3 mounts from a FreeBSD NFS server.
> ...
> # rm -r /home/2/vladimir
> rm: Unable to remove directory /home/2/vladimir/CVS/blowup/c: File exists
> ...
Yes, this is very
Garance A Drosihn wrote (1999/08/23):
> Why would the filter be reading the control file? It is just a
> filter, supposedly reading from stdin and writing to stdout...
Yes and not.
You can look into apsfilter for example. It gets from control file
JOB, USER and HOST items in case of ASCII inp
Is anybody capable to solve or fix bin/7973 in lpd? I have found the
problem is still there (FreeBSD-3.2). Or am I anything missing/doing wrong?
bin/7973: Bad control file owner in case of remote printing. The problem
is that print filters ("if" in printcap) cannot read control files cf* in
case
Mike Smith wrote (1999/08/11):
> > Yes, thanks. Information reported by 0x4F01 function about any video
> > mode has set MODE_NON_VGA attribute indeed. And now I have found DOS TSR
> > program for VESA support...
>
> Bleagh. Have you tried ignoring that attribute in our code and seeing
> what
Soren Schmidt wrote (1999/08/09):
> It seems Kazutaka YOKOTA wrote:
> > There is a good possibility that the VESA BIOS extension for this card
> > is provided in a DOS TSR program and the VESA BIOS entry in the ROM
> > BIOS is just a stub. Such implementation is allowed in the VESA spec.
> Act
I have switched graphics card from S3Virge to ATI Mach64 RagePro rev 92
with 8 MB RAM a I have noticed that VESA module doesn't work with this
graphics card on my -current box - I can't use VESA_XXX console modes now.
Command kldstat says there is loaded module vesa.ko. No errors are
reported whe
>The only thing that bit me was that I used wd0 and wd2 with the older
>driver, whereas the newer driver automatically decided to use ad0 and
>ad1. This is "expected" behaviour, but it's something for other weenies
>to watch out for. :-)
This breakage was announced :
19 matches
Mail list logo
