devd started with single-user mode?

2011-03-20 Thread David Demelier
Hello, I just realized that I can't use my USB keyboard if I start FreeBSD in single user mode. The keyboard is still detected but I can't use it. It works with the loader of course. I don't know if it's related to devd and if it's running. I also have USB legacy enabled in the BIOS

Re: devd started with single-user mode?

2011-03-20 Thread Polytropon
On Sun, 20 Mar 2011 09:55:35 +0100, David Demelier demelier.da...@gmail.com wrote: Hello, I just realized that I can't use my USB keyboard if I start FreeBSD in single user mode. The keyboard is still detected but I can't use it. It works with the loader of course. I don't know if it's

Minimum system requirements

2011-03-20 Thread aaron van caster
Just would like to know what are the minimum system/hardware requirements to run 8.2 OS and do to have a simple video showing installation? Thanks! ___ freebsd-questions@freebsd.org mailing list

Re: Minimum system requirements

2011-03-20 Thread Polytropon
On Sun, 20 Mar 2011 02:52:59 -0500, aaron van caster darkstar99...@gmail.com wrote: Just would like to know what are the minimum system/hardware requirements to run 8.2 OS and do to have a simple video showing installation? This primarily depends on the codecs used for the video. If there is

Re: devd started with single-user mode?

2011-03-20 Thread David Demelier
On 20/03/2011 12:13, Polytropon wrote: On Sun, 20 Mar 2011 09:55:35 +0100, David Demelierdemelier.da...@gmail.com wrote: Hello, I just realized that I can't use my USB keyboard if I start FreeBSD in single user mode. The keyboard is still detected but I can't use it. It works with the

devd started with single-user mode?

2011-03-20 Thread Robert Huff
David Demelier writes: I just realized that I can't use my USB keyboard if I start FreeBSD in single user mode. The keyboard is still detected but I can't use it. My memory says I had this problem several years ago. Back in 5.*, or maybe 6.*? It could fixed in the

Re: Minimum system requirements

2011-03-20 Thread Daniel Marsh
I'm sure he meant is there a video that shows the steps taken to complete the install. This will also list hardware requirements, but in short it does depend on what you want, I run BSD on a pentium m, 1ghz with 1gb ram and it runs sweet. You could run it on lesser hardware without a problem...

Organize your computer in under an hour

2011-03-20 Thread PC Tools
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN h= ttp://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd !--[if gte mso 9] ![endif]-- Helpful tips to organize your PC. [1]Read More | [2]View Online !--[if g= te mso 9] ![endif]-- [e=] [3Dhttps=] [=] [3]3DPC

Re: Shell script termination with exit function in backquotes

2011-03-20 Thread Ian Smith
in freebsd-questions Digest, Vol 354, Issue 10, Message: 4 On Sat, 19 Mar 2011 12:15:26 -0400 Maxim Khitrov m...@mxcrypt.com wrote: Here's another, but related, problem that I just ran into. The man page reads: Commands may be grouped by writing either (list) or

glabel causes GEOM: ada1: media size does not match label messages

2011-03-20 Thread Maxim Khitrov
Hi all, Executing the following commands on any valid storage device seems to cause media size does not match label kernel messages (FreeBSD 8.2 amd64). I understand why they happen - glabel metadata occupies the last sector, so bsdlabel sees a device that is 1 sector smaller than what the kernel

Re: glabel causes GEOM: ada1: media size does not match label messages

2011-03-20 Thread Maxim Khitrov
On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov m...@mxcrypt.com wrote: Hi all, Executing the following commands on any valid storage device seems to cause media size does not match label kernel messages (FreeBSD 8.2 amd64). I understand why they happen - glabel metadata occupies the last

Re: glabel causes GEOM: ada1: media size does not match label messages

2011-03-20 Thread Carl Johnson
Maxim Khitrov m...@mxcrypt.com writes: On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov m...@mxcrypt.com wrote: Hi all, Executing the following commands on any valid storage device seems to cause media size does not match label kernel messages (FreeBSD 8.2 amd64). I understand why they happen