Invasion of FreeBSD!

Message

avieth · Post by **avieth** » Wed Sep 07, 2005 3:41 am

Gentoo's emblem is so much better than freeBSD's. Thats why I'll never use bsd.

To · Post by To » Wed Sep 07, 2005 1:36 pm

that's a real good point

Tó

synr9 · Post by **synr9** » Fri Sep 09, 2005 2:03 am

GNU/Linux has long been superior in just about every way than FreeBSD for some years now.

GNU/Linux is faster, supports more hardware, and the code is just as clean as FreeBSD if not cleaner.

I switched from FreeBSD to Gentoo GNU/Linux.

lightvhawk0 · Post by **lightvhawk0** » Fri Sep 09, 2005 9:00 am

pilla wrote:
EldermysticRazorsnout wrote:(yes that's sarcasm, the fact that you use udev proves you are an idiot)
No need for this rage. Banned for now. (and yes I use udev).

Oh man I was going to point him to http://www.kroah.com/linux/talks/ols_20 ... LS2003.pdf. Which explains that holding lots of device names in kernel memory is bad and I just killed udevd and I have no problems I will when I try to plug in a new device but it's not like crashing udev hurts the system

pilla · Post by **pilla** » Fri Sep 09, 2005 1:24 pm

Check your url, it is pointing to nowhere (prolly the dot in the end)

Shadow Skill · Post by **Shadow Skill** » Wed Sep 14, 2005 3:19 am

I'm thinking about dual booting freebsd on my desktop and I was wondering if anyone here has tried out the recent 6.0 betas specifically for 64bit machines. Have they updated their installer at all, is the beta "stable" as far as betas go? Does anyone have any advice for installing 5.4 without screwing up grub?

vipernicus · Post by **vipernicus** » Wed Sep 14, 2005 3:35 am

Shadow Skill wrote:I'm thinking about dual booting freebsd on my desktop and I was wondering if anyone here has tried out the recent 6.0 betas specifically for 64bit machines. Have they updated their installer at all, is the beta "stable" as far as betas go? Does anyone have any advice for installing 5.4 without screwing up grub?

It is very stable, just make sure you recompile the kernel without debugging, it is really slow with debugging on.

vipernicus · Post by **vipernicus** » Wed Sep 14, 2005 3:38 am

synr9 wrote:GNU/Linux has long been superior in just about every way than FreeBSD for some years now.

GNU/Linux is faster, supports more hardware, and the code is just as clean as FreeBSD if not cleaner.

I switched from FreeBSD to Gentoo GNU/Linux.

Dude, that's sarcasm right? The only right answer is "supports more hardware"

petrjanda · Post by **petrjanda** » Wed Sep 14, 2005 7:08 am

Shadow Skill wrote:I'm thinking about dual booting freebsd on my desktop and I was wondering if anyone here has tried out the recent 6.0 betas specifically for 64bit machines. Have they updated their installer at all, is the beta "stable" as far as betas go? Does anyone have any advice for installing 5.4 without screwing up grub?

6.0 beta4 still hasnt got the fix for my keyboard and mouse. Submited a bug.

Shadow Skill · Post by **Shadow Skill** » Wed Sep 14, 2005 7:51 am

Perhaps a bios issue, what was the model you had a logitech cordless right? I have a very similllar model and a bios flsh for my board fixed the "boot and pray" problem I had, had for the longest time.

Anyone have any suggestions on how I can edit this grub.conf to boot freebsd in place of the sourcemage entries:

Code: Select all

default 0
timeout 30
#splashimage=(hd0,4) /boot/grub/splash.xpm.gz


title Gentoo
root (hd0,4)
kernel /kernel-2.6.12-gentoo-r9 vga=795 gentoo=nodevfs


title Gentoo
root (hd0,4)
kernel /kernel-2.6.11-gentoo-r7 vga=795 gentoo=nodevfs
#initrd /initrd-2.6.11-gentoo-r7

title  Source Mage GNU/Linux
kernel /boot/vmlinubz-2.6.12.2 root=/dev/hdb5 ro

title  Source Mage GNU/Linux
kernel /boot/vmlinubz-2.6.8.1 root=/dev/hdb5 vga=795 ro




title windows
	rootnoverify (hd0,1)
	makeactive
	chainloader +1

BTW is there an explicit option in the installer to not install freebsd's bootloader? [Some systems I have used don't give such an option, hence the question.]

RuiP · Post by **RuiP** » Wed Sep 14, 2005 8:36 am

Shadow Skill wrote:---
Anyone have any suggestions on how I can edit this grub.conf to boot freebsd in place of the sourcemage entries
---

well you ca try:

Code: Select all

title 	FreeBSD
root 	         (hdX,X,x)
kernel          /boot/loader

replacing X and x (on 2nd line) for your slices and particions specifics.

