31.07.2010 01:17, Peter Jeremy написав(ла):
kenv(1) (in the base) should as well.
Cool! Here it is:
smbios.bios.reldate=08/13/2003
smbios.bios.vendor=American Megatrends Inc.
smbios.bios.version=3.13
smbios.chassis.maker=Chassis Manufacture
smbios.chassis.serial=Chassis
On 2010-Jul-29 16:50:24 +0200, Oliver Fromme o...@lurza.secnetix.de wrote:
Install ports/sysutils/dmidecode and type (as root):
# dmidecode -t system -t baseboard
It will tell you the vendor and product name, among
other things.
kenv(1) (in the base) should as well.
--
Peter Jeremy
Mikhail T. mi+t...@aldan.algebra.com wrote:
The motherboard version -- I'm not sure still. Something like
nVidia nForce2 -- does that identify it enough?
Install ports/sysutils/dmidecode and type (as root):
# dmidecode -t system -t baseboard
It will tell you the vendor and product name,
09.07.2010 05:49, Peter Jeremy ???(??):
I doubt I'm personally in a position to debug this and don't personally
use splash screens. Can you reproduce it using an image that you can
re-distribute?
Ok, the splash-screen problem went away after I put back the original
video-card. The one
Hi,
On Jul 28, 2010, at 11:41 PM, Mikhail T. wrote:
09.07.2010 05:49, Peter Jeremy ???(??):
I doubt I'm personally in a position to debug this and don't personally
use splash screens. Can you reproduce it using an image that you can
re-distribute?
Ok, the splash-screen problem went
On 12/07/2010 19:22, Marian Hettwer wrote:
Hi Adam,
Am 12.07.10 19:11, schrieb Adam Vande More:
Automated installations have existed on FreeBSD for a long time. You
can do
this either via netboot or CD based media. Also rolling your own
FreeBSD
media with custom changes is trivial
08.07.2010 09:53, Jeremy Chadwick написав(ла):
Then don't modify loader.conf. Instead, once the Welcome to FreeBSD!
portion of loader appears, press 6 to shell to the loader prompt
and type:
set vfs.root.mountfrom=ufs:/dev/md0
boot
Yes, that works... It just should not be necessary. Red
08.07.2010 12:40, Jeremy Chadwick написав(ла):
set vfs.root.mountfrom=ufs:/dev/md0
boot
Yes, that works... It just should not be necessary.
Okay, so let me get this straight. First the complaint was that you had
to modify loader.conf, which involved extracting the CD image,
08.07.2010 17:06, Peter Jeremy написав(ла):
On 2010-Jul-07 14:22:22 -0400, Mikhail T.mi+t...@aldan.algebra.com wrote:
In no particular order:
1. A picture, that one of the systems was displaying at boot (and
then used as a screen-saver), stopped showing properly. The
08.07.2010 17:36, Lucas Holt написав(ла):
Most of us work on open source for free in our own time, and it's
impossible to test every possible configuration before a release.
I tested several particular configurations -- on several machines -- and
reported the overlooked issues. I didn't write
On Thu, Jul 8, 2010 at 1:28 PM, Mikhail T.
mi+t...@aldan.algebra.commi%2bt...@aldan.algebra.com
wrote:
RedHat's kickstart
http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/custom-guide/ch-kickstart2.html
can do an entire install based on pre-configured rules. Implementing
something
12.07.2010 13:11, Adam Vande More wrote:
Roll it into your media
You lost me right here... Rolling one's own media (for every release and
release-candidate) may be Ok for someone in charge of making, at least,
several installations per week.
For someone like myself, who just wanted to use a
Hi Adam,
Am 12.07.10 19:11, schrieb Adam Vande More:
Automated installations have existed on FreeBSD for a long time. You can do
this either via netboot or CD based media. Also rolling your own FreeBSD
media with custom changes is trivial compared the linux distro's I'm familar
with. I
Am 12.07.10 19:37, schrieb Mikhail T.:
12.07.2010 13:11, Adam Vande More wrote:
Roll it into your media
You lost me right here... Rolling one's own media (for every release
and release-candidate) may be Ok for someone in charge of making, at
least, several installations per week.
For
On Mon, 12 Jul 2010, Marian Hettwer wrote:
While I fully understand that the iso images purpose is _not_ doing a
netinstall, I'd like to have a downloadable image which is easy pxebootable
and just drops into a shell. Ideally it does a dhcp request, if successful
starts a sshd and if not has
In message: aanlktikdj39liaffibdwkfa1vgt4w7m8toxevjykh...@mail.gmail.com
Garrett Cooper yanef...@gmail.com writes:
: On Wed, Jul 7, 2010 at 1:17 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:
: 07.07.2010 14:59, Jeremy Chadwick ???(??):
:
: FREEBSD_COMPAT7 kernel option
On Thu, Jul 08, 2010 at 11:08:04AM -0400, Mikhail T. wrote:
08.07.2010 09:53, Jeremy Chadwick напиÑаÐ=²(ла):
Then don't modify loader.conf. Instead, once the Welcome to FreeBSD!=
portion of loader appears, press 6 to shell to the loader prompt
and type:
set
On 2010-Jul-08 18:10:48 -0400, Mikhail T. mi+t...@aldan.algebra.com wrote:
08.07.2010 17:06, Peter Jeremy написав(ла):
On 2010-Jul-07 14:22:22 -0400, Mikhail T.mi+t...@aldan.algebra.com
wrote1. A picture, that one of the systems was displaying at boot (and
then used as a
Am 07.07.10 22:52, schrieb Mikhail T.:
07.07.2010 16:34, Randi Harper ???(??):
Attached is the kernel config-file (i386), that worked fine under
7.x. The
kernel-compile will break (some *freebsd7* structs undefined),
without the
COMPAT_FREEBSD7 option. Try it for yourself...
Don't
07.07.2010 14:30, Randi Harper написав(ла):
8.
I tried to do an install on one of the systems via netbooting
(pxeload) the disk1-image. It booted, but the sysinstall had to be
started manually and, once started, did not act the same as when
booted off of CD-ROM.
07.07.2010 16:00, Randi Harper написав(ла):
So you're complaining that you have to modify the loader.conf? I
fail to see the problem. This is by design, and isn't a lack of
progress.
Yes, I complain, that I have to modify a loader.conf embedded in a
CD-image. If extracting hundreds of
07.07.2010 16:50, Marcel Moolenaar написав(ла):
Not to mention that if you change uart(4) to create dev entries like sio(4)
after uart(4) has been in the tree for more than 6 years creating ttyu*
entries, you actually introduce a gratuitous change.
If sio and uart could co-exist, then you'd
On Jul 7, 2010, at 5:39 PM, Garrett Cooper wrote:
On Wed, Jul 7, 2010 at 1:17 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:
07.07.2010 14:59, Jeremy Chadwick ???(??):
FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and
thus not an option) -- the kernel-config
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/08/2010 06:54, for whatever Marian Hettwer wrote:
With any major upgrade or release process comes a commitment from the
developers and end-users alike that involves a review, testing release.
The release part on the end-users
On Wed, 7 Jul 2010, Mikhail T. wrote:
07.07.2010 16:00, Randi Harper ???(??):
So you're complaining that you have to modify the loader.conf? I
fail to see the problem. This is by design, and isn't a lack of
progress.
Yes, I complain, that I have to modify a loader.conf
On Wed, Jul 07, 2010 at 04:29:14PM -0400, Mikhail T. wrote:
07.07.2010 16:00, Randi Harper написав(ла):
So you're complaining that you have to modify the loader.conf? I
fail to see the problem. This is by design, and isn't a lack of
progress.
Yes, I complain, that I have to modify a
Hi jhell,
ehm...
Am 08.07.10 14:46, wrote jhell:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/08/2010 06:54, for whatever Marian Hettwer wrote:
I certainly not wrote the text below. That's what, I guess, you wrote.
Your MUA is defect.
And honestly, I don't know why that's a reply to
On Thu, Jul 08, 2010 at 11:08:04AM -0400, Mikhail T. wrote:
08.07.2010 09:53, Jeremy Chadwick написав(ла):
Then don't modify loader.conf. Instead, once the Welcome to FreeBSD!
portion of loader appears, press 6 to shell to the loader prompt
and type:
set vfs.root.mountfrom=ufs:/dev/md0
On 07/08/2010 10:08, Marian Hettwer wrote:
Hi jhell,
ehm...
Am 08.07.10 14:46, wrote jhell:
On 07/08/2010 06:54, for whatever Marian Hettwer wrote:
I certainly not wrote the text below. That's what, I guess, you wrote.
Your MUA is defect.
And honestly, I don't know why that's a reply
On 2010-Jul-07 14:22:22 -0400, Mikhail T. mi+t...@aldan.algebra.com wrote:
In no particular order:
1.
A picture, that one of the systems was displaying at boot (and
then used as a screen-saver), stopped showing properly. The
colors are right, but the picture is distorted
On 07/08/10 17:06, Peter Jeremy wrote:
On 2010-Jul-07 14:22:22 -0400, Mikhail T.mi+t...@aldan.algebra.com wrote:
In no particular order:
1.
A picture, that one of the systems was displaying at boot (and
then used as a screen-saver), stopped showing properly. The
On Thu, Jul 8, 2010 at 2:36 PM, Lucas Holt l...@foolishgames.com wrote:
On 07/08/10 17:06, Peter Jeremy wrote:
On 2010-Jul-07 14:22:22 -0400, Mikhail T.mi+t...@aldan.algebra.com
wrote:
In no particular order:
1.
A picture, that one of the systems was displaying at boot (and
On Thu, Jul 08, 2010 at 02:46:16PM -0700, Freddie Cash wrote:
On Thu, Jul 8, 2010 at 2:36 PM, Lucas Holt l...@foolishgames.com wrote:
On 07/08/10 17:06, Peter Jeremy wrote:
On 2010-Jul-07 14:22:22 -0400, Mikhail T.mi+t...@aldan.algebra.com
wrote:
In no particular order:
1.
Date: Thu, 08 Jul 2010 17:36:17 -0400
From: Lucas Holt l...@foolishgames.com
Sender: owner-freebsd-sta...@freebsd.org
On 07/08/10 17:06, Peter Jeremy wrote:
On 2010-Jul-07 14:22:22 -0400, Mikhail T.mi+t...@aldan.algebra.com
wrote:
In no particular order:
1.
A
On Thu, 8 Jul 2010, Jeremy Chadwick wrote:
With regards to leftover man pages in /usr/share/man/manX, I believe
mergemaster now handles clean-up of those, and probably catX too.
Never has, never will. :) What I actually advocate is 'rm -r
/usr/share/man' before doing installworld. Been
On Wed, Jul 7, 2010 at 11:22 AM, Mikhail T. mi+t...@aldan.algebra.com wrote:
8.
I tried to do an install on one of the systems via netbooting
(pxeload) the disk1-image. It booted, but the sysinstall had to be
started manually and, once started, did not act the same as when
On Wed, 07 Jul 2010 14:22:22 -0400
Mikhail T. mi+t...@aldan.algebra.com wrote:
9.
The k8temp utility (installed by sysutils/k8temp
http://www.freshports.org/sysutils/k8temp), which worked fine on
both of my AMD-machines, no longer works on the Athlon one (still
On Wed, Jul 07, 2010 at 02:22:22PM -0400, Mikhail T. wrote:
I'm upgrading several systems these days to the 8.1 (pre-release)
and have hit the following troubles... I could file a formal PR for
each, I suppose, but, maybe, this way will get the right people's
attention sooner.
2.
Date: Wed, 07 Jul 2010 14:22:22 -0400
From: Mikhail T. mi+t...@aldan.algebra.com
Sender: owner-freebsd-sta...@freebsd.org
I'm upgrading several systems these days to the 8.1 (pre-release) and
have hit the following troubles... I could file a formal PR for each, I
suppose, but, maybe,
2010/7/7 Mikhail T. mi+t...@aldan.algebra.com:
07.07.2010 14:30, Randi Harper написав(ла):
8.
I tried to do an install on one of the systems via netbooting
(pxeload) the disk1-image. It booted, but the sysinstall had to be
started manually and, once started, did not act the same
07.07.2010 14:59, Jeremy Chadwick ???(??):
FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and
thus not an option) -- the kernel-config files, that worked with
7.x, break without this option in them (in addition to all the
nuisance, that's documented in
On Wed, Jul 7, 2010 at 1:17 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:
07.07.2010 14:59, Jeremy Chadwick ???(??):
FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and
thus not an option) -- the kernel-config files, that worked with
7.x, break without this
On Jul 7, 2010, at 1:34 PM, Randi Harper wrote:
Well, pardon the political pun, but I don't believe in change for the sake
of change. These particular changes are gratuitous. If sio is no longer
available -- and replaced by uart, why change the /dev-entries?..
These changes aren't
07.07.2010 16:34, Randi Harper ???(??):
Attached is the kernel config-file (i386), that worked fine under 7.x. The
kernel-compile will break (some *freebsd7* structs undefined), without the
COMPAT_FREEBSD7 option. Try it for yourself...
Don't use a kernel config from 7. We've
On Wed, Jul 7, 2010 at 1:17 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:
07.07.2010 14:59, Jeremy Chadwick ???(??):
FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and
thus not an option) -- the kernel-config files, that worked with
7.x, break without this
On Wed, Jul 7, 2010 at 1:52 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:
I know nothing about the driver. But a utility I regularly used stopped
working after upgrade, so I added that to my list of upgrade-related
grudges.
Was this before or after re-compiling all your installed ports,
On Wed, Jul 7, 2010 at 1:17 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:
07.07.2010 14:59, Jeremy Chadwick ???(??):
FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and
thus not an option) -- the kernel-config files, that worked with
7.x, break without this
On Wed, Jul 7, 2010 at 1:52 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:
07.07.2010 16:34, Randi Harper ???(??):
Attached is the kernel config-file (i386), that worked fine under 7.x.
The
kernel-compile will break (some *freebsd7* structs undefined), without
the
COMPAT_FREEBSD7
5.
One of the upgraded systems would repeatedly hang at boot, until I
disabled the on-board firewire-device through the BIOS... It was
not a problem under 7.x, although I don't know, whether the device
actually worked.
This is a commonly-reported problem,
5.
One of the upgraded systems would repeatedly hang at boot, until I
disabled the on-board firewire-device through the BIOS... It was
not a problem under 7.x, although I don't know, whether the device
actually worked.
This is a commonly-reported problem,
On Wed, Jul 7, 2010 at 1:52 PM, Mikhail T. mi+t...@aldan.algebra.com wrote:
Your telling me this is just as valid as warning me against using
computer-cases of a particular color. It is a silly requirement. My
expecting things, that worked for 7, to work in 8 is reasonable. There may
be
On Wed, 07 Jul 2010 12:34:55 -0700
Kevin Oberman ober...@es.net wrote:
k8temp is for older AMD system running K8 cores. It has been mostly
replaced with amdtemp which works on newer cores. I'm not sure if
amdtemp will work on K8 cores, though.
It does (amdtemp works on K8s):
r...@kg-quiet#
On Thu, 08 Jul 2010 00:20:56 +0200
Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote:
On Wed, 07 Jul 2010 12:34:55 -0700
Kevin Oberman ober...@es.net wrote:
k8temp is for older AMD system running K8 cores. It has been mostly
replaced with amdtemp which works on newer cores. I'm not
For what its worth, we have had good success migrating our kernel configs
from 6 - 7 - 8 with very few changes, and no real problems.
The secret is to create a kernel that is based of GENERIC using include
in a clean the include that config in top level one which adds the specific
additional
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/7/10 4:17 PM, Mikhail T. wrote:
07.07.2010 14:59, Jeremy Chadwick написав(ла):
FREEBSD_COMPAT7 kernel option is, apparently, a requirement (and
thus not an option) -- the kernel-config files, that worked with
7.x, break without
55 matches
Mail list logo
