Re: DragonFly cannot detect existing FreeBSD partitions during install and cannot detect SanDisk USB flash drive during install
:... :> "cd" "md" "ad" "acd" "mfs" :> :> Here, I typed "?" where it doesn't show any "da" device :> :> :Could it be that you have to load the module at boot from loader.conf? :I know I had to fiddle with this when I set up my system to boot from a :vinum mirror volume. Look in /boot/defaults/loader.conf for options and :make your own adapted loader.conf in /boot. : :-- : : Mvh - Stefan - Yah, it should work if specified in loader.conf. Alternatively one can compile up a custom kernel that builds it in. -Matt Matthew Dillon <[EMAIL PROTECTED]>
Re: ath9k - Atheros unveils free Linux driver for its 802.11n devices
2008/7/27 Gergo Szakal <[EMAIL PROTECTED]>: > http://wireless.kernel.org/en/users/Drivers/ath9k > > It is ISC-licenced. > Well, from openbsd-misc: http://www.nabble.com/atheros---just-curious,-ot-td18672937.html It seems like they only had source available, but no documentation... the code might be obscured to the Linux kernel in some way. -- This e-mail may be confidential. You may not copy, forward, distribute, or, use any part of it. Note, this text has no effective legal binding on your part, there is no obligation to abide any or all parts of this. Treat it with the same level of care as any other pretending-to-be-law-speaking-but-not-really texts attached to e-mail messages you normally find on any other e-mails. For more information about disclaimers, please see: http://www.goldmark.org/jeff/stupid-disclaimers/
Re: [ANNOUNCEMENT] The pkgsrc-2008Q2 Branch
On 27/07/2008, Cristi Magherusan <[EMAIL PROTECTED]> wrote: > Hello, > > On Sat, 2008-07-26 at 08:43 +0100, Alistair Crooks wrote: > > The pkgsrc-2008Q2 Branch > > > > > > The pkgsrc developers are very proud to announce the new pkgsrc-2008Q2 > > branch, which has support for more packages than previous branches. > > As well as updated versions of many packages, the infrastructure of > > pkgsrc itself has been improved for better platform and compiler > > support. > > > Congratulations and many thanks to everyone who contributed! > > For the future releases, do you have any plans to include an officially > supported tool that will properly update/rebuild all or some of the > installed packages on a system, without removing everything and > rebuilding from scratch, while still maintaining the binary consistency > of the system? I'm thinking at something like the portupgrade tool from > FreeBSD. Or like `pkg_add -u` on OpenBSD? :-) http://www.openbsd.org/faq/faq15.html#PkgUpdate http://www.openbsd.org/papers/ven05-espie/ br, cnst.su.
Re: [ANNOUNCEMENT] The pkgsrc-2008Q2 Branch
Hello, On Sat, 2008-07-26 at 08:43 +0100, Alistair Crooks wrote: > The pkgsrc-2008Q2 Branch > > > The pkgsrc developers are very proud to announce the new pkgsrc-2008Q2 > branch, which has support for more packages than previous branches. > As well as updated versions of many packages, the infrastructure of > pkgsrc itself has been improved for better platform and compiler > support. Congratulations and many thanks to everyone who contributed! For the future releases, do you have any plans to include an officially supported tool that will properly update/rebuild all or some of the installed packages on a system, without removing everything and rebuilding from scratch, while still maintaining the binary consistency of the system? I'm thinking at something like the portupgrade tool from FreeBSD. Best regards, Cristi
Re: console
On Sun, Jul 27, 2008 at 09:57:55PM +0200, Erik Wikström wrote: > Yes, in a way. [..] > > Either one can choose to use the absolute latest code in HEAD, or one > can go the safe route and follow the changes to a release branch. A > third alternative is to follow the Preview-tag, which is somewhere > between a release branch and HEAD. > > [..] but in general I would advice against using it for a > production system since every update might introduce instabilities, > bugs, and other kinds of problems. In corporate settings regular > releases are usually preferable since they allow for planned upgrades. Probably there's something I'm still missing - but suppose, that we're replacing components "the rolling way", following release branch. As I understand, it contains debugged and well-tested versions, so, actually, why should it differ - when we mean stability - from upgrade of a complete system at once? The idea is, that actually it should be the same - but instead of be done within a hour, it could be done gradually, within six months, for example. After every single component - well-tested - reached release branch. -- pozdrawiam / regards Zbigniew Baniewski
Re: console
On Sun, Jul 27, 2008 at 08:37:59PM +0100, Simon 'corecode' Schubert wrote: > >What a pity - it would be nice to keep both "national" characters and > >semigraphics in text mode. > > We'd love to see contributions in this regard - Well, as soon as I'll be able to - but presently I don't have so deep knowledge about terminals. Was just wondering, if anything planned in that area. > probably this would require a graphics console, however. No, not at all - smacs/rmacs strings are kind of "switch", which allows to utilize both charsets of standard VGA card at one time. Such way one can have 512 characters to choose from - and this is how linux console works, and how one can use mutt, slrn, mc and other console tools, having both national characters and semigraphic ones (using curses library, of course). > DragonFly is no distribution, but a whole OS. That's just semantics. We can say: "there's just one and only `distribution' of DF" as well (I think so). > DragonFly itself doesn't have packages, so there is nothing to be updated > in a rolling way. Except for the base system, which of course is rolling, > like any other software product. I'm not sure, whether one can say, that really "any other"(?) software can be described as having rolling - not "cycled" - release model. Maybe in a way, which Eric used. -- pozdrawiam / regards Zbigniew Baniewski
[ANNOUNCEMENT] The pkgsrc-2008Q2 Branch
The pkgsrc-2008Q2 Branch The pkgsrc developers are very proud to announce the new pkgsrc-2008Q2 branch, which has support for more packages than previous branches. As well as updated versions of many packages, the infrastructure of pkgsrc itself has been improved for better platform and compiler support. At the same time, the pkgsrc-2008Q1 branch has been deprecated, and continuing engineering starts on the pkgsrc-2008Q2 branch. With more than ten years of pkgsrc development behind us, we would like to take this opportunity to thank all of the people who have made pkgsrc the most portable packaging system in the world - to all of the users, developers and supporters a very large "Thank you" from all of us. Some highlights of the new pkgsrc-2008Q2 branch are: + a new ruby gems framework, from Stoned Elipot and Johnny Lam + many more packages have been moved to install into a staging directory - the DESTDIR work that Joerg Sonnenberger has done almost singlehandedly + many, many packages have been updated to newer versions, to take advantage of fixes and improved functionality. The following versions of packages are included in the pkgsrc-2008Q2 branch: + apache-2.2.9 + firefox-2.0.0.16 and firefox-3.0.1 + gnome-2.20.2 + kde-3.5.9 + mysql-5.0.51 + openoffice-2.4.1 + opera-9.27 + postgresql-8.3.3 + python-2.5.2 + ruby-1.8.7.22 + samba-3.0.30 + seamonkey-1.1.11 + wireshark-1.0.2 + zope-3.3.1 + other changes include + Jared Mcneill has re-worked the compiz window manager packages + the new ruby gems framework is easy to use, scalable, and very effective + Eric Gillespie has updated the subversion package to 1.5.0, and reworked part of the additional language support + thanks to Jared Mcneill, David Holland and Reinoud Zandijk, wine-1.0 works well on NetBSD + the addition of some interesting, pertinent, and shiny packages such as acroread8, bind95, blame, boxbackup (client and server), compiz-fusion, drupal6, firefox3, fltk2, freeradius2, ftmenu, gambc, gvfs, java-subversion, mediatomb, mono-tools, mowgli, msel, mtftpd, odt2text, pkg_leaves, qrencode, ruby-snmp, smbldap-tools, stegtunnel, torrentzip, unbound, and xsel. The list of platforms supported by pkgsrc is AIX, BSD/OS, Darwin (Mac OS X), DragonFly BSD, FreeBSD, HP/UX, IRIX, Interix, Linux, NetBSD, OSF1, OpenBSD, QNX and SunOS (Solaris). We are aware that support for some platforms is at a more mature stage than others, and would like to encourage feedback from users and developers on our more esoteric platforms. + continuing engineering on the "stable" branches of pkgsrc has been revitalised, and our release engineering team has done a marvellous job in pulling up changes to the stable branch. Our thanks go to them for all the hard work they do in sanity checking pullup requests, and managing the stable branches in pkgsrc. + constant bulk building on a number of platforms has improved our ability to identify potential areas of concern, and to correct them sooner. It has also improved our ability to make binary packages available, and we are working on ways to improve this further. For more information, please refer to the pkgsrc-bulk mailing list, archives available at http://mail-index.netbsd.org/pkgsrc-bulk/ + the number of packages has been increased to 7721; the number of supported platforms is currently 14. NetBSD, on all its supported architectures, is considered to be one pkgsrc platform. As always, we'd like to encourage users of the packages collection to audit-packages at least every day - this will provide notification of any packages which are vulnerable to exploit. Audit-packages is now part of the new pkg_install tools, and is now much quicker. We have removed the old audit-packages package in this pkgsrc release. Recently Tonnerre Lombard has joined the pkgsrc-security team, and has made a lot of additions to the list of vulnerable packages - a very useful and thorough job - we are grateful to him. The pkgsrc-security team do a marvellous job in tracking notifications of vulnerabilities in packages, and disseminating this information, and our sincere thanks go to them for this essential work. We'd also really appreciate it if people would install the pkgsrc/pkgtools/pkgsurvey package, and then run the pkgsurvey script for us. This will forward us a list of the packages installed on that machine, and the operating system and release level of the operating system. The results will be kept confidential, but the output will help us analyse the packages that are most used. The source tar files for the new branch can be found at: ftp://ftp.NetBSD.org/pub/pkgsrc/pkgsrc-2008Q2/pkgsrc-2008Q2.tar.gz or ftp://f
Re: console
On 2008-07-27 20:08, Zbigniew Baniewski wrote: > On Sun, Jul 27, 2008 at 10:54:00AM -0700, Matthew Dillon wrote: >> :Uh, I forgot - another one: I read, that DragonFlyBSD has two releases >> :yearly. Wouldn't be reasonable to switch to "rolling release" model then? It >> :could mean less work for both the users ant the devs... what do you think? >> >> I don't know what you mean by a 'rolling release' model. > > I mean the thing described at, for example: > http://en.wikipedia.org/wiki/Rolling_release > http://jon-reagan.blogspot.com/2008/01/linux-releases-fixed-vs-rolling-release.html > >> People can >> always stay up to date by tracking the release branch or the development >> branch, which are updated continuously. > > So, does it work in the case of DF exactly the way: > > #v+ > "[..] there are no fixed releases like 0.7 or 1.0, but the whole system is > on the roll, constantly updating bit by bit (not the 'bit' as in bits and > bytes, but a 'bit' as in a bit of this and a bit of that). The flow of > updated packages is constant [..]" > #v- > ( http://eyedeal.team88.org/node/58 ) Yes, in a way. There are no pre-built binaries or installation CD images but ince everyone can access the source-code (even make copies of the source-tree) anyone can checkout any version they like and build and use. Either one can choose to use the absolute latest code in HEAD, or one can go the safe route and follow the changes to a release branch. A third alternative is to follow the Preview-tag, which is somewhere between a release branch and HEAD. All FOSS projects where you can access the repository allows for rolling releases, but in general I would advice against using it for a production system since every update might introduce instabilities, bugs, and other kinds of problems. In corporate settings regular releases are usually preferable since they allow for planned upgrades. -- Erik Wikström
Re: console
Zbigniew Baniewski wrote: :As I can see, DragonFlyBSD uses just cons25 terminal, taken from FreeBSD :most probably. I would to ask: is there support for smacs/rmacs strings :planned? It's needed for full internationalization of text-console, without :a loss of semigraphics. Not that I know of. What a pity - it would be nice to keep both "national" characters and semigraphics in text mode. We'd love to see contributions in this regard - probably this would require a graphics console, however. :Uh, I forgot - another one: I read, that DragonFlyBSD has two releases :yearly. Wouldn't be reasonable to switch to "rolling release" model then? It :could mean less work for both the users ant the devs... what do you think? I don't know what you mean by a 'rolling release' model. I mean the thing described at, for example: http://en.wikipedia.org/wiki/Rolling_release http://jon-reagan.blogspot.com/2008/01/linux-releases-fixed-vs-rolling-release.html People can always stay up to date by tracking the release branch or the development branch, which are updated continuously. So, does it work in the case of DF exactly the way: #v+ "[..] there are no fixed releases like 0.7 or 1.0, but the whole system is on the roll, constantly updating bit by bit (not the 'bit' as in bits and bytes, but a 'bit' as in a bit of this and a bit of that). The flow of updated packages is constant [..]" #v- ( http://eyedeal.team88.org/node/58 ) DragonFly is no distribution, but a whole OS. DragonFly itself doesn't have packages, so there is nothing to be updated in a rolling way. Except for the base system, which of course is rolling, like any other software product. cheers simon
Re: console
On Sun, Jul 27, 2008 at 10:54:00AM -0700, Matthew Dillon wrote: > :Hallo - a question from a person pretty new to DragonFlyBSD: > : > :As I can see, DragonFlyBSD uses just cons25 terminal, taken from FreeBSD > :most probably. I would to ask: is there support for smacs/rmacs strings > :planned? It's needed for full internationalization of text-console, without > :a loss of semigraphics. > > Not that I know of. What a pity - it would be nice to keep both "national" characters and semigraphics in text mode. > :Uh, I forgot - another one: I read, that DragonFlyBSD has two releases > :yearly. Wouldn't be reasonable to switch to "rolling release" model then? It > :could mean less work for both the users ant the devs... what do you think? > > I don't know what you mean by a 'rolling release' model. I mean the thing described at, for example: http://en.wikipedia.org/wiki/Rolling_release http://jon-reagan.blogspot.com/2008/01/linux-releases-fixed-vs-rolling-release.html > People can > always stay up to date by tracking the release branch or the development > branch, which are updated continuously. So, does it work in the case of DF exactly the way: #v+ "[..] there are no fixed releases like 0.7 or 1.0, but the whole system is on the roll, constantly updating bit by bit (not the 'bit' as in bits and bytes, but a 'bit' as in a bit of this and a bit of that). The flow of updated packages is constant [..]" #v- ( http://eyedeal.team88.org/node/58 ) -- pozdrawiam / regards Zbigniew Baniewski
Re: console
:Hallo - a question from a person pretty new to DragonFlyBSD: : :As I can see, DragonFlyBSD uses just cons25 terminal, taken from FreeBSD :most probably. I would to ask: is there support for smacs/rmacs strings :planned? It's needed for full internationalization of text-console, without :a loss of semigraphics. Not that I know of. :Uh, I forgot - another one: I read, that DragonFlyBSD has two releases :yearly. Wouldn't be reasonable to switch to "rolling release" model then? It :could mean less work for both the users ant the devs... what do you think? :-- : pozdrawiam / regards : : Zbigniew Baniewski I don't know what you mean by a 'rolling release' model. People can always stay up to date by tracking the release branch or the development branch, which are updated continuously. -Matt Matthew Dillon <[EMAIL PROTECTED]>
console
Hallo - a question from a person pretty new to DragonFlyBSD: As I can see, DragonFlyBSD uses just cons25 terminal, taken from FreeBSD most probably. I would to ask: is there support for smacs/rmacs strings planned? It's needed for full internationalization of text-console, without a loss of semigraphics. Uh, I forgot - another one: I read, that DragonFlyBSD has two releases yearly. Wouldn't be reasonable to switch to "rolling release" model then? It could mean less work for both the users ant the devs... what do you think? -- pozdrawiam / regards Zbigniew Baniewski
ath9k - Atheros unveils free Linux driver for its 802.11n devices
http://wireless.kernel.org/en/users/Drivers/ath9k It is ISC-licenced. -- Gergo Szakal MD <[EMAIL PROTECTED]> University Of Szeged, HU Faculty Of General Medicine /* Please do not CC me with replies, thank you. */
ThinkPad G40 BCM5901?
Hello there, I have been considering getting an IBM ThinkPad G40 for using DragonFly BSD on it, from googling I found that it probably uses Broadband BCM5901 chipset for its NIC, does anyone know if it would be supported by DBSD? Thanks. Sunnz.
Re: DragonFly cannot detect existing FreeBSD partitions during install and cannot detect SanDisk USB flash drive during install
Archimedes Gaviola wrote: Hi Matt, Yes, you are right. After kldload'ing the ehci driver manually, it automatically detects my SanDisk USB flash drive. I proceeded to installation and got successful with it. However when booting after installation, it stops somewhere while mounting the device. Below is the error encountered. Mounting root from ufs:/dev/da0s1a no disk named 'da0s1a' setrootbyname failed ffs_mountroot: can't find rootvp root mount failed: 6 Manual root filesystem specification: : Specify root (e.g. ufs:da0s1a) ? List valid disk boot devices panic Just panic abort Abort manual input mountroot> mountroot> ? Possibly valid device for 'ufs' root: "cd" "md" "ad" "acd" "mfs" Here, I typed "?" where it doesn't show any "da" device Could it be that you have to load the module at boot from loader.conf? I know I had to fiddle with this when I set up my system to boot from a vinum mirror volume. Look in /boot/defaults/loader.conf for options and make your own adapted loader.conf in /boot. -- Mvh - Stefan -
Re: DragonFly cannot detect existing FreeBSD partitions during install and cannot detect SanDisk USB flash drive during install
On Sat, Jul 26, 2008 at 1:32 PM, Matthew Dillon
<[EMAIL PROTECTED]> wrote:
>
> :Hi,
> :
> :I have a notebook PC with existing FreeBSD disk partitions of 6.2 and
> :5.5 releases and then to install DragonFly 2.0 for multiple OS
> :booting. Before I begin installing DragonFly, I already created a
> :slice for it using FreeBSD-6.2 installer and I assume the same slice
> :type of 165 that DragonFly is using but somehow it failed to detect
> :existing FreeBSD partitions. So, what I did next is to try installing
> :DragonFly on my 1GB SanDisk USB flash drive but somehow it failed to
> :detect the device during installation. Although I know this USB
> :drive's driver is supported by DragonFly as I've have tried plugging
> :it on another PC with DragonFly.
> :
> :da0 at umass-sim0 bus 0 target 0 lun 0
> :da0: Removable Direct Access SCSI-2 device
> :da0: Serial Number \^_
> :da0: 1.000MB/s transfers
> :da0: 973MB (1994385 512 byte sectors: 64H 32S/T 973C)
> :
> :Thanks,
> :Archimedes
>
>If the installer isn't seeing the usb device it could be that
>booting from the live CD or equivalent isn't loading all the necessary
>modules. You'd have to play with it manually from a root prompt.
>Try kldload'ing the ehci driver maybe.
>
>Maybe we could figure out what is going on from the dmesg output
>on the laptop after booting the DFly live-cd?
>
>-Matt
>Matthew Dillon
><[EMAIL PROTECTED]>
>
Hi Matt,
Yes, you are right. After kldload'ing the ehci driver manually, it
automatically detects my SanDisk USB flash drive. I proceeded to
installation and got successful with it. However when booting after
installation, it stops somewhere while mounting the device. Below is
the error encountered.
Mounting root from ufs:/dev/da0s1a
no disk named 'da0s1a'
setrootbyname failed
ffs_mountroot: can't find rootvp
root mount failed: 6
Manual root filesystem specification:
: Specify root (e.g. ufs:da0s1a)
? List valid disk boot devices
panic Just panic
abort Abort manual input
mountroot>
mountroot> ?
Possibly valid device for 'ufs' root:
"cd" "md" "ad" "acd" "mfs"
Here, I typed "?" where it doesn't show any "da" device
mountroot> panic or abort
panic :panic from console
Trace beginning at frame 0xc07bdcb8
panic (c07bdcdc,a,c07bdce5,62,c07bdd6c) at panic+0x8c
panic (c0539aee,c07bdce0,696e6170,c16a0063,80283) at panic+0x8c
vfs_mountroot_ask (c05d6ef8,cb286c20,c07bdd98,c02a54c8,0) at
vfs_mountroot_ask+0x1cb
vfs_mountroot(0,,7bac00,7c8000,7c8000) at vfs_mountroot + 0xa9
mi_starup (7ba000,d,c0613ab8,c07bdc64,c07bdc54) at mi_startup+0x92
begin () at begin+0x42
Debugger ("panic")
Stopped at Debugger+0x34 : movb$0,in_Debugger.3949
db>
Panic is displayed when I invoked "abort" or "panic". Is this a bug?
Thanks,
Archimedes