I spend the summer palying with FreeBSD. I always find linux a little slow for my taste...
I suppose i was expecting to much from the good critics a read all aroung.
I was very disappointed. It turns out that the bestie was (at least in my computer) even slower then any linux i had.
Maybe it compiles fast or do any system/no-gui stuff faster, but not things of my dailly use.
Boot takes 1,5 min (my gentoo takes 20~30 sec. and ubuntu 30~40 sec.) X+gdm takes almost a full minute to get ready!
Xfce and Gnome runs slower then in linux. Menus was not updated with new apps installed.
Plug-in hardware was a pain to mount. Printer was a nightmare... take me almost 2 days to make it work!!
I found some ports broken... and portupgrade never compille everything without errors or stuff that keeps without upgrade.

Maybe i have done something wrong... I'll wait for 6 versions and will try again. But i loose a little the hope.

petrjanda · Post by **petrjanda** » Wed Sep 14, 2005 9:57 am

Shadow Skill wrote:Perhaps a bios issue, what was the model you had a logitech cordless right? I have a very similllar model and a bios flsh for my board fixed the "boot and pray" problem I had, had for the longest time.

Logitech Cordless Desktop LX700
What makes you think its a bios issue? Wouldnt it screw up in linux also? By the way, the bios is up to date. flashed it a couple of months ago.

Shadow Skill · Post by **Shadow Skill** » Wed Sep 14, 2005 6:46 pm

petrjanda wrote:
Shadow Skill wrote:Perhaps a bios issue, what was the model you had a logitech cordless right? I have a very similllar model and a bios flsh for my board fixed the "boot and pray" problem I had, had for the longest time.
Logitech Cordless Desktop LX700
What makes you think its a bios issue? Wouldnt it screw up in linux also? By the way, the bios is up to date. flashed it a couple of months ago.

Simply because my keyboard [MX duo for bluetooth, which I think is based off of the cordless eliete model] finally behaved after I flashed my bios, prior to that every single Linux distro I put on this machine would boot sometimes and other times it would hang while initializing my keyboard. Had to do with the bluetooth reciever. It might not break Linux since Linux may be handling things differently from BSD.

petrjanda · Post by **petrjanda** » Thu Sep 15, 2005 2:25 am

Shadow Skill wrote:
petrjanda wrote:
Shadow Skill wrote:Perhaps a bios issue, what was the model you had a logitech cordless right? I have a very similllar model and a bios flsh for my board fixed the "boot and pray" problem I had, had for the longest time.
Logitech Cordless Desktop LX700
What makes you think its a bios issue? Wouldnt it screw up in linux also? By the way, the bios is up to date. flashed it a couple of months ago.
Simply because my keyboard [MX duo for bluetooth, which I think is based off of the cordless eliete model] finally behaved after I flashed my bios, prior to that every single Linux distro I put on this machine would boot sometimes and other times it would hang while initializing my keyboard. Had to do with the bluetooth reciever. It might not break Linux since Linux may be handling things differently from BSD.

The problem I have is that it hangs after i move my mouse in CLI, but when i move the mouse goodbye input + restart. I have no problem during the actual bootup process, its even recognized correcrtly, it creates proper ums0 and ukb0 entries in /dev.

Shadow Skill · Post by **Shadow Skill** » Thu Sep 15, 2005 3:54 am

If its any consolation Freebsd6.0beta4 wouldn't even install unless I unplugged the reciever thereby disabling the mouse entirely.

petrjanda · Post by **petrjanda** » Thu Sep 15, 2005 5:39 am

Shadow Skill wrote:If its any consolation Freebsd6.0beta4 wouldn't even install unless I unplugged the reciever thereby disabling the mouse entirely.

yes it is

Shadow Skill · Post by **Shadow Skill** » Thu Sep 15, 2005 5:59 am

I officially have the most secure Freebsd installation ever created..............because I can't fucking connect to the internet which pretty much renders the entire installation USELESS! From what I can tell my error which goes something like dhclient cannot get any addresses [It basically just keeps timing out.] I tried adding ifconfig_nve0="dhcp" to rc.conf big mistake all that does is make the error happen during the boot prior to login. Has anyone here got dhcp to work with freebsd6.0beta4 64bit on an nforce4 ultra with the default driver which lists the nic as nve0? I would really, really like to finish setting up my system...

CorpseOfMystic · Post by **CorpseOfMystic** » Thu Sep 15, 2005 2:11 pm

Shadow Skill wrote:I officially have the most secure Freebsd installation ever created..............because I can't fucking connect to the internet which pretty much renders the entire installation USELESS! From what I can tell my error which goes something like dhclient cannot get any addresses [It basically just keeps timing out.] I tried adding ifconfig_nve0="dhcp" to rc.conf big mistake all that does is make the error happen during the boot prior to login. Has anyone here got dhcp to work with freebsd6.0beta4 64bit on an nforce4 ultra with the default driver which lists the nic as nve0? I would really, really like to finish setting up my system...

If its the "device timeout" problem, then its not a DHCP-specific issue, its one with the driver. There are a couple of reports of the nve driver's buffer filling up and causing the device to time out (both on an x86_64 system, so perhaps specific to that). Even if you used statically assigned IP's, it would only be a matter of time before the error appeared. It seems your only option is to wait for the next beta/RC/release and see if its been fixed. You can pass the time by filing another bug report. It's a new driver, more information could only help.

