Search results

  1. J

    [CFT] linux_base-c6 with CentOS 6.5, linux-c6 ports, Skype

    Re: [CFT] linux_base-c6 with CentOS 6.5, linux-c6 ports, Sky Oh, thanks. I thought that most of the security issues with Linux stack originated from the recent Heartbleed bug. But where do these vulnerabilities stem from then? $ pkg audit linux-f10-expat-2.0.1 is vulnerable: expat2 -- Parser...
  2. J

    [CFT] linux_base-c6 with CentOS 6.5, linux-c6 ports, Skype

    Re: [CFT] linux_base-c6 with CentOS 6.5, linux-c6 ports, Sky Seeing how almost entire Linux compatibility layer based on Fedora 10 is now vulnerable to Heartbleed, will this port replace it anytime soon, or will it still be in testing for a while? Also, do you think that Steam for Linux will...
  3. J

    Porting libraries with USE_GCC

    Hi guys, I've been away for about a year now and I see a lot has changed. Well, in any case, I have a problem that I hope you will be able to help me with. I made a port for a library called math/mathgl and the port did compile and passed all the tests suggested in the Porter's Handbook. I...
  4. J

    Problem with patching. Hmm... Looks like a unified diff to me...

    I think it means that the patch is using unified format. You can also see this page to see more information, and how to find it.
  5. J

    Posting on forums.freebsd.org quite a hassle

    I like the high quality standards and the attitude of the moderators/administrators that this forum has. Writing quality posts takes time and effort, and this is how it should be. If you want to write junk, there is always 4chan.
  6. J

    pkg_which does not find package

    OK, cool. BTW, portmaster and portupgrade both have options to use packages as well. For example, en excerpt from portmaster(8): man portmaster ... -P|--packages use packages, but build port if not available -PP|--packages-only fail if no package is available. The...
  7. J

    pkg_which does not find package

    OK. I'm not sure if you should really reinstall yet, it's best to see what the senior members will say. It's good that you already have a backup, in case something "funny" happens while you're rebuilding the ports -- this way you can write the error output somewhere safe, restore the files from...
  8. J

    pkg_which does not find package

    Now before you try anything funny, make a backup ;). Another link to make backups for non-root UFS partitions is awesome HOW-TO, by @graudeejs, which shows you how to make snapshots (it's faster).
  9. J

    FreeBSD panics during first boot

    No, I apologize for not looking at the error more clearly :r, you were right, those are related to CPUs. But the first error goes to the missing "hard drive" (da1) so it's hard to say if the errors after that are just consequences of the first one. Like I said in the later post, (so my previous...
  10. J

    FreeBSD panics during first boot

    Not in such a way (I mean, it's not like you're putting computer under any stress, you're just trying to boot), unless your laptop really needs cleaning ASAP (you have to know this yourself -- when is the last time you cleaned it, and what are the common temperatures). I took a look at your...
  11. J

    FreeBSD panics during first boot

    The name da is reserved for USB sticks and alike (removable cards, etc.). And no, the last line has nothing to do with the CPU. As for the hardware incompatibility/breakage, you're running on a fairly standard CPU and GPU which are both well supported (Core Duo is explicitly taken out, but...
  12. J

    pkg_which does not find package

    Uffff, this is a lot of ports. The portmaster entry should be smaller, because it only shows the root ports (so, if you install these, it will automatically install the other 1000, since those are just the dependencies). I can see why you don't want to install all those ports. One such way is...
  13. J

    pkg_which does not find package

    Once you convert your database to PKGNG (e.g. run pkg2ng) you cannot (must not) use the pkg_* tools anymore, but you have to add WITH_PKGNG=yes in your /etc/make.conf and use the pkg(8) utilities (see pkg help for list of commands, and then pkg help which for example to see the manpage for the...
  14. J

    FreeBSD panics during first boot

    It's just the USB stick (the da1 line) -- I would try a different one (I use these for the practical design and durability), or at least run some tests on it. However, you might want to try some other things before that: There are some AHCI options you can enable/disable (I'm not sure) in...
  15. J

    nice try

    If you want a good overview of what you've gotten yourself into, read this. It outlines the key differences between FreeBSD and Linux. It will also answer most of your "what-if" questions (if you didn't do it until now, then this is really the last time for you to read it). In order to see how...
  16. J

    nice try

    Well, what did you do to try to fix your problems? Computer is a tool, and using tools requires a certain level of proficiency. Luckily for you FreeBSD has a very good documentation (FreeBSD Handbook, FreeBSD Wiki -- they're very good source of documentation and are there for a reason) and...
  17. J

    Migrating from UFS to ZFS

    You think you can create a snapshot of the UFS root drive, but you cannot do it directly: with a LiveCD. Start the LiveCD, when prompted for actions, choose LiveCD. When prompted for a user name use `root'. Let's say that the old root partition is /dev/ada0s2. So you run fsck -t ufs -y...
  18. J

    What about implementing a desktop using OpenGL?

    @wblock, this was the article I was reading a few days ago, but I couldn't find it now, thanks! ;)
  19. J

    What about implementing a desktop using OpenGL?

    Well, it's almost, because only part of it is rewritten. Wayland is supposed to be just the protocol, whereas X.Org has a bunch of other things that go with it. Also, if I remember correctly, Wayland isn't meant to work as a server, so I don't think it offers that powerful functionality as X11...
  20. J

    msk0 watchdog timeout and interrupt storm

    Well, 10-CURRENT is prone to breakage, a lot of it is work in progress, and most of all, it's just not stable (it's not even guaranteed to build all the time). Also, it's officially not supported by this forum, but by the freebsd-current@freebsd.org mailing list: report your issue there...
Back
Top