Kris Kennaway wrote:
On Fri, Oct 11, 2002 at 08:12:47AM +0200, Roelof Osinga wrote:
Since NETSMB support is not in GENERIC, you must have added it to your
kernel yourself at some point. When you modify your kernel
configuration you need to read the documentation to make sure you're
addin
Kris Kennaway wrote:
> On Fri, Oct 11, 2002 at 06:41:33AM +0200, Roelof Osinga wrote:
>
>>Kris Kennaway wrote:
>>
>
> You don't have these files *INSTALLED* yet. cvsupping doesn't install
> them for you, 'make world' (not 'make buildworld
Phil Kernick wrote:
>>> You probably forgot options LIBICONV from your kernel config file,
>>> which is mandatory for SMBFS support (as documented).
>>
> ...
>
> # grep SMBFS /usr/src/sys/i386/conf/LINT
> # grep LIBICONV /usr/src/sys/i386/conf/LINT
Ta. Making as we type.
>> PS did make w
Kris Kennaway wrote:
> On Fri, Oct 11, 2002 at 04:35:53AM +0200, Roelof Osinga wrote:
>
> ...
> You have to have an up-to-date world before other targets like
> 'modules-clean' are guaranteed to work. As you show:
>
> ...
>
> You don't have these file
faSty wrote:
> ah you says so. I did it on one of my rack DNS server. I managed get
> kernel compiled without any error. sorry i tried help you anyway.
Oh no, don't be. Any help is always welcome!
But I did notice one thing and that is that the good compiles were done just
after the 2002.07.05 c
faSty wrote:
> no no you need clean up in /usr/src/sys/i386/compile/NISSER (type make clean)
> then cd /usr/src/sys/i386/conf and config NISSER then cd ../../compile/NISSER
> lastly make depend
Make absolutely no difference whatsoever. Still get stuck on that linux code. But
how the heck it ever
"Antoine Beaupre (LMC)" wrote:
>
> ...
> Ah! Heard that before! What's your IP again? ;)
Well, now, that's a secret, you hear.
But that would be proving a point. That's something different ;). That
has once been done in 1997. Because I was too lazy to reboot the box
to load the new kernel befo
Erik Trulsson wrote:
>
> On Wed, May 16, 2001 at 01:41:55AM +0900, Eugene M. Kim wrote:
> > Greetings,
> >
> > I'm having some hard time getting a machine upgraded from 3.3-stable to
> > 4-stable.
> > ...
>
> You will probably have to do the upgrade in several steps:
> First upgrade to 3.5-STABL
Rasputin wrote:
>
> >...
> > -rw-r--r-- 1 root wheel 1955761 May 10 00:30 gnome
> > -rw-r--r-- 1 root wheel 636835 May 10 02:46 kde2
>
> Freaky - those two both work for me.
>
> Sounds like your ports tree is shafted, because the ports work for others.
Interesting suggestion. Never min
Kris Kennaway wrote:
>
> ...
> There's nothing wrong with the xemacs21 port. You could go and fetch
> the package to prove this (if the port was broken, the package
> wouldn't build).
Granted that the xemacs example was a bad one.
But never mind, I've already been asked, off-list, to stop was
Matthew Reimer wrote:
>
> Do you have the openssl port installed? Since openssl was imported to
> -stable, the port is not necessary and can actually get in the way. Try
> deleting it (pkg_delete openssl-xxx).
>
> BTW, same goes for the ssh port.
No, I haven't installed either of those. This bo
Jim King wrote:
>
> Just setup my first box with a 3Ware controller. The Feb. 9 snapshot
> installed and ran like a champ - absolutely nothing special required to use
> the 3Ware volume. Kudos to Mike Smith for the great work!
That reminds me. I had cause to talk with the german distributor
re
Jordan Hubbard wrote:
>
> ...
> Erm, well, let's just get one thing straight first: There's only one
> release candidate currently under test and that's RC2. It's only
> available on ONE place and in ONE form, an ISO image, so there's
> really only:
>
> ftp://ftp.freebsd.org/pub/FreeBSD/release
Martin Nilsson wrote:
>
> ...
> I tried to remove one IDE cable from my motherboard and then starting the
> computer. Result: THE HPT370 BIOS HUNG, when detecting drives and the machine
> never even tried to boot. Nice! Vinum would do way much better than that!
> As usual Taiwanese hardware prove
Jordan Hubbard wrote:
>
> Erm, I guess the practice of providing details has fallen out of
> fashion or something since I still have NO IDEA what you are referring
> ...
Well, one step further. Using the 4.1.1.-RELEASE or something I
did/noticed the following:
8 <> 7 (on 4.2) conflicts after ke
Jing-Tang Keith Jang wrote:
>
> --
> Keep it simple and stupid.
A little off topic, but... This is too nice for an old USA army
expression (genie forces). Try:
Keep It Simple, Stupid!
Roelof
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the
Yesterday I installed the 4.2 RC1 in dangerously dedicated
mode on a SCSI disk I had lying around.
Loo and behold, on booting I got:
BTX loader 1.00 (BTX version 1.01)
Error Client format not supported
Same old, same old. I remembered having had to deal with just
this somewhere in the 3.x r
"Rodney W. Grimes" wrote:
>
> > ifconfig_ep1="inet 212.187.0.39 netmask 255.255.248.0"
> ^^
> Are you really supernetted here? This could be a major part of
> your problem. Don't you mean ``255.255.255.248''?
You had me going there for a se
"Daniel C. Sobral" wrote:
>
> mount wd0a /mnt? Is it too much typing for you?
And then they tell *me* to stop being sarcastic! HAH! Since when, pray
tell, does root reside below mnt?
> You mean two _slices_, one on the first 1024, and the other at the
> end of the disk containing the usual _par
"Daniel C. Sobral" wrote:
>
> M how about:
>
> 1) boot the installation disks until sysinstall comes up.
> 2) select the Fixit option (the one that mentiones a shell, y'know)
> on the main menu.
Alas, won't work. Root is most definitely not the root on the hard
disk. You can do thing wi
20 matches
Mail list logo