petrjanda · Post by **petrjanda** » Fri Sep 16, 2005 12:01 am

CorpseOfMystic wrote:
Shadow Skill wrote:I officially have the most secure Freebsd installation ever created..............because I can't fucking connect to the internet which pretty much renders the entire installation USELESS! From what I can tell my error which goes something like dhclient cannot get any addresses [It basically just keeps timing out.] I tried adding ifconfig_nve0="dhcp" to rc.conf big mistake all that does is make the error happen during the boot prior to login. Has anyone here got dhcp to work with freebsd6.0beta4 64bit on an nforce4 ultra with the default driver which lists the nic as nve0? I would really, really like to finish setting up my system...
If its the "device timeout" problem, then its not a DHCP-specific issue, its one with the driver. There are a couple of reports of the nve driver's buffer filling up and causing the device to time out (both on an x86_64 system, so perhaps specific to that). Even if you used statically assigned IP's, it would only be a matter of time before the error appeared. It seems your only option is to wait for the next beta/RC/release and see if its been fixed. You can pass the time by filing another bug report. It's a new driver, more information could only help.

while we are talking NIC drivers, how long does it take to fix a driver for a National Semiconductor dp8381x based NIC? These "applying short cable fix" messages have been appearing in every version of FreeBSD i tried.

CorpseOfMystic · Post by **CorpseOfMystic** » Fri Sep 16, 2005 1:58 am

while we are talking NIC drivers, how long does it take to fix a driver for a National Semiconductor dp8381x based NIC? These "applying short cable fix" messages have been appearing in every version of FreeBSD i tried.

Are you having any problems with the networking? AFAIK "short cable fix" messages are simply a report for logging purposes; they are indicative of an issue in the network, not the software. Usually it means a misconfigured router. If the network still functions there should be no problems.

petrjanda · Post by **petrjanda** » Fri Sep 16, 2005 2:28 am

CorpseOfMystic wrote:
while we are talking NIC drivers, how long does it take to fix a driver for a National Semiconductor dp8381x based NIC? These "applying short cable fix" messages have been appearing in every version of FreeBSD i tried.
Are you having any problems with the networking? AFAIK "short cable fix" messages are simply a report for logging purposes; they are indicative of an issue in the network, not the software. Usually it means a misconfigured router. If the network still functions there should be no problems.

No problems with networking whatsoever. First time this came up i searched google and people with the same chip had the same problems. Cant remember if there was any solution to it or not, probably wasnt since it would be included in the next RELEASE.

cousin · Post by **cousin** » Fri Sep 16, 2005 7:09 am

Shadow Skill wrote:Does anyone have any advice for installing 5.4 without screwing up grub?

I'd suggest you enforce the Linux's view of your HD's geometry at install time. Cylinders / Heads / Sectors.

Don't forget to backup the MBR just in case...
dd if=/dev/hda of=mbr bs=512 count=1

cousin · Post by **cousin** » Fri Sep 16, 2005 7:26 am

RuiP wrote:Boot takes 1,5 min (my gentoo takes 20~30 sec. and ubuntu 30~40 sec.) X+gdm takes almost a full minute to get ready!

The default delay for the loader is 10 secs. Change it with:
echo autoboot_delay="5" >>/boot/loader.conf

There are many things that could be configured to make it even smaller. Filesystem checks at startup are done in the background. If you're mounting ext2 partitions it's very likely that these checks are done at every boot 'cause a bug in the ext2 driver leaves vnodes waiting at shutdown. The fix for this is to add code that explicitly unmounts all ext2 filesystems in /etc/rc.shutdown

Configure your modules properly, specially sound. All available modules would be loaded at startup otherwise. And of course: recompile your kernel.

Xfce and Gnome runs slower then in linux. Menus was not updated with new apps installed.

I'm using KDE 3.4.0
Linux has a better response to high multimedia load but FreeBSD runs as fast as linux. I still don't know why menus aren't updated.

Plug-in hardware was a pain to mount.

Make an /etc/fstab entry for your user and add the icon to your desktop

I found some ports broken... and portupgrade never compille everything without errors or stuff that keeps without upgrade.

I've never experienced this with 5.4 :s

Shadow Skill · Post by **Shadow Skill** » Fri Sep 16, 2005 7:36 am

Oh I figured out how to make it boot I like how I was able to see the partition sizes in a format that didn't require that I knew the conversion off hand with the bsd fdisk utility. Now if only my nic would work I could get going.

CorpseOfMystic · Post by **CorpseOfMystic** » Fri Sep 16, 2005 1:14 pm

I'm using KDE 3.4.0
Linux has a better response to high multimedia load but FreeBSD runs as fast as linux. I still don't know why menus aren't updated.

My menus update in KDE on FreeBSD just fine. Perhaps FAM is not setup? You can get the guide for it with:

Code: Select all

cat /usr/ports/devel/fam/pkg-message