N30N wrote:
> Hi there,
>
> Mozilla have made a fork of the libjpeg-turbo package called mozjpeg,
> which features improved encoding:
> https://blog.mozilla.org/research/2014/03/05/introducing-the-mozjpeg-project/
>
> I'd like to propose making the switch. The "library configuration
> defaults ar
On Sat, Mar 08, 2014 at 03:56:28AM +, Cao, Renzhi (MU-Student) wrote:
> I plan to use :
> dd if=/dev/hda bs=512 count=1 2>&1 | grep GRUB
> dd if=/dev/hda bs=512 count=1 2>&1 | grep LILO
>
> to check the bootloader I have. I am really new to arch linux, but I want to
> fix that problem. It see
All,
Is it possible to create multiple packages that have different package names
but are the same package (with different patches) and have them install without
conflict? (for testing) Currently I'm testing systemd patches for pkg
'tde-tdebase'. I built a separate package with the systemd patc
[2014-03-08 04:32:28 +0100] N30N:
> https://aur.archlinux.org/packages/mozjpeg/
When you take the existing libjpeg-turbo PKGBUILD, change a few lines,
and remove the Contributor/Maintainer tags altogether, you're not
showing much respect for the community.
> I'd like to propose making the switch.
I plan to use :
dd if=/dev/hda bs=512 count=1 2>&1 | grep GRUB
dd if=/dev/hda bs=512 count=1 2>&1 | grep LILO
to check the bootloader I have. I am really new to arch linux, but I want to
fix that problem. It seems I almost fix the problem, just solve the lilo and
grub-common problem. If I reins
On 8 March 2014 03:29, Cao, Renzhi (MU-Student) wrote:
> I am not sure which one is used as my boot loader, could you please tell me
> how to check that? I am thinking using this following command:
>
> #pacman -Rs lilo
> #pacman -Rs grub-common
> #pacman -S grub
>
> Is that correct?
> Thank you
Hi there,
Mozilla have made a fork of the libjpeg-turbo package called mozjpeg,
which features improved encoding:
https://blog.mozilla.org/research/2014/03/05/introducing-the-mozjpeg-project/
I'd like to propose making the switch. The "library configuration
defaults are the same as for libjpeg-tu
I am not sure which one is used as my boot loader, could you please tell me how
to check that? I am thinking using this following command:
#pacman -Rs lilo
#pacman -Rs grub-common
#pacman -S grub
Is that correct?
Thank you so much!
Renzhi Cao
Email : rc...@mail.missouri.edu
Thank you. Could you give me more details about updating them? I am new to arch
linux, can I try to uninstall them, and later after my problem solved, install
the new one by pacman?
Renzhi Cao
Email : rc...@mail.missouri.edu
From: arch-general on beha
On 8 March 2014 02:23, Doug Newgard wrote:
>
>> From: rc...@mail.missouri.edu
>> Date: Fri, 7 Mar 2014 19:30:59 -0600
>> To: arch-general@archlinux.org
>> Subject: Re: [arch-general] Problems of using pacman and updating the
>> filesystem
>>
>> Hi, it seem
> From: rc...@mail.missouri.edu
> Date: Fri, 7 Mar 2014 19:30:59 -0600
> To: arch-general@archlinux.org
> Subject: Re: [arch-general] Problems of using pacman and updating the
> filesystem
>
> Hi, it seems your method is really complex. Is there any simple
Hi, it seems your method is really complex. Is there any simple way? For my
case, do you know how to fix the problem of lilo and grub-common?
Sent from my iPhone
On Mar 7, 2014, at 17:18, Nowaker wrote:
> It seems OP is already done, but I hope this will by useful for anyone
> struggling to u
It seems OP is already done, but I hope this will by useful for anyone
struggling to upgrade a VERY old Arch Linux.
Warning: this is only for experienced users. Beginners do the backups
and install Arch from scratch.
Before proceeding, be sure to have several ssh sessions, logged as root.
Do
Hi,
Continue previous email, I think the warning of "core" does not exists if
fixed.
I try this command: #pacman -Syu mkinitcpio systemd linux
Finally, it shows:
error: failed to commit transaction (conflicting files)
filesystem: /bin exists in filesystem
filesystem: /sbin exi
Hi,
Before my system crash, I try this link:
https://www.archlinux.org/news/binaries-move-to-usrbin-requiring-update-intervention/
And I only get few non-official packages in /bin, /sbin, usr/sbin:
sysvinit-tool 2.88-9
lilo 23.2-3
grub-common 2.00-1
sysvinit-to
Thank guys for the reply!
On Fri, Mar 7, 2014 at 3:49 PM, Ralf Mardorf wrote:
>
> If you take a look at https://www.archlinux.org/ you'll be informed
> about what you need to do, if there should be something to do. There
> might be an arch website in your native language too. I use
> https://www
Hi
On Fri, Mar 7, 2014 at 10:45 AM, Ralf Mardorf
wrote:
> On Fri, 2014-03-07 at 16:21 +, Paul Gideon Dann wrote:
>> If the last time you updated was before 2012-11-04, there's a good
>> chance you never made the switch to systemd, which will make things
>> even harder for you.
>
> ... for sev
If you take a look at https://www.archlinux.org/ you'll be informed
about what you need to do, if there should be something to do. There
might be an arch website in your native language too. I use
https://www.archlinux.de/ as my web browser's startpage.
On Fri, 2014-03-07 at 16:21 +, Paul Gideon Dann wrote:
> If the last time you updated was before 2012-11-04, there's a good
> chance you never made the switch to systemd, which will make things
> even harder for you.
... for several reasons, e.g. eth0 likely will become enp3s0.
On Fri, 2014-03-07 at 16:15 +0100, Thomas Bächler wrote:
> You are right, only files in /bin, /sbin and /usr/sbin should be gone.
> Everything should be in /usr/bin after the update.
JFTR if I build packages for private usage, I prefer to install
to /usr/local/bin, /usr/local/sbin, those packages
On Fri, 2014-03-07 at 04:20 -0300, Andres Fernandez wrote:
> I think you should boot with an Arch Installer, then chroot and try to fix
> your system removing the package that has files on those directories,
> following the steps on the Arch news about this issue. An then update
> again. I think th
Hello, and welcome to the arch side!
The transitions are made so that if you update often enough and do as the
postinstall scripts and main page tell you to, then the transition goes
easily. Both the systemd and moving to /usr/bin were done almost
automatically (systemd had initscripts support for
Hi,
I'm a new Archer and I'm planning to install arch linux in a production
server environment, but I have doubts because Arch is a rolling release. My
question is: what does it happen when there are big changes? e.g. changes
in the filesystem or when Arch has started using systemd.
Regards,
Ary
-
On Friday 07 Mar 2014 09:26:19 Caorenzhi wrote:
> Thank you! I remember when I run the command to find out the packages I
> should remove, it shows: lilo, grub-common, initvlinux( something like
> this), but I don't know how to move them to /usr/bin. I try directly mv
> lilo to /usr/bin, and use th
On Friday 07 Mar 2014 09:12:39 Caorenzhi wrote:
> Thank you Paul, I will check it in my lab later and tell you the details.
I
> try add ip eth0 yesterday , and the system says there is no eth0.
In that case, you need to do:
# ip link
to see a list of your network interfaces. It might not be cal
On 07.03.14 at 12:28, arnaud gaboury wrote:
> >
> > I've had a quick look at systemd-networkd, and I don't think it would be
> > significantly different to set up than netctl in your case. I think the
> > problem
> > was one of theory: I don't know how much reading you've done, but you need
> > to
Thank you! I remember when I run the command to find out the packages I should
remove, it shows: lilo, grub-common, initvlinux( something like this), but I
don't know how to move them to /usr/bin. I try directly mv lilo to /usr/bin,
and use the command to search which package I should remove, it
Am 07.03.2014 16:09, schrieb Caorenzhi:
> Do I also need to remove files in /usr/bin as you said? Or you mean
> /usr/sbin, /sbin, /bin?
You are right, only files in /bin, /sbin and /usr/sbin should be gone.
Everything should be in /usr/bin after the update.
> Since that is what I see the error f
Thank you Paul, I will check it in my lab later and tell you the details. I try
add ip eth0 yesterday , and the system says there is no eth0.
Sent from my iPhone
On Mar 7, 2014, at 9:01, Paul Gideon Dann wrote:
> On Friday 07 Mar 2014 08:46:02 Caorenzhi wrote:
>> Thank you for your good sugge
That is my fault. Do I also need to remove files in /usr/bin as you said? Or
you mean /usr/sbin, /sbin, /bin? Since that is what I see the error from at
beginning. There are a lot of files in /sbin, should I remove all of them? Let
me check my system in my lab and I will reply you later for deta
On Friday 07 Mar 2014 08:46:02 Caorenzhi wrote:
> Thank you for your good suggestion! I think I can use pacman to
remove the
> packages, however, I cannot connect to Internet after chroot, so
cannot use
> pacman to update. Do you have any idea?
Assuming you can plug your computer in with an ethe
Am 07.03.2014 15:51, schrieb Caorenzhi:
> Yes, I try pacman -Su, and they said the /usr/sbin is exists. I am thinking
> that is ok, so I reboot the system.
The instructions explicitly stated that this is NOT okay.
> I have a cd to load the system, and I have another computer to download
> packa
Yes, I try pacman -Su, and they said the /usr/sbin is exists. I am thinking
that is ok, so I reboot the system. I have a cd to load the system, and I have
another computer to download packages and have a external hard disk to use,
like copy files there.
Is there still any way to solve my proble
Thank you for your good suggestion! I think I can use pacman to remove the
packages, however, I cannot connect to Internet after chroot, so cannot use
pacman to update. Do you have any idea?
Sent from my iPhone
On Mar 7, 2014, at 1:20, Andres Fernandez
wrote:
> I think you should boot with a
On Friday 07 Mar 2014 12:28:56 arnaud gaboury wrote:
> I read a lot, especially when it comes to networking. As for me, it is
> the trickiest part of administrating my machine.
Yeah, networking can get complex very quickly. (I'm by no means an expert
either!)
> I found many posts
> asking help a
>
> I've had a quick look at systemd-networkd, and I don't think it would be
> significantly different to set up than netctl in your case. I think the
> problem
> was one of theory: I don't know how much reading you've done, but you need
> to understand some theory of the networking stack, network
On Thursday 06 Mar 2014 23:46:59 arnaud gaboury wrote:
> I finally managed to boot the container with a working network and a
> static IP. I only used netctl, as systemd-networkd is still a mistery
> to me.
[...]
> It lacks in
> fact a good example, from the container creation to the network setup.
On Thursday 06 Mar 2014 23:01:30 arnaud gaboury wrote:
> On Thu, Mar 6, 2014 at 8:00 PM, arnaud gaboury
> wrote:
> >> 1) Two new virtual interfaces are create: one that is visible to the
> >> container, and one that is visible to the host. The host now has two
> >> interfaces, which may be bridge
Am 07.03.2014 10:38, schrieb Jesse Jaara:
Delcypher kirjoitti:
Or you could just build LLVM (and clang if you need it) from source
and link your project against that. That way, you can upgrade your
system's LLVM/clang packages without breaking your project.
Or even better port the codebase to
Delcypher kirjoitti:
Or you could just build LLVM (and clang if you need it) from source
and link your project against that. That way, you can upgrade your
system's LLVM/clang packages without breaking your project.
Or even better port the codebase to llvm 3.4.
> but I need to link c++ code against the llvm library so I don't think that
> an update will help. But I will just wait for some days now, then everything
> will be fine, because the project is finished.
Or you could just build LLVM (and clang if you need it) from source
and link your project aga
Thanks for taking the effort to finally update Apache!
When trying to start Apache with PHP, I get the same error as Rene.
Just to be clear, what is the recommended way to run Apache+PHP now? Will
mod_php5 will still be supported?
Thanks!
Sebastiaan
2014-03-07 0:52 GMT+01:00 Armin K. :
> On 0
Am 07.03.2014 07:06, schrieb Cao, Renzhi (MU-Student):
> After this, I use the following command to update the system:
> pacman -Syu --ignore filesystem,bash
> pacman -S bash
>
> and then reboot, get the following information:
And why didn't you complete the instructions by running 'pacman -Su'
b
Am 07.03.2014 07:35, schrieb Laurent Carlier:
Le jeudi 6 mars 2014, 09:46:25 Heiko Becker a écrit :
I think I found it in the Xorg.0.log :
[27.415] (EE) AIGLX error: dlopen of
/usr/lib/xorg/modules/dri/r600_dri.so failed (libLLVM-3.4.so: cannot
open shared object file: No such file or dire
44 matches
Mail list logo
