Is somebody still working on IPX, Netware functionality?
I'm having quite unexpected problems on 4.10-RELEASE when trying to
mount netware volumes.
In former 4-releases, I could a) add IPX+ef to kernel, b) recompile, c)
run IPXrouted and d) make ifconfig iff[0-3] ipx net, then everything
Dmitry Morozovsky wrote:
DM YT an option to IPFIREWALL, you have to build your kernel with
DM YT both IPFIREWALL and IPDIVERT:
DM YT ...
DM YT I did. See the config contents in originating posting. That was the essence
DM YT of the problem -- familiar procedure unexplainably not working.
DM
DM
Gary Jennejohn wrote:
Yury Tarasievich writes:
Hello? anybody? So how come IPDIVERT option is outright ignored in
system build here?? The system isn't even connected to internet, nor to
any other net anyway!
And as if I don't know how to compile kernel? And it is stock
4.10-RELEASE, too (and 4
Yar Tikhiy wrote:
On Tue, Nov 16, 2004 at 03:08:54PM +0200, Yury Tarasievich wrote:
I'm adding IPDIVERT option (options IPDIVERT) to config file and
...
You seem to be confused by the well-known kernel vs. module
configuration issue. Alas, kernel options you specify in your
kernel config file
Hello? anybody? So how come IPDIVERT option is outright ignored in
system build here?? The system isn't even connected to internet, nor to
any other net anyway!
And as if I don't know how to compile kernel? And it is stock
4.10-RELEASE, too (and 4-STABLE has same problem). The process is
Yury Tarasievich wrote:
Just recently I've run into this:
when compiling kernel in 4.10-RELEASE and in 4-STABLE, options
IPDIVERT does not produce enabled divert in firewall code. Previously
(meaning other machines and previous 4.* variants) the configuration
compiled/worked okay.
I've used
Hello,
Just recently I've run into this:
when compiling kernel in 4.10-RELEASE and in 4-STABLE, options
IPDIVERT does not produce enabled divert in firewall code. Previously
(meaning other machines and previous 4.* variants) the configuration
compiled/worked okay.
I've used the attached config
Søren Schmidt wrote:
Yury Tarasievich wrote:
Do I understand right (after looking into sources) that 4-STABLE has
no support for serial ATA devices??
Almost none, it works with a few controllers that looks like stock ATA
ones (HPT fx).
Anyhow you want 5.3 to get real SATA support..
I see
Do I understand right (after looking into sources) that 4-STABLE has no
support for serial ATA devices??
regards
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL
I prefer it that way:
1. run freebsd install
partition the disk, using multiplies of heads*sectors as base unit
make ...s1 slice of type 6 (and possibly make fairly big ad0s2 of
type 5)
make ...s3 and install freebsd there
(I have seen windows at my place occasionally removing
At http://freebsddvb.narod.ru, there exists an adequately up-to-date
port of linux DVB drivers, seemingly supporting DVB adapters up to rev.1.5.
Regarding porting of V4L. I may be utterly wrong, but isn't the whole
V4L/V4L2/V4L2-whatever thing rather made ad hoc, not really designed?
Could
Brian Buchanan wrote:
I'm having problems getting SMP to work on a Tyan S4520 Thunder GCHE
motherboard with 4x 1.9GHz Xeon processors:
Programming 16 pins in IOAPIC #0
IOAPIC #0 intpin 2 - irq 0
Programming 16 pins in IOAPIC #1
Programming 16 pins in IOAPIC #2
AP #1 (PHY# 2) failed!
panic y/n?
clemens fischer wrote:
Yury Tarasievich [EMAIL PROTECTED]:
...then, Tim Kientzle wrote:
A better approach might be to simply fob it
off on the user, i.e.,
# pkg_install foo-1.5
Warning: foo-1.5 requires bar-2.3, you have bar-1.7 installed.
Proceed? [Y/n]
i think this is the best
...first, clemens fischer wrote:
Yury Tarasievich [EMAIL PROTECTED]:
I'd like to see in dependencies not only like was built with
-1.9_2abc, so wants it, but also something like -1.5+ (obviously
1.5.0 and newer), -* (any version will do). Perhaps something else. At
least to have possibility
I have yet another suggestion regarding packaging subsystem -- could it
be possible to extend pkg_* functionality (and, in fact, ports
functionality) to recognize modest set of wildcards in dependencies names?
It seems pretty unreasonable to have various subrevisions of, say,
libiconv, pulled
Nat Lanza wrote:
On Mon, 2003-02-03 at 18:06, Terry Lambert wrote:
But if that's the argument for removing it, then it's probably
time to remove the ability to use non-DMA IDE drives from the
ATA driver, and kill all the ethernet drivers that have alignment
requirements for their DMA engines,
Narvi wrote:
If only Joe-Bob or some other very limited set of people have the
card, then the severity of the bug in the *FreeBSD* bug database
should probably not be 5 - orherwise the database will contain a
large amount of bugs that claim to be of high severity but only
ever affect neglible
Terry Lambert wrote:
Yury Tarasievich wrote:
[...info and pointers greatly appreciated...]
Now:
Most of the reasons this stuff is not in FreeBSD is NIH (not
being the pet research project of a committer), license, the
need to productize the code from research, etc..
For the complaints
Terry Lambert wrote:
FreeBSD is actually adding pointers and other complexity to its
stack
[...etc.]
So you are referring to common features of stacks of both 4.* and 5.*,
right? As far as I understand the matter, this all have to be (and I
guess actually is) provable.
Now, you were saying
Want to attract your attention once more. At my place double Xeons fails
to start (with only SMP and APIC options added to GENERIC) with
following diagnostics:
I tried both 4.7-RELEASE srs/sys and that of January 14. That's what I
get when booting with SMP enabled (copied from screen):
Hello,
Is there any possibility of helping me to get started FreeBSD with SMP
option (and no SMP works okay) on modern 2 Xeon procs server?
I have about two weeks for accomplishing that, after that machine either
goes under Linux, or even under Windows, as there is a complementary
(and very
Andreas Klemm wrote:
On Fri, Dec 13, 2002 at 02:28:00PM -0800, Nate Lawson wrote:
I've successfully repaired a fs with the superblock backup at 32. Now how
do I copy that backup to the default superblock location? fsck_ffs does
NOT automatically do this.
It does. With fsck -b 32 you
Wanted to ask about it for quite some time.
I've got two 20G disks installed with basically same geometry. They were
partitioned (by linux fdisk) approx. similarly (+/- 10 cylinders):
part. 1: ~1-250
part. 2 (Extended): ~751-everything that remains
part. 3: ~251-500
part. 4: ~501-750
There's
On Sat, Nov 30, 2002 at 10:27:27PM -0800, Terry Lambert wrote:
Robert Watson wrote:
On Mon, 25 Nov 2002, Terry Lambert wrote:
Yury Tarasievich wrote:
I need to port some driver from linux to freebsd and, somehow,
I can't find documentation on kernel locks and mutexes
Hi,
Regarding vn subsystem: since about 4.6-RELEASE vnconfig -d no longer disables /dev/vn
entry.
That means that...
vnconfig -e /dev/vnsomething file
vnconfig -d /dev/vnsomething
vnconfig -e /dev/vnsomething anotherfile
...gives vnconfig: VNIOCATTACH: Devise busy...
and only kldunload vn
On Fri, Nov 29, 2002 at 09:20:52AM +0300, Fred Souza wrote:
Regarding vn subsystem: since about 4.6-RELEASE vnconfig -d no longer disables
/dev/vn entry.
[]
Actually, it does disable it (or at least, using the same words from
the manpage, if it's possible). Your problem most likely is
Hello,
I need to port some driver from linux to freebsd and, somehow,
I can't find documentation on kernel locks and mutexes.
There are no man pages, links from handbook are broken, and search on
freebsd site gives nothing (besides the handbook itself).
Where can I find some docs?
,Yury.
To
27 matches
Mail list logo
