钱是用来干什么的？
钱是满足我们不同需求的一种工具，而不是我们追求的目标。明确了自己追求的目标，努力为之奋斗，我们就不会迷失在纷繁复杂的花花世界里。
钱是用来干什么的？这个问题看似好笑，其实并不是那么简单。
在语文课上学到葛朗台的小说，课堂氛围是欢快愉悦的，因为这是别人的故事。以前提到过，别人的故事无论悲剧还是喜剧，因为不涉及到自己的悲喜，不用为之负责人，所以别人的故事都让大家喜闻乐见。这就好比看电影的感觉一样，看喜剧电影，和主人公一起嬉笑怒骂，非常过瘾；看悲剧电影，同情电影中的人物，但是看过之后，庆幸自己比电影里的主人公幸福太多，于是欣欣然。
作家的写作来源于生活而高于生活，无论在哪个朝代，在哪个国家，都存在着众多的葛朗台，原因无他，他们不是把钱当成工具，而是把钱当作一种奋斗目标。
我们从小到大都知道钱的重要性，从我们呱呱坠地开始，我们人生的每个阶段都和钱息息相关。钱可以买玩具，可以买糖果；钱可以上学，可以买课本书桌；钱可以买漂亮衣服和帅帅的鞋子；有钱可以有更多的朋友，可以买豪宅名车，有钱办事情更加轻松自在……甚至在我们弥留之际，有钱没有钱也让我们做出不同的抉择。
中国大学生至少有16年的学校生活，知识非常丰富，博古通今，可以说是上知天文下知地理，中间知道人文，但是我们从来没有学过钱是用来干什么的。似乎我们在学校、在社会从老师那里，从父母那里学到了钱是很重要的，学到了该如何努力就可以挣钱，但是没有人告诉我们钱是用来干什么的。
按照马斯诺的理论来讲，在生存阶段，钱是用来购置生活必需品；在安全阶段，钱是用来满足安全的需求；在社会需要阶段，钱是用来满足个人的归属感；在尊重的阶段，钱用来满足个人获得社会尊重，能体验到自己活着的价值；而在最高级的自我实现阶段，钱是用来自己的抱负和立项。无论在哪个层次中，钱都是满足我们不同层次需求的一种工具，而不是我们追求的目标。
化繁为简，我们只用明确自己追求的目标，努力为之奋斗，我们就不会迷失在纷繁复杂的花花世界里。
已投稿到：
以上网友发言只代表其个人观点，不代表新浪网的观点或立场。女神是用来干嘛的啊？啪啪啪就算了吧。。。还能干嘛？_百度知道
色情、暴力
我们会通过消息、邮箱等方式尽快将举报结果通知您。
女神是用来干嘛的啊？啪啪啪就算了吧。。。还能干嘛？
我有更好的答案
女神是心中的偶像
女神是用来给土豪跪着的
手撸跟意银，没了，
女神这个名字，可以让你在啪啪啪时更兴奋更满足
女神是用来敬仰的，是阅读的。
其他5条回答
为您推荐：
其他类似问题
算了吧的相关知识
等待您来回答→ 红花油主要是用来干嘛的呢？
红花油主要是用来干嘛的呢？
健康咨询描述：
医生你好，我最近听人家说红花油红花油的，我不知道是干嘛用的，之前我的额朋友烫到手了说是也用这个，我不是很懂，所以来问下这个主要是干嘛用的呢？
想得到怎样的帮助：红花油是干嘛用的啊。
其他类似问题
医生回复区
微信扫描关注直接与我沟通已扫6784次
&&&&&&你好，这个药物主要是驱风药。用于风湿骨痛，跌打扭伤，外感头痛，皮肤瘙痒。外用，涂擦患处，一日4～6次。禁忌。1.皮肤、粘膜破损处禁用。2.皮肤过敏者停用。3.禁止内服。4.孕妇禁用。
您可能关注的问题
用药指导/吃什么药好
驱风药。用于风湿骨痛，跌打扭伤，外感头痛，皮肤瘙...
参考价格：￥6
下载APP，免费快速问医生
赞赏：医生
医生，随时向其咨询
使用微信扫码支付1元sub-projects
From FedoraProject
English (en)
This page is outdated and is only retained for historical referenceFedUp (FEDora UPgrader) was the official tool for upgrading between Fedora releases, until the introduction of the . FedUp is now obsolete and should not be used in any circumstances.
FedUp (FEDora UPgrader) is the official tool for upgrading Fedora installations. Anaconda, the Fedora installer program, has no built-in upgrade functionality. Upgrade from one release of Fedora to the immediate successor has been completely delegated to FedUp. Fedup may use a network repository or a DVD image for the package sources.
The FedUp system consists of two parts - the client, used to download packages and prepare for the upgrade and a pre-boot environment. The pre-boot environment does the actual upgrade using
(or yum). More details are available in .
Files are downloaded to /var/cache/system-upgrade and will be automatically cleaned up after the upgrade process is finished.
The FedUp client runs on the system to be upgraded. It gathers the packages needed for upgrade in addition to downloading the required initramfs and kernel needed for the actual upgrade. At this time, only the fedup command-line interface is implemented but a GUI interface is expected...sometime.
The actual upgrade takes place when the system has been rebooted after running the FedUp client. The filesystems are mounted during boot, the already downloaded packages are installed and some upgrade-related tasks are performed. During the upgrade process, a special plymouth theme is used which has a progress bar to indicate current upgrade progress.
Once the upgrade is complete, FedUp will reboot the system automatically. This is so you can run this part of the process unattended and later return to the upgraded system, if you leave any bootable media attached to the system during the upgrade process, once the upgrade has completed, the system may boot from that medium instead of the hard disk. If you return to see the Fedora installer or something similar...that's probably what happened!
to check if the problem is a very prominent issue we already know of. If it is not there, the component for reporting problems depends on the exact issue that you hit:
If you hit issues when using the FedUp client () before reboot,
or file a bug against FedUp using the version you are upgrading from.
If you hit issues after upgrade preparation and the initial reboot,
or file a bug against
using the version you are upgrading to.
If you hit issues after upgrade with a specific package, file a bug against the package with which you are having issues.
A troubleshooting and debug guide will be written at some point and linked to from here.
Yes. The package signing keys for newer Fedora releases are sent to older Fedora releases in order to allow FedUp to verify the integrity of the packages it downloads. You can disable this function with the --nogpgcheck parameter if you need to do so for any reason.
Yes, if they are set up like regular yum/dnf repositories and do not hard code the repository path. Commonly-used third party repositories usually work fine, but if you attempt to upgrade prior to or soon after an official Fedora release, they may not have updated their repository paths yet, and FedUp may be unable to find their packages. This will usually not prevent the upgrade running successfully, though, and you can update the packages from the third-party repository later.
Yes. After a Fedora release has been branched, it should be possible to upgrade to it using FedUp. It should also work after the Alpha and Beta releases. Of course, this function is as subject to temporary breakage as is any other aspect of a pre-release.
for more details.
As alluded to above, there are three parts to upgrading with FedUp - preparation, execution and cleanup.
Before you start doing anything, be sure to have a look at
and read about the most common bugs found.
In order to select one of the new Fedora flavors, FedUp has a new option, --product=&PRODUCT&. When upgrading from Fedora 20 or earlier to Fedora 21 or later, you must pass this --product option.
You can use the values workstation, server, cloud or nonproduct. If you upgrade to
or , all the packages that are included in a default installation of that flavor will be installed after the upgrade (that is, any that are not currently installed will be added). Your firewall configuration will also be reset to the default for that flavor (in the Workstation case, this is a fairly open configuration). If you do not wish these things to happen, use the value nonproduct.
Do a full system update and reboot to ensure that any kernel changes are running
Install/Update
Usually, it is best to try first with the latest fedup available in the stable update repository for the release you are running. If you encounter problems with the upgrade, and a newer fedup is available in the updates-testing repository for your current release, you may wish to try with this newer version: yum --enablerepo=updates-testing install fedup or with dnf: dnf --enablerepo=updates-testing install fedup at the command line)
Make sure the system is running a Fedora issued kernel if possible -- if you use your own kernel and it does not have a corresponding initramfs, the upgrade will fail.
There are three options for sourcing the packages needed for upgrade - using a network repository, a local ISO file or a local device (hard drive, optical disk etc).
Network upgrade is strongly recommendedIt is strongly recommended to use the network upgrade instead of offline update modes (ISO, local device). Network upgrade will ensure you receive the latest packages from the target release. If you use local media containing older packages, you might end up with a mixture of packages from your former and target release, and the system might not work properly until you fully update it after reboot (if it boots at all).
Using a network source is the easiest method of upgrading and will pull in updates while upgrading - eliminating the potential issue if your current system has a newer kernel version than the Fedora release to which you are upgrading.
Start the upgrade prep by executing following command:
sudo yum update fedup fedora-release
or with dnf for Fedora 22 and later versions:
sudo dnf upgrade fedup fedora-release
If you are upgrading from Fedora 20 to Fedora 21, run the following command:
sudo fedup --network 21 --product=[workstation | server| cloud | nonproduct]
If you are upgrading from Fedora 21 to Fedora 22 or above, run the following command:
sudo fedup --network 22
Once the preparations have completed, check the /var/log/fedup.log file if any errors show up in the output from fedup
Older Fedora releases included an installation image with a large number of packages, making it suitable for upgrading some systems.
Upgrading by booting this image was possible until Fedora 17, and using the image for upgrades with Fedup was supported until Fedora 20. Beginning with Fedora 21, the universal DVD i as of now, there is no media available for offline upgrades.
Optical drives and other mountable storage can also be used as a package source for upgrade preparations.
Mount the source material
For the sake of example, we will assume that this source is mounted at /mnt/fedora but you can mount it anywhere as long as you replace /mnt/fedora in the command below with the actual mounted location of the upgrade source.
Start the upgrade preparations by executing the following command
sudo fedup --device /mnt/fedora --debuglog=fedupdebug.log
Once the preparations have completed, check the fedupdebug.log file if any errors show up in the output from fedup
Reboot the system if fedup has completed without error.
Once the system reboots, there should be a new entry in the GRUB menu titled System Upgrade.
Select the System Upgrade option from the GRUB menu
Remark: If the System Upgrade item is not shown in the grublist at boot, it is most often caused by having an incompatible grub, most often installed by another Linux distribution you may have in your multiboot environment. To correct this quickly: reinstall grub:
grub2-mkconfig -o /boot/grub2/grub.cfg
grub2-install /dev/sda (replace /dev/sda by any other device you prefer to boot from)
The system should boot into the upgrade process and a plymouth boot screen should be displayed
There is a root shell on virtual terminal two (VT2) so you can tinker with the system if something goes wrong. (To disable this, boot with rd.upgrade.noshell)
Press 'esc' to view a more detailed log. If you switch back to the graphical progress indicator, it may show 0% for the remainder of the upgrade but that does not mean the upgrade has stopped.
Once the upgrade process has completed, the system will reboot and an option to boot Fedora 26 will be on the grub menu
It is worth rebuilding the RPM DB to prevent RPMDB checksum error when doing a distribution sync:
sudo rpm --rebuilddb
There are a collection of post-upgrade things to do. Some of which are fixed by doing a distro sync:
sudo yum distro-sync --setopt=deltarpm=0
If you have upgraded to Fedora 22 or above, run the following command instead:
(If you run dnf the first time and you're behind a proxy add your proxy settings to /etc/dnf/dnf.conf)
sudo dnf distro-sync --setopt=deltarpm=0
The rpmconf tool searches for .rpmnew, .rpmsave and .rpmorig files and asks you what to do with them: Keep current version, place back old version, watch the diff or merge.
sudo yum install rpmconf
If you have upgraded to Fedora 22 or above, run the following command instead:
sudo dnf install rpmconf
sudo rpmconf -a
If you are using google-chrome from the Google repository, you must re-install google-chrome due to a packaging bug on the Google side of things. Make sure to adjust the command to the build type you would like to install:
sudo yum remove google-chrome-\* && sudo yum install google-chrome-[beta,stable,unstable]
If you have upgraded to Fedora 22 or above, run the following command instead:
sudo dnf remove google-chrome-\* && sudo dnf install google-chrome-[beta,stable,unstable]
Write fedup troubleshooting and debug guide
add note about blob drivers if needed
Copyright & 2017 Red Hat, Inc. and others. For comments or queries, .
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, and JBoss are trademarks or registered trademarks of
Red Hat, Inc. or its subsidiaries in the United States and other countries.
Linux& is the registered trademark of Linus Torvalds in the U.S. and other countries.
The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community
maintained site. Red Hat is not responsible for content.
This page was last modified on 6 November 2015, at 01:57.